An AI Receptionist that books, reschedules & cancels appointments — 24/7 — and writes them straight into
Salesforce.
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 — Salesforce integration.
Does this actually work with my Salesforce org?
Will it create duplicate Leads in Salesforce?
Can it route different leads to different team members?
Sforce-Auto-Assign: TRUE header so your Assignment Rules and Territory rules fire normally.Where do the meetings actually live, calendar or Salesforce?
Can it cancel or reschedule a meeting from a phone call?
What if a caller has two upcoming Events in Salesforce?
Does it handle our validation rules and restricted picklists?
Does it handle timezones correctly?
How is this different from Salesforce's own Agentforce?
Does it create Opportunities?
AI Receptionist Call or AI Receptionist Web). Your flow decides which Stage, which pipeline, which LeadSource, which Flow trigger. AnyCRM doesn't try to encode policy that will drift out of date the moment your business changes.How does the conversion tracking work?
What about my existing website forms? Do they go through the same pipe?
How long until it's actually capturing leads into Salesforce?
Captures the website inquiry or caller as the right Salesforce record, books the meeting if there's real intent, and feeds one unified conversion pipe for your website forms AND your AI Receptionist.
Every caller who lands on the line becomes the right Salesforce record (a Lead when they're net-new, a Task on the existing Contact when they're already on an Account, with the right OwnerId, LeadSource, and Account link). When they want a meeting, AnyCRM creates a native Salesforce Event on the matched team member'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 Salesforce business logic and your Google / Facebook / LinkedIn Ads both stay in sync.
Every caller becomes the right Salesforce record, not a stray missed call
The AI Receptionist captures first name, last name, email, phone, company, and call intent. Then AnyCRM writes the record into Salesforce as a Lead (with the right OwnerId, LeadSource, and RecordTypeId) for net-new callers, or as a Task on the existing Contact and any open Opportunity for returning ones. DURING the call.
Books meetings as native Salesforce Events
The meeting lands as a Salesforce Event with OwnerId set to the matched team member (so it lands on their calendar, not the integration user's), WhoId pointing at the Lead or Contact, and WhatId pointing at the related Account or Opportunity. Surfaces on the activity timeline of every related record, and syncs to the team member's Google or Outlook calendar through Lightning Sync or Einstein Activity Capture.
Sends the lead event straight to your CRM. You decide what happens next.
AnyCRM does not pretend to know your deal-creation rules. Every Lead-create and every Event-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. Convert the Lead, open the Opportunity, set the Stage, assign the Territory, route through a Flow. We set up the receiving end inside your Salesforce org for you during onboarding, tuned to your industry and your client 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 businesses run two completely separate conversion-tracking stacks: one for the website (Web-to-Lead forms, chatflows, 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 analytics double-count or miss real conversations entirely. AnyCRM closes that gap by running BOTH surfaces through a single conversion pipe.
1. Capture
A lead arrives either through your website form / chatflow 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 Salesforce org, into the receiving flow we wired up for you at onboarding. Your business logic decides what happens next: which Lead Queue, which Assignment Rule, which Opportunity, which Stage, which Flow. 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 revenue (not just form-fill noise), your Facebook Ads campaigns see the high-intent traffic that 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 conversations and booked Salesforce Events, not against the noisy subset of leads that happen to fill a Web-to-Lead form.
- Lower ad costs. Once Google Ads and Facebook Ads learn what a real lead looks like, they stop spending against lookalikes of low-quality form-fills.
- Enriched analytics. Every conversation surface (web form, web chat, phone call, AI Receptionist chat) feeds the same event shape into your analytics, so funnels are complete instead of half-blind.
- Correct attribution. A caller who first saw a Google Ad, then visited the site, then phoned three days later gets attributed end-to-end. Voice traffic stops being invisible to your marketing stack.
- One source of truth for lead policy. Your Salesforce flow owns Lead conversion, Opportunity creation, and Stage 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 when an Opportunity is created, what Stage it goes in, and which LeadSource to apply. That approach breaks the moment your business changes, 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 Salesforce org (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 Salesforce org AND the server-side conversion tracking at onboarding, matched to your specific industry, 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.
For your developer: how this wires into Salesforce
The AI Receptionist asks AnyCRM for availability against the people on your team and gets back open slots in the caller's timezone. No double bookings. Your busy time is always respected. Every AnyCRM call prevents duplicate records by running cross-object dedup across Lead and Contact, links to the existing Account, sets the OwnerId (matched from your team), sends the <code>Sforce-Auto-Assign: TRUE</code> header so your Assignment Rules and Territory rules fire, writes the Event so Lightning Sync / Einstein Activity Capture surfaces it on the team member's connected Google or Outlook calendar, 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, here is the uncomfortable truth: those platforms only get smarter when they see real conversions. Today, a Web-to-Lead form-fill counts. A real phone call from a high-intent buyer who picked up the phone at 7pm does NOT count. So Google bids harder on the audience that fills 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 Web-to-Lead form-fills. That's why your Cost per Lead looks low but your AEs complain the leads are weak. 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.
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 people closer to ready-to-buy; and Customer Acquisition Cost shrinks because more of your Ad budget reaches buyers who will actually convert into closed-won Opportunities.
The same pipe carries your website forms too. One source of truth across Ads, Salesforce, and Analytics.
AnyCRM doesn't just track AI Receptionist conversions. It also runs your existing Web-to-Lead forms and chatflows through the same pipeline. So a lead from a Google Ad that fills 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 Salesforce org stops being half-blind to where your leads 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 audience that picks up the phone.
- Return on Ad Spend (ROAS) goes up. Because the Ads now optimise toward conversations that actually close, not toward whichever cheap audience generates the most Web-to-Lead submissions.
- Customer Acquisition Cost (CAC) shrinks. Because a higher share of every Ad dollar reaches buyers ready to talk to a human (or in this case, your AI Receptionist).
- 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."
- Attribution stops fragmenting. A buyer who first clicked a Google Ad, then called the business three days later, finally shows up correctly attributed. Today, that buyer is invisible to your Ads stack.
- You finally know if Ads are working. Most businesses cannot honestly tell you whether their Google or Facebook spend is profitable. With AnyCRM's Conversion Lift, you can.
Imagine you spend $5,000/month on Google Ads. Today, you see 80 Web-to-Lead 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 buyer. Same $5,000 spend, more real conversations, 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 Salesforce
Every Lead-create and Event-book fires through AnyCRM's Conversion Lift pipeline. The lead event lands inside your Salesforce org 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 Web-to-Lead forms run through the same pipeline, so Web and Voice conversions feed the SAME training signal.
Manages the full Event and Task lifecycle inside Salesforce for anyone calling or chatting.
Every "push the demo to Thursday" or "actually, cancel that" lands with the AI Receptionist instead of in your email inbox. AnyCRM reschedules update the existing Salesforce Event in place. Cancellations follow Salesforce's own idiom. Outcome flagged, reason captured as a completed Task on the related record. Instead of DELETING the Event and erasing the activity timeline, you get crystal clarity on when a Salesforce Event was created, and when and why it was updated by your AI Receptionist.
Finds the meeting by email in a single step without needing a Salesforce record ID
Customers DO NOT quote Salesforce 18-character record IDs over the phone. We've tested with hundreds of callers and each time they were asked 'Can you tell me the meeting 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 Event associated to the matching Lead or Contact. And the AnyCRM response forces the AI Receptionist to be human. It reads back the Subject, date, time, and owning team member before changing anything.
Reschedules in place and keeps the Event data clean
Rescheduling updates the existing Event in a single confirmation. No cancel-then-rebook round-trip means the Event history, the WhoId/WhatId links to the Contact and Opportunity, and the calendar sync all stay intact. Failed reschedules leave the original Event untouched.
Cancels without erasing the audit trail
When a caller cancels, AnyCRM flags the Event cancelled the way Salesforce's own reporting expects (a completed Task with the reason on the related Lead, Contact, or Opportunity, plus the Event updated in place). No DELETE that would Recycle-Bin the record and strip WHY the meeting fell through. This lets you intuitively track changes for Salesforce Events 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 Salesforce Event linked to the matching Lead or Contact is resolved inside AnyCRM. No record IDs 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 team member. And maintains the existing OwnerId on the Lead, Contact, or Opportunity instead of randomly reassigning to someone else.
Salesforce orgs run on Users, Roles, Profiles, Queues, and Territories. At setup AnyCRM imports your active Salesforce User roster into its database and enriches each team member with lane, expertise, languages, timezone, and the meeting templates they actually book. The AI Receptionist then routes each caller to the team member who actually handles that lane. Existing OwnerId on Leads, Contacts, and Opportunities is honoured as the source of truth.
Routes by lane: AE vs SDR vs CS vs SE
"I'd like to talk to someone about pricing" routes to your AE pool. "I'm still evaluating" routes to an SDR for qualification. "I'm already a customer and have a question" routes to the CSM looking after the Account. And the existing OwnerId on the Contact or Opportunity is always preserved.
Honours existing OwnerId on Leads, Contacts, and Opportunities
If a Lead, Contact, or Opportunity already has an OwnerId, the AI Receptionist doesn't reassign. The Task, the Event, and any new related record attach under the existing Owner. No orphaned duplicate Lead, no Opportunity poached off a team member's forecast.
Matches fresh inbound callers and website chatters to the right person on the team
New leads with no existing Lead or Contact get assigned via the Lead Queue and Assignment Rule you've designated for that lane, honouring the criteria you set in AnyCRM for matching a lead to a team member. AnyCRM sends Sforce-Auto-Assign: TRUE on every Lead create so your Territory rules, Round-Robin Flows, and Einstein Lead Scoring kick in normally. 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 Salesforce at setup (every active User with their Profile, Role, Queue memberships, and timezone), enriched with lane, expertise, languages, timezone, and meeting-template duration (valuable context for the AI Receptionist that Salesforce doesn't provide by default). At runtime, one read of the team roster matches caller → lane → team member. New Leads get the matched team member as OwnerId (or drop into the right Queue). Existing records keep theirs. AnyCRM does NOT cache your Opportunity stages, your Lead conversion paths, or your Flows. That policy stays inside your Salesforce org, 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 Salesforce orgs.
You connect Salesforce once. AnyCRM imports your team, your LeadSource picklist, your Record Types, your Queues, and your meeting templates. AnyCRM also wires up the receiving end inside your Salesforce org so lead events from the AI Receptionist land where your business logic can act on them. Then the AI Receptionist starts capturing leads and booking meetings the same afternoon. No middleware. No prompt-engineering by you.
Connect Salesforce (Connected App OAuth, 60 seconds)
Authorize AnyCRM on your Salesforce org via the OAuth 2.0 Web Server flow against our Connected App. AnyCRM scopes to the least amount of access needed for the booking lifecycle (REST and SOQL on the standard objects, plus offline refresh). Nothing for analytics, marketing, billing, or forecast data. You can always revoke permissions at any time from Setup → Connected Apps OAuth Usage. Every update to your Salesforce org is signed with AnyCRM's Connected App credentials so it's easy to track what the AI Receptionist did when you audit in Login History and Setup Audit Trail.
Import the team. Lock in your picklists and Record Types. Wire up your CRM's lead-receiving flow.
AnyCRM imports every active Salesforce User as a bookable team member with lane, expertise, languages, timezone, and meeting-template duration. AnyCRM also freezes your LeadSource picklist values, your Record Type IDs per object, and your active Lead Queues so the AI Receptionist can only write values that actually exist in your org, 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 Salesforce org so the lead events from the AI Receptionist land where your business logic can act on them. AnyCRM does NOT replicate your Opportunity stages, your conversion Flows, or your Approval processes. Your Salesforce org 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 Salesforce org, same lead-event pipe into your CRM and your ad platforms) answers both voice and web. Live the same afternoon.
Why not just use Salesforce's Web-to-Lead + Salesforce Scheduler + Agentforce?
Web-to-Lead, Salesforce Scheduler, and Salesforce's own Agentforce (the AI agent platform formerly known as Einstein Copilot, with its SDR agent and Agentforce Voice) are excellent at the steps AFTER a prospect has chosen to come to you via your website, your authenticated portal, or your existing customer-service surface. They don't pick up your inbound business phone line. A new caller at 9pm gets a missed call, not a Lead. A Web-to-Lead submission sits in the Lead Queue until someone reads it. Agentforce is powerful, but it lives inside your Salesforce licensing footprint (Agentforce Sales tiers start at $175/user/month and climb steeply), it's tuned to the agent-building paradigm rather than the inbound-phone-receptionist paradigm, and the configuration work to make it answer the phone, capture the right Lead, and book on the right team member's calendar is substantial. The AI Receptionist is the layer BEFORE all of that. It picks up the call, asks the right qualifying questions, books the meeting as a native Salesforce Event on the right team member's calendar, writes a clean Lead (with the source set to AI Receptionist Call or AI Receptionist Web, the right RecordTypeId, your locked LeadSource, and a call summary as a Task), AND sends the same lead event straight into your CRM's downstream business logic plus your ad platforms server-side. So your Salesforce Flows, your analytics, and your Google / Facebook Ads bidding all start optimising on a real conversation, not a name and a missed call. Buyers who already run Agentforce: AnyCRM sits in front, captures the call cleanly, and hands the Lead off to Agentforce's downstream agents the way the rest of your stack expects.
For your developer: the enrichment layer (raw Salesforce API vs our MCP tools)
Every tool the AI Receptionist calls is an opinionated wrapper inside AnyCRM. AnyCRM does the messy work for you. Cross-object dedup across Lead and Contact, Account linking, picklist validation against your Record Type, polymorphic WhoId/WhatId pairing, ActivityDateTime UTC math, validation-rule survival, error normalisation, lead-event delivery into your Salesforce org, 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 Salesforce internals.
Capturing a new lead
Sforce-Auto-Assign: TRUE header (it's off by default, so naive integrations create Leads that sit unassigned in the integration user's personal queue forever). And nothing in raw Salesforce fires a server-side conversion event to your ad platforms, so call-driven and chat-driven leads never get optimised for.createOrUpdatesSalesforceContact accepts name, email, phone, note, company, lead_intent, plus the matched team member. AnyCRM runs the cross-object dedup across Lead and Contact, picks the surviving record (or creates a new Lead with the right Record Type, your locked LeadSource, and required fields populated from setup defaults), always sends Sforce-Auto-Assign: TRUE so your Assignment Rules fire, parses validation-rule errors into human-readable messages, attaches the call note as a Task on the resulting record, 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 meeting
createSalesforceContactAppointment takes email, scheduled_datetime (a naive date and time, no offset needed), invitee_timezone, and meeting_template_key. AnyCRM resolves the right team member from the lane, handles the timezone and duration math, builds the polymorphic WhoId/WhatId pair correctly (Lead with no WhatId, or Contact with the Account in WhatId, or Contact with the open Opportunity in WhatId), sets OwnerId to the routed team member so the Event lands on their calendar (not the integration user's), sends the 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
cancelSalesforceAppointment takes email and reason. AnyCRM resolves the soonest upcoming Event, writes a completed Task with the reason as Description on the related Lead, Contact, or Opportunity, and updates the Event in place with the reason on a CancellationReason field (or a [CANCELLED] Subject prefix if the custom field isn't deployed). All in one AnyCRM call. No DELETE, full audit trail, the Event stays on the activity timeline and in the team member's Activity reporting.Every AnyCRM tool for Salesforce follows the same AI-alignment contract, so the AI Receptionist never has to think about transport:
- Naive datetimes in, Salesforce-native shape out. The AI Receptionist passes
2026-05-15T11:00:00and a timezone string. AnyCRM converts to UTC ActivityDateTime and splits DurationInMinutes from the meeting template. - Email is the identity. Cancel and reschedule never need a Salesforce 18-character ID at the AI Receptionist layer. Email and soonest-upcoming resolves inside AnyCRM across Lead and Contact.
- LeadSource, Record Type, Stage, and meeting template come from setup, not the LLM. The AI Receptionist can't invent free-text values that violate your restricted picklists or validation rules. Every value is inherited from the setup-time freeze.
- Existing OwnerId is sacred. Lead, Contact, and Opportunity OwnerId is preserved on every write. New Leads only get the matched team member (or drop into the right Queue) when no Owner exists.
- Cancellation preserves the audit trail. Salesforce's idiom for completed-but-cancelled meetings is honoured so reporting stays accurate, the activity timeline keeps the entry, and the Recycle Bin doesn't swallow the audit trail.
- Assignment Rules fire on every Lead create. AnyCRM always sends
Sforce-Auto-Assign: TRUEso your Territory, Round-Robin, and Einstein Lead Scoring rules kick in. Leads don't get orphaned in the integration user's personal queue. - 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. A field-custom-validation error from Salesforce 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 Salesforce Event is preserved. The customer never ends up with nothing.
Multi-team-member setup. Team roster, lanes & system-prompt assembly
If you run more than one team member on Salesforce, AnyCRM imports the team roster once, you link each team member to the lanes they actually cover (AE / SDR / CSM / SE / Partner), 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.
- Team roster import. AnyCRM imports your active Salesforce Users once and writes each one into its database keyed by
crm_user_id(with name, role, lane, timezone, Profile, and Queue memberships). - Per-team-member meeting templates. For each team member AnyCRM resolves the default Record Type per object, the meeting templates they actually book (discovery, demo, technical, executive), and the duration per template. One call per person, cached.
- Lane visibility. Each lane 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.
- Lead-event receiving flow inside your CRM. During onboarding we wire up the flow inside your Salesforce org that receives lead events from AnyCRM. That's where your Lead-conversion and Opportunity-creation policy lives. AnyCRM doesn't try to own it.
- System-prompt assembly. The cached team roster, lane, picklist, and meeting-template 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 team 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 team roster lookup or a picklist describe. Updates to team members, lanes, or templates re-run the cache. The AI Receptionist picks them up on its next deploy.
The end result: the AI Receptionist can match "I'd like to demo the platform with someone on the sales team" → the AE pool → that team member's Demo meeting template → that team member's calendar availability → a booked Salesforce Event on the right team member's calendar with the Lead in WhoId and the Account in WhatId → a lead event delivered straight into your Salesforce org → a server-side conversion event in your ad platforms. Without a single team roster query during the call.
Currently running for B2B SaaS revenue teams, financial-services advisors, manufacturing sales orgs, and professional-services partners. Anyone whose pipeline is in Salesforce but whose phone keeps ringing after the AE has logged off.
How most AI Receptionists built on Smith.ai, My AI Front Desk, or Goodcall fail for B2B SaaS revenue teams, financial-services advisors, manufacturing sales orgs, and professional-services partners that use Salesforce. And why AnyCRM can't.
Most AI Receptionists fail on Salesforce in the same handful of ways. Duplicate Leads when the caller is already a Contact, Leads orphaned in the integration user's personal queue, invented LeadSource and Record Type values that fail validation, Events on the wrong calendar, wrong polymorphic WhoId/WhatId pairing, destructive DELETEs that erase the activity timeline, hardcoded Opportunity-Stage 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 Lead-conversion and Opportunity-creation 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 Leads when the caller is already a Contact
Leads stuck in the integration user's personal queue
Sforce-Auto-Assign: TRUE header. My AI Front Desk's Zapier-style "Create Lead" action and Zapier surfaces generally don't set this header. Goodcall writes through a connector that applies whatever default behaviour the underlying integration shipped with. Smith.ai pushes Leads in without published documentation that the header is set. So captured Leads sit in the integration user's personal queue, invisible to your actual sales team, with no Lead Score, no Territory assignment, and no AE notification.Sforce-Auto-Assign: TRUE on Lead creates. Your Assignment Rules, Lead Queues, Territory rules, and Einstein Lead Scoring all fire automatically. The captured Lead lands in the right Queue, on the right team member, with the right score, the way a Web-to-Lead submission would. Two steps (set the header, write the Lead) where Smith.ai/My AI Front Desk/Goodcall do one.Inventing LeadSource and Record Type values that don't exist in your org
Events on the wrong calendar (the integration user's)
Wrong WhoId / WhatId polymorphic pairing
Cancelling by DELETE instead of by completed Task + Event update
[CANCELLED] Subject prefix if the custom field isn't deployed). The Event stays on the timeline, queryable in Activity reporting, with the reason attached. Three operations where Smith.ai/My AI Front Desk/Goodcall do one (and usually the wrong one).Encoding your deal-creation 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 Salesforce org, while quietly fixing the conversion-tracking gap nobody else has thought to close.
AnyCRM vs Smith.ai, My AI Front Desk, Goodcall on Salesforce
| Capability | AnyCRM | Smith.ai | My AI Front Desk | Goodcall |
|---|---|---|---|---|
| Live Salesforce Event booked DURING the call | Yes. Native Salesforce Event, team-member-matched OwnerId, calendar-synced via Lightning Sync / Einstein Activity Capture. | No. Task logged for manual follow-up. | Partial. "Create Event" connector action without OwnerId-as-routed-team-member or polymorphic-pair validation. | Partial. Scheduler hop, not a structured native Salesforce Event. |
| Cross-object dedup-before-write across Lead AND Contact on email and phone | Yes. Always. | Manual. | No. Dedups against one chosen object, not cross-object. | No published guarantee. |
| Preserves existing OwnerId on Leads, Contacts, and Opportunities for returning callers | Yes. Existing OwnerId is sacred. | Implicit, not guaranteed. | No. Can overwrite. | Depends on the underlying connector's defaults. |
| Routes by lane (AE / SDR / CSM / SE) | Yes. Lane is part of AnyCRM's team roster. | Manual, depends on the receptionist. | No. | No. |
| LeadSource, Record Type & meeting templates frozen from your real org values | Yes. Read at setup, baked into the prompt as a frozen table. | Not API-enforced. | No. Writes can fail on unknown values (FIELD_CUSTOM_VALIDATION_EXCEPTION). | No structural guard. |
Assignment Rules fire on every Lead create (Sforce-Auto-Assign: TRUE) |
Yes. Always set. | Not documented. | No. Zapier surfaces don't set it. | Not documented. |
| Cancellation preserves the audit trail (completed Task + Event update, not DELETE) | Yes. Salesforce-native cancellation. | Manual. | No. DELETE strips the timeline. | No. Cancellation happens in the scheduler, not the Event. |
| Reschedule in place (no cancel-then-rebook) | Yes. | Manual. | No. | No. |
| Lead-conversion / Opportunity-creation policy delegated to YOUR Salesforce flow | Yes. Lead event delivered straight into your CRM, into the receiving flow we wire up at onboarding. | No. Policy lives in Zapier or in the receptionist's training. | No. Hardcoded "Create Lead" / "Change Opportunity Stage" actions. | No. Connector-default behaviour. |
| 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. Web and voice run on separate stacks. |
| Server-side conversion events to Google Ads, Facebook Ads, and analytics (origin = your registered domain) | Yes. Every call and chat lead lands server-side. | No. | No. | No. |
| Source attribution stays consistent across web and voice | Yes. AI Receptionist Call, AI Receptionist Web, plus your Web-to-Lead form identifiers. | Manual / inconsistent. | No standardised taxonomy. | Whatever the underlying connector defaults to. |
| Scale ceiling | Bounded by Salesforce API limits, not by staffing. | Bounded by human receptionist staffing. | Bounded by Zapier rate limits and action contracts. | Bounded by the scheduler-and-sync hop. |
Your Salesforce data passes through AnyCRM. It doesn't stick.
AnyCRM processes your Salesforce 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. Leads, Contacts, Accounts, Opportunities, Events, Tasks. All of it stays in Salesforce, owned by your Salesforce org.
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 record data, no caller PII.
What AnyCRM doesn't
Caller names, emails, phone numbers, Salesforce 18-character IDs, your team roster, your picklists, your Record Types, your Opportunity stages, your forecast 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 Salesforce org and in whatever systems your CRM's flow forwards lead events to. Leads, Contacts, Accounts, Opportunities, Events, Tasks all live in Salesforce. Source-attributed (always AI Receptionist Call or AI Receptionist Web), attributable to AnyCRM's Connected App in Login History and Setup Audit Trail, revocable. AnyCRM does not build a shadow CRM alongside yours.
Revocation
Revoke the AnyCRM Connected App in Setup → Connected Apps OAuth Usage 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
Salesforce uses OAuth 2.0 scopes on a Connected App. AnyCRM requests only the smallest set required for the contact + meeting capture lifecycle. Nothing for analytics, nothing for marketing, nothing for billing, nothing for forecast or quote data.
api(REST + SOQL). Read and write on Lead, Contact, Account, Opportunity, Event, Task, User. The lead-capture and booking work.refresh_token,offline_access. So the AI Receptionist can refresh its access token without re-prompting your admin every two hours.- Read-only on User, Profile, UserRole, Group, GroupMember. The SOQL the setup workflow runs once to hydrate the team roster. No write access to User records.
- Read on Account and Opportunity. So an inbound call from a Contact in an open Opportunity is attached to the right WhatId, not orphaned on the Account.
- Not requested: Forecast, Quote, Order, Product2, PricebookEntry, AccountTeamMember, OpportunityLineItem, billing or subscription objects, custom finance objects, your other Connected Apps.
Same OAuth grant any Salesforce AppExchange app uses. Just a smaller surface. AnyCRM holds the access and refresh tokens (every write is signed by AnyCRM's Connected App credentials, so each Event and Lead change is attributable to AnyCRM in your org's Login History and Setup Audit Trail). 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 Salesforce
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.