Lawmatics logoThe AI Receptionist for Lawmatics
Trusted by 100+ service businesses

An AI Receptionist that books, reschedules & cancels appointments — 24/7 — and writes them straight into Lawmatics logoLawmatics.

Plugs into your website and phone line. Voice in 30+ languages. Live by tonight, booking customers by tomorrow. No Zapier, no n8n, no code.

Intentionally cheap so you can prove it works before spending more.
SalonsHair stylistsBarbershopsMed spasNail studiosLash barsDental clinicsChiropractorsPhysiotherapyMassage therapistsWellness clinicsDermatologyVeterinary clinicsPet groomingHome servicesPlumbersElectriciansHVACCleaning servicesLawn careTutorsPersonal trainersYoga studiosPilates studiosLaw firmsAccountantsReal-estate agentsPhotographers SalonsHair stylistsBarbershopsMed spasNail studiosLash barsDental clinicsChiropractorsPhysiotherapyMassage therapistsWellness clinicsDermatologyVeterinary clinicsPet groomingHome servicesPlumbersElectriciansHVACCleaning servicesLawn careTutorsPersonal trainersYoga studiosPilates studiosLaw firmsAccountantsReal-estate agentsPhotographers
§ 01 — See it in action

Talk to the agent on the left. Watch the booking appear on the right.

This is the same agent shape you'll deploy. Ask it about a haircut on Tuesday, a reschedule, or a cancel — it'll write the appointment straight into the calendar.

Live AI chat → connected to Lawmatics
Bookings land here in real time
Lawmatics logoWorks with Lawmatics
§ 02 — Questions you'd ask before buying

FAQ — Lawmatics integration.

Does this actually work with my Lawmatics account?
Yes. AnyCRM uses Lawmatics' official API via OAuth (or a personal API token). Every captured caller lands as a Contact with a linked Matter at the right practice area, the right responsible attorney, the right intake-pipeline stage, and original-source attribution, plus a first activity note from the call. Consultations land as native Lawmatics appointments on the right attorney's calendar.
Will it create duplicate Contacts in Lawmatics?
No. AnyCRM resolves the existing contact first (normalising email and phone) before writing. A returning caller becomes a new note on the existing contact's linked matter, never a second contact, and the existing responsible attorney is preserved.
Can it route different intakes to different attorneys?
Yes. AnyCRM reads your Lawmatics user roster once at setup. Every active attorney, with their practice areas, bar admissions, jurisdictions, and consultation length. Family-law, personal-injury, estate, immigration calls each route differently — and only to attorneys actually admitted in the matter's jurisdiction. Existing matter assignments are always preserved.
Where do the consultations actually live, calendar or Lawmatics?
Both. AnyCRM writes the consultation as a native Lawmatics appointment with the attorney as host and the prospective client as invitee, and links it to the matter. Which makes Lawmatics' Google/Outlook calendar sync fire automatically. You see one appointment on the matter timeline, one calendar invite on the attorney's calendar, one source-attributed contact.
Can it cancel or reschedule a consultation from a phone call?
Yes. The caller gives their email, AnyCRM finds the soonest upcoming consultation on their linked matter, the AI Receptionist reads it back, and AnyCRM either reschedules in place or records the cancellation outcome the Lawmatics-native way (with the reason captured on the matter timeline). Never a deletion that would strip the audit trail.
Does it open a matter, or just a contact?
It opens the matter alongside the contact, every time. Lawmatics' intake pipeline runs on matters — without one, intake automations don't fire, conflict checks don't run, and the contact never appears on any attorney's docket. AnyCRM never leaves a contact without a matter linked to it.
What if a caller has two upcoming consultations in Lawmatics?
AnyCRM returns every upcoming appointment on every linked matter (date, time, attorney, practice area) and the AI Receptionist asks which one to change before doing anything. It never assumes.
Does it handle timezones correctly?
Yes. The AI Receptionist confirms the caller's country/timezone, AnyCRM converts the consultation time into the format the Lawmatics appointment requires, and the AI Receptionist reads the time back to the caller in their local timezone. No customer-facing UTC strings, no off-by-an-hour confirmations — which matters especially for firms with out-of-state intakes.
Does it create new matters at the right pipeline stage?
Not by guessing. AnyCRM stays focused on the conversation surface: capturing the contact, opening the matter at the first intake stage you configured, matching the right attorney, booking the consultation. What happens AFTER that — moving the matter through your intake pipeline, firing the conflict check, sending the engagement letter — is YOUR business policy, and that policy lives inside your CRM, in the receiving flow we wire up for you at onboarding. Every contact-create and every consultation-book in AnyCRM sends a lead event straight into that flow (tagged with source AI Receptionist Call or AI Receptionist Web). Your flow decides which pipeline transitions, which automations, which workflow trigger. AnyCRM doesn't try to encode policy that will drift out of date the moment your firm changes.
How does the conversion tracking work?
Every lead event AnyCRM produces (from a phone call, a chat conversation, OR a website intake form / chat widget) flows through a single conversion pipe. It lands in your CRM for intake automations. AND it fires server-side into Google Ads, Facebook Ads, and your analytics platform, using the origin of the domain you registered with AnyCRM. Server-side means the conversion can't be blocked by ad-blockers and doesn't degrade under iOS / Safari tracking restrictions. The result: higher ROAS, lower ad costs, enriched analytics, and attribution that doesn't fragment between web and voice. As far as we can tell, none of our competitors have built this yet.
What about my existing website intake forms? Do they go through the same pipe?
Yes — that's the whole point. Web intake forms / chat widgets AND the AI Receptionist produce the same lead-event shape with the same source taxonomy. They land in the same place in your CRM, and they fire the same server-side conversion event into your ad platforms. So your bid strategy optimises against unified, real consultations instead of fragmenting across web-only and voice-only stacks.
How long until it's actually capturing intakes into Lawmatics?
Most firms are live the same afternoon. The OAuth grant takes a minute. The roster, practice areas, matter types, and pipeline stages import is automatic. We wire up the lead-receiving flow inside your CRM during onboarding. The phone integration is usually under an hour. Web chat is faster.
Lawmatics logoWorks with Lawmatics
§ 03 — Availability & Booking

Captures the intake as a Lawmatics contact, opens the matter, books the consultation, and feeds one unified conversion pipe for your website forms AND your AI Receptionist.

Every caller who lands on the line becomes a Lawmatics contact (with a linked matter, the right practice area, the right responsible attorney, and original-source attribution). When they want a consultation, AnyCRM creates a native Lawmatics appointment on the matched attorney's calendar. AND the same lead event flows through one unified pipe (with the same shape, same source attribution, and same server-side conversion path used by your website forms) so your Lawmatics intake pipeline AND your Google / Facebook / LinkedIn Ads both stay in sync.

A.01

Every caller becomes a Lawmatics contact, not a missed intake

The AI Receptionist captures name, email, phone, practice area, opposing party, jurisdiction, and the caller's account of the situation. Then AnyCRM writes the record into Lawmatics as a contact with a linked matter, the right responsible attorney, lead status, and intake-pipeline stage attached DURING the call.

A.02

Books consultations as native Lawmatics appointments

The consultation lands as a Lawmatics appointment with the matched attorney as host, the prospective client as invitee, and the matter linked. So it shows on the matter timeline and the attorney's calendar exactly the way Lawmatics expects — and Lawmatics' Google/Outlook calendar sync fires automatically.

A.03

Sends the lead event straight to your CRM. You decide what happens next.

