What we do
Tools
Industries
Department
How we workLet's talk →
Home/Clio/Clio Grow Intake
Clio Grow

Clio Grow: Getting Every Lead Into the Pipeline, Not Only the Form Fills

Clio Grow is Clio's client intake and CRM product. It gives you intake forms, a pipeline of leads by stage, e-signature on engagement letters and automated follow-up emails, and it turns a signed lead into a Clio Manage matter. It works best on leads it captures itself. Below is every way a lead can get in, and where firms still end up typing.

How a lead gets into Clio Grow

Grow's own intake forms. Embed one on your website or send it as a link. Submissions land in the pipeline as new leads, already filled in.

Native connections. CallRail (US only) can send calls, texts and form fills to Grow, and Google Local Services Ads leads can flow in too. Both are set up from the integration settings.

The lead capture token. Grow's integration settings give you a token that a website form, a third-party tool or a custom integration uses to post leads to Grow's API endpoint. Zapier also has a Clio Grow connector.

Everything else is typed by hand. Answering-service messages, referral emails from other lawyers, directory inquiries and chat transcripts only reach Grow if someone keys them in.

From first contact to an open matter

The path Grow is built around, and the spot in each step where manual work tends to hide.

  1. 1

    The lead is created

    From a form, a native integration or the API, Grow creates the contact and the lead together, with the practice area and source if the form asked for them.

    Watch for: the source field. Leads typed in by hand often go in with no source, or with "Other", so your marketing report undercounts the channels that actually work.

  2. 2

    It moves through your stages

    You define the stages, for example new, contacted, consult booked, retained. Automated follow-up emails can go out as a lead moves from one stage to the next.

    Watch for: leads that never move. If intake staff work from the phone and a notepad, Grow shows a pipeline that's weeks out of date.

  3. 3

    The engagement letter goes out

    Grow fills the letter from the lead's details and sends it for e-signature. The signed copy stays with the lead.

  4. 4

    The lead becomes a matter

    Once it's signed, converting the lead creates the matter in Clio Manage with the intake details carried over, so the case file doesn't start from a blank record.

    Watch for: fields that exist in Grow's form but have no matching custom field in Manage. Map them before launch, or that detail stays behind on the lead.

Where Grow intake still leaks

None of these are Grow bugs. They're the sources and habits that sit outside it.

The answering service emails a message instead of creating a lead

How you'll know: Every morning someone reads last night's call summaries and keys each caller into Grow. The ones that come in at 7pm on a Friday wait until Monday.

Fix: Parse the service's message, or use its own integration if it has one, and post it to Grow with the lead capture token, so the caller is in the pipeline and gets your first follow-up email the same night.

The same person shows up as two leads

How you'll know: A prospect calls, then fills out the website form. Or CallRail is connected to both Grow and Manage, which CallRail itself warns will create duplicates.

Fix: Send each source to Grow once, and match on phone and email before a new lead is created. Merge the old duplicates while you're at it.

Referral emails sit in one lawyer's inbox

How you'll know: A colleague sends over a client by email. It becomes a lead only if the lawyer forwards it to intake, and the referrer never hears back.

Fix: A shared referral address that creates the Grow lead, tags the referring lawyer as the source, and lets you send them a thank-you when the matter opens.

Grow's pipeline and your ad spend never meet

How you'll know: Leadership asks what a signed client costs per channel, and someone builds it in a spreadsheet from a Grow export and three ad dashboards.

Fix: Push stage changes and conversions from Grow into the report leadership already reads, next to spend by source. Our Clio API integrations page covers how that data comes out.

Questions people ask

What is Clio Grow?

Clio's client intake and legal CRM product: intake forms, a lead pipeline by stage, e-signature for engagement letters and automated follow-up emails. It's built to run alongside Clio Manage, which handles the matters once a lead is retained.

How does a lead in Clio Grow become a matter in Clio Manage?

After the lead signs the engagement letter through Grow's e-signature, you convert it, and Grow creates the matter in Clio Manage with the intake details carried across. Check that your Grow form fields map to custom fields in Manage, or some details won't follow.

Does Clio Grow have its own intake forms?

Yes. You can customize them, embed them on your website or send them as a standalone link, and each submission arrives in Grow's pipeline as a lead.

How much does Clio Grow cost?

Clio sells Grow on its own and in a bundle with Clio Manage. Plans and prices change, so check Clio's pricing page for the current numbers rather than a figure quoted elsewhere.

Can Clio Grow connect to tools outside Clio?

Some, natively: CallRail and Google Local Services Ads, plus a Zapier connector. Anything else can post leads through Grow's lead capture token and API endpoint. Answering services, referral inboxes and directories usually need that custom route, which is the work we do.

Why are we getting duplicate leads in Clio Grow?

Usually because one source is connected twice, for example CallRail sending to both Grow and Manage, or because a person both called and filled in a form. Send each source to Grow once and check phone and email for a match before creating a new lead.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.