AI Intake That Writes Directly to Clio: How It Works in 2026

The integration most firms actually want

Clio is the dominant legal practice management platform — Clio Grow for client intake and pre-engagement, Clio Manage for matter management after engagement. Most small firms run both. When evaluating an AI intake agent, the question that matters isn't "does it integrate with Clio" — every vendor will say yes. The question is "what does the agent actually write to Clio, and when?"

Here's what a properly built integration does and doesn't do.

What gets created in Clio when the agent takes a call

When a new prospective client calls in and completes the intake, the agent creates four things in Clio in this order:

1. Contact — name, phone, email, address (if provided), referral source if mentioned. Custom fields populated from the intake script (e.g. case type, opposing party).
2. Matter — opened in your "Pending Intake" or "Lead" status (configurable per firm). Practice area assigned based on the agent's case-type detection. Description field gets the structured intake summary.
3. Calendar event — only if the caller booked a consultation during the call. The agent honors your availability blocks and respects buffer time set in Clio.
4. Note attached to the matter — full call transcript, structured intake answers, and the agent's confidence assessment of fit (high / medium / low).

Existing-client calls take a different path: the agent looks up the contact by phone, attaches a new note to their open matter, and routes the call to you (or your assistant) per your rules.

Conflict-check: where AI intake is honest about its limits

Conflict-check is the part of legal intake AI cannot fully automate, and any vendor who tells you otherwise is glossing over a real ethics issue. The agent captures the data your conflict-check process needs — caller name, opposing party, family members, previous representation, business affiliations — but it does not run the conflict check itself. That stays with a human on your team.

The workflow we deploy:

• Agent captures all required intake data
• Matter is created in Clio with status "Pending Conflict Check"
• Your assistant (or you) gets a Slack/email notification of the new intake
• Standard conflict-check process runs against your existing Clio Contacts
• If clear: matter advances to "Pending Engagement Review"; if not: caller gets a polite decline and matter is marked accordingly

This preserves the supervising-attorney responsibility that ABA Model Rule 5.3 requires. The agent is a tool; you supervise.

Custom fields and intake variants

Clio's custom-field system is the unsung hero of intake automation. Every practice area has different qualifying questions. The agent's intake script and the matter's custom-field set should match.

Examples we deploy:

• Personal injury: incident date, incident type (auto / premises / med-mal / dog bite / other), injury severity, hospital visited, photographs available, insurance coverage on caller's side
• Family law: dissolution / custody / modification / support, marriage date if dissolution, children's ages and counts, current living arrangement, prior counsel
• Estate planning: existing will / no existing will, total estate value range, real property in multiple states, guardianship needs, executor preference
• Real estate transactional: purchase / sale / refinance, property address, closing date target, title insurance status, financing type

The agent asks these questions in plain conversational order during the intake. Each answer maps directly to a custom field on the resulting Clio matter — searchable, reportable, ready for the next step in your workflow.

Setup mechanics

The integration runs through Clio's REST API. We use the Clio API Application system: you authorize WildRun's application against your Clio account, granting scopes for Contacts, Matters, Calendar, Notes, and Custom Fields. OAuth refresh tokens stay in encrypted storage; no Clio credentials ever touch the agent.

Setup typically runs 5–7 business days for a single-attorney firm:

1. Discovery call (60 min) — practice areas, intake questions, conflict-check workflow, calendar rules
2. Custom-field provisioning in Clio (your firm or us, depending on access)
3. Intake script architecture per practice area
4. Voice tuning and review
5. OAuth integration and test calls
6. Soft launch with active monitoring for 30 days

Failure modes nobody warns you about

• Clio API rate limits. Clio's standard plan caps writes at modest rates per minute. A high-volume intake practice can hit this; we batch and retry. Most small firms never notice.
• Practice-area drift. If your firm's practice mix changes and you don't update the intake script, the agent keeps qualifying for whatever it was trained on. Schedule a quarterly review.
• Custom-field schema changes. If you reorganize Clio's custom fields without telling us, intake breaks until we re-map. Treat the intake schema like a contract.
• Phone-number consistency. Existing-client lookups work by phone match. If a client calls from a new number, the agent treats them as a new prospect. Ask returning clients to confirm their identity at the start of the call (this is good practice anyway).
• Conflict-check delays. If your assistant is slow on conflict-check, callers wait. Plan the human turnaround time as part of your intake commitment.

What about Clio Grow specifically

Clio Grow is the pre-engagement intake product. If you use Grow, the agent writes leads to Grow first, and they only flow to Clio Manage if the prospect engages. The integration looks the same on the surface but the lead status flows through Grow's stages (Inquired → Consulted → Engaged → Closed/Lost). We support both Grow-only and Manage-only setups, plus the combined Suite.

The honest pricing comparison

Some firms ask why a Clio-integrated AI intake costs $497–$1,997/month when Clio's own built-in intake forms are free. The answer is what the agent does that a form can't:

• Web forms only capture self-motivated visitors who finish the form. The agent captures the bigger pool of phone-first prospects who never visit your website.
• Forms don't qualify; agents do. A form pushes raw data to your inbox; the agent decides routing and books the consultation in real time.
• Forms run business-hours only when paired with a human. The agent runs 24/7.

If your inbound is heavy on form fills and light on phones, your Clio integration spend is wasted. The math only works if you have meaningful phone volume. See the full pricing breakdown.

Next step

If you're a Clio-using firm and you've ever lost a prospective client to voicemail because you were in court, book a free 30-minute call. We'll show you a live intake into a sandboxed Clio account during the call.

For more on after-hours intake compliance specifically, see the ORPC and ABA guidance breakdown.

Frequently asked questions