AnyCRM does not pretend to know your intake-conversion rules. Every contact-create and every consultation-book sends a lead event straight to your CRM (with source: "AI Receptionist Call" or source: "AI Receptionist Web") where YOUR intake automations take over. Move the matter through the pipeline, fire the conflict check, send the engagement letter, route the workflow. We set up the receiving end inside your CRM for you during onboarding, tuned to the practice areas you handle and your firm's configuration. AnyCRM doesn't get in the way of policy you've already encoded.

One conversion pipe for your website forms AND your AI Receptionist.

Most law firms run two completely separate conversion-tracking stacks: one for the website (intake forms, chat widgets, page-load pixels) and a totally absent one for the phone and the AI Receptionist. So Google Ads and Facebook Ads only learn from web form-fills, the bidding optimises for the wrong audience (often tire-kickers comparing five firms), attribution is broken, and analytics double-count or miss real consultation requests entirely. AnyCRM closes that gap by running BOTH surfaces through a single conversion pipe.

1. Capture

A lead arrives either through your website intake form / chat widget OR through the AI Receptionist on phone / chat. Either way, AnyCRM produces the same clean lead-event shape, tagged at source with either AI Receptionist Call, AI Receptionist Web, or your website's form identifier. One vocabulary across both surfaces.

2. Deliver to your CRM

AnyCRM sends the lead event straight to your CRM, into the receiving flow we wired up for you at onboarding. Your intake automations decide what happens next: which pipeline stage, which conflict check, which engagement-letter template, which attorney's docket. You don't have to maintain two sets of rules. Web leads and AI Receptionist leads both arrive through the same door.

3. Fire server-side conversion to your ad platforms

The same lead event fires server-side into Google Ads, Facebook Ads, and your analytics platform, using the origin of the domain you registered with AnyCRM. Server-side means the conversion can't be blocked by ad-blockers, doesn't degrade under iOS / Safari tracking restrictions, and lands with full attribution context.

4. Optimise, attribute, report

Because website conversions AND AI Receptionist consultations flow through the same pipe with the same source taxonomy, your Google Ads bid strategy now optimises against real signed engagements (not just form-fill noise), your Facebook Ads campaigns see the high-intent traffic that picks up the phone at 9pm, your analytics platform sees a single unified funnel, and attribution stops fragmenting between web and voice.

Most competitor AI Receptionists try to maintain rules for when a matter is opened, what pipeline stage it lands on, and which source tag to apply. That approach breaks the moment your firm changes (new practice area, new intake-team workflow), and it ignores the conversion-tracking surface entirely. AnyCRM inverts the responsibility. AnyCRM stays focused on the conversation (capture, dedup, route, book, cancel) and delivers a clean lead event to the two destinations that matter: your CRM (for intake policy) and your ad platforms server-side (for conversion optimisation, attribution, and ROAS). This is a custom service baked into the AI Receptionist package. We configure the lead-receiving flow inside your CRM AND the server-side conversion tracking at onboarding, matched to your specific practice areas, ad mix, and analytics setup.

We'll be candid: as far as we can tell, none of our competitors have thought of this yet. They sell AI Receptionists as a phone-answering product. AnyCRM treats the AI Receptionist as one of two equally weighted entries into a unified lead-event pipe, and that's where the real compounding value sits — especially in legal, where one signed engagement can cover a year of Ad spend.

For your developer: how this wires into Lawmatics

The AI Receptionist asks AnyCRM for availability against the attorneys on your team and gets back open slots in the caller's timezone. No double bookings. Existing busy time on the attorney's calendar is always respected. Every AnyCRM call prevents duplicate contacts, opens or links the matter with the right practice area, sets the responsible attorney (matched from your team), writes the appointment so Lawmatics' calendar sync to Google/Outlook fires automatically, and sends the lead event straight into your CRM tagged with <code>AI Receptionist Call</code> or <code>AI Receptionist Web</code>. The same lead also feeds the AnyCRM Conversion Lift pipeline (covered in the next capability) so your Google, Facebook, and LinkedIn Ads start optimising against the call and chat leads that actually pick up the phone.

getLawmaticsAvailability()createLawmaticsContactAppointment()
POST/mcp/tools/getLawmaticsAvailability
{
  "invitee_timezone": "America/New_York",
  "start_time": "2026-05-15",
  "end_time":   "2026-05-17",
  "event_type_uuid": ["b050bcf6-b5b0-42a8-9359-aba11e711311"],
  "multi_day": true,
  "include_scheduling_url": false
}
200response
{
  "date_range_label": "Friday, May 15, 2026 – Sunday, May 17, 2026",
  "event_types": [{
    "event_type_uuid": "b050bcf6-b5b0-42a8-9359-aba11e711311",
    "total_slots": 15,
    "available_times_by_date": {
      "Friday, May 15, 2026": [
        { "start_time": "2026-05-15T10:00:00-04:00", "status": "available" },
        { "start_time": "2026-05-15T10:30:00-04:00", "status": "available" },
        { "start_time": "2026-05-15T11:00:00-04:00", "status": "available" }
      ]
    }
  }]
}
POST/mcp/tools/createLawmaticsContactAppointment
{
  "name": "Jane Doe",
  "email": "jane@example.com",
  "phone": "+14155551234",
  "scheduled_datetime": "2026-05-15T11:00:00",
  "invitee_timezone": "America/New_York",
  "event_type_uuid": "b050bcf6-b5b0-42a8-9359-aba11e711311",
  "questions_and_answers": []
}
200response
{
  "event_uuid": "a7c1f4e9-...",
  "start_time": "2026-05-15T11:00:00-04:00",
  "start_time_utc": "2026-05-15T15:00:00Z",
  "invitee_timezone": "America/New_York",
  "reschedule_url": "https://...",
  "cancel_url": "https://..."
}
Lawmatics logoWorks with Lawmatics
§ 04 — Ads Conversion Lift

Turns every call and chat into a real conversion event your Google, Facebook, and LinkedIn Ads can actually optimise against. So Cost per Lead drops, ROAS goes up, and CAC stops being a guess.

If your firm runs paid Ads on Google, Facebook, or LinkedIn, here is the uncomfortable truth: those platforms only get smarter when they see real conversions. Today, a website intake form-fill counts. A real phone call from a high-intent prospective client who picked up the phone at 7pm and described their case for fifteen minutes does NOT count. So Google bids harder on the audience that fills forms (often tire-kickers comparison-shopping five firms) and ignores the audience that actually calls. Cost per Lead looks fine. CAC quietly creeps up. ROAS looks misleading. AnyCRM fixes this. Every call and chat the AI Receptionist handles is sent as a real conversion event to Google Ads, Facebook Ads, AND LinkedIn Ads. The bidding algorithm finally sees what's actually working.

1b.01

Every phone call and every chat becomes a tracked conversion. Not just website form-fills.

Today, Google Ads and Facebook Ads probably think your only conversions are website intake-form submissions. That's why your Cost per Lead looks low but your intake coordinator complains the leads are weak — they're price-shoppers, not signed engagements. The high-intent traffic is calling you instead of filling a form, and the Ad platforms have no idea. AnyCRM sends every call and every chat the AI Receptionist handles into your Ad platforms as a real conversion event. Suddenly Google, Facebook, and LinkedIn can see the FULL picture of who is converting from your Ads.

1b.02

Lower Cost per Lead. Better ROAS. Smaller CAC.

Once your Ad platforms can see the phone calls and chats as real conversions, they re-train on a better signal. Bidding shifts toward audiences that actually pick up the phone with a real case, not just the audience that loves filling out forms. In practice this means: Cost per Lead drops because you stop overpaying for low-intent form-fills; Return on Ad Spend goes up because the Ads now find people closer to a signed retainer; and Customer Acquisition Cost shrinks because more of your Ad budget reaches prospects who will actually convert into clients.

