This article may be out of date!
Visit the New Knowledge Center

Clio Grow Lead Inbox


Lead Inbox Sources
Inbox Token
Managing Leads in Your Inbox
Lead Inbox API Endpoint


The Clio Grow Lead Inbox is the place where new potential clients will be captured from third party sources or integrations. It’s intended to be an area where pending leads can be stored and reviewed prior to being added to the pipeline or created into actual contacts.



Lead Inbox Sources

Clio Scheduler

The Lead Inbox can capture appointments booked through public appointment link which can then be accepted or rejected.


Third-party integrations

Note: Most 3rd party integrations (including the list of virtual receptionist, and website live chat services) are only available for accounts using Clio Grow on the US server. The only third-party integration currently available to EMEA accounts from the below list is the WordPress Plugin. 

You can connect the Lead Inbox to a number of existing third-party integrations, or even build your own integration using the Clio Grow's Lead Inbox API. The following tools include some of our most popular integrations with Clio Grow and can easily be used to submit new potential clients into the Lead Inbox:

Website Integrations

  • WordPress Plugin

Virtual Receptionist Service

  • Ruby
  • Back Office Betties
  • Alert Communications
  • LexReception

Website Live Chat Services

  • Apex Chat
  • Ngage Live Chat
  • Client Chat Live

Lead Generation Services

  • Unbundled Attorneys
  • LawLytics
  • Martindale-Nolo

Inbox Token

Note: To access your Clio Grow Inbox Token, go to Settings Integrations.

Each Clio Grow account has a unique “Inbox Token”, which is how your account can be identified and distinguished from other accounts.

Any time a new lead is submitted to Clio Grow from a third party source, Clio Grow finds the appropriate account using the inbox token that is submitted with the lead and then creates the lead in that account's Lead Inbox.

You can find your token by going to the Integrations tab in your account settings area. Be careful about sharing this token with anyone since it is like a key to unlock your account!

Managing Leads in Your Inbox

Once a lead is created in your Lead Inbox, there are a number of different things that happen and actions that you can take. These are explained below:

Create A Contact

You can add the pending lead as a contact in your Clio Grow account. This is designed for if the inbox lead is not a potential client.

Quick Intake

You can “Quick Intake” the pending lead to create a contact and a matter, assuming the person is a potential client.


If a lead is spam, a duplicate, or someone irrelevant, you can simply ignore the lead to remove it from the lead inbox by clicking "Ignore".

Clicking "ignore" does not permanently delete the inbox lead. You can view all of your previously ignored leads, in the event that you need to restore a lead, by clicking "Show Ignored" at the top of the lead inbox.

Once you click "Show Ignored" at the top of the Lead Inbox, if you want to restore one of your previously ignored leads, click "Restore" next to the lead or, if you want to delete all of your ignored leads permanently, click "Delete All" at the top of the page.


Any user can receive an email notification whenever a new lead is added to the Lead Inbox. You can manage this feature in your settings.

Best Practices

In order to make your Lead Inbox work and get the most value possible from it, we have a few recommendations:

  • Call or email each person immediately after they are added. This will significantly increase your conversion rate.
  • Don’t let your leads pile up because they become difficult to manage. Get in the habit of reviewing each one quick or the entire inbox every morning and either ignoring your leads or adding them to your pipeline or contact database.
  • Use “Quick Intake” if the lead is a potential client, and just add them as a regular contact if they are any other type of contact.

Lead Inbox API Endpoint

If you need to create your own integration to submit leads to the Lead Inbox, you can do this using our API Endpoint.

Clio Grow's Lead Inbox API endpoint enables you to submit leads into Clio Grow via a simple web form or other source using a POST request in JSON format. Sound like Greek to you? Your webmaster can probably help to add this to your website.

There are 5 basic data fields, 2 URL/source parameters (to track the source of the lead), and an API authorization token that connects the request to the appropriate user’s account in Clio Grow.

Sample JSON Parameters


For EU Accounts:


Content-Type: application/json

Accept: application/json




"inbox_lead" : {

  "from_first" : "John",

  "from_last" : "Doe",

  "from_message" : "I have a DUI and I need a lawyer",

  "from_email" : "",

  "from_phone" : "8987648934",

  "referring_url" : "",

  "from_source" :"DUI Landing Page"


"inbox_lead_token" : "ABCDEFGHIJKL0123456789"

Fields to include in a POST:

  • First Name (required)
  • Last Name (required)
  • Email (optional)
  • Phone Number (optional)
  • Message (required)

URL & Source (these should be hidden fields on a web form, and both are required):

Referring URL: intended to be the URL of the webpage where the lead was submitted; you can pass in some static text, e.g. “Call handled by virtual receptionist” if it is not submitted via a web form

Source: intended to be the name of the service submitting the lead; this will be used to identify the source and distinguish it from any other integrations, e.g. “XYZ Virtual Receptionist” or “Leads for Lawyers”, etc.

API Token

The API token should be a hidden field if you are submitting the lead from a web form. It’s by itself in the JSON object with the parameter name “inbox_lead_token” - users will generate their unique API token from their Clio Grow account settings under the “Integrations” tab. Have your client generate the token and email it to you to connect to their account.

Note: you must add an “Accept” Header of “application/JSON” in order to accept a JSON response. You should receive a 201 response message with the JSON parameters of the lead that was created in Clio Grow.

Additional web form fields can be combined and submitted as part of the "from_message." All message field data gets created as a Note in Clio Grow.

  "from_message" : "field 1: | field 2: | field 3",


Was this article helpful?
This information is confusing or wrong
This isn't the information that I was looking for
I don't like this functionality