An AI Receptionist that books, reschedules & cancels appointments — 24/7 — and writes them straight into
ServiceTitan.
Plugs into your website and phone line. Voice in 30+ languages. Live by tonight, booking customers by tomorrow. No Zapier, no n8n, no code.
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.
FAQ — ServiceTitan integration.
Does this actually work with my ServiceTitan tenant?
Will it create duplicate Customers in ServiceTitan?
Can it route different calls to different Business Units — HVAC, Plumbing, Electrical, Drain?
Where do the bookings actually live — on the dispatch board or somewhere else?
Can it cancel or reschedule a Job from a phone call?
What if a caller has two upcoming Jobs in ServiceTitan?
Does it handle Memberships and Service Agreements?
Does it handle timezones correctly?
Does it create Jobs with the right Campaign attribution?
How does the conversion tracking work?
What about my existing website forms and online booking? Do they go through the same pipe?
How long until it's actually capturing calls into ServiceTitan?
Captures the caller as a ServiceTitan Customer, books the Job on the right dispatch board, and feeds one unified conversion pipe for your website forms AND your AI Receptionist.
Every caller who rings the shop lands as a ServiceTitan Customer with a Location, a Job of the right Job Type on the right Business Unit, and a scheduled Appointment on a qualified Technician's board. AnyCRM writes all of it through ServiceTitan's own API DURING the call. 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 CRM business logic and your Google / Facebook / LinkedIn Ads both stay in sync.
Every caller becomes a ServiceTitan Customer + Location, not a missed ring
The AI Receptionist captures name, primary phone, email, service address, and the trade-specific symptom (no cool air, dripping shutoff valve, breaker tripping). Then AnyCRM writes the Customer and the Location into ServiceTitan on the right Business Unit before the call has ended.
Books Jobs against the right capacity board
AnyCRM resolves the right Job Type, reads live Technician capacity from the dispatch board for that Business Unit and trade, and books the Appointment on a Technician qualified for the work. Not on the first open slot it sees.
Sends the lead event straight to your CRM. You decide what happens next.
AnyCRM does not pretend to know your dispatch policy. Every Customer-create and every Job-book sends a lead event straight to your CRM (with source: "AI Receptionist Call" or source: "AI Receptionist Web") where YOUR business logic takes over. Which Campaign, which priority Job Type, which recall workflow, which member-rate pricing. We set up the receiving end inside your CRM for you during onboarding, tuned to your trades and your tenant 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 home-services shops run two completely separate conversion-tracking stacks: one for the website (forms, online booking, page-load pixels) and a totally absent one for the phone and the AI Receptionist. So Google Ads and Facebook Ads only learn from form-fills, the bidding optimises for the wrong audience, attribution is broken, and the no-heat caller who phoned at 9pm is invisible to your marketing reporting. AnyCRM closes that gap by running BOTH surfaces through a single conversion pipe.
1. Capture
A lead arrives either through your website form / online booking 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 business logic decides what happens next: which Campaign, which priority, which Membership pricing tier, which recall workflow, which dispatch escalation. 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 conversions flow through the same pipe with the same source taxonomy, your Google Ads bid strategy now optimises against real booked Jobs (not just form-fill noise), your Facebook Ads campaigns see the high-intent homeowner who picks up the phone, your analytics platform sees a single unified funnel, and attribution stops fragmenting between web and voice.
- Higher ROAS. Ad bidding optimises against actual booked Jobs and confirmed arrival windows, not against the noisy subset of leads that happen to fill a web form.
- Lower ad costs. Once Google Ads and Facebook Ads learn what a real HVAC / plumbing / electrical lead looks like, they stop spending against lookalikes of low-quality form-fills.
- Enriched analytics. Every conversation surface (web form, online booking, phone call, AI Receptionist chat) feeds the same event shape into your analytics, so funnels are complete instead of half-blind.
- Correct attribution. A homeowner who first saw a Google Ad, then visited the site, then phoned three days later when the AC quit gets attributed end-to-end. Voice traffic stops being invisible to your marketing stack.
- One source of truth for lead policy. Your CRM's flow owns Campaign tagging, Membership pricing, recall workflows, and priority routing. AnyCRM doesn't drift out of date because AnyCRM never tried to own that policy in the first place.
Most competitor AI Receptionists try to maintain rules for which Campaign to tag, when to create the Job, what priority to set, and which source value to apply. That approach breaks the moment your tenant adds a Business Unit or your marketing team launches a new Campaign, and it ignores the conversion-tracking surface entirely. AnyCRM inverts the responsibility. AnyCRM stays focused on the conversation (capture, dedup, trade-route, book, cancel) and delivers a clean lead event to the two destinations that matter: your CRM (for business logic) 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 trades, your Campaigns, your Membership tiers, and your 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 to contractors 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 for a shop spending $10k+/month on Google Ads.
For your developer: how this wires into ServiceTitan
The AI Receptionist asks AnyCRM for availability against the Technicians on your roster and gets back open arrival windows in the caller's timezone. No double bookings. Qualified-Technician-only. Every AnyCRM call dedups the Customer by phone then email, creates or links the Location, opens the Job of the correct Job Type on the right Business Unit, writes the Appointment with the assigned Technician, attributes the Job to the AI Receptionist Campaign you configured at setup, 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.
{
"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
}
{
"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" }
]
}
}]
}
{
"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": []
}
{
"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://..."
}
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 you run paid Ads on Google, Facebook, or LinkedIn for your shop, here is the uncomfortable truth: those platforms only get smarter when they see real conversions. Today, a website form-fill counts. A real phone call from a homeowner with a no-heat emergency at 7pm does NOT count. So Google bids harder on the audience that fills web forms (often the cheaper, lower-intent one) 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.
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 form-fills and online-booking submissions. That's why your Cost per Lead looks low but your dispatch board is light. The high-intent homeowner 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.
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, 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 homeowners closer to ready-to-book; and Customer Acquisition Cost shrinks because more of your Ad budget reaches buyers who will actually become booked Jobs.
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 forms and online booking through the same pipeline. So a lead from a Google Ad that filled a form on your website 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 Jobs actually came from.
- Cost per Lead drops. Because Google, Facebook, and LinkedIn stop wasting your Ad budget on lookalikes of low-intent form-fillers, and start finding the homeowner that picks up the phone.
- Return on Ad Spend (ROAS) goes up. Because the Ads now optimise toward conversations that actually close into booked Jobs, not toward whichever cheap audience generates the most form submissions.
- Customer Acquisition Cost (CAC) shrinks. Because a higher share of every Ad dollar reaches homeowners ready to schedule a truck.
- Analytics get a complete funnel. Web and voice leads sit side by side, with the same source taxonomy. You stop seeing "50% of revenue: unknown source" in your reporting.
- Attribution stops fragmenting. A homeowner who first clicked a Google Ad, then called the shop three days later, finally shows up correctly attributed. Today, that homeowner is invisible to your Ads stack.
- You finally know if Ads are working. Most contractors cannot honestly tell you whether their Google or Facebook spend is profitable. With AnyCRM's Conversion Lift, you can.
Imagine you spend $15,000/month on Google Ads for your HVAC shop. Today, you see 90 web form-fills and online-booking submissions and assume that's the full picture. With AnyCRM running, you'll also see (say) 140 phone calls and 70 web chats the AI Receptionist handled, all flowing into Google Ads as real conversions. Suddenly Google sees 300 conversions a month instead of 90. It re-trains on that bigger, better signal. Within weeks, the bidding finds you more of the right kind of homeowner: the one with a $12,000 system replacement, not the one comparison-shopping for a $79 tune-up. Same $15,000 spend, more booked Jobs at higher ticket, lower Cost per Lead, higher 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 ServiceTitan
Every Customer-create and Job-book fires through AnyCRM's Conversion Lift pipeline. The lead event lands inside your CRM for business logic, 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 forms and online-booking widget run through the same pipeline, so Web and Voice conversions feed the SAME training signal.
Owns the full Job + Appointment lifecycle inside ServiceTitan.
Every "can you push my Tuesday service to Thursday?" or "the part came in early, can the tech come tomorrow?" lands with the AI Receptionist instead of in dispatch's queue. AnyCRM reschedules update the Appointment in place. Cancellations follow ServiceTitan's own best practice. Cancel reason mapped, note written on the Customer AND on the Job's history, parent Job transitioned to the right state. Instead of deleting the Appointment and stranding the parent Job on the dispatch board, you get crystal clarity on when a ServiceTitan Job was created, and when and why it was updated by your AI Receptionist.
Finds the Appointment by phone in a single step without needing a Job number
Customers DO NOT quote Job numbers over the phone. We've tested with hundreds of callers and each time they were asked 'Can you tell me the job number from your booking confirmation?', 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 Appointment linked to the matching Customer (phone first, email fallback). And the AnyCRM response forces the AI Receptionist to be human. It reads back the Job Type, arrival window, and service address before changing anything.
Reschedules in place and keeps the Job open
Rescheduling moves the Appointment to a new arrival window on the same (or a re-resolved qualified) Technician, in one confirmation. The Job stays open, the Customer stays linked, the Membership stays attached. Failed reschedules leave the original Appointment untouched. So a botched reschedule never strands the homeowner.
Cancels without stranding the parent Job
When a caller cancels, AnyCRM patches the Appointment with the right Cancel Reason from your tenant's configured values, transitions the parent Job to the correct cancelled state so the dispatch board reflects it, and writes the caller's reason onto the Customer's notes AND on the Job's history. Instead of patching only the Appointment and leaving the Job stuck in Scheduled triggering recall workflows. This lets you intuitively track changes for ServiceTitan Jobs created or updated by your AI Receptionist.
For your developer: reschedule & cancel by email
AnyCRM's search, reschedule, and cancel all accept just a phone number. The soonest upcoming Appointment linked to the matching Customer is resolved inside AnyCRM. No Job numbers at the AI Receptionist layer.
{
"email": "jane@example.com"
}
{
"meetings": [{
"event_uuid": "a7c1f4e9-...",
"event_type_name": "Haircut Only | $50",
"start_time": "2026-05-15T11:00:00-04:00",
"status": "active"
}]
}
{
"email": "jane@example.com",
"scheduled_datetime": "2026-05-16T14:00:00",
"invitee_timezone": "America/New_York",
"reason": "Customer asked to move 1 day later"
}
{
"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"
}
{
"email": "jane@example.com",
"reason": "Customer is unwell"
}
{
"cancelled_event_uuid": "a7c1f4e9-...",
"status": "cancelled",
"reason": "Customer is unwell"
}
Routes every caller to the right trade, Business Unit, and qualified Technician. And maintains existing Customer ownership and Membership status instead of fragmenting the record.
ServiceTitan shops run on Business Units (HVAC, Plumbing, Electrical, Drain, sometimes per-location), Job Types, Technician skills and license categories, and zone-based dispatch. At setup AnyCRM imports your full ServiceTitan roster into its database and enriches each Technician with lane, expertise, languages, and a callable arrival-window calendar. The AI Receptionist then routes each caller to the trade, the Business Unit, and the Technician who actually handles that work. Existing Customer ownership and Membership status in ServiceTitan are honoured as the source of truth.
Routes by trade: HVAC vs Plumbing vs Electrical vs Drain
"My AC is blowing warm" routes to the HVAC Business Unit. "Water heater leaking" routes to Plumbing. "Half my outlets are dead" routes to Electrical. The AI Receptionist matches the symptom to the trade, then to the Business Unit your dispatch already uses. It doesn't cross-book a plumber on an HVAC call. And the existing Customer record is always preserved.
Honours Membership status and prior Customer history
If the caller is an existing ServiceTitan Customer with a Service Agreement or Membership, the AI Receptionist surfaces it on the Job, applies the member arrival-window priority your dispatch encodes, and keeps the Customer record intact. No duplicate Location, no lost Membership tier.
Books on Technicians qualified for the work
Technician skills (refrigerant certification, gas-line license, master electrician) are imported at setup. AnyCRM will not book a Job Type that requires a license the assigned Technician doesn't carry. Instead it falls back to the next qualified Technician on the board for that Business Unit and arrival window. 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 ServiceTitan at setup, enriched with lane, expertise, languages, license categories, and arrival-window preferences (valuable context for the AI Receptionist that ServiceTitan's user object doesn't carry by default). At runtime, one read of the team roster matches caller symptom → trade → Business Unit → Job Type → qualified Technician → arrival window. New Customers inherit the routed Technician's Business Unit. Existing Customers keep their Membership and Job history. AnyCRM does NOT cache your Campaigns, your pricebook, or your recall workflows. That policy stays inside your CRM, where it belongs.
{}
{
"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" }
]
}
{
"user_uuid": "3d2ed2c0-a8fc-45d7-9f67-fc3e6b898bb2"
}
{
"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 }
]
}
Setup in 3 steps. Battle-tested on real ServiceTitan shops.
You connect ServiceTitan once. AnyCRM imports your Business Units, Job Types, Technician roster, skills, zones, and arrival windows. AnyCRM also wires up the receiving end inside your CRM so lead events from the AI Receptionist land where your business logic can act on them. Then the AI Receptionist starts capturing calls and booking Jobs the same afternoon. No middleware. No prompt-engineering by you.
Connect ServiceTitan (Tenant ID + Integration App Key, 5 minutes)
AnyCRM is already registered as a ServiceTitan Integration on the Developer Portal. Every request the AI Receptionist makes carries AnyCRM's integration credentials alongside your tenant's OAuth bearer token, so ServiceTitan can see exactly which integration created which Job and which Appointment in the audit trail. From the Integrations page in your ServiceTitan account, install AnyCRM, grant the requested scopes (CRM, JPM, Dispatch read+write, plus read on settings), and copy the Tenant ID. Both the OAuth grant and the App Key are revocable from your ServiceTitan account at any time.
Import Business Units, Job Types, Technicians, skills & zones. Wire up your CRM's lead-receiving flow.
AnyCRM imports every Business Unit (with active flag and tax rules), every Job Type (with default duration, priority, and required skill set), every Technician (with Business Unit assignments, position, home zone, license categories), and your booking-provider arrival-window configuration. Membership tiers and Service Agreement types are read so the AI Receptionist can recognise them on returning callers. AnyCRM also freezes the Campaigns and Cancel Reasons so the AI Receptionist can only attribute and cancel with values that actually exist in your tenant. Inbound-call source attribution is locked (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 business logic can act on them. AnyCRM does NOT replicate your pricebook, your Campaign tagging rules, or your recall workflows. Your CRM decides what happens after a lead is captured. AnyCRM just delivers a clean event.
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 ServiceTitan tenant, same Business Units, same lead-event pipe into your CRM and your ad platforms) answers both voice and web. Live the same afternoon.
Why not just use ServiceTitan's Schedule Engine and online booking widget?
Schedule Engine and ServiceTitan's online booking are excellent at the steps AFTER a homeowner has chosen to come to your website to book. They expose your arrival windows, qualify the Job Type, and write into ServiceTitan natively. They don't pick up the phone. A call at 9pm with a no-heat emergency goes to a missed call, or an answering service that doesn't know your Business Units, your Job Types, your Membership tiers, or which Technicians are qualified for what. The AI Receptionist is the layer BEFORE all of that. It picks up the call, triages the symptom into the right trade and Job Type, surfaces Membership priority for returning callers, books the Appointment on a qualified Technician's board (through the same booking-provider surface Schedule Engine uses, with the same audit attribution and the same arrival-window rules), AND sends the same lead event straight into your CRM's downstream business logic plus your ad platforms server-side. So your ServiceTitan reporting, your analytics, and your Google / Facebook Ads bidding all start optimising on a real conversation, not a missed call.
For your developer: the enrichment layer (raw ServiceTitan 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 by phone then email, Customer + Location creation, Job Type resolution, Business Unit attribution, skill matching, arrival-window math, Campaign attribution, 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 lead
createOrUpdatesServicetitanContact accepts name, phone, email, service_address, customer_type, and the inferred Business Unit. AnyCRM queries existing Customers by phone then email, picks the surviving Customer (or creates a new one with the right values in the right order), normalises the service address and creates or reuses the Location, attaches the call summary as a Customer note, 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 Job
createServicetitanContactAppointment takes phone, service_address, symptom, scheduled_datetime (a naive date and time, no offset needed), and invitee_timezone. AnyCRM resolves the right Business Unit and Job Type from the symptom, resolves the right qualified Technician from the lane + skill match, picks a valid arrival window aligned to your booking-provider configuration, sets the AI Receptionist Campaign (locked at setup) so source attribution is preserved, creates the Job and Appointment in one server-side flow, 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 tenant times in the response.Cancelling with a reason
cancelServicetitanAppointment takes phone and reason. AnyCRM resolves the soonest upcoming Appointment, maps the caller's free-text reason to your tenant's configured Cancel Reason (locked at setup), writes the reason as a Customer note AND on the Job's history, patches the Appointment with the right Cancel Reason, and transitions the Job to the correct cancelled state. All in one AnyCRM call. No deletion, full audit trail, dispatch board reflects reality.Every AnyCRM tool for ServiceTitan follows the same AI-alignment contract, so the AI Receptionist never has to think about transport:
- Naive datetimes in, tenant-timezone-aligned shape out. The AI Receptionist passes
2026-05-15T11:00:00and a timezone string. AnyCRM aligns it to your tenant's booking-provider arrival windows and converts to the tenant's timezone. - Phone is the identity. Cancel and reschedule never need a Job number at the AI Receptionist layer. Phone and soonest-upcoming resolves inside AnyCRM.
- Job Type, Business Unit, Campaign, and Cancel Reason come from setup, not the LLM. The AI Receptionist can't invent a Job Type, tag a free-text Campaign, or cancel with a free-text reason. Every value is frozen against your tenant's configuration.
- Existing Customers and Memberships are sacred. If a Customer exists in ServiceTitan, AnyCRM updates the existing record and preserves Membership tier, Service Agreement, and prior Job history. New Customers are only created when no match exists.
- Skill-aware booking. AnyCRM refuses to assign a Job Type to a Technician whose skills don't cover the required license categories. Instead it falls back to the next qualified Technician on the board, never failing silently.
- Every lead event leaves AnyCRM in two places at once. Your CRM gets the lead event so your business logic can run. Your ad platforms get the server-side conversion event so bidding optimises against real conversations. 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 ServiceTitan 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 Appointment and Job are preserved. The homeowner never ends up with no service window.
Multi-trade setup. Business Units, Technician skills & system-prompt assembly
Most ServiceTitan shops run multiple Business Units (HVAC, Plumbing, Electrical, Drain) with their own Job Types, their own Technicians, and their own arrival-window rules. AnyCRM imports all of it once, links each Technician to the Business Units and Job Types they actually run, and bakes the result into the AI Receptionist's system prompt at setup time. Not at runtime. The AI Receptionist doesn't query your roster on every call. It already knows who runs what trade out of which depot.
- Roster import. AnyCRM imports your ServiceTitan Technicians once and writes each one into its database keyed by
crm_user_id(with name, role, Business Units, home zone, license categories, position). - Per-Technician Job Types & skills. For each Technician AnyCRM resolves the Job Types they're qualified for (intersection of Business Unit + skill set + license category) with default duration and priority. One call per person, cached.
- Trade visibility. Each Business Unit + Job Type combination is flagged Public, Private, or Ignored. The AI Receptionist only routes to and books on Public lanes. You toggle this in the AnyCRM dashboard without re-deploying (useful when a Business Unit is paused for staffing).
- 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 Campaign tagging policy, Membership-priority routing, and recall-workflow triggers live. AnyCRM doesn't try to own them.
- System-prompt assembly. The cached roster, Business Unit, Job Type, and Membership-tier 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 shop before it reads its own instructions.
- Runtime stays minimal. On a live call the AI Receptionist makes at most one availability call and one booking call. Never a roster lookup. Updates to Technicians, Business Units, Job Types, or skills re-run the cache. The AI Receptionist picks them up on its next deploy.
The end result: the AI Receptionist can match "my AC isn't blowing cold, it's 95 outside" → HVAC Business Unit → Service Call - No Cool Job Type → a refrigerant-certified Technician in the caller's home zone → the next valid arrival window on that Technician's board → a booked ServiceTitan Job + Appointment with the Customer's Membership tier surfaced → a lead event delivered straight into your CRM → a server-side conversion event in your ad platforms. Without a single roster query during the call.
Currently running for HVAC contractors, plumbing shops, electrical contractors, drain & sewer specialists, and multi-trade home-services franchises. Anyone whose dispatch board is in ServiceTitan but whose phone keeps ringing after the CSRs have logged off.
How most AI Receptionists built on Smith.ai, My AI Front Desk, or even ServiceTitan's own native AI Voice Agent fall short for HVAC, plumbing, electrical, and multi-trade home-services shops that use ServiceTitan. And why AnyCRM closes the gap.
Most AI Receptionists fall short on ServiceTitan in the same handful of ways. Third-party services (Smith.ai, My AI Front Desk) duplicate Customers, invent Job Types and Business Units, leak Campaign attribution, miss skill-aware Technician assignment, and run web/voice conversions on separate stacks. ServiceTitan's own native AI Voice Agent fixes most of the booking-side gaps natively — Adaptive Capacity, Membership Greetings, Job-Type Selection, dispatch-board awareness — but it only works on calls arriving through ServiceTitan's phone surface, treats conversion attribution as a ServiceTitan-internal concern (no server-side path to Google / Facebook / LinkedIn Ads), and keeps dispatch policy inside ServiceTitan's configuration surface rather than alongside your web-form flow. AnyCRM closes the remaining gaps. Each booking-side failure is solved one layer down inside AnyCRM, and the lead event flows through one unified pipe into your CRM AND your ad platforms server-side regardless of which phone surface the call came in on.
Duplicate Customers and orphaned Locations
Inventing Job Types, Business Units, and Cancel Reasons
Jobs with no source attribution (the Campaign trap)
Booking on a Technician without the right skill or license
Appointments that don't reach the right dispatch board
Cancellation that strands the Job on the dispatch board
Losing Membership status on returning callers
Encoding your dispatch policy in the prompt or in middleware
Web leads and AI Receptionist leads run on two separate conversion-tracking stacks
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 unified-conversion-tracking gap that even ServiceTitan's native Voice Agent doesn't close.
AnyCRM vs Smith.ai, My AI Front Desk, ServiceTitan's native AI Voice Agent on ServiceTitan
| Capability | AnyCRM | Smith.ai | My AI Front Desk | ServiceTitan AI Voice Agent |
|---|---|---|---|---|
| Live ServiceTitan Job + Appointment booked DURING the call | Yes. Native ServiceTitan Job + Appointment, Business-Unit-matched, on a qualified Technician's dispatch board. | Partial. Schedules through Scheduling Pro per their integration page; depth on Business Unit / Job Type intersection not exposed in published materials. | Partial. Zapier-style "Create Job" without Business-Unit/Job-Type intersection guard. | Yes. Native to ServiceTitan, books "straight to the dispatch board with real-time, unified knowledge of technician availability" per their product page. |
| Dedup-before-write on phone and email | Yes. Always, live during the call. | Yes, but after the call ends. Native integration does "match calls to existing customers" per their integration page — but the dedup state during the live AI Receptionist conversation is still stale. | No. Zapier action has no search step. | Yes (first-party tenant data access). |
| Preserves existing Customer + Membership on returning callers | Yes. Existing Customer and Membership tier are sacred. | Yes for Customer match. Whether member-rate pricing and member-priority arrival window flow through to the resulting Job isn't exposed in published materials. | No. Duplicate Customer orphans the Membership. | Yes. Ships "Membership Greetings" natively; product page confirms it recognises returning Customers and VIP Members. |
| Routes by trade and Business Unit (HVAC / Plumbing / Electrical / Drain) | Yes. Trade-to-Business-Unit-to-Job-Type chain is part of AnyCRM's roster. | Manual, depends on the receptionist. | No structural guard. | Yes via native dispatch-board access (Adaptive Capacity); specific trade-to-Business-Unit guards not exposed in published materials. |
| Job Types, Business Units, Campaigns, and Cancel Reasons frozen from your real tenant values | Yes. Read at setup, baked into the prompt as a frozen table. | Not API-enforced. | No. Writes can fail on unknown values. | Yes for Job Types and dispatch fees ("Job-Type Selection" + Custom Dispatch Fee Messaging in product); Campaign and Cancel Reason behaviour not exposed in published materials. |
| Skill-aware Technician assignment (refrigerant cert, gas-line license, master electrician) | Yes. License categories filtered before write. | Receptionist memory. | No. | Books with Adaptive Capacity by job type and required skill sets per product page; filtering by specific license categories (refrigerant cert, master electrician) not exposed in published materials. |
| Campaign attribution set on every Job (no "unknown source" leaks) | Yes. AI Receptionist Campaign locked at setup. | Native integration creates Customer records; Campaign attribution on the resulting Job not exposed in published materials. | No. Campaign field rarely set by Zapier action. | Writes its own attribution natively, but only for calls arriving through ServiceTitan's phone surface. |
| Cancellation preserves the audit trail and transitions the parent Job state | Yes. Appointment patched, Job transitioned, reason on Customer + Job history. | Logs a call summary as a Customer note; Cancel Reason + parent-Job state transition not exposed in published materials. | No. Patches Appointment only, Job stuck on dispatch board. | Reschedule yes (natively). Cancel-with-reason and parent-Job state transition treated as the CSR's job in the published product, not the Voice Agent's. |
| Reschedule in place (no cancel-then-rebook) | Yes. | Manual. | No. | Yes (native Reschedule Appointments capability). |
| Dispatch 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. | No. Hardcoded "Create Job" action. | Partial. Firm owns the rules and thresholds inside ServiceTitan's Voice Agent configuration, but that surface is separate from the flow handling your web-form / online-booking 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. Voice Agent attribution lives inside ServiceTitan reporting; web-form / online-booking attribution lives elsewhere. |
| Server-side conversion events sent to Google Ads, Facebook Ads, and analytics (origin = your registered domain) | Yes. Every call and chat booking lands server-side. | No. | No. | Not part of the Voice Agent product per published materials. Marketing Pro Ads handles ad-platform attribution separately; server-side conversion events for AI-booked Jobs aren't exposed. |
| 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 ServiceTitan source only for calls arriving through the Voice Agent surface. |
| Scale ceiling | Bounded by ServiceTitan API limits, not by staffing. | Bounded by human receptionist staffing for the human tier. | Bounded by Zapier rate limits and action contracts. | Bounded by ServiceTitan's Voice Agent capability surface and pricing tier. |
Your ServiceTitan data passes through AnyCRM. It doesn't stick.
AnyCRM processes your ServiceTitan 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. Customers, Locations, Jobs, Appointments, Memberships. All of it stays in ServiceTitan, owned by your tenant.
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 Customer records, no caller PII.
What AnyCRM doesn't
Caller names, phone numbers, service addresses, ServiceTitan Customer IDs, Job histories, Membership data, your Technician roster, your Business Unit revenue, your dispatch board. 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 ServiceTitan tenant and in whatever systems your CRM's flow forwards lead events to. Customers, Locations, Jobs, Appointments, notes, Memberships all live in ServiceTitan. Source-attributed (always AI Receptionist Call or AI Receptionist Web), attributed to AnyCRM in the integration audit log, revocable. AnyCRM does not build a shadow CRM alongside yours.
Revocation
Revoke the AnyCRM integration in your ServiceTitan account → Integrations page (or rotate the App Key on the Developer Portal) 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
ServiceTitan uses scoped OAuth plus a per-integration App Key. AnyCRM requests only the smallest set of scopes required for the booking lifecycle. Nothing for accounting, nothing for inventory, nothing for payroll.
- CRM Customers + Locations (read + write). Read and write Customers and service Locations, dedup against existing records by phone then email.
- JPM Jobs + Appointments (read + write). Read availability and write Jobs + Appointments on the routed-to Technician's board, plus reschedule and cancel.
- Dispatch Technicians (read). Read the Technician roster at setup time, including Business Unit assignments, position, home zone, and active flag.
- Settings (read). Read Business Units, Job Types, Cancel Reasons, Campaigns, and Membership Types at setup, so every value the AI Receptionist uses is frozen against your tenant's configuration.
- Not requested: accounting, inventory, payroll, pricebook prices, technician earnings, financing, marketing-spend data, your other integrations.
Same OAuth grant any ServiceTitan integration uses. Just a smaller surface. AnyCRM holds the OAuth bearer token and the integration App Key (every write is signed by AnyCRM's integration credentials, so each Job and Appointment change is attributable to AnyCRM in ServiceTitan's audit log). The LLM never sees the token, and every tool call is logged with the operation name, never the raw payload.
$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.
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.
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
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
Adds the first round of MCP tools so the AI Receptionist actually books appointments into your CRM (not just talks about booking them).
getAvailability+createContactAppointmentMCP tools- Live booking into your CRM
- Dedup-before-write on email and phone
- Still DIY — you wire the tools yourself with our videos
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
We build it for you. The whole stack: MCP tools wired, web forms unified into the same lead-event pipe, server-side conversion tracking into Google / Facebook / LinkedIn Ads, AND the lead-receiving flow inside your CRM tuned to your industry and your client configuration.
- Everything in Steps 1–3, done for you
- Unified conversion pipe (web + AI Receptionist)
- Server-side conversion tracking with your domain origin
- CRM-side lead-event flow we configure at onboarding
- One-time custom quote — no monthly subscription
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.
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.
Four steps. One afternoon.
No Zapier. No n8n. If you can copy and paste, you can do this.
Open the Quickstart
You get the prompt pack, the humaniser prompts, and the deployment guide.
Connect ServiceTitan
One API key. The agent reads contacts and writes appointments — both ways.
Pick your channel
Web chat, voice line, or both. Same backend, same brain.
Go live
Test five calls yourself. Send the number to your team. Done.
Live by tonight. Booking customers by tomorrow.
$36 once. If it doesn't work for your business, you've lost less than dinner.