Clio integration

The Clio integration logs every call you make or take in CallForges as a phone call in Clio Manage, on the matching contact and on their matter when they have exactly one open matter. If you turn it on, it also adds a time entry for each call with talk time.

Written by CallForges Support · Updated 7 November 2026

Before you start

• You need a CallForges owner or admin role to connect, configure or disconnect Clio. Other users don't see the integration settings, but their calls are logged once they are mapped.
• Connect with a Clio administrator. If Clio's Contacts Visibility hides contacts from the user who connects, CallForges can't find those contacts.
• The integration works with Clio Manage. Someone who exists only in Clio Grow counts as an unknown number.
• Clio is offered for accounts in the United States, the ones you sign in to at app.clio.com.
• Your Clio plan needs to allow third-party apps. If Clio refuses the connection, check your plan with Clio.
• One CallForges workspace connects to one Clio account.

Connect Clio

1. In CallForges, open Integrations and choose Clio.
2. Click Connect.
3. Under Where is your Clio account?, choose United States and click Continue to Clio.
4. Sign in to Clio if asked and allow access.
5. You come back to the Connection tab, which shows the Clio account, who connected it and when.

If the Clio account is already connected to another CallForges workspace, CallForges asks before moving it. That other workspace then stops logging calls to Clio.

If Clio later asks CallForges to sign in again, the Connection tab shows Reconnect. Calls made in the meantime wait and are sent once you reconnect.

Map users

Calls are logged only for CallForges users who are matched to a Clio user. Open the Map users tab:

1. Click Auto-map by e-mail to match every user whose e-mail address is the same in both products.
2. For anyone left, choose their Clio user from the list, or leave them on Not mapped.
3. Click Save mappings.

Calls by an unmapped user are skipped, and each skip shows up in Activity with the reason. Use Show unmapped only to find the users who still need a match. After you map them, you can send their skipped calls from Activity.

Call logging settings

Open the Settings tab, change what you need and click Save changes.

Workflow: what each call becomes

Choose separately for outbound answered calls, outbound unanswered calls, inbound answered calls, missed calls and voicemails:

Note isn't available for Clio. Every logged call is saved as a phone call, because Clio can only link a time entry to a phone call.

Which matter a call goes on

The phone call is linked to a matter only when the contact has exactly one open matter. With no open matter, or more than one, it stays on the contact alone. To put a call on a matter afterward, click Move to a matter on that call.

What each phone call includes

• Link to the recording adds a link to the call's page in CallForges, where the recording plays.
• Link to the transcript adds a link to the call's page in CallForges, where the transcript is read.
• AI summary adds the call's AI summary, when it has one. Summaries are made for English calls long enough to summarise, on plans that include them.
• Add a time entry for each call is explained under Time entries.
• Save the recording in Clio stores the recording in the matter's documents, or the contact's when the call has no matter. It's off by default and works only while Secured recording links is off in Settings → Call settings. A call on no contact stores nothing.

Transcripts stay in CallForges, and so do recordings unless you turn on Save the recording in Clio. Only signed-in users of your CallForges workspace can open the links.

Connected numbers

Leave Log calls on all numbers on to log calls on every number your workspace owns, including numbers bought later. Turn it off to pick the numbers to log. Calls on numbers that aren't picked are skipped.

When calls are logged

A call is written to Clio within a few minutes of ending, so the disposition and notes the user adds after the call are included. If the call is changed later, for example a new disposition, the same phone call is updated.

A phone call you delete in Clio stays deleted. CallForges doesn't write a new one, and Activity says so.

Time entries

CallForges can add a Clio time entry for each call. This is a setting on your Clio connection and it is off by default. To turn it on, open Settings, go to What each phone call includes, turn on Add a time entry for each call and click Save changes.

While it is on:

• Each call with talk time gets one time entry. A call with no talk time gets none.
• Time entries are non-billable by default. Turn on Make time entries billable to change that.
• In Map users, the Time entries switch turns them off for one user.
• The time entry is linked to the phone call, and to the matter when the phone call has one.
• It is dated in the mapped user's Clio time zone.
• A later edit updates the phone call and leaves the time entry alone, except Move to a matter, which moves both.
• A time entry you delete in Clio isn't added back.

