{
"icp": "sales teams running their pipeline on Zoho CRM — SaaS, agencies, B2B services, manufacturing, and consultancies that close on the phone",
"capabilities": {
"availability": {
"headline": "Captures the website inquiry or caller as a Zoho Contact or Lead, books the meeting if there's real intent, and feeds one unified conversion pipe for your website forms AND your AI Receptionist.",
"lede": "Every caller who lands on the line becomes a Zoho Contact (or, when the caller isn't qualified yet, a Zoho Lead) with the right Owner, the right Account, and the right Lead Source attached. When they want a meeting, AnyCRM creates a native Zoho Event on the matched team member's calendar with the Contact in Participants and the team member as Host. 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 Zoho business logic and your Google / Facebook / LinkedIn Ads both stay in sync.",
"cards": [
{
"num": "A.01",
"title": "Every caller becomes a Zoho record, not a stray missed call",
"body": "The AI Receptionist captures first name, last name, email, phone, Account, and call intent. Then AnyCRM writes the record into Zoho as a Contact (or Lead, when no Account exists yet) with the right team member Owner, Lead Source, and pick-list values attached DURING the call."
},
{
"num": "A.02",
"title": "Books meetings as native Zoho Events",
"body": "The meeting lands as a native Zoho Event of the right type, with the matched team member as Host, the caller in Participants, the duration computed from the meeting type, and the Event tied to the related Lead, Contact, or Deal so it shows on every module view and on the team member's Google or Outlook calendar."
},
{
"num": "A.03",
"title": "Sends the lead event straight to your CRM. You decide what happens next.",
"body": "AnyCRM does not pretend to know your deal-creation rules. Every contact-create, lead-open, and meeting-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. Open the Deal, set the stage, fire the Blueprint, run the Workflow Rule, route the Assignment Rule. We set up the receiving end inside your CRM for you during onboarding, tuned to your industry and your Zoho configuration. AnyCRM doesn't get in the way of policy you've already encoded."
}
],
"apiSummary": "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 Contacts, creates or links the Account, sets the team member Owner (matched from your team), writes the Event so Zoho's calendar sync to Google or Outlook fires automatically, fires your Workflow Rules and Blueprints by default, and sends the lead event straight into your CRM tagged with AI Receptionist Call or AI Receptionist Web. 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.",
"tools": [
"getZohoAvailability",
"createZohoContactAppointment"
],
"curl1Path": "/mcp/tools/getZohoAvailability",
"curl2Path": "/mcp/tools/createZohoContactAppointment",
"pipeIntro": "Most businesses run two completely separate conversion-tracking stacks: one for the website (forms, SalesIQ chat, 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.",
"pipeStages": [
{
"stage": "1. Capture",
"body": "A lead arrives either through your website form / SalesIQ chat 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."
},
{
"stage": "2. Deliver to your CRM",
"body": "AnyCRM sends the lead event straight to Zoho, into the receiving flow we wired up for you at onboarding. Your business logic decides what happens next: which Deal, which pipeline, which stage, which Workflow Rule, which Blueprint, which Assignment Rule. You don't have to maintain two sets of rules. Web leads and AI Receptionist leads both arrive through the same door."
},
{
"stage": "3. Fire server-side conversion to your ad platforms",
"body": "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."
},
{
"stage": "4. Optimise, attribute, report",
"body": "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."
}
],
"outcomes": [
"Higher ROAS. Ad bidding optimises against actual conversations and booked meetings, not against the noisy subset of leads that happen to fill a 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, SalesIQ 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. Zoho's Workflow Rules, Blueprints, and Assignment Rules own deal-creation, pipeline assignment, and stage routing. AnyCRM doesn't drift out of date because AnyCRM never tried to own that policy in the first place."
],
"whyThisIsBetter": "Most competitor AI Receptionists try to maintain rules for when a Deal is created, what pipeline it goes in, and which Lead Source value to apply. That approach breaks the moment your Zoho config 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 Zoho account (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 Zoho AND the server-side conversion tracking at onboarding, matched to your specific industry, ad mix, and analytics setup.",
"honestAside": "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."
},
"adsConversionLift": {
"headline": "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.",
"lede": "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 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.",
"cards": [
{
"num": "1b.01",
"title": "Every phone call and every chat becomes a tracked conversion. Not just website form-fills.",
"body": "Today, Google Ads and Facebook Ads probably think your only conversions are website form-fills. That's why your Cost per Lead looks low but your sales team complains the leads are weak. The high-intent traffic is calling you instead of filling a Zoho Web 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."
},
{
"num": "1b.02",
"title": "Lower Cost per Lead. Better ROAS. Smaller CAC.",
"body": "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 customers."
},
{
"num": "1b.03",
"title": "The same pipe carries your website forms too. One source of truth across Ads, Zoho, and Analytics.",
"body": "AnyCRM doesn't just track AI Receptionist conversions. It also runs your existing Zoho Web Forms and SalesIQ 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 Zoho stops being half-blind to where your leads actually came from."
}
],
"apiSummary": "Every contact-create, lead-open, and meeting-book fires through AnyCRM's Conversion Lift pipeline. The lead event lands inside Zoho 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 Zoho Web Forms and SalesIQ chatflows run through the same pipeline, so Web and Voice conversions feed the SAME training signal.",
"businessImpact": [
"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 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, 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."
],
"plainEnglishExample": "Imagine you spend $5,000/month on Google Ads. Today, you see 80 Zoho Web Form submissions 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.\"",
"tools": [
"createOrUpdatesZohoContact",
"createZohoContactAppointment"
]
},
"lifecycle": {
"headline": "Manages the full Event lifecycle inside Zoho CRM for anyone calling or chatting.",
"lede": "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 Zoho Event in place. Cancellations follow the Zoho-native idiom (a cancellation prefix on the Description plus a Note on the linked record) instead of deleting the audit trail into the Recycle Bin. So you get crystal clarity on when a Zoho Event was created, and when and why it was updated by your AI Receptionist.",
"cards": [
{
"num": "B.01",
"title": "Finds the Event by email in a single step without needing Zoho record IDs",
"body": "Customers DO NOT quote Zoho 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 linked to the matching Contact. And the AnyCRM response forces the AI Receptionist to be human. It reads back the subject, date, time, and team member Host before changing anything."
},
{
"num": "B.02",
"title": "Reschedules in place and keeps the Event record clean",
"body": "Rescheduling updates the existing Event in a single confirmation. No cancel-then-rebook round-trip means the Event history, the related-record link, and the calendar invite all stay intact. Failed reschedules leave the original Event untouched."
},
{
"num": "B.03",
"title": "Cancels without erasing the audit trail",
"body": "When a caller cancels, AnyCRM flags the Event cancelled the Zoho-native way (prefixing the Description so the cancellation stays queryable in reporting) and writes the caller's reason as a Note on the linked Contact or Lead. Instead of issuing a DELETE that would send the Event to the Recycle Bin and strip WHY the meeting fell through. This lets you intuitively track changes for Zoho Events created or updated by your AI Receptionist."
}
],
"apiSummary": "AnyCRM's search, reschedule, and cancel all accept just an email. The soonest upcoming Event linked to the matching Contact is resolved inside AnyCRM. No Event IDs at the AI Receptionist layer.",
"tools": [
"searchZohoAppointments",
"rescheduleZohoAppointment",
"cancelZohoAppointment"
],
"curl1Path": "/mcp/tools/searchZohoAppointments",
"curl2Path": "/mcp/tools/rescheduleZohoAppointment",
"curl3Path": "/mcp/tools/cancelZohoAppointment"
},
"routing": {
"headline": "Routes every caller to the right team member. And maintains the existing team member looking after the lead instead of randomly reassigning to someone else.",
"lede": "Zoho accounts run on Users, Roles, Profiles, and Territories. At setup AnyCRM imports your Zoho user roster into its database and enriches each team member with lane, expertise, languages, timezone, and bookable meeting-type duration. The AI Receptionist then routes each caller to the team member who actually handles that lane. Existing Owner on Contacts, Leads, and Deals is honoured as the source of truth.",
"cards": [
{
"num": "C.01",
"title": "Routes by lane: AE vs SDR vs CS",
"body": "\"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 Owner on the Contact is always preserved."
},
{
"num": "C.02",
"title": "Honours existing Owners in Zoho",
"body": "If a Contact already has an Owner in Zoho, the AI Receptionist doesn't reassign them. The Event, the Note, and any new Lead all attach to the existing record under the existing Owner. No orphaned duplicate, no lead poached off a team member's pipeline, and no Assignment Rule misfire."
},
{
"num": "C.03",
"title": "Matches fresh inbound callers and website chatters to the right person on the team",
"body": "New leads with no existing Zoho record get matched to a team member on the lane you've designated (AE, SDR, CS), with Territory and Role filters honoured. The AI Receptionist doesn't fight the rules you already use."
}
],
"apiSummary": "Team details live in AnyCRM's database, pulled once from Zoho at setup, enriched with lane, expertise, languages, timezone, default Event type, and meeting-type duration (valuable context for the AI Receptionist that Zoho's user object doesn't carry by default). At runtime, one read of the team roster matches caller → lane → team member. New Contacts and Leads inherit that team member as Owner. Existing records keep theirs. AnyCRM does NOT cache your deal pipelines, your stages, your Workflow Rules, or your Blueprints. That policy stays inside Zoho, where it belongs.",
"tools": [
"listZohoTeamMembers",
"getZohoUserProfile"
],
"curl1Path": "/mcp/tools/listZohoTeamMembers",
"curl2Path": "/mcp/tools/getZohoUserProfile"
}
},
"setup": {
"headline": "Setup in 3 steps. Battle-tested on real Zoho CRM accounts.",
"lede": "You connect Zoho CRM once. AnyCRM imports your team, your modules, your Lead Sources, your Event types, and your pick-list values. AnyCRM also wires up the receiving end inside Zoho 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.",
"steps": [
{
"num": "S.01",
"title": "Connect Zoho CRM (OAuth, 60 seconds)",
"body": "Authorize AnyCRM on your Zoho account via the standard OAuth grant. AnyCRM scopes to the least amount of access needed for the booking lifecycle. Nothing for analytics, nothing for marketing email, nothing for billing. Zoho's regional data centres (.com / .eu / .in / .com.au / .jp / .ca / .sa) are detected automatically so every call hits the right Zoho data centre. You can revoke permissions at any time from Zoho Account → Active Sessions or Settings → Apps & Add-ons. Every update to your Zoho is signed with AnyCRM's connected-app credentials so it's easy to track what the AI Receptionist did when you audit."
},
{
"num": "S.02",
"title": "Import the team. Lock in your meeting types. Wire up your CRM's lead-receiving flow.",
"body": "AnyCRM imports every active Zoho user as a bookable team member with lane, expertise, languages, timezone, and default Event-type duration. AnyCRM also reads your Lead Source pick-list values (the exact strings Zoho will accept, which are otherwise enum-bound), freezes your Event types so the AI Receptionist can only book types you actually use, 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 Zoho so the lead events from the AI Receptionist land where your business logic can act on them. AnyCRM does NOT replicate your deal pipelines, stages, Workflow Rules, or Blueprints. Zoho decides what happens after a lead is captured. AnyCRM just delivers a clean event."
},
{
"num": "S.03",
"title": "Drop the AI Receptionist on your phone line and your site",
"body": "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 Zoho account, same lead-event pipe into your CRM and your ad platforms) answers both voice and web. Live the same afternoon."
}
],
"nativeAlternative": {
"headline": "Why not just use Zoho's Bookings + Web Forms + SalesIQ?",
"body": "Zoho Bookings, Web Forms, and SalesIQ chat are excellent at the steps AFTER a lead has chosen to come to you via your website. They don't pick up the phone. A new caller at 9pm gets a missed call, not a Contact record. A Web Form sits in your Leads module until someone reads it. SalesIQ runs on the website only, with no voice surface, and the Zia AI tier handles only chat. 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 Zoho Event on the right team member's calendar, writes a clean Contact or Lead (with the source set to AI Receptionist Call or AI Receptionist Web, the right Lead Source pick-list value, and a call summary as the first Note), AND sends the same lead event straight into Zoho's downstream business logic plus your ad platforms server-side. So your Zoho Workflow Rules, your Blueprints, your Assignment Rules, your analytics, and your Google / Facebook Ads bidding all start optimising on a real conversation, not a name and a missed call."
},
"enrichmentSummary": "Every tool the AI Receptionist calls is an opinionated wrapper inside AnyCRM. AnyCRM does the messy work for you. Dedup by email then phone, Account linking, Event-type resolution, timezone math, Participants assembly, pick-list value enforcement, regional data-centre routing, 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.",
"enrichmentExamples": [
{
"title": "Capturing a new lead",
"raw": "Writing a Contact or Lead straight into Zoho looks simple. But the plain insert endpoint creates a duplicate if the same email or phone is sent twice. The body has to be wrapped in a very specific shape and include the trigger array, otherwise your existing Workflow Rules, Blueprints, and Assignment Rules never fire on the new record. Lead Source is pick-list-bound: any value not in your configured set returns INVALID_DATA. And if you want the inquiry to live as a Lead (the Zoho idiom for unqualified inbound) rather than a Contact, that's a different module entirely with its own pick-list (Lead Status), and Leads can't be created in the same request as a Contact. On top of all that, nothing in raw Zoho fires a server-side conversion event to your ad platforms, so call-driven and chat-driven leads never get optimised for.",
"mcp": "createOrUpdatesZohoContact accepts name, email, phone, note, account, lead_intent, plus the matched team member. AnyCRM handles dedup, picks the surviving record (or creates a new one with the right values in the right order), creates or links the Account, sets the team member Owner, appends a Note, fires your Workflow Rules / Blueprints / Approvals by default, opens a Lead in the Leads module when the caller isn't ready for a Deal, sends the lead event straight into Zoho (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."
},
{
"title": "Booking the meeting",
"raw": "Creating an Event directly against Zoho is a tight contract. The start and end times have to be ISO-8601 with the right timezone offset (Zoho does no timezone math; send a naive datetime and the API 400s). The Contact or Lead has to be linked through one field, the Deal or Account through another, and the two are NOT interchangeable. Participants is an array where each entry has a type and the type has to match the record type exactly. The team member Host has to be set on the Owner field, otherwise the Event lands on the API user's calendar instead of the team member's. And the Google or Outlook calendar sync only fires when the team member has Calendar Sync enabled in their user profile, which is set per-user, not per-record.",
"mcp": "createZohoContactAppointment takes email, scheduled_datetime (a naive date and time, no offset needed), invitee_timezone, and meeting_type_key. AnyCRM resolves the right team member from the lane, handles the timezone and duration math, builds the Contact / Lead / Deal links correctly, assembles Participants with the right type per entry, sets the team member as Host, sends the same lead event straight into Zoho 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."
},
{
"title": "Cancelling with a reason",
"raw": "Deleting an Event in Zoho sends it to the Recycle Bin for 60 days, then permanently removes it. No cancellation outcome field exists, no reason is recorded, and the Event disappears from Event-search queries the moment it lands in the bin. Zoho-experienced admins use a Description-prefix convention instead so the cancellation stays queryable in reporting, with the reason on the linked record as a Note. Doing that cleanly takes several round-trips: read the Event, write a Note with the reason, then update the Event's Description.",
"mcp": "cancelZohoAppointment takes email and reason. AnyCRM resolves the soonest upcoming Event, records the reason on the linked Contact or Lead as a Note, and flags the Event cancelled the Zoho-native way. All in one AnyCRM call. No DELETE, no Recycle Bin, full audit trail, Event stays queryable in the team member's reporting."
}
],
"alignmentSummary": "Every AnyCRM tool for Zoho follows the same AI-alignment contract, so the AI Receptionist never has to think about transport:",
"alignment": [
"Naive datetimes in, Zoho-native shape out. The AI Receptionist passes 2026-05-15T11:00:00 and a timezone string. AnyCRM converts it into whatever shape the Zoho Event API requires, on both start and end.",
"Email is the identity. Cancel and reschedule never need an Event ID at the AI Receptionist layer. Email and soonest-upcoming resolves inside AnyCRM.",
"Lead Source and pick-list values come from setup, not the LLM. The AI Receptionist can't invent a Lead Source or a Lead Status. It inherits the values you configured at setup. Pick-list fields are constrained to your existing enum so INVALID_DATA 400s are structurally impossible.",
"Existing Owners are sacred. If a Zoho Contact, Lead, or Deal already has an Owner, AnyCRM preserves it. New records only get the matched team member when no Owner exists.",
"Cancellation preserves the audit trail. Zoho's audit trail survives because AnyCRM never sends Events to the Recycle Bin. Every cancellation stays queryable in reporting with the reason on the record.",
"Workflow Rules, Blueprints, and Approvals fire by default. Every write asks Zoho to fire your existing automations, so new records behave exactly as if a human had created them through the UI.",
"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 4xx from Zoho 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 Zoho Event is preserved. The customer never ends up with nothing.",
"Regional DC awareness. AnyCRM routes every call to the right Zoho data centre (.com / .eu / .in / .com.au / .jp / .ca / .sa) based on the OAuth grant, so cross-region requests don't silently fail."
],
"industryLine": "Currently running for B2B SaaS sales teams, agencies, consultancies, manufacturers, and professional services. Anyone whose pipeline is in Zoho CRM but whose phone keeps ringing after the AE has logged off.",
"teamsSetup": {
"headline": "Multi-team-member setup. Team roster, lanes & system-prompt assembly",
"body": "If you run more than one team member on Zoho, AnyCRM imports the team roster once, you link each team member to the lanes they actually cover (AE / SDR / CSM / pre-sales), 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.",
"steps": [
"Team roster import. AnyCRM imports your Zoho team members once and writes each one into its database keyed by crm_user_id (with name, role, lane, timezone, role, profile, territory).",
"Per-team-member Event types and modules. For each team member AnyCRM resolves the Event types they actually book, the default duration per type, and the modules they have write access to. 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 Zoho that receives lead events from AnyCRM. That's where your deal-creation policy lives. AnyCRM doesn't try to own it.",
"System-prompt assembly. The cached team roster, lane, and Event-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 team members, lanes, or Event types re-run the cache. The AI Receptionist picks them up on its next deploy."
],
"note": "The end result: the AI Receptionist can match \"I'd like to demo the platform with someone on the sales team\" → the AE team → that team member's Demo Event type → that team member's calendar availability → a booked Zoho Event with the Contact in Participants and the right team member as Host → a lead event delivered straight into Zoho → a server-side conversion event in your ad platforms. Without a single team roster query during the call."
}
},
"privacy": {
"headline": "Your Zoho CRM data passes through AnyCRM. It doesn't stick.",
"lede": "AnyCRM processes your Zoho CRM data to answer the call. Then forgets it. The only thing AnyCRM persists is a conversation history ID so the AI Receptionist can recognise a returning caller. Contacts, Leads, Events, Deals, Notes. All of it stays in Zoho, owned by your Zoho account.",
"cards": [
{
"kind": "stored",
"label": "What AnyCRM stores",
"body": "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."
},
{
"kind": "not-stored",
"label": "What AnyCRM doesn't",
"body": "Caller names, emails, phone numbers, Zoho record IDs, your team roster, your modules, your pick-list values, your Event types, your Deal data. None of it. AnyCRM reads what it needs, hands it to the LLM, fires the events, and discards the payload."
},
{
"kind": "data-lives",
"label": "Where data lives",
"body": "In your Zoho account, in your regional data centre, and in whatever systems your CRM's flow forwards lead events to. Contacts, Leads, Events, and Notes all live in Zoho. Source-attributed (always AI Receptionist Call or AI Receptionist Web), attributed to AnyCRM in the Zoho audit log, revocable. AnyCRM does not build a shadow CRM alongside yours."
},
{
"kind": "revoke",
"label": "Revocation",
"body": "Revoke the AnyCRM connected-app OAuth grant in Zoho Account → Active Sessions or Zoho CRM → Settings → Apps & Add-ons 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."
}
],
"scopesSummary": "Zoho uses granular OAuth scopes. AnyCRM requests only the smallest set required for the contact + meeting capture lifecycle. Nothing for marketing, nothing for ads, nothing for billing, nothing for deal-policy enforcement (that's your CRM-side flow's job).",
"scopes": [
"Contacts (read + write). Read and write Contacts, dedup against existing records, set source attribution and Lead Source.",
"Leads (read + write). Open Leads when the caller isn't ready for a Deal yet, with the right Lead Source pick-list value.",
"Events (read + write). Read availability and write Events on the right team member's calendar; reschedule and flag cancelled the Zoho-native way.",
"Deals (read). Read existing Deals so an inbound call from a customer in pipeline is attached to the right Deal, not orphaned.",
"Users (read). Read your team roster at setup so the AI Receptionist knows who exists and who owns existing records.",
"Settings (read). Read your account-specific pick-list values for Lead Source, Lead Status, and custom enums at setup, so AnyCRM writes only valid values.",
"Not requested: billing / subscription data, Products, Quotes, Invoices, Campaigns, Zoho Mail, Zoho Books, your other Zoho One apps. Deal-creation policy stays inside your CRM's own flow."
],
"surfaceNote": "Same OAuth grant any Zoho Marketplace app uses. Just a smaller surface, scoped to the regional data centre your account lives in. AnyCRM holds the access and refresh tokens (every write is signed by AnyCRM's connected-app credentials, so each Event and record change is attributable to AnyCRM in Zoho's audit log). The LLM never sees the token, and every tool call is logged with the operation name, never the raw payload."
},
"failureModes": [
{
"title": "Duplicate Contacts",
"raw": "Zoho's default Contact dedup is strict. Email-only at the system level, case-sensitive, no automatic dedup on phone. Send the same caller with a slightly different email casing or by phone alone, and you get a second Contact with a different team member Owner and a different timeline. My AI Front Desk runs on a Zapier-style \"Create Contact\" action — a single API call that hands the caller's email straight to Zoho's default dedup. Same caller, slightly different casing? Duplicate. Phone-only? Duplicate. Goodcall writes through a connector that does the same single-step create. Smith.ai's AI tier logs the Contact after the call through a similar one-shot create. None of these can do a \"search-then-write\" because their architecture is one call in, one call out.",
"mcp": "AnyCRM does NOT do a one-shot create. AnyCRM first searches Zoho on a normalised lowercased + trimmed email, then on a normalised phone, then decides whether to update the existing Contact or create a new one (using Zoho's upsert path with both Email and Phone as duplicate-check fields). A returning caller lands on the existing record with a new Note on the timeline, never as a duplicate. This costs us an extra API call per contact-create. We do it anyway, because the alternative is the duplicate-Contact mess Smith.ai, My AI Front Desk, and Goodcall users live with.",
"competitorsAffected": ["My AI Front Desk", "Goodcall", "Smith.ai (AI tier)"]
},
{
"title": "Workflow Rules and Blueprints never fire",
"raw": "Zoho's write endpoints accept an optional trigger array that determines whether your existing Workflow Rules, Blueprints, Approvals, and Assignment Rules fire on the new record. Omit it and the record lands in Zoho silently. No Assignment Rule fires, no Workflow Rule runs, no Blueprint transition triggers. My AI Front Desk's Zapier-style actions have no way to pass that trigger array on writes — Zapier surfaces don't expose it. So every Contact, Lead, and Event lands without firing any of your Zoho automations. Records appear in the UI but never enter your nurture sequence. Goodcall's connector defaults to the same behaviour, because the underlying integration doesn't surface the trigger array either. Smith.ai's AI tier writes through a similar single-step path and inherits the same gap.",
"mcp": "Every AnyCRM write (Contact, Lead, Event, Note) asks Zoho to fire your Workflow Rules, Blueprints, and Approvals by default. The AI Receptionist can't bypass your Zoho automations. New records behave exactly as if a human had created them through the UI. Two operations where Smith.ai/My AI Front Desk/Goodcall do one.",
"competitorsAffected": ["My AI Front Desk", "Goodcall", "Smith.ai (AI tier)"]
},
{
"title": "Events that don't reach the team member's real calendar",
"raw": "Writing an Event to Zoho looks like it creates a calendar event. And it does, but only inside Zoho. Whether it actually syncs to the team member's Google or Outlook calendar depends on the Event being assembled correctly. The right team member set as Host, Participants assembled with the correct entry type per record, and the team member having Calendar Sync enabled in their user profile. My AI Front Desk's Zapier-style \"Schedule Meeting\" action posts whatever it has straight at Zoho — no checking the Host field, no validating the Participants entry types, no confirming the team member actually has Calendar Sync enabled. Goodcall doesn't write a native Zoho Event at all; it writes to a connected scheduler, and then a separate sync tries to mirror it back into Zoho — so the Event either doesn't exist in Zoho, or exists but never syncs to Google or Outlook. Either way, the team member opens their calendar and the meeting isn't there.",
"mcp": "AnyCRM does multiple things in one call: looks up the team member's Zoho user ID, validates the time format Zoho's calendar sync requires, builds the Participants entries with the correct type per record, sets the team member as Host (filtered to users with Calendar Sync enabled at setup), then writes the Event. The meeting lands in Zoho AND on the team member's Google or Outlook calendar atomically. We do four checks where Smith.ai/My AI Front Desk/Goodcall do one. That's why a meeting booked through AnyCRM is never missing from the team member's calendar.",
"competitorsAffected": ["My AI Front Desk", "Goodcall"]
},
{
"title": "Inventing Lead Sources and pick-list values that don't exist in your account",
"raw": "Zoho pick-list fields (Lead Source, Lead Status, custom enums) reject any value not in the configured set. There is no auto-creation. My AI Front Desk's Zapier-style action takes whatever the AI generates and posts it. There is no \"read your portal's real pick-list values first\" step in a Zapier path; it's a single action. So the AI invents a value like \"Hot Lead\" when your account only accepts \"Phone Inquiry\", the write fails with INVALID_DATA (or the field gets silently dropped), and your source-attribution reporting silently breaks. Goodcall's connector hands the value through to Zoho the same way. Smith.ai's AI tier picks values from a generic playbook that doesn't match your account's pick-list. The architecture is one-shot; there is no \"check the portal first\" step.",
"mcp": "AnyCRM reads your account's real pick-list values at setup and bakes them into the AI Receptionist's system prompt as a frozen table. So when the AI Receptionist captures a lead, it CAN ONLY pick from values that actually exist in your account. This is an extra API call 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.",
"competitorsAffected": ["My AI Front Desk", "Goodcall"]
},
{
"title": "Booking the wrong team member's calendar",
"raw": "Zoho happily accepts any user on an Event as Host, including deactivated users, users from another Territory, or users without Calendar Sync enabled. My AI Front Desk's Zapier action takes whichever team-member name the AI generates and posts it — no \"is this person still active?\" check, no \"does this person own the existing Contact?\" check. So an SDR-side qualification call gets booked on the CSM's calendar, or worse, on a deactivated former employee or a user whose Google Calendar sync was disconnected six months ago. Goodcall's scheduler hop assigns based on connector defaults rather than the lane the call actually belongs to. Smith.ai's human receptionists rely on the receptionist's memory of who handles what — fine on a Tuesday morning, less reliable on a Friday at 8pm with a relief receptionist.",
"mcp": "AnyCRM does the heavy work in multiple steps: matches the lane (sales / qualification / customer-success) from the call's intent, looks up the right team member from the AnyCRM team roster, filters out deactivated team members and users without Calendar Sync enabled, AND checks whether the existing Zoho Contact already has an Owner. If the existing Owner contradicts the inferred lane, AnyCRM refuses to overwrite — instead, the AI Receptionist surfaces the conflict so the call respects who is already on the Contact. Smith.ai/My AI Front Desk/Goodcall can't do this because their architecture is one-shot.",
"competitorsAffected": ["Smith.ai (human tier)", "Goodcall", "My AI Front Desk"]
},
{
"title": "Cancelling by DELETE into the Recycle Bin",
"raw": "Issuing a DELETE on a Zoho Event moves the Event to the Recycle Bin for 60 days, then permanently removes it. No reason field exists, no cancellation outcome is recorded, and the Event vanishes from Event-search queries the moment it lands in the bin. My AI Front Desk's Zapier-style cancel action (where it exists at all) issues a single DELETE — that's the only Zoho operation Zapier exposes for it. The Event disappears, the team member gets no signal of WHY it fell through, and \"meetings booked vs cancelled\" reporting breaks because the Event no longer exists to be counted. Goodcall's cancellation goes through its scheduler, not the native Zoho Event — so the scheduler is updated but the Zoho audit trail never reflects the cancellation reason. Smith.ai receptionists ask the caller why, but the cancellation lands as a Note rather than as a properly outcome-flagged Event, so Zoho's reporting doesn't count it correctly.",
"mcp": "AnyCRM's cancellation is multi-step: find the soonest upcoming Event, capture the caller's reason, write the reason as a Note on the linked Contact, AND flag the Event cancelled the Zoho-native way (prefixing the Description so it stays queryable in reporting). The Event stays in Zoho, never in the Recycle Bin, with the reason attached. Three operations where Smith.ai/My AI Front Desk/Goodcall do one (and usually the wrong one).",
"competitorsAffected": ["My AI Front Desk", "Goodcall"]
},
{
"title": "Encoding your deal-creation policy in the prompt or in middleware",
"raw": "My AI Front Desk ships a hardcoded \"Create Deal\" action that fires on every inbound call. There is no \"only create the Deal if the caller is actually ready to buy\" logic — the action is single-step, so every call becomes a stage-1 Deal in the default pipeline, clogging your Zoho forecast with unqualified records. Worse, the moment you change your pipeline structure or your Blueprint stages, you have to go back into Zapier and rebuild the zap. Goodcall's connector applies whatever default behaviour the underlying integration shipped with — change your business, and the connector keeps doing what it did six months ago. Smith.ai's AI tier and human receptionists work from playbooks that drift out of date as your real Zoho policy (Workflow Rules, Blueprints, Assignment Rules) evolves.",
"mcp": "AnyCRM does not encode your deal policy at all. AnyCRM sends a clean lead event straight to Zoho, into the receiving flow we wire up for you at onboarding. YOUR flow decides what happens: new pipeline? Update the flow. New Blueprint stage? Update the flow. New source-tag scheme? Update the flow. AnyCRM's behaviour stays consistent because AnyCRM's job stops at the conversation. Smith.ai/My AI Front Desk/Goodcall can't separate these concerns because their architecture forces business policy into either Zapier middleware or a hardcoded action.",
"competitorsAffected": ["My AI Front Desk", "Goodcall", "Smith.ai (AI tier)"]
},
{
"title": "Web leads and AI Receptionist leads run on two separate conversion-tracking stacks",
"raw": "Smith.ai, My AI Front Desk, and Goodcall all treat phone and chat conversions as separate from web Zoho Web Form / SalesIQ conversions. None of them fire a real conversion event into Google Ads, Facebook Ads, or LinkedIn Ads when the AI Receptionist closes a call. So your Ad platforms only see the website form-fills, the bidding optimises for that (lower-intent) audience, your Cost per Lead looks deceptively low, ROAS reporting becomes a fiction, and the high-intent traffic that picks up the phone stays invisible to your Ad stack. Worse, when these competitors DO fire any tracking, it's client-side — blocked by ad-blockers and degraded under iOS / Safari tracking restrictions.",
"mcp": "AnyCRM runs your website conversions AND your AI Receptionist conversions through the same Conversion Lift pipeline. Same event shape, same source taxonomy, same delivery to your CRM, AND the same server-side conversion event into Google Ads, Facebook Ads, and LinkedIn Ads — using the verified origin of your registered domain. Server-side means it can't be blocked client-side and doesn't degrade on iOS or Safari. The result is what Smith.ai/My AI Front Desk/Goodcall structurally can't deliver: lower Cost per Lead, higher ROAS, smaller CAC, complete analytics funnels, and attribution that doesn't fragment between web and voice.",
"competitorsAffected": ["Smith.ai", "My AI Front Desk", "Goodcall"]
}
],
"failureModesMeta": {
"headline": "How most AI Receptionists built on Smith.ai, My AI Front Desk, or Goodcall fail for B2B SaaS sales teams, agencies, consultancies, manufacturers, and professional services that use Zoho CRM. And why AnyCRM can't.",
"lede": "Most AI Receptionists fail on Zoho in the same handful of ways. Duplicate Contacts, Workflow Rules and Blueprints that never fire, Events that never sync to the team member's real calendar, invented Lead Sources and pick-list values, the wrong team member's calendar, DELETEs that empty into the Recycle Bin, hardcoded deal-creation 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 deal-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.",
"closer": "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."
},
"comparisonTable": {
"headline": "AnyCRM vs Smith.ai, My AI Front Desk, Goodcall on Zoho CRM",
"columns": [
{ "key": "anycrm", "label": "AnyCRM" },
{ "key": "smithai", "label": "Smith.ai" },
{ "key": "myaifrontdesk", "label": "My AI Front Desk" },
{ "key": "goodcall", "label": "Goodcall" }
],
"rows": [
{
"capability": "Live Zoho Event booked DURING the call",
"anycrm": "Yes. Native Zoho Event, team-member-matched, calendar-synced.",
"smithai": "No. Note logged on the Contact for manual follow-up.",
"myaifrontdesk": "Partial. Zapier-style \"Schedule Meeting\" without structural detail for calendar sync.",
"goodcall": "Partial. Scheduler hop, not a native Zoho Event."
},
{
"capability": "Dedup-before-write on email and phone",
"anycrm": "Yes. Always.",
"smithai": "Manual.",
"myaifrontdesk": "No. Zoho's default email-only dedup, single-step.",
"goodcall": "No published guarantee."
},
{
"capability": "Preserves existing Zoho Owner on returning callers",
"anycrm": "Yes. Existing Owner is sacred.",
"smithai": "Implicit, not guaranteed.",
"myaifrontdesk": "No. Can overwrite via the update action.",
"goodcall": "Depends on the underlying connector's defaults."
},
{
"capability": "Routes by lane (AE / SDR / CSM)",
"anycrm": "Yes. Lane is part of AnyCRM's team roster.",
"smithai": "Manual, depends on the receptionist.",
"myaifrontdesk": "No.",
"goodcall": "No."
},
{
"capability": "Lead Source, Lead Status, and Event types frozen from your real Zoho values",
"anycrm": "Yes. Read at setup, baked into the prompt as a frozen table.",
"smithai": "Not API-enforced.",
"myaifrontdesk": "No. Writes can fail with INVALID_DATA on unknown values.",
"goodcall": "No structural guard."
},
{
"capability": "Workflow Rules, Blueprints, and Assignment Rules fire on every write",
"anycrm": "Yes. Trigger requested by default.",
"smithai": "Inconsistent.",
"myaifrontdesk": "No. Zapier surfaces don't expose the trigger array.",
"goodcall": "No. Connector default."
},
{
"capability": "Cancellation preserves the audit trail (Zoho-native, not DELETE into Recycle Bin)",
"anycrm": "Yes. Zoho-native cancellation, Event stays queryable.",
"smithai": "Manual.",
"myaifrontdesk": "No. DELETE strips the Event into the Recycle Bin.",
"goodcall": "No. Cancellation happens in the scheduler, not the Zoho Event."
},
{
"capability": "Reschedule in place (no cancel-then-rebook)",
"anycrm": "Yes.",
"smithai": "Manual.",
"myaifrontdesk": "No.",
"goodcall": "No."
},
{
"capability": "Deal-creation policy delegated to YOUR CRM's own flow",
"anycrm": "Yes. Lead event delivered straight into Zoho, into the receiving flow we wire up at onboarding.",
"smithai": "No. Policy lives in Zapier or in the receptionist's training.",
"myaifrontdesk": "No. Hardcoded \"Create Deal\" action.",
"goodcall": "No. Connector-default behaviour."
},
{
"capability": "Unified conversion pipe: web forms AND AI Receptionist → CRM + ad platforms server-side",
"anycrm": "Yes. Same shape, same source taxonomy, same server-side delivery to your CRM and your ad platforms.",
"smithai": "No. Web and voice run on separate stacks.",
"myaifrontdesk": "No. Web and voice run on separate stacks.",
"goodcall": "No. Web and voice run on separate stacks."
},
{
"capability": "Server-side conversion events sent to Google Ads, Facebook Ads, and analytics (origin = your registered domain)",
"anycrm": "Yes. Every call and chat lead lands server-side.",
"smithai": "No.",
"myaifrontdesk": "No.",
"goodcall": "No."
},
{
"capability": "Source attribution stays consistent across web and voice",
"anycrm": "Yes. AI Receptionist Call, AI Receptionist Web, plus your Zoho Web Form identifiers.",
"smithai": "Manual / inconsistent.",
"myaifrontdesk": "No standardised taxonomy.",
"goodcall": "Whatever the underlying connector defaults to."
},
{
"capability": "Scale ceiling",
"anycrm": "Bounded by Zoho API limits, not by staffing.",
"smithai": "Bounded by human receptionist staffing.",
"myaifrontdesk": "Bounded by Zapier rate limits and action contracts.",
"goodcall": "Bounded by the scheduler-and-sync hop."
}
],
"footer": "Every row in this table is solved one layer down inside AnyCRM. Not in the prompt. Not by humans. Not by Zapier."
},
"faqs": [
{
"q": "Does this actually work with my Zoho CRM account?",
"a": "Yes. AnyCRM uses Zoho's official API via a standard OAuth grant, routed to whichever regional data centre your account lives in (.com / .eu / .in / .com.au / .jp / .ca / .sa). Every captured caller lands as a Contact (or a Lead, when no Account exists yet) with the right team member Owner, the right Lead Source pick-list value, and a first Note from the call. Meetings land as native Zoho Events on the right team member's calendar, with the Contact in Participants and the Event tied to the related Lead, Contact, or Deal so it shows on every module view."
},
{
"q": "Will it create duplicate Contacts in Zoho?",
"a": "No. AnyCRM resolves the existing Contact first (normalising email and phone, using Zoho's upsert path with both Email and Phone as duplicate-check fields) before writing. A returning caller becomes a new Note on the existing record, never a second Contact, and the existing team member Owner is preserved."
},
{
"q": "Can it route different leads to different team members?",
"a": "Yes. AnyCRM reads your Zoho team roster once at setup. Every active team member, with their lane (AE / SDR / CS), role, profile, territory, and timezone. Sales-side, qualification-side, and customer-side calls each route differently, and existing record ownership in Zoho is always preserved."
},
{
"q": "Where do the meetings actually live, calendar or Zoho?",
"a": "Both. AnyCRM writes the meeting as a native Zoho Event with the right team member as Host, the Contact in Participants, and the right timing. Which makes Zoho's Google or Outlook calendar sync fire automatically when the team member has Calendar Sync enabled. You see one Event in Zoho, one calendar invite on the team member's calendar, one source-attributed Contact."
},
{
"q": "Can it cancel or reschedule a meeting from a phone call?",
"a": "Yes. The caller gives their email, AnyCRM finds the soonest upcoming Zoho Event linked to the matching Contact, the AI Receptionist reads it back, and AnyCRM either reschedules in place or flags the Event cancelled the Zoho-native way (with the reason captured as a Note on the linked Contact). Never a DELETE that would send the Event to the Recycle Bin and erase the audit trail."
},
{
"q": "What if a caller has two upcoming Events in Zoho?",
"a": "AnyCRM returns every upcoming Event for that Contact (subject, date, time, team member Host) and the AI Receptionist asks which one to change before doing anything. It never assumes."
},
{
"q": "Does it handle timezones correctly?",
"a": "Yes. The AI Receptionist confirms the caller's country / timezone, AnyCRM converts the meeting time into the format the Zoho Event API requires, and the AI Receptionist reads the time back to the caller in their local timezone. No customer-facing UTC strings, no off-by-an-hour confirmations."
},
{
"q": "Does it create Leads or Contacts?",
"a": "It depends on the call. Qualification-stage callers land in the Leads module with your configured Lead Source and Lead Status. Existing customers update the Contact and append a Note. Hot inbound asking to buy can be flagged for direct Contact creation at setup. AnyCRM uses the lead_intent hint inferred from the call so the right record type lands in the right module."
},
{
"q": "Will my existing Workflow Rules, Blueprints, and Assignment Rules still fire?",
"a": "Yes. Every AnyCRM write asks Zoho to fire your Workflow Rules, Blueprints, Approvals, and Assignment Rules by default. Records created by the AI Receptionist behave exactly as if a human had created them through the UI. Assignment Rules route, Workflow Rules send emails, Blueprints advance the record through your defined state machine."
},
{
"q": "How does this relate to Zia, Zoho's own AI?",
"a": "Zia is Zoho's in-CRM AI assistant. It does lead scoring, prediction, recommendations, generative AI for record summaries, email intelligence, call transcription, and Vision AI for image fields. What Zia does NOT do: pick up your phone when a stranger calls, qualify the caller, route them to the right team member, book a native Zoho Event during the call, AND fire a server-side conversion event to your Google / Facebook / LinkedIn Ads. AnyCRM is the conversation-and-conversion-tracking layer in front of Zoho. The two are complementary. Zia makes the data inside Zoho smarter. AnyCRM makes sure the conversation that happened at 7pm on a Friday actually became a Zoho record and a tracked Ads conversion."
},
{
"q": "Does it create Deals?",
"a": "Not directly. AnyCRM stays focused on the conversation surface: capturing the Contact or Lead, matching the right team member, booking the meeting. Deal creation is YOUR business policy, and that policy lives inside Zoho, in the receiving flow we wire up for you at onboarding. Every contact-create and every meeting-book in AnyCRM sends a lead event straight into that flow (tagged with source AI Receptionist Call or AI Receptionist Web). Your flow decides which pipeline, which Blueprint stage, which Workflow Rule, which Assignment Rule. AnyCRM doesn't try to encode policy that will drift out of date the moment your business changes."
},
{
"q": "How does the conversion tracking work?",
"a": "Every lead event AnyCRM produces (from a phone call, a chat conversation, OR a Zoho Web Form / SalesIQ chatflow) flows through a single conversion pipe. It lands in Zoho for business logic. AND it fires server-side into Google Ads, Facebook Ads, and your analytics platform, using the origin of the domain you registered with AnyCRM. Server-side means the conversion can't be blocked by ad-blockers and doesn't degrade under iOS / Safari tracking restrictions. The result: higher ROAS, lower ad costs, enriched analytics, and attribution that doesn't fragment between web and voice. As far as we can tell, none of our competitors have built this yet."
},
{
"q": "What about my existing website forms? Do they go through the same pipe?",
"a": "Yes — that's the whole point. Zoho Web Forms / SalesIQ chatflows AND the AI Receptionist produce the same lead-event shape with the same source taxonomy. They land in the same place in Zoho, and they fire the same server-side conversion event into your ad platforms. So your bid strategy optimises against unified, real conversions instead of fragmenting across web-only and voice-only stacks."
},
{
"q": "How long until it's actually capturing leads into Zoho?",
"a": "Most teams are live the same afternoon. The OAuth grant takes a minute. The team roster, pick-list values, and Event-types import is automatic. We wire up the lead-receiving flow inside Zoho during onboarding. The phone integration is usually under an hour. Web chat is faster."
}
]
}