1b.03

The same pipe carries your website forms too. One source of truth across Ads, CRM, and Analytics.

AnyCRM doesn't just track AI Receptionist conversions. It also runs your existing website intake forms and chat widgets through the same pipeline. So a lead from a Google Ad that fills your "free consultation" form AND a lead from a Facebook Ad that called the AI Receptionist three days later both end up tagged, attributed, and counted in exactly the same way. Your Ads platform stops double-counting, your analytics stop fragmenting, and your CRM stops being half-blind to where your leads actually came from.

Imagine your firm spends $5,000/month on Google Ads for "family law attorney." Today, you see 80 web form-fills and assume that's the full picture. With AnyCRM running, you'll also see (say) 60 phone calls and 45 web chats the AI Receptionist handled, all flowing into Google Ads as real conversions. Suddenly Google sees 185 conversions a month instead of 80. It re-trains on that bigger, better signal. Within weeks, the bidding finds you more of the right kind of prospect — people ready to retain, not price-shoppers. Same $5,000 spend, more real consultations, lower Cost per Lead, higher signed-engagement revenue. That is what "AI Receptionist with AnyCRM" actually means for the bottom line. Not just "it answers the phone."

For your developer: how the Conversion Lift pipeline works with Lawmatics

Every contact-create and consultation-book fires through AnyCRM's Conversion Lift pipeline. The lead event lands inside your CRM for intake policy, AND fires a real conversion event server-side into Google Ads, Facebook Ads, and LinkedIn Ads using the verified origin of your registered domain. Server-side means the conversion can't be blocked by ad-blockers, doesn't degrade on iOS or Safari, and arrives with full attribution context so the Ad platforms' bidding algorithms can re-train on it. Your existing website intake forms run through the same pipeline, so Web and Voice conversions feed the SAME training signal.

createOrUpdatesLawmaticsContact()createLawmaticsContactAppointment()
Lawmatics logoWorks with Lawmatics
§ 05 — Search, Reschedule & Cancel

Manages the full consultation lifecycle inside Lawmatics for anyone calling or chatting.

Every "push the consult to Thursday" or "actually, I want to cancel" lands with the AI Receptionist instead of on the intake coordinator's desk. AnyCRM reschedules update the existing Lawmatics appointment in place. Cancellations follow Lawmatics' own best practice. Reason recorded on the appointment, on the matter timeline. Instead of deleting the appointment and erasing the audit trail, you get crystal clarity on when a Lawmatics consultation was created, and when and why it was updated by your AI Receptionist.

B.01

Finds the consultation by email in a single step without needing a Lawmatics appointment ID

Clients DO NOT quote appointment IDs over the phone. We've tested with hundreds of callers and each time they were asked 'Can you tell me the appointment id from your email?', the response was the same: 'Why can't you find it yourself?'. AnyCRM gives the AI Receptionist an easy way to find the soonest upcoming consultation on the matter linked to the matching contact. And the AnyCRM response forces the AI Receptionist to be human. It reads back the date, time, attorney, and practice area before changing anything.

B.02

Reschedules in place and keeps the matter data clean

Rescheduling updates the existing appointment in a single confirmation. No cancel-then-rebook round-trip means the matter, the intake pipeline stage, the conflict-check status, and the calendar invite all stay intact. Failed reschedules leave the original appointment untouched.

B.03

Cancels without erasing the audit trail

When a caller cancels, AnyCRM records the cancellation the way Lawmatics' own reporting expects. Then it writes the caller's reason onto the linked matter timeline, instead of deleting the appointment and stripping WHY the consult fell through. This lets you intuitively track changes for Lawmatics consultations created or updated by your AI Receptionist.

For your developer: reschedule & cancel by email

AnyCRM's search, reschedule, and cancel all accept just an email. The soonest upcoming Lawmatics appointment on a matter linked to the matching contact is resolved inside AnyCRM. No appointment IDs at the AI Receptionist layer.

searchLawmaticsAppointments()rescheduleLawmaticsAppointment()cancelLawmaticsAppointment()
POST/mcp/tools/searchLawmaticsAppointments
{
  "email": "jane@example.com"
}
200response
{
  "meetings": [{
    "event_uuid": "a7c1f4e9-...",
    "event_type_name": "Haircut Only | $50",
    "start_time": "2026-05-15T11:00:00-04:00",
    "status": "active"
  }]
}
POST/mcp/tools/rescheduleLawmaticsAppointment
{
  "email": "jane@example.com",
  "scheduled_datetime": "2026-05-16T14:00:00",
  "invitee_timezone": "America/New_York",
  "reason": "Customer asked to move 1 day later"
}
200response
{
  "cancelled_event_uuid": "a7c1f4e9-...",
  "new_event_uuid": "f0e22c91-...",
  "new_start_time": "2026-05-16T14:00:00-04:00",
  "new_start_time_utc": "2026-05-16T18:00:00Z"
}
POST/mcp/tools/cancelLawmaticsAppointment
{
  "email": "jane@example.com",
  "reason": "Customer is unwell"
}
200response
{
  "cancelled_event_uuid": "a7c1f4e9-...",
  "status": "cancelled",
  "reason": "Customer is unwell"
}
Lawmatics logoWorks with Lawmatics
§ 06 — Match Specialists & Services

Routes every caller to the right attorney. By practice area and jurisdiction. And maintains the existing attorney on an open matter instead of randomly reassigning to someone else.

Law firms run on practice areas, jurisdictions, and the attorney who actually handles each one. At setup AnyCRM imports your Lawmatics user roster into its database and enriches each attorney with practice areas, bar admissions, jurisdictions, languages, timezone, and consultation length. The AI Receptionist then routes each caller to the attorney who actually handles that matter type — and is admitted in that jurisdiction. Existing responsible-attorney assignments in Lawmatics are honoured as the source of truth.

C.01

Routes by practice area: family vs personal injury vs estate

"My spouse filed for divorce" routes to your family-law attorneys. "I was rear-ended on the 405" routes to PI. "I need to update my will" routes to estate. Each routing decision is made against the practice areas and jurisdictions you actually cover. And the existing responsible attorney on the matter is always preserved.

C.02

Honours existing matter assignments in Lawmatics

If a contact already has an open matter with a responsible attorney in Lawmatics, the AI Receptionist doesn't reassign them. The new appointment and activity note attach to the existing matter under the existing attorney. No orphaned duplicate matter, no client poached off another lawyer's docket.

C.03

Matches fresh inbound callers and website chatters to the right attorney

Net-new callers with no existing Lawmatics contact get matched to an attorney in the practice area you've designated, filtered by bar admission and jurisdiction, honouring the criteria you set in AnyCRM for matching a new intake to an attorney. The AI Receptionist doesn't fight the rules you already use.

For your developer: specialist roster & per-service routing

Team details live in AnyCRM's database, pulled once from Lawmatics at setup, enriched with practice areas, bar admissions, jurisdictions, languages, timezone, and consultation length (valuable context for the AI Receptionist that Lawmatics' user object doesn't carry by default). At runtime, one read of the team roster matches caller → practice area → attorney. New matters get assigned to the right attorney. Existing matters keep theirs. AnyCRM does NOT cache your intake pipelines, your stages, or your matter automations. That policy stays inside your CRM, where it belongs.

