An AI Receptionist that books, reschedules & cancels appointments — 24/7 — and writes them straight into
Follow Up Boss.
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 — Follow Up Boss integration.
Does this actually work with my Follow Up Boss account?
How is this different from Follow Up Boss's own AI features?
Will it create duplicate people in Follow Up Boss?
Can it route different inquiries to different agents on my team?
Where do the showings actually live, calendar or Follow Up Boss?
Can it cancel or reschedule a showing from a phone call?
What if a caller has two upcoming showings in Follow Up Boss?
Does it handle timezones correctly?
Does it create Deals in Follow Up Boss?
AI Receptionist Call or AI Receptionist Web). Your flow decides which stage, which action plan, which Smart List, which Pond. 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 Follow Up Boss?
Captures the website inquiry or caller as a Follow Up Boss person, books the showing 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 a Follow Up Boss person (with the right source, stage, assigned agent, and first note). When they want a showing, AnyCRM creates a Follow Up Boss appointment on the matched agent'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 CRM business logic and your Google / Facebook / LinkedIn Ads both stay in sync.
Every caller becomes a Follow Up Boss person, not a stray missed call
The AI Receptionist captures first name, last name, email, phone, the listing they asked about, and buying/selling intent. Then AnyCRM writes the record into Follow Up Boss with the right agent owner, source, and stage attached DURING the call.
Books showings as native Follow Up Boss appointments
The showing lands as a Follow Up Boss appointment with the matched agent as the user-invitee, the person associated, and a duration that matches your configured appointment type. So it shows on the person's timeline and the agent's Gmail/Outlook calendar exactly the way Follow Up Boss expects.
Sends the lead event straight to your CRM. You decide what happens next.
AnyCRM does not pretend to know your deal-creation rules. Every person-create and every showing-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. Drop into a Smart List, fire the action plan, assign to the Pond Lead Agent, route the workflow. We set up the receiving end inside your CRM for you during onboarding, tuned to your team's lanes and listing config. AnyCRM doesn't get in the way of policy you've already encoded in Follow Up Boss.
One conversion pipe for your website forms AND your AI Receptionist.
Most real estate teams run two completely separate conversion-tracking stacks: one for the website (IDX 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 IDX form / website 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 CRM, into the receiving flow we wired up for you at onboarding. Your Follow Up Boss logic decides what happens next: which stage, which action plan, which Pond, which Smart List, which agent. 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 bookings (not just form-fill noise), your Facebook Ads campaigns see the high-intent traffic that picks up the phone for a showing, 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 showings, not against the noisy subset of leads that happen to fill an IDX 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 Zillow form-fills.
- Enriched analytics. Every conversation surface (IDX 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 listing page, 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 Follow Up Boss flow owns stage routing, action-plan firing, and Pond assignment. 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 a person is created, what stage they land at, and which source tag 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 CRM (for action plans and Pond routing) 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 Follow Up Boss AND the server-side conversion tracking at onboarding, matched to your specific market, 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 Follow Up Boss
The AI Receptionist asks AnyCRM for availability against the agents on your roster and gets back open slots in the caller's timezone. No double bookings. Every AnyCRM call prevents duplicate people, sets the right agent owner (matched from your team), writes the appointment so Follow Up Boss's calendar sync to Google/Outlook fires automatically, and sends the lead event straight into your CRM tagged with <code>AI Receptionist Call</code> or <code>AI Receptionist Web</code>. The same lead also feeds the AnyCRM Conversion Lift pipeline (covered in the next capability) so your Google, Facebook, and LinkedIn Ads start optimising against the call and chat leads that actually pick up the phone.
{
"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 Zillow form-fill counts. A real phone call from a high-intent buyer who picked up the phone at 7pm asking about 14 Maple Street 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 IDX form-fills. That's why your Cost per Lead looks low but your agents 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 closings.
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 IDX forms and chatflows through the same pipeline. So a lead from a Google Ad that fills a form on your listing page AND a lead from a Facebook Ad that called the AI Receptionist three days later both end up tagged, attributed, and counted in exactly the same way. Your Ads platform stops double-counting, your analytics stop fragmenting, and your CRM stops being half-blind to where your leads actually came from.
- 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 to ask about a listing.
- Return on Ad Spend (ROAS) goes up. Because the Ads now optimise toward conversations that actually book a showing, not toward whichever cheap audience generates the most form 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 on a listing, then called the brokerage 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 brokerages cannot honestly tell you whether their Zillow or Google spend is profitable. With AnyCRM's Conversion Lift, you can.
Imagine you spend $5,000/month on Google Ads for your listings. Today, you see 80 IDX 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 showings booked, 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 Follow Up Boss
Every person-create and showing-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 run through the same pipeline, so Web and Voice conversions feed the SAME training signal.
Manages the full showing lifecycle inside Follow Up Boss for anyone calling or chatting.
Every "can we push the Tuesday viewing?" or "actually, cancel that" lands with the AI Receptionist instead of in your inbox. AnyCRM reschedules update the existing Follow Up Boss appointment in place. Cancellations preserve the audit trail. Reason recorded on the person's timeline, outcome flagged on the appointment. Instead of deleting the appointment and erasing the trail, you get crystal clarity on when a Follow Up Boss appointment was created, and when and why it was updated by your AI Receptionist.
Finds the showing by email in a single step without needing an appointment ID
Customers DO NOT quote appointment IDs over the phone. We've tested with hundreds of callers and each time they were asked 'Can you tell me the appointment id from your email?', the response was the same: 'Why can't you find it yourself?'. AnyCRM gives the AI Receptionist an easy way to find the soonest upcoming appointment associated to the matching person. And the AnyCRM response forces the AI Receptionist to be human. It reads back the title, date, time, and listing before changing anything.
Reschedules in place and keeps the appointment data clean
Rescheduling updates the existing appointment in a single confirmation. No cancel-then-rebook round-trip means the appointment history, person association, and calendar invite all stay intact. Failed reschedules leave the original appointment untouched.
Cancels without erasing the audit trail
When a caller cancels, AnyCRM writes the caller's reason onto the person's timeline as a note and flags the appointment with a cancellation outcome BEFORE the cancellation completes. Instead of just deleting the appointment and stripping WHY it fell through. This lets you intuitively track changes for Follow Up Boss appointments 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 appointment associated to the matching person is resolved inside AnyCRM. No appointment 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 agent. And maintains the existing agent looking after the lead instead of randomly reassigning to someone else.
Follow Up Boss accounts run on users, teams, and Ponds. At setup AnyCRM imports your Follow Up Boss roster into its database and enriches each agent with lane, expertise, languages, timezone, and bookable appointment-type duration. The AI Receptionist then routes each caller to the agent who actually handles that lane. Existing person assignments in Follow Up Boss are honoured as the source of truth.
Routes by lane: listing vs buyer's vs ISA vs repeat client
"I want to list my house" routes to your listing-side agents. "I saw 14 Maple Street on Zillow" routes to that listing's agent. "I'm already working with Sarah" routes back to Sarah. And the existing agent on the person is always preserved.
Honours existing assigned agents in Follow Up Boss
If a person already has an assigned agent in Follow Up Boss, the AI Receptionist doesn't reassign them. The appointment and the note attach to the existing person under the existing agent. No orphaned duplicate, no lead poached off an agent's pipeline.
Matches fresh inbound callers and website chatters to the right person on the team
New leads with no existing Follow Up Boss person get matched to an agent on the lane you've designated (listing / buyer's / ISA), honouring the criteria you set in AnyCRM for matching a lead to an agent. New leads with no existing owner are released to the right Pond and inherit the Pond Lead Agent. 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 Follow Up Boss at setup, enriched with lane, expertise, languages, timezone, and appointment-type duration (valuable context for the AI Receptionist that Follow Up Boss's user object doesn't carry by default). At runtime, one read of the team roster matches caller → lane → agent. New persons get assigned to the right agent or released to the right Pond. Existing persons keep theirs. AnyCRM does NOT cache your stages, your action plans, or your Smart Lists. 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 Follow Up Boss accounts.
You connect Follow Up Boss once. AnyCRM imports your roster, your sources, and your stages. 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 leads and booking showings the same afternoon. No middleware. No prompt-engineering by you.
Connect Follow Up Boss (API key + system registration, 60 seconds)
Generate a Follow Up Boss API key (Admin → API) and paste it in. AnyCRM is registered as an integrating system with Follow Up Boss, so every request the AI Receptionist makes carries auditable system-attribution headers. Follow Up Boss can see exactly which system created which person and which appointment. Both your API key and the system registration are revocable from your Follow Up Boss account at any time.
Import the roster. Lock in your sources and stages. Wire up your CRM's lead-receiving flow.
AnyCRM imports every active Follow Up Boss user as a bookable agent with lane, expertise, languages, timezone, and appointment-type duration. AnyCRM also reads your existing Source list (e.g. AI Receptionist), freezes the stage new leads enter at, and locks inbound-call source attribution (always AI Receptionist Call or AI Receptionist Web) so reporting stays consistent. During onboarding we set up the receiving flow inside your CRM so the lead events from the AI Receptionist land where your business logic can act on them. AnyCRM does NOT replicate your stages, action plans, or Smart Lists. 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 Follow Up Boss account, same lead-event pipe into your CRM and your ad platforms) answers both voice and web. Live the same afternoon.
Why not just use Follow Up Boss's Lead Flow + native action plans + Follow Up Boss AI?
Follow Up Boss's Lead Flow, action plans, Smart Lists, and the newer Follow Up Boss AI features (smart summaries, suggested tasks, smart messages) are excellent at the steps AFTER a lead exists in Follow Up Boss. Follow Up Boss AI itself is positioned as an assistant for your human agents (it learns from your conversations, suggests replies, summarises calls), not as a phone-answering front line. A new caller at 9pm still gets a missed call, not a person record. An inbound IDX inquiry still sits in the queue until someone reads it. The AI Receptionist is the layer BEFORE all of that. It picks up the call, asks the right qualifying questions, books the showing as a native Follow Up Boss appointment on the right agent's calendar, writes a clean person (with the source set to AI Receptionist Call or AI Receptionist Web, the right stage, and a call summary as the first note), AND sends the same lead event straight into your CRM's downstream Lead Flow plus your ad platforms server-side. So your Follow Up Boss action plans, Follow Up Boss AI's smart-summary learnings, your analytics, and your Google / Facebook Ads bidding all start optimising on a real conversation, not a name and a voicemail.
For your developer: the enrichment layer (raw Follow Up Boss 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, source registration, owner assignment, stage mapping, appointment-type resolution, timezone math, dual-invitee assembly, 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
createOrUpdatesFollowupbossContact accepts name, email, phone, note, source, tag, plus an inferred event type. AnyCRM routes through the action-plan-firing Event path (never the raw People create), picks the right action-plan-triggering type from the call intent, locks the source to the one you configured at setup, dedups against existing persons by email then phone, preserves the existing assigned agent if there is one, appends the note to the timeline, 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 showing
createFollowupbossContactAppointment takes email, scheduled_datetime (a naive date and time, no offset needed), invitee_timezone, and appointment_type_uuid. AnyCRM resolves the right agent from the lane and listing, builds the dual-invitee payload (person + Follow Up Boss user, so calendar sync to Gmail/Outlook fires), computes end-time from the appointment-type duration, handles the timezone math, attributes the creator correctly, sends the same lead event straight into your CRM with the booking context, fires the server-side conversion event into your ad platforms, and returns both local and UTC start times in the response.Cancelling with a reason
cancelFollowupbossAppointment takes email and reason. AnyCRM resolves the soonest upcoming appointment, writes the reason onto the person's timeline BEFORE the cancellation fires, applies a cancellation outcome for reporting, then cancels. All in one AnyCRM call. Full audit trail, the appointment stays queryable in reporting under the right outcome.Every AnyCRM tool for Follow Up Boss follows the same AI-alignment contract, so the AI Receptionist never has to think about transport:
- Naive datetimes in, Follow Up Boss-native shape out. The AI Receptionist passes
2026-05-15T11:00:00and a timezone string. AnyCRM converts it into whatever shape the Follow Up Boss appointment requires, on both start and end. - Email is the identity. Cancel and reschedule never need an appointment ID at the AI Receptionist layer. Email and soonest-upcoming resolves inside AnyCRM.
- Source and stage come from setup, not the LLM. The AI Receptionist can't invent a source or a stage. It inherits the values you configured at setup.
- Existing assigned agents are sacred. If a Follow Up Boss person already has an agent, AnyCRM preserves it. New persons only get the matched agent (or Pond) when no owner exists.
- Cancellation preserves the audit trail. The reason lands on the person's timeline and the cancellation outcome lands on the appointment, so reporting still counts the showing under the right outcome.
- 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 Follow Up Boss 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 Follow Up Boss appointment is preserved. The customer never ends up with nothing.
Multi-agent setup. Team roster, lanes & system-prompt assembly
If you run more than one agent on Follow Up Boss, AnyCRM imports the roster once, you link each agent to the lanes they actually cover (listing / buyer's / ISA / repeat-client desk), 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 roster on every call. It already knows who handles what.
- Team roster import. AnyCRM imports your Follow Up Boss users once and writes each one into its database keyed by
crm_user_id(with name, role, lane, timezone, Pond membership). - Per-agent appointment types. For each agent AnyCRM resolves the appointment types they actually book and the duration per type. 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 CRM that receives lead events from AnyCRM. That's where your action-plan and stage-routing policy lives. AnyCRM doesn't try to own it.
- System-prompt assembly. The cached team roster, lane, and appointment-type 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. Updates to agents, lanes, or appointment types re-run the cache. The AI Receptionist picks them up on its next deploy.
The end result: the AI Receptionist can match "I saw 14 Maple Street on Zillow" → the listing's owning agent → that agent's showing appointment type → that agent's calendar availability → a booked Follow Up Boss appointment on the right agent's calendar → a lead event delivered straight into your CRM → a server-side conversion event in your ad platforms. Without a single team roster query during the call.
Currently running for residential brokerages, listing teams, buyer's-agent pools, ISA teams, and solo agents. Anyone whose pipeline is in Follow Up Boss but whose phone keeps ringing after the agent has logged off.
How most AI Receptionists built on Smith.ai, My AI Front Desk, or Goodcall fail for residential brokerages, listing teams, buyer's-agent pools, ISA teams, and solo agents that use Follow Up Boss. And why AnyCRM can't.
Most AI Receptionists fail on Follow Up Boss in the same handful of ways. Duplicate people, the wrong capture endpoint so action plans never fire, appointments that never sync to the agent's real calendar, invented sources and stages, the wrong agent's calendar, deletions that destroy the audit trail, hardcoded 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 stage and action-plan 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 person records
Capturing leads through the wrong endpoint so action plans never fire
Appointments that don't reach the agent's real calendar
Inventing sources and stages that don't exist in your account
source trap can't fire because the source isn't a variable — it's a constant. This is two API calls at setup time that Smith.ai, My AI Front Desk, and Goodcall don't make, and it's the difference between writes that always succeed and writes that silently rot your reporting.Booking the wrong agent's calendar
Cancelling by deletion instead of by outcome
Encoding your stage and action-plan 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 conversion-tracking gap nobody else has thought to close.
AnyCRM vs Smith.ai, My AI Front Desk, Goodcall on Follow Up Boss
| Capability | AnyCRM | Smith.ai | My AI Front Desk | Goodcall |
|---|---|---|---|---|
| Live Follow Up Boss appointment booked DURING the call | Yes. Native Follow Up Boss appointment, agent-matched, calendar-synced via dual-invitee. | No. Human receptionists book manually after the call; AI tier logs a note for follow-up. | Partial. Zapier-style "Schedule Appointment" without the dual-invitee structural detail for calendar sync. | Partial. Zapier hop, not a structurally-correct Follow Up Boss appointment. |
| Dedup-before-write on email and phone | Yes. Always. | Manual. | No. Zapier "Add Lead" is exact-match only. | No. Single-step Zapier create. |
| Preserves existing Follow Up Boss agent on returning callers | Yes. Existing assigned agent is sacred. | Implicit, not guaranteed. | No. "Assign Lead to Agent" can overwrite. | Depends on the Zapier connector's defaults. |
| Routes by lane (listing / buyer's / ISA) | Yes. Lane is part of AnyCRM's team roster, with listing-aware matching. | Manual, depends on the receptionist. | No. | No. |
| Sources, stages & listings frozen from your real Follow Up Boss values | Yes. Read at setup, baked into the prompt as a frozen table. | Not API-enforced. | No. Writes can fail or create dirty source values. | No structural guard. |
| Cancellation preserves the audit trail (outcome-flagged, not deleted) | Yes. Reason on timeline + cancellation outcome on appointment. | Manual. | No. Deletion strips the timeline. | No. Single-step Zapier delete. |
| Reschedule in place (no cancel-then-rebook) | Yes. | Manual. | No. | No. |
| Action-plan and stage policy delegated to YOUR Lead 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 "Update Lead Status" Zapier action. | No. Zapier 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 sent 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 IDX form identifiers. | Manual / inconsistent. | No standardised taxonomy. | Whatever the Zapier connector defaults to. |
| Scale ceiling | Bounded by Follow Up Boss API limits, not by staffing. | Bounded by human receptionist staffing. | Bounded by Zapier rate limits and action contracts. | Bounded by the Zapier hop. |
Your Follow Up Boss data passes through AnyCRM. It doesn't stick.
AnyCRM processes your Follow Up Boss 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. Person records, notes, sources, stages, assignments. All of it stays in Follow Up Boss, owned by your Follow Up Boss account.
What AnyCRM stores
Conversation history IDs only. So the AI Receptionist can pick up where it left off if a caller hangs up and rings back. No call audio, no transcripts of person records, no caller PII.
What AnyCRM doesn't
Caller names, emails, phone numbers, Follow Up Boss person IDs, your team roster, your sources, your stages, your pipeline 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 Follow Up Boss account and in whatever systems your CRM's flow forwards lead events to. Person records, notes, timeline events, appointments all live in Follow Up Boss. Source-attributed (always AI Receptionist Call or AI Receptionist Web), attributed to AnyCRM in the audit log, revocable. AnyCRM does not build a shadow CRM alongside yours.
Revocation
Revoke the API key in your Follow Up Boss admin panel 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
Follow Up Boss uses a single account-level API key. AnyCRM only calls the smallest set of endpoints required for the lead-capture and booking lifecycle. Nothing for analytics, nothing for marketing, nothing for billing.
- People (read + write). Read and write person records, dedup against existing leads, append notes.
- Events (write). Write inbound activity events so the call shows up on the timeline as a real interaction and the right action plans fire.
- Appointments (read + write). Read existing appointments (for reschedule and cancel) and write new ones on the right agent's calendar.
- Users (read). Read your team roster at setup so the AI Receptionist knows who exists and who owns existing leads.
- Not requested: billing / subscription data, transactions, Smart Lists, action-plan internals, your other integrations.
Same API key any Follow Up Boss integration uses. Just a smaller surface. AnyCRM holds the key and the auditable system-attribution headers (every write is signed so each appointment and person change is attributable to AnyCRM in Follow Up Boss's audit trail). The LLM never sees the key, 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 Follow Up Boss
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.