Turning the setting on writes nothing by itself for calls already in Clio. One of those calls gets a time entry the next time it is sent to Clio, for example after an edit, if it had talk time. Calls you send with Log past calls while it is on get one too, if they had talk time. Turning it off removes nothing: time entries already written stay in Clio.

Unknown numbers

CallForges finds the Clio contact by phone number, trying the number in several formats.

A call to a number that is on no contact is still logged. Clio keeps it under Inbox → Logs, on no contact and no matter. CallForges doesn't create a contact by default. To add one after the call, click Add to Clio on that call. To create one automatically, use Settings → General:

• Create a Clio contact if the number isn't found: when no contact in Clio has the number, CallForges creates one and logs the call on it. Off by default.
• Use the phone number as the new contact's name: used when CallForges has no name for the caller. When this is off, the new contact is named "Unknown caller". This applies only while creating contacts is on.

Add to Clio and Move to a matter

Both actions are on the call's page and on its row in Activity, for anyone who can log that call.

• Add to Clio shows on a call logged with no contact. Fill in the name and CallForges creates the contact with the call's number and links the call to it. If a Clio contact already has that number, the call is linked to it. If several do, nothing changes and you link the call in Clio.
• Move to a matter shows on a call with a contact and no matter. Pick one of the contact's open matters, and the phone call and its time entry move there. If Clio keeps the time entry where it is, for example because it was billed, only the phone call moves and CallForges says so. You need to be mapped to a Clio user to see matters.

The caller's name when a call rings

When someone who isn't in your CallForges Contacts calls one of your numbers, CallForges looks the number up in Clio while the call rings, and the name appears on the ring card a moment later.

The ring never waits for the answer. If Clio is slow or busy, or several contacts share the number, the card shows the number alone. A contact saved in CallForges always comes first. CallForges keeps the answer in memory for a few minutes and doesn't save it.

Users mapped to a Clio user also see the caller's open matters. Clio allows fewer requests per second than other CRMs, so its name can take a few seconds to appear.

Contacts

The Contacts tab lists the contacts in your Clio account who have a phone number, read live from Clio, with a link to open each one in Clio.

Clio contacts can't be imported into CallForges, so they stay in Clio. The import buttons and Sync now are greyed out for Clio, and so is Add Clio contacts to CallForges Contacts in Settings. Clio has no contact lists, so All lists is greyed out too.

Log past calls

Connecting logs the calls that happen from then on. To send calls your workspace made before you connected, use Settings → Log past calls:

1. Under How far back, pick a date range. It reaches back up to 1 year.
2. Click Log past calls. CallForges counts the calls first and shows how many would be logged, and which users' calls would be skipped because they aren't mapped.
3. Confirm. A progress bar shows the calls being sent.

Past calls are sent in the background and never delay the logging of new calls. To stop a run, open Activity, go to the Queued tab and click Stop queued.

Activity

The Activity tab lists every call and what happened to it in Clio: logged, queued, failed or skipped, with the reason. You can retry one call, or use Retry all for every failed or skipped call that matches your filters. Never logged lists calls that were never sent to Clio.

Clio limits how many requests an app can make. After a burst of calls, some phone calls may appear in Clio a little late. Nothing is lost.

Disconnect

1. Open Integrations → Clio.
2. Click Disconnect and confirm.

Calls stop being logged to Clio and the user mapping is cleared. CallForges gives up its access to your Clio account and forgets the Clio names and e-mail addresses it held. Phone calls and time entries already written stay in Clio, and your logging settings are kept in case you reconnect.

If Clio doesn't confirm the removal, CallForges shows Disconnected here, but Clio did not confirm it and asks you to remove CallForges' access in Clio's settings too.

You can also remove CallForges in Clio, under My Integrations, at any time. CallForges then shows Not connected or Reconnect.

What CallForges can access

When you connect, CallForges asks Clio for these permissions on your account:

CallForges doesn't ask for your Clio notes or calendars. Connections made before recordings could be saved need to reconnect to use that switch; calls are logged either way.

Your Clio access is stored encrypted and used only for the features above. See our Security page and Privacy Policy.