listLawmaticsTeamMembers()getLawmaticsUserProfile()
POST/mcp/tools/listLawmaticsTeamMembers
{}
200response
{
  "total_members": 3,
  "members": [
    { "user_uuid": "3d2ed2c0-...", "name": "Michelle Arcona", "role": "user",  "timezone": "America/New_York" },
    { "user_uuid": "2b00d6f3-...", "name": "Casey",           "role": "user",  "timezone": "America/New_York" },
    { "user_uuid": "1809c459-...", "name": "Cielona Boco",    "role": "owner", "timezone": "America/New_York" }
  ]
}
POST/mcp/tools/getLawmaticsUserProfile
{
  "user_uuid": "3d2ed2c0-a8fc-45d7-9f67-fc3e6b898bb2"
}
200response
{
  "user_name": "Michelle Arcona",
  "user_timezone": "America/New_York",
  "services": [
    { "event_type_uuid": "b050bcf6-...", "name": "Haircut Only | $50",                 "duration": 50  },
    { "event_type_uuid": "9a858539-...", "name": "Fine Density Haircut & Finish | $70",  "duration": 60  },
    { "event_type_uuid": "c1f70bb1-...", "name": "Full Head + Gloss + Finish | $335",    "duration": 210 },
    { "event_type_uuid": "3c01fa3d-...", "name": "All Over Keratin Treatment | $300",    "duration": 240 }
  ]
}
Lawmatics logoWorks with Lawmatics
§ 07 — Setup & why it's not just another Lawmatics wrapper

Setup in 3 steps. Battle-tested on real Lawmatics firms.

You connect Lawmatics once. AnyCRM imports your roster, your practice areas, your matter sub-types, and your intake pipeline stages. AnyCRM also wires up the receiving end inside your CRM so lead events from the AI Receptionist land where your intake automations can act on them. Then the AI Receptionist starts capturing intakes and booking consultations the same afternoon. No middleware. No prompt-engineering by you.

S.01

Connect Lawmatics (OAuth or API token, 60 seconds)

Authorize AnyCRM on your Lawmatics account via the standard OAuth grant, or paste a personal API token from your Lawmatics settings. AnyCRM scopes to the least amount of access needed for the intake + booking lifecycle. Nothing for billing, time entries, trust accounting, or document automation. You can always revoke permissions at any time from your firm-level integrations page. Every update to your Lawmatics is signed with AnyCRM's connected-app credentials so it's easy to track what the AI Receptionist did when you audit.

S.02

Import the team. Lock in your practice areas and matter types. Wire up your CRM's lead-receiving flow.

AnyCRM imports every active Lawmatics user as a bookable attorney with practice areas, bar admissions, jurisdictions, languages, timezone, and consultation length. AnyCRM also freezes the practice areas, matter sub-types, and intake pipeline stages so the AI Receptionist can only open matters that actually exist, and locks inbound-call source attribution (always AI Receptionist Call or AI Receptionist Web) so reporting stays consistent. During onboarding we set up the receiving flow inside your CRM so the lead events from the AI Receptionist land where your intake automations can act on them. AnyCRM does NOT replicate your intake pipelines, stages, or matter automations. Your CRM decides what happens after a lead is captured. AnyCRM just delivers a clean event.

S.03

Drop the AI Receptionist on your phone line and your site

Forward your business number to the AI Receptionist's number and paste the chat widget into your site. The same AI Receptionist (same team roster, same Lawmatics account, same lead-event pipe into your CRM and your ad platforms) answers both voice and web. Live the same afternoon.

Why not just use Lawmatics' intake forms + automations + scheduling links?

Lawmatics' intake forms, automations, and built-in scheduling links are excellent at the steps AFTER a prospective client has chosen to come to you via your website. They don't pick up the phone. A new caller at 9pm gets a missed call, not a contact record. A submitted intake form sits in the pipeline until the intake coordinator reads it. The scheduling link only helps people who already navigated to it. The AI Receptionist is the layer BEFORE all of that. It picks up the call, runs your intake script, books the consultation as a native Lawmatics appointment on the right attorney's calendar, writes a clean contact and matter (with the source set to AI Receptionist Call or AI Receptionist Web, intake stage, and a call summary as the first activity note), AND sends the same lead event straight into your CRM's downstream intake automations plus your ad platforms server-side. So your Lawmatics automations, your analytics, and your Google / Facebook Ads bidding all start optimising on a real conversation, not a name and a missed call.

For your developer: the enrichment layer (raw Lawmatics API vs our MCP tools)

Every tool the AI Receptionist calls is an opinionated wrapper inside AnyCRM. AnyCRM does the messy work for you. Dedup, matter creation with the right practice area, responsible-attorney assignment, intake-pipeline stage mapping, consultation-length resolution, timezone math, dual-array assembly for calendar sync, error handling, lead-event delivery into your CRM, and server-side conversion tracking into your ad platforms. All of it happens before the LLM ever sees a response. So the AI Receptionist reasons over clean, AI-aligned payloads instead of raw CRM internals.

Capturing a new intake

Raw APIWriting a contact straight into Lawmatics looks simple. But Lawmatics treats Contact and Matter as separate first-class entities, and a contact without a matter never enters the intake pipeline. To capture an inbound caller correctly you'd have to write the contact, then write the matter with the right practice area and matter sub-type and intake pipeline stage, then write the intake note on the matter. The matter's source is set-once at creation. You can't fix it later. The practice area and matter type are enum-bound to whatever your admin configured. Get any of them wrong and the matter exists but never fires intake automations. And nothing in raw Lawmatics fires a server-side conversion event to your ad platforms, so call-driven and chat-driven leads never get optimised for.
Our MCPcreateOrUpdatesLawmaticsContact accepts name, email, phone, note, practice_area, jurisdiction, plus the matched attorney. AnyCRM handles dedup, picks the surviving record (or creates a new one with the right values in the right order), opens the linked matter with the right practice area and matter sub-type from the frozen setup values, drops it at the intake pipeline's first stage, locks the source, appends the intake summary as a note on the matter, sends the lead event straight into your CRM (with source AI Receptionist Call or AI Receptionist Web), AND fires a server-side conversion event into your ad platforms using the origin of your registered domain. All in one AnyCRM call.

Booking the consultation

