An AI Receptionist that books, reschedules & cancels appointments — 24/7 — and writes them straight into
Square.
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 — Square integration.
Does this actually work with my Square Appointments account?
Will it create duplicate customers in Square?
Can it route different inquiries to different team members?
Where do the appointments actually live, calendar or Square?
Can it cancel or reschedule an appointment from a phone call?
What if I edit a service price in the Square Dashboard mid-day?
Does it handle multiple locations correctly?
Does it handle timezones correctly?
Does it handle deposits or take payment over the phone?
AI Receptionist Call or AI Receptionist Web). Your flow decides whether a deposit invoice fires, which loyalty tier applies, which follow-up sequence runs. 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 and online booking page? Do they go through the same pipe?
How long until it's actually capturing bookings into Square?
Captures the caller as a Square customer, books the service in the same call, and feeds one unified conversion pipe for your website forms AND your AI Receptionist.
Every caller who asks about a service lands as a customer in Square (with name, email, phone, and a booked appointment on the right team member's calendar, tied to the correct service variation and location). When they want a booking, AnyCRM writes a native Square booking through the Bookings API. 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 inquiry becomes a Square customer, not a missed call
Caller's name, phone, email, the service they asked about, and any preferences land as a Square customer with source attribution and a profile note. Then AnyCRM writes the record into Square DURING the call.
Books against the right team member's real availability
The AI Receptionist asks AnyCRM for live availability for the routed-to team member at the right location — honouring service duration, buffer times, existing bookings, and business hours — then AnyCRM writes the booking onto that team member's Square calendar in the same conversation.
Sends the lead event straight to your CRM. You decide what happens next.
AnyCRM does not pretend to know your follow-up rules. Every customer-create and every booking sends a lead event straight to your CRM (with source: "AI Receptionist Call" or source: "AI Receptionist Web") where YOUR business logic takes over. Send the deposit invoice, fire the loyalty trigger, push to your email tool. We set up the receiving end inside your CRM for you during onboarding, tuned to your industry. 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 service businesses run two completely separate conversion-tracking stacks: one for the website (booking site visits, form-fills, 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 and online-booking-page conversions, 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 / online booking page 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 marketing list, which loyalty tier, which follow-up sequence, which staff notification. 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 online-booking-page visits), 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 appointments, not against the noisy subset of leads that happen to fill a form or click the booking page.
- Lower ad costs. Once Google Ads and Facebook Ads learn what a real booking looks like, they stop spending against lookalikes of low-quality clicks.
- Enriched analytics. Every conversation surface (web form, online booking page, 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 CRM's flow owns deposit policy, loyalty triggers, and follow-up sequences. 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 customer is created, which list to add them to, and which follow-up to fire. 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 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 specific vertical, 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 Square
The AI Receptionist asks AnyCRM for availability against the team members on your roster and gets back open slots in the caller's timezone. No double bookings. Existing bookings are always respected. Every AnyCRM call prevents duplicate customers, resolves the right service variation, sets the matched team member, writes the booking so it lands on the team member's Square 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 website form-fill or an online-booking-page visit 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 clicks (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-page completions. That's why your Cost per Lead looks low but you can't tell which Ads are actually filling chairs. The high-intent traffic is calling you instead of navigating the booking page, 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 clicking. In practice this means: Cost per Lead drops because you stop overpaying for low-intent clicks; Return on Ad Spend goes up because the Ads now find people closer to ready-to-book; and Customer Acquisition Cost shrinks because more of your Ad budget reaches buyers who will actually walk through the door.
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-page conversions through the same pipeline. So a lead from a Google Ad that books online 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 bookings actually came from.
- Cost per Lead drops. Because Google, Facebook, and LinkedIn stop wasting your Ad budget on lookalikes of low-intent clickers, 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 book, not toward whichever cheap audience generates the most clicks.
- Customer Acquisition Cost (CAC) shrinks. Because a higher share of every Ad dollar reaches buyers ready to book a service.
- Analytics get a complete funnel. Web and voice bookings sit side by side, with the same source taxonomy. You stop seeing "50% of bookings: unknown source."
- Attribution stops fragmenting. A buyer who first clicked a Google Ad, then called the salon 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 service businesses cannot honestly tell you whether their Google or Facebook spend is profitable. With AnyCRM's Conversion Lift, you can.
Imagine you spend $3,000/month on Google and Facebook Ads for your salon. Today, you see 60 online bookings and assume that's the full picture. With AnyCRM running, you'll also see (say) 90 phone calls and 30 web chats the AI Receptionist handled, all flowing into Google Ads and Facebook Ads as real conversions. Suddenly your Ad platforms see 180 conversions a month instead of 60. They re-train on that bigger, better signal. Within weeks, the bidding finds you more of the right kind of buyer. Same $3,000 spend, more booked chairs, 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 Square
Every customer-create and booking 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 page run through the same pipeline, so Web and Voice conversions feed the SAME training signal.
Owns the full booking lifecycle inside Square.
Every "can we push my Tuesday cut?" or "actually, cancel that" lands with the AI Receptionist instead of on your front desk. AnyCRM reschedules update the existing booking in place. Cancellations follow Square's idiom (a proper cancel with the reason on the customer profile) instead of leaving the slot in limbo.
Finds the booking by email. No booking IDs on the call
Customers DO NOT quote booking IDs over the phone. AnyCRM resolves the Square customer by email, lists their upcoming bookings, and reads back the service, date, time, and team member before changing anything.
Reschedules in place and keeps the booking record clean
Rescheduling updates the existing booking in a single confirmation, preserving the customer link and the team member assignment. Failed reschedules leave the original booking untouched. The customer never ends up with no appointment.
Cancels with the reason on the record
When a caller cancels, AnyCRM writes the customer's reason onto the Square customer profile, then calls Square's cancel endpoint. So the next time the team member opens the customer's record, they know WHY the slot opened up. No silent disappearing bookings.
For your developer: reschedule & cancel by email
AnyCRM's search, reschedule, and cancel all accept just an email. The soonest upcoming Square booking for that customer is resolved inside AnyCRM. No booking 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 respects which services they actually perform.
Square Appointments accounts run on team members, locations, and service variations. A barber doesn't do colour. An esthetician doesn't do massage. The senior stylist's haircut is a different price and duration than the junior's. At setup AnyCRM imports your Square team members and your service variations into its database and enriches each member with qualified services, expertise, languages, timezone, and location assignment (context Square's team member object doesn't carry). The AI Receptionist then routes each caller to a team member who is actually qualified for the requested service at the right location.
Routes by service variation, not by free-text request
"I want a balayage" only resolves to the team members whose qualified services include balayage. "A men's cut with Marco" pins both the variation and the team member. "Anyone available for a quick beard trim" assigns across the qualified pool.
Honours existing customer-to-team-member relationships
If a returning customer has a history of bookings with one team member, the AI Receptionist offers that member first. The customer profile, the notes, and any new booking all attach to the existing Square customer record. No orphaned duplicate, no lead poached off a stylist's chair.
Respects location boundaries
Multi-location businesses (two salon branches, two studios) keep separate rosters per location. "Can I book at the downtown location" only surfaces team members assigned to that location. The AI Receptionist never books a stylist who isn't actually working at the requested branch.
For your developer: specialist roster & per-service routing
Team details live in AnyCRM's database, pulled once from Square at setup (active team members joined against each member's bookable-flag and per-location assignments, and against the Catalog for each service variation the member is qualified to perform). Enriched with expertise, languages, timezone, and display order. AnyCRM keeps the Square team member identifier on the record as the bridge for booking writes. <code>listSquareTeamMembers</code> and <code>getSquareSpecialistServices</code> are hydration and re-sync calls, not per-call lookups. At runtime, one read of the team roster matches caller → service → qualified member at the right location. AnyCRM does NOT cache your follow-up policy or your loyalty rules. 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 Square accounts.
You connect Square once. AnyCRM imports your locations, your team members, your service variations, and your booking profiles. 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 inquiries and booking appointments the same afternoon. No middleware. No prompt-engineering by you.
Connect Square (OAuth, 60 seconds)
Authorize AnyCRM on your Square account via the standard OAuth grant. AnyCRM scopes to the least amount of access needed for the booking lifecycle. Nothing for payments, orders, or payroll. You can always revoke permissions at any time from your Square Dashboard → Apps & Subscriptions → Authorised Applications. Every update to your Square is signed with AnyCRM's connected-app credentials so it's easy to track what the AI Receptionist did when you audit.
Import locations, team members, service variations & booking profiles. Wire up your CRM's lead-receiving flow.
AnyCRM imports every Square location, every active team member, every service variation from the Catalog (with the current variation version captured for booking writes), and each member's booking profile so we know who is actually bookable at which location. AnyCRM also freezes the service variations so the AI Receptionist can only book services you actually offer, 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 loyalty rules, your deposit policy, or your follow-up sequences. Your CRM decides what happens after a booking 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 Square 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 Square's online booking site + Square Assistant?
Square's online booking site and Square Assistant SMS confirmations are excellent at the steps AFTER a customer has chosen to come to your booking page. Square Assistant is a text-only reply bot. It only replies to SMS appointment reminders to confirm, cancel, or change a booking that already exists. It doesn't pick up the phone, it doesn't qualify a new caller, and it doesn't book first-time customers. A new caller at 7pm gets a missed call, not a customer record. The booking site assumes the customer can navigate a service menu and pick a variation themselves. The AI Receptionist is the layer BEFORE all of that. It picks up the call, asks the right qualifying questions ("are you looking for the men's cut or the women's cut?"), books the appointment as a native Square booking on the right team member's calendar at the right location, writes a clean, sourced customer with the call summary in the profile note (with the source set to AI Receptionist Call or AI Receptionist Web), AND sends the same lead event straight into your CRM's downstream business logic plus your ad platforms server-side. So your Square workflow, 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 Square 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 email and phone, location resolution, service-variation-version capture, segment assembly, timezone math, 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 Catalog and Bookings internals.
Capturing a new inquiry
createOrUpdatesSquareContact accepts name, email, phone, note, plus the inferred source. AnyCRM searches by email then phone, picks the surviving record (or creates a new one with a deterministic idempotency key derived from the call), sets AnyCRM's reference on the customer for attribution, appends the call summary to the profile 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. Duplicate creation is structurally impossible.Booking the appointment
createSquareContactAppointment takes email, scheduled_datetime (naive, no offset needed), invitee_timezone, and the service variation key. AnyCRM resolves the right team member from the service and location, refreshes the service variation version from the Catalog on every booking (never cached stale), reads duration from the variation, assembles the full segment array, runs the availability pre-check, converts the naive datetime to the format Square's booking endpoint requires, submits with a deterministic idempotency key, 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. Version-mismatch and invalid-slot errors are structurally impossible.Cancelling with a reason
cancelSquareAppointment takes email and reason. AnyCRM resolves the soonest upcoming booking, fetches the current booking version, writes the reason as a note on the customer record BEFORE the cancel fires, then calls Square's cancel endpoint with a deterministic idempotency key. All in one AnyCRM call. Stale-version 400s are handled with a single retry against the refreshed version. The response contains the cancelled booking ID and the recorded reason, so the AI Receptionist can read it back to the caller. No deletion, full audit trail, the customer profile preserves WHY the slot opened up.Every AnyCRM tool for Square follows the same AI-alignment contract, so the AI Receptionist never has to think about transport:
- Naive datetimes in, Square-native shape out. The AI Receptionist passes
2026-05-15T11:00:00and a timezone string. AnyCRM does the offset math against the location's timezone. - Email is the identity. Cancel and reschedule never need a booking ID at the AI Receptionist layer. Email and soonest-upcoming resolves inside AnyCRM.
- Service variation, location, and team member come from setup, not the LLM. The AI Receptionist can't book a free-text "haircut". It resolves caller intent to a real service variation against your live Catalog.
- Existing customer relationships are sacred. If a returning caller has booking history with a team member, AnyCRM offers that member first. Duplicate customers are structurally impossible.
- Service variation version is always fresh. AnyCRM re-reads from the Catalog on every booking so version-mismatch can't fire when a stylist edits a price in the Dashboard mid-day.
- Cancellation preserves the audit trail. Square's idiom (a proper cancel with the reason captured on the customer profile) is honoured so the customer record reflects WHY the slot opened up.
- 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 bookings. 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 Square becomes a one-sentence reason the AI Receptionist can repeat to the caller without translation.
- Idempotent reschedules. Every write carries a deterministic idempotency key. If a network blip retries the call, the booking is preserved. The customer never ends up with two appointments or none.
Multi-team-member setup. Team roster, services & system-prompt assembly
If you run more than one team member on Square, AnyCRM imports the team roster once, you link each member to the service variations they actually perform (cuts / colour / treatments / training / grooming), 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 at which location.
- Team roster import. AnyCRM imports every active Square team member once and writes each one into its database keyed by
crm_user_id(with name, role, timezone, Square's team member identifier, and per-location assignments). - Per-team-member services. For each team member AnyCRM joins the booking profile against the Catalog to return the exact service variations they're qualified to perform, with current variation version, duration, and price. One call per person, cached.
- Service visibility. Each service variation is flagged Public, Private or Ignored. The AI Receptionist only routes to and books Public variations. 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 deposit policy, your loyalty triggers, and your follow-up sequences live. AnyCRM doesn't try to own them.
- System-prompt assembly. The cached roster, service-variation, and location 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 team members, services, or prices 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 a balayage with someone senior at the downtown location next Thursday afternoon" → senior colourists qualified for the balayage variation at the downtown location → that member's calendar availability → a booked Square appointment with the full segment array correctly assembled → 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 salons, barbershops, day spas, nail studios, lash & brow bars, personal training studios, pet groomers, and mobile services. Anyone whose business is in Square Appointments but whose phone keeps ringing while staff are with clients.
How most AI Receptionists built on Smith.ai, My AI Front Desk, or Goodcall fail for salons, barbershops, spas, fitness studios, pet groomers, and other service businesses that use Square. And why AnyCRM can't.
Most AI Receptionists fail on Square in the same handful of ways. Duplicate customers, stale service-variation versions, bookings against unavailable slots, the wrong team member's calendar, invented services and free-text bookings, cancellations that destroy the audit trail, multi-location confusion, hardcoded deposit and loyalty 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 deposit and loyalty 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 customers
Stale service-variation versions on booking
Booking against an unavailable slot
Booking the wrong team member's calendar
Inventing services and free-text bookings
Cancelling by DELETE or by walking away
Location confusion in multi-location accounts
Encoding your deposit and loyalty policy in the prompt or in middleware
Web bookings and AI Receptionist bookings 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 Square
| Capability | AnyCRM | Smith.ai | My AI Front Desk | Goodcall |
|---|---|---|---|---|
| Live Square booking written DURING the call | Yes. Native Square booking, team-member-matched, location-scoped, calendar-synced. | No. Booked manually after the call via your public Square booking page link. | Partial. Zapier-style "Schedule Appointments" action without per-call version refresh or availability pre-check. | Partial. Connector write without published team-member-booking-profile awareness. |
| Dedup-before-write on email and phone | Yes. Always. | Manual. | No. Zapier customer-create is one-shot. | No published guarantee. |
| Preserves existing customer-to-team-member relationship on returning callers | Yes. Returning customers offered their previous stylist first. | Implicit, not guaranteed. | No. Can overwrite. | Depends on connector defaults. |
| Routes by service variation, not free-text request | Yes. Service variation is part of AnyCRM's frozen Catalog snapshot. | Manual, depends on the receptionist. | No. | No. |
| Service variations & prices frozen from your real Catalog at setup | Yes. Read at setup, baked into the prompt as a frozen table. | Not API-enforced. | No. Writes can fail on unknown variations. | No structural guard. |
| Cancellation preserves the audit trail (reason on customer profile, not deleted) | Yes. Square-native cancel + reason note. | Manual. | No. Reason isn't captured. | No. Connector default with no reason path. |
| Reschedule in place (no cancel-then-rebook) | Yes. | Manual. | No. | No. |
| Service-variation version refreshed on every booking (no VERSION_MISMATCH) | Yes. Re-read from Catalog on every booking. | N/A — bookings are manual. | No. Version cached at Zapier trigger-setup time. | No published guarantee. |
| Availability pre-checked before booking write (no BOOKING_INVALID_SLOT after the call) | Yes. Always. | Receptionist checks visually. | No. | No published guarantee. |
| Location-scoped routing in multi-branch accounts | Yes. Every booking resolves to the right location. | Manual, depends on the receptionist. | No. Defaults to trigger-setup location. | No published per-call resolution. |
| Deposit & loyalty 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 Invoice" / "Automate Payments" actions. | No. Connector-default behaviour. |
| Unified conversion pipe: web bookings AND AI Receptionist → CRM + ad platforms server-side | Yes. Same shape, same source taxonomy, same server-side delivery. | 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 web form identifiers. | Manual / inconsistent. | No standardised taxonomy. | Whatever the connector defaults to. |
| Scale ceiling | Bounded by Square API limits, not by staffing. | Bounded by human receptionist staffing. | Bounded by Zapier rate limits and action contracts. | Bounded by the connector hop. |
Your Square data passes through AnyCRM. It doesn't stick.
AnyCRM processes your Square 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, bookings, services, team members. All of it stays in Square, owned by your Square 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 customer records, no caller PII.
What AnyCRM doesn't
Caller names, emails, phone numbers, Square customer IDs, your team roster, your service variations, your prices, your booking history. 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 Square account and in whatever systems your CRM's flow forwards lead events to. Customers, bookings, profile notes all live in Square. 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 AnyCRM OAuth grant in your Square Dashboard → Apps & Subscriptions → Authorised Applications 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
Square uses OAuth scopes. AnyCRM requests only the smallest set required for the booking lifecycle. Nothing for payments, nothing for orders, nothing for payroll.
- Customers (read + write). Read and write customer records, dedup against existing records, append profile notes (the lead-capture work).
- Appointments (read + write). Read availability and write bookings on the routed-to team member's calendar; reschedule in place; cancel with the reason on the customer profile (the booking work).
- Items (read). Read your Catalog so the AI Receptionist knows which service variations exist, with current versions, durations, and prices.
- Appointments business settings (read). Read team-member booking profiles so the AI Receptionist only books members who are actually bookable at the requested location.
- Employees (read). Read your team roster at setup time, so the AI Receptionist knows who exists and who is currently active.
- Not requested: payments, orders, invoices, payroll, bank accounts, gift cards, loyalty, marketing campaigns (deposit and loyalty policy stays inside your CRM's own flow), your other integrations.
Same OAuth grant any Square 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 customer and booking change is attributable to AnyCRM in Square'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 Square
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.