Integrations

Connect Clio from Settings → Integrations → Clio. We use Clio's OAuth 2.0 flow, so you click "Connect Clio," authorize ClaireAI against your Clio Manage or Clio Grow account, and you're done — no API keys to copy, no manual webhook URLs. You need to be a Clio user with permission to install third-party apps (typically firm admin or someone with "Manage firm settings"). We request the smallest scope set needed to create contacts and matters and read calendars; you can revoke access anytime from Clio's Connected Apps screen, which instantly invalidates our refresh token.

By default we map caller name to Clio Contact first_name + last_name, caller phone to primary_phone, email to primary_email, practice-area tag to Clio's practice_area, and the call summary to a Matter description on a newly created Matter. Custom field mapping is supported via the integration's Field Mapping screen — any Clio custom field (Date of Incident, Referring Attorney, Case Value) can be wired to a question Claire asks on the call. Mapping is per-tenant and survives Claire prompt changes.

Yes. MyCase released a public API in 2023, available on their Advanced tier, and Claire uses it natively. When a call ends, we POST the lead via the REST API: a new Contact is created (or matched on phone number), a Lead pipeline record is added with the call summary, and the caller is placed in the stage you choose during setup (default: "New Lead — Intake Complete"). If your MyCase plan doesn't include API access, we fall back to Zapier or webhook delivery so nothing is lost.

Yes. Filevine custom fields use the custom.<selector> convention (e.g., custom.dateOfIncident), and ClaireAI's Filevine mapper supports every selector type Filevine exposes — text, currency, date, dropdown, multi-select. You point Claire at a section (Project, Contact, or a custom tab), pick the selector, and tell Claire which intake question fills it. Currency fields can only map to currency answers and dates to date answers — same constraint Filevine itself enforces — so Claire validates the shape on the call.

Yes — Claire is designed for dual-stack firms. A single call can fan out to multiple destinations: contact + matter into Clio Grow for the legal pipeline, contact + deal into HubSpot for marketing attribution, and a notification into Slack for the intake team. Each destination has its own field map, and we don't rely on Clio's native HubSpot connector (which is largely one-way HubSpot → Clio). Latency is sub-second per destination on call end; failures retry independently so a HubSpot outage won't block Clio.

Yes. Claire reads each attorney's Google Workspace or Microsoft 365 working-hours setting, honors their primary time zone (callers are auto-converted), and enforces firm-wide booking rules: minimum notice (e.g., no consults inside 2 hours), buffer time before/after (e.g., 15 minutes for conflicts check), max consults per day, and blackouts for court dates. For multi-attorney firms, Claire supports round-robin, weighted round-robin (load-balanced by case count), and practice-area routing (PI calls only to PI attorneys).

DocuSign fires when Claire reaches the "send retainer" step in the call flow — typically right after the caller confirms their name, email, and engagement scope. Claire uses your firm's DocuSign template (Standard plan or higher, since templates require it), pre-populates client name, address, matter description, and fee structure as DocuSign tabs, and sends the envelope. The template is fully firm-branded — your logo, your letterhead, your fee schedule — Claire never injects ClaireAI branding. Signing reminders fire on DocuSign's schedule, and the signed PDF auto-files back to the matching Clio/MyCase/Filevine matter.

Yes. Every Claire account ships with a generic webhook destination and a Zapier app. On call end, Claire POSTs the full payload (transcript, structured intake fields, recording URL, custom-field answers, booked-meeting details) to any URL you supply, with HMAC signing so you can verify it. For no-code teams, our Zapier app exposes "New Call Completed" and "New Lead Qualified" triggers that work with 8,000+ Zapier apps — handy for tools we don't natively support yet. We always prefer native when it exists (lower latency, richer field mapping, no Zapier task cost); use Zapier or webhooks as the escape hatch.

Native integrations (Clio, MyCase, Filevine, Lawmatics, HubSpot, Salesforce) post within 1–3 seconds of call end — the contact, matter, and call summary are all visible by the time your intake team's screen refreshes. Zapier-routed deliveries add 5–30 seconds depending on Zapier's task queue. Calendar bookings happen during the call (not after), so the consult slot is locked the moment the caller confirms the time. If a downstream system is down, we retry with exponential backoff for 24 hours and surface the failure in your Claire dashboard.

We request the minimum scopes per integration — e.g., Clio: read/write contacts, matters, calendars, communications; Google Workspace: calendar.events only (no Gmail unless you enable the email-followup add-on). Tokens are stored encrypted at rest with AES-256 and scoped per tenant; we don't co-mingle tokens across firms. Data residency follows your Claire plan — U.S. firms stay in US-East AWS; we honor Clio's regional rule (U.S. Clio account → U.S. ClaireAI tenant). Disconnect from Settings → Integrations and we revoke the refresh token within seconds; audit logs of every token use are retained for 12 months.

Yes — you can run both integrations in parallel during the cutover. Configure Claire to dual-write to Clio AND Filevine for the migration window (typically 2–4 weeks), then disable the Clio writer when your case-management team has fully moved. Historical ClaireAI calls aren't migrated to the new CRM automatically — we don't backfill, since field mappings are rarely retroactive — but every call recording, transcript, and structured intake field is permanently stored in your Claire vault and exportable as CSV or JSON for one-shot import into Filevine.

Yes. Claire asks a practice-area qualifier question on every call ("Is this about a car accident, a family law matter, or something else?") and tags the resulting Matter or Lead with your firm's own taxonomy. In Clio, that populates the Matter's practice_area field; in Lawmatics, it routes to the corresponding Intake Pipeline (PI, Family, Criminal); in Filevine, it picks the right Project Type Template. Practice-area-specific custom fields only show up in Claire's intake script for matching calls — so a PI caller is asked about insurance carriers, a family-law caller never is.