Raw APICreating a consultation appointment directly against Lawmatics is a tight contract. The time format has to be exactly what Lawmatics accepts, the responsible attorney has to be set as host (not just listed), and the appointment has to be linked to the matter (not just the contact) for it to surface on the matter timeline and the attorney's docket. Leave the host attorney off and the appointment writes into Lawmatics but never lands on the attorney's actual Google/Outlook calendar. Skip the matter link and the appointment won't surface on the matter record either.
Our MCPcreateLawmaticsContactAppointment takes email, scheduled_datetime (a naive date and time, no offset needed), invitee_timezone, and appointment_type. AnyCRM resolves the right attorney from the practice-area lane, handles the timezone and duration math, builds the host + invitee structure correctly (so Lawmatics' Google/Outlook calendar sync fires), links the appointment to the matter, sends the same lead event straight into your CRM with the booking context, fires the server-side conversion event into your ad platforms, and returns both local and UTC start times in the response.

Cancelling with a reason

Raw APIDeleting a consultation in Lawmatics strips it off the matter timeline entirely. No reason, no audit trail, no signal to the attorney of WHY the prospective engagement fell through. Lawmatics' own best practice is to record the cancellation outcome instead of deleting it, so it stays queryable in reporting and on the matter timeline. Doing that cleanly takes several round-trips: read the appointment, write a note on the matter with the reason, then update the appointment.
Our MCPcancelLawmaticsAppointment takes email and reason. AnyCRM resolves the soonest upcoming consultation, records the reason on the matter timeline, and records the cancellation outcome the Lawmatics-native way. All in one AnyCRM call. No deletion, full audit trail, the consultation stays queryable in reporting and the matter pipeline reflects the real outcome.

Every AnyCRM tool for Lawmatics follows the same AI-alignment contract, so the AI Receptionist never has to think about transport:

  • Naive datetimes in, Lawmatics-native shape out. The AI Receptionist passes 2026-05-15T11:00:00 and a timezone string. AnyCRM converts it into whatever shape the Lawmatics appointment requires, on both start and end.
  • Email is the identity. Cancel and reschedule never need an appointment ID at the AI Receptionist layer. Email and soonest-upcoming resolves inside AnyCRM.
  • Practice area, matter type, intake stage, and source come from setup, not the LLM. The AI Receptionist can't invent a practice area or a matter type. It inherits the values you configured at setup.
  • Existing responsible attorneys are sacred. If a matter already has a responsible attorney, AnyCRM preserves it. New matters only get the matched attorney when no existing matter applies.
  • Matter is first-class, not an afterthought. Every booked consultation is linked to a matter, not just a contact. So the intake pipeline, conflict-check workflow, and reporting all reflect a real prospective engagement.
  • Cancellation preserves the audit trail. Lawmatics' best practice for cancelled consultations is honoured so the timeline stays intact and reporting still counts the matter under the right outcome.
  • Every lead event leaves AnyCRM in two places at once. Your CRM gets the lead event so your intake automations can run. Your ad platforms get the server-side conversion event so bidding optimises against real consultations. Both happen on the same AnyCRM call. No race conditions, no missing events.
  • Flat, deterministic shapes. Every AnyCRM response has the same top-level keys across every tool, so the AI Receptionist's prompt never grows with edge-case branching.
  • Errors are messages, not codes. An error from Lawmatics becomes a one-sentence reason the AI Receptionist can repeat to the caller without translation.
  • Idempotent reschedules. If a reschedule fails mid-flight, the original Lawmatics appointment is preserved. The prospective client never ends up with nothing.

Multi-attorney setup. Team roster, practice areas & system-prompt assembly

If your firm runs more than one attorney on Lawmatics, AnyCRM imports the team roster once, you link each attorney to the practice areas and jurisdictions they actually cover, and AnyCRM bakes the result into the AI Receptionist's system prompt at setup time. Not at runtime. The AI Receptionist doesn't query your team roster on every call. It already knows who handles what.

  1. Team roster import. AnyCRM imports your Lawmatics users once and writes each attorney into its database keyed by crm_user_id (with name, role, practice areas, bar admissions, jurisdictions, timezone).
  2. Per-attorney practice areas & consultation types. For each attorney AnyCRM resolves the practice areas they actually handle and the consultation length per area. One call per person, cached.
  3. Practice-area visibility. Each practice area is flagged Public, Private or Ignored. The AI Receptionist only routes to and books on Public areas. You toggle this in the AnyCRM dashboard without re-deploying.
  4. Lead-event receiving flow inside your CRM. During onboarding we wire up the flow inside your CRM that receives lead events from AnyCRM. That's where your intake-conversion policy lives. AnyCRM doesn't try to own it.
  5. System-prompt assembly. The cached team roster, practice-area, and jurisdiction JSON is prepended to the AI Receptionist's system prompt before the humaniser splits (personality, etiquettes, tone, speech style). So the AI Receptionist reads the firm before it reads its own instructions.
  6. Runtime stays minimal. On a live call the AI Receptionist makes at most one availability call and one booking call. Never a team roster lookup. Updates to attorneys, practice areas, or consultation types re-run the cache. The AI Receptionist picks them up on its next deploy.

The end result: the AI Receptionist can match "my husband filed for divorce in Cook County last week" → family-law lane → the attorney admitted in Illinois who covers that practice area → that attorney's consultation length → that attorney's calendar availability → a booked Lawmatics appointment linked to a new matter on the right attorney's docket → a lead event delivered straight into your CRM → a server-side conversion event in your ad platforms. Without a single team roster query during the call.

Currently running for family-law, personal-injury, estate-planning, immigration, criminal-defence, and small-business boutiques. Any firm whose intake pipeline is in Lawmatics but whose phone keeps ringing after the intake coordinator has logged off.

Lawmatics logoWorks with Lawmatics
§ 08 — How AI receptionists usually fail, and why ours can't

How most AI Receptionists built on Smith.ai, My AI Front Desk, Goodcall, or Lawmatics' native AI agents fail for family-law, personal-injury, estate-planning, immigration, criminal-defence, and small-business boutiques that use Lawmatics. And why AnyCRM can't.

Most AI Receptionists fail on Lawmatics in the same handful of ways. Duplicate contacts, contacts captured without matters, invented practice areas and matter types, consultations that never sync to the attorney's real calendar, bookings outside the attorney's bar admission, deletions that destroy the audit trail, hardcoded intake-conversion rules that drift away from your real policy, and conversion data that never reaches your ad platforms server-side. AnyCRM can't fail in any of these ways, because each failure was solved one layer down inside AnyCRM. And because AnyCRM delegates intake-conversion policy to your CRM's own flow rather than trying to encode it, AND runs web and AI Receptionist conversions through a single unified conversion pipe instead of two disconnected stacks.

Duplicate contacts

Affects:My AI Front DeskGoodcallSmith.ai
Why it happensLawmatics has no implicit dedup at the API layer. Send the same caller twice and you get two contacts with two matters and two truncated timelines. My AI Front Desk runs on a Zapier-style "Add Contact" action — a single API call that hands the caller's email straight to Lawmatics, with no "search first" step in the path. Same caller, slightly different casing? Duplicate. Phone-only? Duplicate. Goodcall writes through a connector that does the same single-step create. Smith.ai's native Lawmatics integration does search-then-update on phone or email, which is the right shape — but the write happens after the call ends, not live during the booking flow, so dedup state at the moment the AI Receptionist is deciding what to say to the caller is still stale.
Why ours can'tAnyCRM does NOT do a one-shot create. AnyCRM first searches Lawmatics on a normalised lowercased + trimmed email, then on a normalised phone, then decides whether to update the existing contact or create a new one. A returning caller lands on the existing record with a new note on the linked matter, never as a duplicate. This costs us an extra API call per contact-create. We do it anyway, because the alternative is the duplicate-contact mess that My AI Front Desk and Goodcall users live with, and the after-the-call dedup window that Smith.ai users live with.

Capturing a contact without a matter

Affects:My AI Front DeskGoodcallSmith.ai
Why it happensLawmatics' intake pipeline runs on matters, not contacts. A contact without a matter never enters the intake pipeline, never fires intake automations, never appears on any attorney's docket, and never triggers the conflict-check workflow. My AI Front Desk exposes "Add Contact" and "Create Matter" as separate Zapier-style actions — there is no atomic "capture contact + open matter" composition, so each step can succeed or fail independently and leave the intake half-built. Goodcall writes a contact through its connector but rarely opens the matter, because its action surface treats the contact as the primary entity. Smith.ai's Lawmatics integration can create new matters and contacts and fill firm-supplied Lawmatics intake forms — but it does this on a per-firm configuration that has to be set up with Smith.ai support, and the create happens after the call rather than as part of the live booking flow. Lawmatics' native AI agents (QualifyAI, EngageAI) can capture intake into matters natively — it's the one place that surface has a structural edge — but the rest of this section's failure modes still apply.
Why ours can'tAnyCRM always creates the matter alongside the contact, with the right practice area, matter sub-type, intake pipeline stage, and responsible attorney set from the routed lane. The contact never exists without a matter linked to it. AnyCRM does three things in one call, atomically and live during the call, where Zapier-style competitors do one and where Smith.ai's create happens after the call ends.

Inventing practice areas, matter types, and sources that don't exist in your firm

Affects:My AI Front DeskGoodcallSmith.ai
Why it happensLawmatics' practice areas, matter types, and intake pipeline stages are all firm-specific. The actual values differ from firm to firm. My AI Front Desk's "Create Matter" action exposes practice area as a Zapier field — which means the LLM picks the value at runtime, with no frozen enum constraint. Free-text guesses produce silent matter-creation failures, and the matter's source is set-once at creation so you can't fix it later. Goodcall's connector hands the value through to Lawmatics the same way. Smith.ai can fill firm-supplied Lawmatics intake forms (which constrains the values) but only on the forms the firm chose to share with Smith.ai support — anything outside that surface, including practice-area routing decisions, is a plain-English note that doesn't map cleanly to Lawmatics' enum.
Why ours can'tAnyCRM reads your firm's real practice areas, matter types, and pipeline stages at setup, in a separate call to Lawmatics, and bakes them into the AI Receptionist's system prompt as a frozen table. So when the AI Receptionist captures an intake, it CAN ONLY pick from values that actually exist in your firm. This is API calls at setup time that My AI Front Desk and Goodcall don't make, and a runtime constraint that Smith.ai's form-fill route only achieves for the specific forms the firm pre-shared.

Consultations that don't reach the attorney's real calendar

Affects:My AI Front DeskGoodcallSmith.ai
Why it happensWriting an appointment to Lawmatics looks like it creates a calendar event. And it does, but only inside Lawmatics. Whether it actually syncs to the attorney's Google/Outlook calendar depends on the appointment being assembled correctly. The host attorney has to be set on the right field, not just listed alongside the prospective client. My AI Front Desk's Zapier-style "Schedule Appointment" action does not surface the host-vs-invitee structure — it posts whatever it has and hopes. The appointment shows up in Lawmatics but never lands on the attorney's actual calendar, and the attorney walks into Tuesday morning unaware they have a 10am consult. Goodcall writes to its own scheduler and then a separate sync tries to mirror it back into Lawmatics — so the appointment either doesn't exist in Lawmatics, or exists but never syncs to Google/Outlook. Smith.ai's chat tier books into Lawmatics' calendar, but appointment booking via the phone product is a paid add-on rather than a default, and how it assembles the host-vs-invitee structure isn't exposed in the published materials.
Why ours can'tAnyCRM does multiple things in one call: looks up the attorney's Lawmatics user ID, validates the time format Lawmatics' calendar sync requires, builds the host + invitee structure Lawmatics' calendar sync requires, links the appointment to the matter, then writes it. The consultation lands in Lawmatics AND on the attorney's Google/Outlook calendar atomically. We do four checks where Smith.ai/My AI Front Desk/Goodcall do one. That's why a consult booked through AnyCRM is never missing from the attorney's calendar.

Booking outside the attorney's jurisdiction or practice area

Affects:Smith.aiGoodcallMy AI Front Desk
Why it happensLawmatics' API has no built-in guard against booking a family-law intake on a PI attorney's calendar, or booking an Illinois matter on an attorney admitted only in California. The responsible-attorney field accepts any user in the firm. Whether that attorney is actually licensed to take the matter is a business-rule concern the API doesn't enforce. My AI Front Desk's Zapier-style action takes whichever attorney name the AI generates and posts it. No "is this person admitted in this jurisdiction?" check. Goodcall's scheduler hop assigns based on connector defaults rather than the bar admission the call actually requires. Smith.ai's human receptionists rely on the receptionist's memory of who handles what in which state. Fine on a Tuesday morning, less reliable on a Friday at 8pm with a relief receptionist. Lawmatics' native AI agents have the firm data to enforce this, but the published materials don't expose whether they filter candidates by bar admission before checking availability.
Why ours can'tAnyCRM does the heavy work in multiple steps: matches the practice area from the call's intent, looks up the right attorneys from the AnyCRM team roster, filters by bar admission and jurisdiction BEFORE checking availability, AND checks whether the existing Lawmatics matter already has a responsible attorney. If the existing attorney contradicts the inferred lane, AnyCRM refuses to overwrite. Instead, the AI Receptionist surfaces the conflict so the call respects who is already on the matter. Smith.ai/My AI Front Desk/Goodcall can't do this because their architecture is one-shot.

Cancelling by deletion instead of by outcome

Affects:My AI Front DeskGoodcallSmith.ai
Why it happensDeleting a consultation from Lawmatics strips the appointment off the matter timeline entirely. No reason, no cancellation outcome, no audit trace. My AI Front Desk's Zapier-style cancel action (where it exists) issues a single delete. That's the only Lawmatics operation Zapier exposes for it. The consultation vanishes, the attorney gets no signal of WHY it fell through, and "consultations booked vs cancelled" reporting breaks because the appointment no longer exists to be counted. Goodcall's cancellation goes through its scheduler, not the Lawmatics appointment. So the scheduler is updated but the Lawmatics matter timeline never reflects the cancellation reason. Smith.ai receptionists ask the caller why and add a summary of the call as a note on the matter, but cancellation handling on the consultation appointment itself (outcome-flagged vs deleted) isn't exposed in the published integration materials.
Why ours can'tAnyCRM's cancellation is multi-step: find the soonest upcoming consultation, capture the caller's reason, write the reason onto the matter timeline as a note, AND record the cancellation outcome the Lawmatics-native way. The consultation stays queryable in reporting, with the reason attached. Three operations where Smith.ai/My AI Front Desk/Goodcall do one (and usually the wrong one).

Encoding your intake-conversion policy in the prompt or in middleware

Affects:My AI Front DeskGoodcallSmith.aiLawmatics native AI agents
Why it happensMy AI Front Desk ships hardcoded "Set Pipeline Stage" and "Log Activity" actions that fire on every inbound call. There is no "only advance the matter if the caller is actually a qualified prospect" logic. The action is single-step, so every call advances the matter in the default way, clogging your intake pipeline with unqualified records. Worse, the moment you change your intake pipeline structure or add a new stage, you have to go back into Zapier and rebuild the zap. Goodcall's connector applies whatever default behaviour the underlying integration shipped with. Change your intake process, and the connector keeps doing what it did six months ago. Smith.ai's receptionists work from playbooks that drift out of date as your real intake policy evolves. Lawmatics' native AI agents (QualifyAI, EngageAI) are customisable per practice area and the firm sets the rules and thresholds — so policy is in your control — but the policy lives inside Lawmatics' configuration surface rather than in the same flow that handles your web form conversions, which means you maintain two policy surfaces instead of one.
Why ours can'tAnyCRM does not encode your intake policy at all. AnyCRM sends a clean lead event straight to your CRM, into the receiving flow we wire up for you at onboarding. YOUR flow decides what happens: new intake pipeline? Update the flow. New stage? Update the flow. New source-tag scheme? Update the flow. AnyCRM's behaviour stays consistent because AnyCRM's job stops at the conversation. Smith.ai/My AI Front Desk/Goodcall can't separate these concerns because their architecture forces business policy into either Zapier middleware or a hardcoded action. Lawmatics' native AI agents let you own policy but keep it in a separate surface from your web-form intake flow.

Web leads and AI Receptionist leads run on two separate conversion-tracking stacks

Affects:Smith.aiMy AI Front DeskGoodcallLawmatics native AI agents
Why it happensSmith.ai, My AI Front Desk, Goodcall, and Lawmatics' native AI agents all treat phone and chat conversions as separate from web intake-form / chat-widget conversions. Lawmatics' own Google Ads integration logs ad spend and supports sending offline conversions back to Google Ads, but only via a manual Zapier setup that maps the GClid captured on a Lawmatics web form — it doesn't fire a server-side conversion event when the AI Receptionist closes a consultation, and Facebook Ads and LinkedIn Ads aren't covered. So your Ad platforms only see the website form-fills, the bidding optimises for that (often lower-intent) audience, your Cost per Lead looks deceptively low, ROAS reporting becomes a fiction, and the high-intent traffic that picks up the phone stays invisible to your Ad stack. Worse, when these competitors DO fire any tracking, it's client-side. Blocked by ad-blockers and degraded under iOS / Safari tracking restrictions.
Why ours can'tAnyCRM runs your website conversions AND your AI Receptionist consultations through the same Conversion Lift pipeline. Same event shape, same source taxonomy, same delivery to your CRM, AND the same server-side conversion event into Google Ads, Facebook Ads, and LinkedIn Ads — using the verified origin of your registered domain. Server-side means it can't be blocked client-side and doesn't degrade on iOS or Safari. The result is what Smith.ai/My AI Front Desk/Goodcall/Lawmatics' native AI agents structurally can't deliver: lower Cost per Lead, higher ROAS, smaller CAC, complete analytics funnels, and attribution that doesn't fragment between web and voice.

The AI Receptionist is honest because AnyCRM doesn't let it lie. And AnyCRM is sophisticated because it doesn't pretend to own policy that belongs inside your CRM, while quietly fixing the conversion-tracking gap nobody else has thought to close.

Lawmatics logoWorks with Lawmatics
§ 09 — Side-by-side comparison

AnyCRM vs Smith.ai, My AI Front Desk, Lawmatics' native AI agents on Lawmatics

CapabilityAnyCRMSmith.aiMy AI Front DeskLawmatics native AI agents
Live Lawmatics consultation booked DURING the call Yes. Native Lawmatics appointment, attorney-matched, calendar-synced, linked to the matter.Partial. Chat tier books; phone tier logs the call for the firm to book manually.Partial. Zapier-style "Schedule Appointment" without structural detail for host-vs-invitee calendar sync.Yes. Native to Lawmatics.
Opens a matter alongside the contact, every time Yes. Atomically — contact + matter + intake stage in one call.Conditional. Native Lawmatics integration can create matters and contacts, but on the firm's pre-shared form configuration with Smith.ai support, after the call.No. Add Contact and Create Matter are separate Zapier-style actions.Yes.
Dedup-before-write on email and phone Yes. Always, live during the call.Yes, but after the call ends. Native integration does search-then-update on phone or email — but the dedup state during the live AI Receptionist conversation is still stale.No. Zapier-style "Add Contact" is one-shot.Unclear from published materials.
Preserves existing responsible attorney on returning callers Yes. Existing attorney is sacred.Implicit, not guaranteed.No. Can overwrite.Unclear from published materials.
Routes by practice area + filters by bar admission / jurisdiction Yes. Bar admission is part of AnyCRM's team roster.Manual, depends on the receptionist's memory.No.Practice-area routing yes; bar-admission filtering not exposed.
Practice areas, matter types & sources frozen from your real firm values Yes. Read at setup, baked into the prompt as a frozen table.Not API-enforced.No. Writes can fail on unknown enum values.Yes (first-party data access).
Cancellation preserves the audit trail (outcome-recorded, not deleted) Yes. Lawmatics-native cancellation with reason on the matter.Reason captured as a note, not as an outcome.No. Deletion strips the timeline.Unclear from published materials.
Reschedule in place (no cancel-then-rebook) Yes.Manual.No.Yes.
Intake-conversion policy delegated to YOUR CRM's own flow Yes. Lead event delivered straight into your CRM, into the receiving flow we wire up at onboarding.No. Policy lives in the receptionist's training and the firm-supplied form configuration.No. Hardcoded "Set Pipeline Stage" action.Partial. Firm owns the rules and thresholds inside Lawmatics' AI agent configuration, but that surface is separate from the flow handling web-form leads.
Unified conversion pipe: web forms AND AI Receptionist → CRM + ad platforms server-side Yes. Same shape, same source taxonomy, same server-side delivery to your CRM and your ad platforms.No. Web and voice run on separate stacks.No. Web and voice run on separate stacks.No. Conversion tracking is not part of the product.
Server-side conversion events sent to Google Ads, Facebook Ads, and analytics (origin = your registered domain) Yes. Every call and chat consultation lands server-side.No.No.No.
Source attribution stays consistent across web and voice Yes. AI Receptionist Call, AI Receptionist Web, plus your web form identifiers.Manual / inconsistent.No standardised taxonomy.Native Lawmatics source only.
Scale ceiling Bounded by Lawmatics API limits, not by staffing.Bounded by human receptionist staffing.Bounded by Zapier rate limits and action contracts.Bounded by Lawmatics' AI agent capability surface and pricing tier.
Lawmatics logoWorks with Lawmatics
§ 10 — Your Lawmatics data passes through. It doesn't stick.

Your Lawmatics data passes through AnyCRM. It doesn't stick.

AnyCRM processes your Lawmatics data to answer the call. Then forgets it. The only thing AnyCRM persists is a conversation history ID so the AI Receptionist can recognise a returning caller. Contacts, matters, appointments, notes. All of it stays in Lawmatics, owned by your firm's account.

What AnyCRM stores

Conversation history IDs only. So the AI Receptionist can pick up where it left off if a caller hangs up and rings back. No call audio, no transcripts of contact records, no caller PII, no matter content.

What AnyCRM doesn't

Caller names, emails, phone numbers, Lawmatics contact IDs, matter IDs, your attorney roster, your practice areas, your pipeline stages, your intake-form content, your conflict-check data. None of it. AnyCRM reads what it needs, hands it to the LLM, fires the events, and discards the payload.

Where data lives

In your Lawmatics account and in whatever systems your CRM's flow forwards lead events to. Contacts, matters, appointments, notes all live in Lawmatics. Source-attributed (always AI Receptionist Call or AI Receptionist Web), attributed to AnyCRM in the audit log, revocable, and inside the firm's existing privilege-aware data boundary. AnyCRM does not build a shadow CRM alongside yours.

Revocation

Revoke the AnyCRM OAuth grant in your Lawmatics firm-level integrations page (or rotate the API token) and the AI Receptionist loses access immediately. There is no "export your data" step because there is no data to export. It was never AnyCRM's to hold.

For your developer: OAuth scopes & the smallest-surface principle

Lawmatics uses OAuth scopes (or a personal API token). AnyCRM requests only the smallest set required for the intake + booking lifecycle. Nothing for billing, time entries, trust accounting, document automation, or e-signature.

  • Contacts (read + write). Read and write contacts, dedup against existing records, append notes (the intake-capture work).
  • Matters (read + write). Create matters with the right practice area, sub-type, and intake-pipeline stage. Update for reschedules and cancellation outcomes.
  • Appointments (read + write). Read availability and write appointments on the responsible attorney's calendar. Update to reschedule and cancel (the booking work).
  • Practice areas & matter types (read). Read your firm-specific values at setup so AnyCRM only writes values that exist.
  • Users (read). Read your attorney roster at setup so the AI Receptionist knows who exists and who owns existing matters.
  • Not requested: billing / subscription data, time entries, trust accounting, document templates, e-signature, your other integrations.

Same OAuth grant any Lawmatics integration uses. Just a smaller surface. AnyCRM holds the access and refresh tokens (every write is signed by AnyCRM's connected-app credentials, so each contact and matter change is attributable to AnyCRM in Lawmatics' audit log). The LLM never sees the token, and every tool call is logged with the operation name, never the raw payload.

Lawmatics logoWorks with Lawmatics
§ 11 — Pricing & the Transparency Ladder

$36 to get started. No monthly subscription. No commission on voice minutes. Ever.

The AI Receptionist industry has settled into a quiet little racket: wrap a public voice provider (usually Eleven Labs) and a public chat platform in your own UI, sell it back on a monthly subscription with a metered minute allowance, and pocket a 3–5× markup on every minute your customer's caller spends on the phone. The customer never sees the underlying price. We did not want to build that business.

AnyCRM uses Eleven Labs for voice. We say that out loud because it is true and because pretending otherwise would be the start of a small lie that grows. You pay Eleven Labs directly — at Eleven Labs' published price — and AnyCRM charges 0% commission on top. We make money from the Quickstart, the DIY Upgrades, and the optional Custom Implementation. Not from your call volume. The more customers call your business, the better — for you, not us.

The Transparency Ladder — you choose how far up you climb.

Most AI Receptionist products sell one thing: a monthly plan with a minute cap. AnyCRM sells five things, ordered by how much we do for you. Start at $36 with a prompt-and-pasted DIY agent. Stop there if it's enough. Or keep climbing through the upgrades to a full custom implementation with MCP tools, conversion tracking, and a CRM-side flow we configure for you.

Step 1
The Quickstart
$36 one-time

A prompt pack and a deployment guide. You wire up a basic AI Receptionist on web chat and voice using OUR humanizer prompts and OUR step-by-step videos.

  • Two humanizer prompts (warmth, pacing, filler words)
  • Web chat + voice setup videos
  • Same-afternoon live deployment
  • No MCP tools (no booking writes into your CRM)
  • No conversion tracking
  • No CRM-side lead-event flow
Step 1b · Order bump
30-min 1:1 Setup Call
+$63 one-time

Add this at checkout. We walk through your setup together so the Quickstart lands faster, without you reading the docs alone.

  • Live setup walkthrough
  • Humanizer prompt tuning to your voice
  • Q&A about your industry's quirks
Step 2
Availability & Booking Upgrade
$98–$196 one-time

Adds the first round of MCP tools so the AI Receptionist actually books appointments into your CRM (not just talks about booking them).

  • getAvailability + createContactAppointment MCP tools
  • Live booking into your CRM
  • Dedup-before-write on email and phone
  • Still DIY — you wire the tools yourself with our videos
Step 3
Full Lifecycle Upgrade
$196–$392 one-time

Adds search, reschedule, and cancel MCP tools. Now the AI Receptionist owns the whole appointment lifecycle — the same one we describe in the Availability and Lifecycle sections above.

  • Search + reschedule + cancel MCP tools
  • Audit-preserving cancellation
  • Specialist / team-member routing if your CRM supports it
  • Still DIY — conversion tracking and CRM flow not included

How AnyCRM stacks up against the monthly-subscription crowd.

Here is what you would pay each provider to handle 500 voice minutes a month — a fair mid-volume number for a service business that picks up after hours. Sourced directly from each vendor's published pricing page.

Cost & structure AnyCRM Smith.ai My AI Front Desk Vocaly AI
Pricing model One-time fee ($36 → $850+) + you pay Eleven Labs directly Monthly subscription, billed per call Monthly subscription, billed per minute Monthly subscription, billed per minute
Entry tier $36 one-time $300/mo (30 calls) $99/mo (200 voice min) $399/mo (2,500 min)
Cost for ~500 voice min / month $0 to AnyCRM + ~$25–85 paid directly to Eleven Labs ~$2,100/mo (Pro tier, ~300 calls) $99 + 300 overage min @ $0.25 = $174/mo $399/mo (2,500 min cap)
Commission / markup on voice minutes 0%. You pay Eleven Labs directly. Bundled (per-call pricing hides minute markup) ~3–5× markup on Eleven Labs' published rate Bundled (rate not disclosed)
Hard monthly minute cap No cap. Eleven Labs scales with your traffic. Yes, by call count Yes (200 min on $99 tier) Yes (2,500 min on $399 tier)
Underlying voice provider disclosed Yes — Eleven Labs. We say it openly. N/A (human receptionists) Not disclosed Not disclosed
CRM-side lead-event flow built for you Yes (Custom Implementation, tuned to your industry) No No (Zapier action list only) No (custom tier only, opaque)
Server-side conversion tracking to Google / Facebook / LinkedIn Ads Yes (Custom Implementation) No No No
Cost over 12 months at ~500 min/mo $36–$850 one-time + ~$300–$1,020 paid to Eleven Labs ~$25,200 ~$2,088 ~$4,788

Pricing as listed on each vendor's published pricing page (Smith.ai, My AI Front Desk / Frontdesk, Vocaly AI, Eleven Labs) at time of publication. Eleven Labs Conversational AI is currently $0.05–$0.17/min depending on plan; "$25–85 paid directly" assumes you sit on the Free, Starter, or Creator plan for low-volume usage. Smith.ai is human-staffed; My AI Front Desk & Vocaly AI are AI-only.

The math is uncomfortable for the industry. A service business paying My AI Front Desk $174/mo for 500 voice minutes is paying roughly $0.35/min, when Eleven Labs' own published rate for that traffic is $0.05–$0.17/min. The difference is pure margin sitting between you and the underlying provider. AnyCRM removes that layer. The Quickstart is $36 once. The Custom Implementation is a one-time quote. You pay your voice provider at their price. We never touch your call volume.
Lawmatics logoWorks with Lawmatics
§ 12 — The arithmetic

One backend. Six channels. Stacked ROI.

Indicative monthly numbers based on what service businesses already see from a single channel — multiplied by the channels you switch on. Update the agent once; every channel reflects it.

Channel
Customer reach
Leads / mo
Conv. value
Monthly ROI
Website ChatChatKit by OpenAI
100%
45–80
$150 / lead
$6,750 – $12,000
Voice AIEleven Labs
85%
30–50
$200 / lead
$6,000 – $10,000
WhatsAppBird Platform
78%
35–60
$125 / lead
$4,375 – $7,500
Instagram DMsBird Platform
65%
25–45
$100 / lead
$2,500 – $4,500
MessengerBird Platform
55%
20–35
$100 / lead
$2,000 – $3,500
TelegramBotFather direct
35%
15–25
$100 / lead
$1,500 – $2,500
Combined deployment
170–295
$23,125 – $40,000
The single-backend advantage. Six channels, one agent. Update the prompt once and every surface reflects it instantly — no middleware subscriptions, no fragmented flows, no Zapier per-execution billing.
Lawmatics logoWorks with Lawmatics
§ 13 — How it works

Four steps. One afternoon.

No Zapier. No n8n. If you can copy and paste, you can do this.

01

Open the Quickstart

You get the prompt pack, the humaniser prompts, and the deployment guide.

02

Connect Lawmatics

One API key. The agent reads contacts and writes appointments — both ways.

03

Pick your channel

Web chat, voice line, or both. Same backend, same brain.

04

Go live

Test five calls yourself. Send the number to your team. Done.

Lawmatics logoWorks with Lawmatics
§ 14 — Get started

Live by tonight. Booking customers by tomorrow.

$36 once. If it doesn't work for your business, you've lost less than dinner.

Lawmatics logoWorks with Lawmatics