{
"icp": "sales teams already running their pipeline on Pipedrive — B2B SaaS, agencies, consultancies, and professional services that close on the phone",
"capabilities": {
"availability": {
"headline": "Captures the website inquiry or caller as a Pipedrive Person, 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 Pipedrive Person (with the right owner, the right Organization, and a source value frozen from your real account). When they want a meeting, AnyCRM creates a Pipedrive Activity on the matched team member's calendar. AND the same lead event flows through one unified pipe (with the same shape, same source attribution, and same server-side conversion path used by your website forms) so your CRM business logic and your Google / Facebook / LinkedIn Ads both stay in sync.",
"cards": [
{
"num": "A.01",
"title": "Every caller becomes a Pipedrive Person, not a stray missed call",
"body": "The AI Receptionist captures first name, last name, email, phone, Organization, and call intent. Then AnyCRM writes the record into Pipedrive as a Person with the right team member as owner and the call summary attached as a Note. Before the call has ended."
},
{
"num": "A.02",
"title": "Books meetings as native Pipedrive Activities",
"body": "The meeting lands as a Pipedrive Activity of the right type (Meeting, Call, Demo), with the assigned team member as organizer, the Person as participant, and a duration that matches your configured Activity type. So it shows on the pipeline view and the team member's calendar exactly the way Pipedrive expects."
},
{
"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 Person-create and every Activity-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 Lead in the Leads Inbox, open the Deal, set the stage, assign the pipeline, route the workflow. We set up the receiving end inside your CRM for you during onboarding, tuned to your industry and your team 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 Persons, creates or links the Organization, sets the team member owner (matched from your team), writes the Activity so Pipedrive's calendar sync to Google/Outlook fires automatically, 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": [
"getPipedriveAvailability",
"createPipedriveContactAppointment"
],
"curl1Path": "/mcp/tools/getPipedriveAvailability",
"curl2Path": "/mcp/tools/createPipedriveContactAppointment",
"pipeIntro": "Most businesses run two completely separate conversion-tracking stacks: one for the website (forms, LeadBooster 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 / LeadBooster 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 your CRM, into the receiving flow we wired up for you at onboarding. Your business logic decides what happens next: which Lead, which Deal, which pipeline, which stage, which workflow, which team channel. 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, LeadBooster chat, phone call, AI Receptionist chat) feeds the same event shape into your analytics, so funnels are complete instead of half-blind.",
"Correct attribution. A caller who first saw a Google Ad, then visited the site, then phoned three days later gets attributed end-to-end. Voice traffic stops being invisible to your marketing stack.",
"One source of truth for lead policy. Your CRM's flow owns 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 source to apply. That approach breaks the moment your business changes, and it ignores the conversion-tracking surface entirely. AnyCRM inverts the responsibility. AnyCRM stays focused on the conversation (capture, dedup, route, book, cancel) and delivers a clean lead event to the two destinations that matter: your CRM (for 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 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 and LeadBooster chats. 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 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, CRM, and Analytics.",
"body": "AnyCRM doesn't just track AI Receptionist conversions. It also runs your existing website forms and LeadBooster chatflows through the same pipeline. So a lead from a Google Ad that fills a form on your website AND a lead from a Facebook Ad that called the AI Receptionist three days later both end up tagged, attributed, and counted in exactly the same way. Your Ads platform stops double-counting, your analytics stop fragmenting, and your CRM stops being half-blind to where your leads actually came from."
}
],
"apiSummary": "Every Person-create and Activity-book fires through AnyCRM's Conversion Lift pipeline. The lead event lands inside your CRM for business logic, AND fires a real conversion event server-side into Google Ads, Facebook Ads, and LinkedIn Ads using the verified origin of your registered domain. Server-side means the conversion can't be blocked by ad-blockers, doesn't degrade on iOS or Safari, and arrives with full attribution context so the Ad platforms' bidding algorithms can re-train on it. Your existing website forms and LeadBooster chats 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 form-fills and assume that's the full picture. With AnyCRM running, you'll also see (say) 60 phone calls and 45 web chats the AI Receptionist handled, all flowing into Google Ads as real conversions. Suddenly Google sees 185 conversions a month instead of 80. It re-trains on that bigger, better signal. Within weeks, the bidding finds you more of the right kind of buyer. Same $5,000 spend, more real conversations, lower Cost per Lead, higher revenue. That is what \"AI Receptionist with AnyCRM\" actually means for the bottom line. Not just \"it answers the phone.\"",
"tools": [
"createOrUpdatesPipedriveContact",
"createPipedriveContactAppointment"
]
},
"lifecycle": {
"headline": "Manages the full Activity lifecycle inside Pipedrive 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 Pipedrive Activity in place. Cancellations follow Pipedrive's own idiom. Outcome flagged, reason captured on the Note timeline. Instead of deleting the Activity and erasing the audit trail, you get crystal clarity on when a Pipedrive Activity was created, and when and why it was updated by your AI Receptionist.",
"cards": [
{
"num": "B.01",
"title": "Finds the Activity by email in a single step without needing an Activity ID",
"body": "Customers DO NOT quote Activity 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 Activity linked to the matching Person. And the AnyCRM response forces the AI Receptionist to be human. It reads back the subject, date, time, and team member organizer before changing anything."
},
{
"num": "B.02",
"title": "Reschedules in place and keeps the Activity data clean",
"body": "Rescheduling updates the existing Activity in a single confirmation. No cancel-then-rebook round-trip means the Activity history, the Deal or Lead link, and the calendar invite all stay intact. Failed reschedules leave the original Activity untouched."
},
{
"num": "B.03",
"title": "Cancels without erasing the audit trail",
"body": "When a caller cancels, AnyCRM flags the Activity cancelled the Pipedrive-native way. Then it writes the caller's reason as a Note on the Person and on the Activity, instead of issuing a delete that strips WHY the meeting fell through. This lets you intuitively track changes for Pipedrive Activities created or updated by your AI Receptionist."
}
],
"apiSummary": "AnyCRM's search, reschedule, and cancel all accept just an email. The soonest upcoming Activity linked to the matching Person is resolved inside AnyCRM. No Activity IDs at the AI Receptionist layer.",
"tools": [
"searchPipedriveAppointments",
"reschedulePipedriveAppointment",
"cancelPipedriveAppointment"
],
"curl1Path": "/mcp/tools/searchPipedriveAppointments",
"curl2Path": "/mcp/tools/reschedulePipedriveAppointment",
"curl3Path": "/mcp/tools/cancelPipedriveAppointment"
},
"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": "Pipedrive accounts run on owners, visibility groups, and pipelines. At setup AnyCRM imports your Pipedrive team into its database and enriches each team member with lane, expertise, languages, timezone, and bookable Activity-type duration. The AI Receptionist then routes each caller to the team member who actually handles that lane. Existing Person ownership in Pipedrive 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 Person is always preserved."
},
{
"num": "C.02",
"title": "Honours existing assigned owners in Pipedrive",
"body": "If a Person already has an owner in Pipedrive, the AI Receptionist doesn't reassign them. The Activity and the Note attach to the existing Person under the existing owner. No orphaned duplicate, no lead poached off a team member's pipeline."
},
{
"num": "C.03",
"title": "Matches fresh inbound callers and website chatters to the right person on the team",
"body": "New leads with no existing Pipedrive Person get matched to a team member on the lane you've designated (AE, SDR, CS), honouring the criteria you set in AnyCRM for matching a lead to a team member. The AI Receptionist doesn't fight the rules you already use."
}
],
"apiSummary": "Team details live in AnyCRM's database, pulled once from Pipedrive at setup, enriched with lane, expertise, languages, timezone, and Activity-type duration (valuable context for the AI Receptionist that Pipedrive's user object doesn't carry by default). At runtime, one read of the team roster matches caller → lane → team member. New Persons get assigned to the right team member. Existing Persons keep theirs. AnyCRM does NOT cache your deal pipelines, your stages, or your Lead Sources beyond what's needed to write valid records. That policy stays inside your CRM, where it belongs.",
"tools": [
"listPipedriveTeamMembers",
"getPipedriveUserProfile"
],
"curl1Path": "/mcp/tools/listPipedriveTeamMembers",
"curl2Path": "/mcp/tools/getPipedriveUserProfile"
}
},
"setup": {
"headline": "Setup in 3 steps. Battle-tested on real Pipedrive accounts.",
"lede": "You connect Pipedrive once. AnyCRM imports your team, your pipelines, your Activity types, and your Lead Sources. AnyCRM also wires up the receiving end inside your CRM so lead events from the AI Receptionist land where your business logic can act on them. Then the AI Receptionist starts capturing leads and booking meetings the same afternoon. No middleware. No prompt-engineering by you.",
"steps": [
{
"num": "S.01",
"title": "Connect Pipedrive (OAuth, 60 seconds)",
"body": "Authorize AnyCRM on your Pipedrive account via the standard OAuth grant in your Marketplace Apps page. AnyCRM scopes to the least amount of access needed for the booking lifecycle. Nothing for billing, nothing for products, nothing for mail sync. You can always revoke permissions at any time from your account-level Marketplace Apps page. Every update to your Pipedrive 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 Activity types and Lead Sources. Wire up your CRM's lead-receiving flow.",
"body": "AnyCRM imports every active Pipedrive user as a bookable team member with lane, expertise, languages, timezone, and Activity-type duration. AnyCRM also freezes the Activity 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 your CRM 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, or Lead Inbox routing. Your CRM 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 Pipedrive 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 Pipedrive's Scheduler + Web Forms + LeadBooster?",
"body": "Pipedrive's Scheduler, Web Forms, and LeadBooster chatbot 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 Person record. A Web Form sits in the Leads Inbox until someone reads it. LeadBooster runs on the website only, with no voice surface. And Pipedrive's own AI Sales Assistant (the OpenAI-powered insight feature inside Pipedrive) answers questions about your existing data — it doesn't answer the phone. 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 Pipedrive Activity on the right team member's calendar, writes a clean Person (with the source set to AI Receptionist Call or AI Receptionist Web and a call summary as the first Note), AND sends the same lead event straight into your CRM's downstream business logic plus your ad platforms server-side. So your Pipedrive workflows, 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, Organization linking, Activity-type resolution, due_date / due_time / duration math, participants vs attendees assembly, error handling, lead-event delivery into your CRM, and server-side conversion tracking into your ad platforms. All of it happens before the LLM ever sees a response. So the AI Receptionist reasons over clean, AI-aligned payloads instead of raw CRM internals.",
"enrichmentExamples": [
{
"title": "Capturing a new lead",
"raw": "Writing a Person straight into Pipedrive looks simple. But Pipedrive does not dedup for you. Send the same caller twice and you end up with two Persons, two owners, two pipelines, two timelines. There is a separate merge operation for cleanup, but you have to know the duplicate exists, find both records, decide which side wins, and call it explicitly. Emails and phones are arrays of objects (with value, primary, label) — naive integrations that pass an email as a plain string silently fail validation. And if you want the inquiry to land in the Leads Inbox instead of the Persons list, it takes a second linked record. Nothing in raw Pipedrive fires a server-side conversion event to your ad platforms, so call-driven and chat-driven leads never get optimised for.",
"mcp": "createOrUpdatesPipedriveContact accepts name, email, phone, note, organization, lead_intent, plus the matched team member. AnyCRM handles dedup on email then phone, picks the surviving record (or creates a new one with the right values in the right order), creates or links the Organization, sets the team member owner, appends the call summary as a Note, optionally opens a Lead in the Leads Inbox, 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."
},
{
"title": "Booking the meeting",
"raw": "Creating an Activity directly against Pipedrive is a tight contract. The Activity type has to match a real type your admin defined (not free text), time is split across separate date / time / duration fields with no timezone parameter (Pipedrive interprets in the team member's timezone, not the invitee's), and the meeting only syncs to the team member's Google/Outlook calendar when the team member is on the Activity as organizer AND the Person is on it as participant. Get any of these wrong and the Activity writes into Pipedrive but never lands on the team member's actual calendar.",
"mcp": "createPipedriveContactAppointment takes email, scheduled_datetime (a naive date and time, no offset needed), invitee_timezone, and activity_type_key. AnyCRM resolves the right team member from the lane, handles the timezone and duration math, builds participants and attendees correctly so calendar sync fires, links the Activity to the Lead or Deal when one exists, 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."
},
{
"title": "Cancelling with a reason",
"raw": "Deleting an Activity in Pipedrive soft-trashes it for 30 days and then removes it permanently. There is no reason field, no cancellation outcome, no audit hook. The Activity disappears from the team member's calendar and the deal view, and after 30 days it's gone forever. Pipedrive's own UI convention for a cancelled meeting is to mark the Activity done with a cancellation prefix on the subject and the reason captured on the Note timeline — so reporting still counts it and the audit trail survives.",
"mcp": "cancelPipedriveAppointment takes email and reason. AnyCRM resolves the soonest upcoming Activity, records the reason as a Note on both the Activity and the linked Person, and flags the Activity cancelled the Pipedrive-native way. All in one AnyCRM call. No soft-delete, full audit trail, Activity stays queryable in the team member's reporting."
}
],
"alignmentSummary": "Every AnyCRM tool for Pipedrive follows the same AI-alignment contract, so the AI Receptionist never has to think about transport:",
"alignment": [
"Naive datetimes in, Pipedrive-native shape out. The AI Receptionist passes 2026-05-15T11:00:00 and a timezone string. AnyCRM converts it into whatever shape the Pipedrive Activity requires.",
"Email is the identity. Cancel and reschedule never need an Activity ID at the AI Receptionist layer. Email and soonest-upcoming resolves inside AnyCRM.",
"Lead Source and Activity type come from setup, not the LLM. The AI Receptionist can't invent a Lead Source or an Activity type. It inherits the values you configured at setup.",
"Existing team member owners are sacred. If a Pipedrive Person already has an owner, AnyCRM preserves it. New Persons only get the matched team member when no owner exists.",
"Cancellation preserves the audit trail. Pipedrive's idiom for cancelled meetings is honoured so reporting stays accurate and the audit trail survives the 30-day soft-delete window.",
"Every lead event leaves AnyCRM in two places at once. Your CRM gets the lead event so your business logic can run. Your ad platforms get the server-side conversion event so bidding optimises against real conversations. Both happen on the same AnyCRM call. No race conditions, no missing events.",
"Flat, deterministic shapes. Every AnyCRM response has the same top-level keys across every tool, so the AI Receptionist's prompt never grows with edge-case branching.",
"Errors are messages, not codes. An error from Pipedrive 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 Pipedrive Activity is preserved. The customer never ends up with nothing."
],
"industryLine": "Currently running for B2B SaaS sales teams, agencies, consultancies, and professional services. Anyone whose pipeline is in Pipedrive 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 Pipedrive, 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 Pipedrive users once and writes each one into its database keyed by crm_user_id (with name, role, lane, timezone, default visibility group).",
"Per-team-member Activity types. For each team member AnyCRM resolves the Activity types they actually book and the duration per type. One call per person, cached.",
"Lane visibility. Each lane is flagged Public, Private or Ignored. The AI Receptionist only routes to and books on Public lanes. You toggle this in the AnyCRM dashboard without re-deploying.",
"Lead-event receiving flow inside your CRM. During onboarding we wire up the flow inside your CRM that receives lead events from AnyCRM. That's where your deal-creation and Leads-Inbox routing policy lives. AnyCRM doesn't try to own it.",
"System-prompt assembly. The cached team roster, lane, and Activity-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 Activity 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 Activity type → that team member's calendar availability → a booked Pipedrive Activity on the right team member's calendar → a lead event delivered straight into your CRM → a server-side conversion event in your ad platforms. Without a single team roster query during the call."
}
},
"privacy": {
"headline": "Your Pipedrive data passes through AnyCRM. It doesn't stick.",
"lede": "AnyCRM processes your Pipedrive 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. Persons, Leads, Activities, Notes. All of it stays in Pipedrive, owned by your Pipedrive 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 Person records, no caller PII."
},
{
"kind": "not-stored",
"label": "What AnyCRM doesn't",
"body": "Caller names, emails, phone numbers, Pipedrive Person IDs, your Activity types beyond their identifiers, 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 Pipedrive account and in whatever systems your CRM's flow forwards lead events to. Persons, Leads, Activities, Notes all live in Pipedrive. 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."
},
{
"kind": "revoke",
"label": "Revocation",
"body": "Revoke the AnyCRM OAuth grant in your Pipedrive account-level Marketplace Apps page 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": "Pipedrive uses OAuth scopes. AnyCRM requests only the smallest set required for the contact + meeting capture lifecycle. Nothing for billing, nothing for products, nothing for mail sync, nothing for deal-policy enforcement (that's your CRM's job).",
"scopes": [
"Contacts (read + write). Read and write Persons, dedup against existing records, append Notes.",
"Activities (read + write). Read availability and write Activities on the routed-to team member's calendar; update to reschedule and cancel.",
"Leads (read + write). Open Leads in the Leads Inbox when the caller isn't ready for a Deal yet.",
"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 Persons.",
"Not requested: billing / subscription data, products, smart docs, mail sync, your other integrations (deal-creation policy stays inside your CRM's own flow)."
],
"surfaceNote": "Same OAuth grant any Pipedrive Marketplace app uses. Just a smaller surface. AnyCRM holds the access and refresh tokens (every write is signed by AnyCRM's connected-app credentials and stamped with an origin_id, so each Lead and Activity change is attributable to AnyCRM in Pipedrive's audit trail). The LLM never sees the token, and every tool call is logged with the operation name, never the raw payload."
},
"failureModes": [
{
"title": "Duplicate Persons",
"raw": "Pipedrive does NOT dedup for you. A single create call against the Persons endpoint will happily produce a second record for the same caller — same email, same phone, different identifier. My AI Front Desk runs on a Zapier-style \"Update Contact\" action — a single API call that hands the caller's email straight to Pipedrive without a search-then-write step. Same caller, slightly different casing? Duplicate. Phone-only? Duplicate. Goodcall's Pipedrive integration writes through a connector that does the same single-step create. Smith.ai's AI Receptionist creates or updates lead records after the call through a similar one-shot create (the integration is marketed as \"updates contacts\" with no published rule about search-first dedup). 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 Pipedrive on a normalised lowercased + trimmed email, then on a normalised phone, then decides whether to update the existing Person or create a new one. 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 Person-create. We do it anyway, because the alternative is the duplicate-Person mess Smith.ai, My AI Front Desk, and Goodcall users live with. We do two checks where they do one.",
"competitorsAffected": ["My AI Front Desk", "Goodcall", "Smith.ai (AI tier)"]
},
{
"title": "Activities that don't reach the team member's real calendar",
"raw": "Writing an Activity to Pipedrive looks like it creates a calendar event. And it does, but only inside Pipedrive. Whether it actually syncs to the team member's Google/Outlook calendar depends on the Activity being assembled correctly — the team member as organizer, the Person as participant, the right Activity type, the right time split across date / time / duration. My AI Front Desk's Zapier-style \"Create Activity\" action posts whatever it has straight at Pipedrive — no checking whether the participants vs attendees arrays are assembled correctly, no validating the Activity type, no confirming the team member actually has a connected calendar. Goodcall describes \"scheduling appointments\" against Pipedrive via its scheduler / Zapier path, so the appointment either doesn't exist as a Pipedrive Activity at all, or exists but never syncs to Google/Outlook. Smith.ai's AI tier creates lead records and notes after the call — not a live Pipedrive Activity with calendar sync. Either way, the team member opens their calendar Tuesday morning and the 10am demo isn't there.",
"mcp": "AnyCRM does multiple things in one call: looks up the team member from the lane, validates the time format Pipedrive's calendar sync requires, splits it across date / time / duration in the team member's timezone, builds participants and attendees correctly (Person in participants, team member as organizer in attendees), then writes the Activity. The Activity lands in Pipedrive AND on the team member's Google/Outlook calendar atomically. We do four checks where Smith.ai/My AI Front Desk/Goodcall do one. That's why an Activity booked through AnyCRM is never missing from the team member's calendar.",
"competitorsAffected": ["My AI Front Desk", "Goodcall", "Smith.ai (AI tier)"]
},
{
"title": "Inventing Activity types and Lead Sources that don't exist in your account",
"raw": "Pipedrive's Activity types and Lead Sources are account-specific — the actual values differ from account to account, and Activity-type identifiers are auto-generated when your admin creates a type. My AI Front Desk's Zapier-style action takes whatever the AI generates and posts it. There is no \"read your account's real Activity types first\" step in a Zapier path; it's a single action. So the AI invents an Activity type like \"Demo Call\" when your account only has \"product_demo,\" the write fails (or worse, the Lead Source comes through as junk free text), and your reporting silently breaks. Goodcall's connector hands the value through to Pipedrive the same way. Smith.ai doesn't book Activities live — but where the integration writes Lead Sources, the values aren't enforced against your account-specific list. The architecture is one-shot; there is no \"check the account first\" step.",
"mcp": "AnyCRM reads your account's real values at setup, in a separate call to Pipedrive, 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 Activity types and Lead Sources that actually exist in your account. This is two API calls at setup time that Smith.ai, My AI Front Desk, and Goodcall don't make — and it's the difference between writes that always succeed and writes that silently rot your reporting.",
"competitorsAffected": ["My AI Front Desk", "Goodcall"]
},
{
"title": "Booking the wrong team member's calendar",
"raw": "Pipedrive happily accepts any team member on an Activity, including deactivated team members or team members in another visibility group whose calendar isn't connected. 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 Person?\" check. So an SDR-side qualification call gets booked on the CSM's calendar, or worse, on a deactivated former employee. 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 checks whether the existing Pipedrive Person 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 Person. 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 deletion instead of by outcome",
"raw": "Deleting an Activity in Pipedrive soft-trashes it for 30 days and then permanently removes it. No reason, no cancellation outcome, no audit trace. My AI Front Desk's Zapier-style cancel action (where it exists at all) issues a single delete — that's the only operation Zapier exposes for it. The Activity vanishes, the team member gets no signal of WHY it fell through, and \"meetings booked vs cancelled\" reporting breaks because the Activity no longer exists to be counted. Goodcall's cancellation goes through its scheduler, not the Pipedrive Activity — so the scheduler is updated but the Pipedrive timeline 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 Activity, so Pipedrive's reporting doesn't count it correctly.",
"mcp": "AnyCRM's cancellation is multi-step: find the soonest upcoming Activity, capture the caller's reason, write the reason as a Note on both the Activity and the linked Person, AND flag the Activity cancelled the Pipedrive-native way. The Activity stays on the timeline, queryable in reporting, 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", "Smith.ai"]
},
{
"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 — it's the headline capability on their Pipedrive integration page. 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 forecast with unqualified records that distort forecasting. Worse, the moment you change your pipeline structure or add a new stage, 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 CRM policy evolves.",
"mcp": "AnyCRM does not encode your deal policy at all. AnyCRM sends a clean lead event straight to your CRM, into the receiving flow we wire up for you at onboarding. YOUR flow decides what happens: Lead in the Leads Inbox? Deal in pipeline 2 at stage 1? Different routing for hot inbound? Update the flow. New stage? 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 form / LeadBooster 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. Pipedrive's own AI Sales Assistant doesn't fix this either; it's a pipeline-insight feature, not a conversion-tracking layer.",
"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, and professional services that use Pipedrive. And why AnyCRM can't.",
"lede": "Most AI Receptionists fail on Pipedrive in the same handful of ways. Duplicate Persons, Activities that never sync to the team member's real calendar, invented Activity types and Lead Sources, the wrong team member's calendar, deletions that destroy the audit trail, 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 Pipedrive",
"columns": [
{ "key": "anycrm", "label": "AnyCRM" },
{ "key": "smithai", "label": "Smith.ai" },
{ "key": "myaifrontdesk", "label": "My AI Front Desk" },
{ "key": "goodcall", "label": "Goodcall" }
],
"rows": [
{
"capability": "Live Pipedrive Activity booked DURING the call",
"anycrm": "Yes. Native Pipedrive Activity, team-member-matched, calendar-synced.",
"smithai": "No. Lead record + call summary Note logged for manual follow-up.",
"myaifrontdesk": "Partial. Zapier-style \"Create Activity\" without structural detail for calendar sync.",
"goodcall": "Partial. Scheduler hop, not a guaranteed native Pipedrive Activity."
},
{
"capability": "Dedup-before-write on email and phone",
"anycrm": "Yes. Always.",
"smithai": "Implicit, not guaranteed.",
"myaifrontdesk": "No. Zapier \"Update Contact\" is single-step.",
"goodcall": "No published guarantee."
},
{
"capability": "Preserves existing Pipedrive owner on returning callers",
"anycrm": "Yes. Existing owner is sacred.",
"smithai": "Implicit, not guaranteed.",
"myaifrontdesk": "No. Can overwrite.",
"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": "Activity types & Lead Sources frozen from your real account values",
"anycrm": "Yes. Read at setup, baked into the prompt as a frozen table.",
"smithai": "Not API-enforced.",
"myaifrontdesk": "No. Writes can fail on unknown values.",
"goodcall": "No structural guard."
},
{
"capability": "Cancellation preserves the audit trail (outcome-flagged, not deleted)",
"anycrm": "Yes. Pipedrive-native cancellation.",
"smithai": "Manual. Note rather than outcome flag.",
"myaifrontdesk": "No. Deletion soft-trashes the timeline.",
"goodcall": "No. Cancellation happens in the scheduler, not the Activity."
},
{
"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 your CRM, 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 web form identifiers.",
"smithai": "Manual / inconsistent.",
"myaifrontdesk": "No standardised taxonomy.",
"goodcall": "Whatever the underlying connector defaults to."
},
{
"capability": "Scale ceiling",
"anycrm": "Bounded by Pipedrive 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 Pipedrive account?",
"a": "Yes. AnyCRM uses Pipedrive's official API via a standard OAuth grant in your Marketplace Apps page. Every captured caller lands as a Person with the right team member as owner, the right Organization, and the right source attribution, plus a first Note from the call. Meetings land as native Pipedrive Activities on the right team member's calendar, with the Activity tied to the Lead or Deal so it shows on every pipeline view."
},
{
"q": "How is this different from Pipedrive's own AI Sales Assistant?",
"a": "Pipedrive's AI Sales Assistant is an OpenAI-powered insight feature inside Pipedrive — it answers questions about your existing data, summarizes deals, predicts win probability, and recommends features. It is not a phone receptionist, and it does not capture leads, book Activities, or talk to callers. AnyCRM is the layer in FRONT of Pipedrive: it picks up the phone, captures the lead as a Person, books the Activity on the right team member's calendar, and feeds the conversion event back to your ad platforms. The two are complementary — Pipedrive's Sales Assistant helps your sales reps analyse the pipeline AnyCRM helps fill."
},
{
"q": "Will it create duplicate Persons in Pipedrive?",
"a": "No. AnyCRM resolves the existing Person first (normalising email and phone) before writing. A returning caller becomes a new Note on the existing record, never a second Person, and the existing team member owner is preserved."
},
{
"q": "Can it route different leads to different team members?",
"a": "Yes. AnyCRM reads your Pipedrive team roster once at setup. Every active team member, with their lane (AE/SDR/CS), default pipeline, Activity types, and timezone. Sales-side, qualification-side, and customer-side calls each route differently, and existing Person ownership in Pipedrive is always preserved."
},
{
"q": "Where do the meetings actually live, calendar or Pipedrive?",
"a": "Both. AnyCRM writes the meeting as a native Pipedrive Activity with the team member as organizer in attendees and the Person as participant, which makes Pipedrive's Google/Outlook calendar sync fire automatically. You see one Activity on the pipeline view, one calendar invite on the team member's calendar, one source-attributed Person."
},
{
"q": "Can it cancel or reschedule a meeting from a phone call?",
"a": "Yes. The caller gives their email, AnyCRM finds the soonest upcoming Activity linked to the matching Person, the AI Receptionist reads it back, and AnyCRM either reschedules in place or flags the Activity cancelled the Pipedrive-native way (with the reason captured as a Note). Never a deletion that would soft-trash the audit trail."
},
{
"q": "What if a caller has two upcoming Activities in Pipedrive?",
"a": "AnyCRM returns every upcoming Activity for that Person (subject, date, time, team member organizer) 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 Pipedrive Activity requires (in the team member's timezone, which is how Pipedrive stores it internally), 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 Deals?",
"a": "Not directly. AnyCRM stays focused on the conversation surface: capturing the Person, matching the right team member, booking the Activity. Whether a call becomes a Lead in the Leads Inbox or a Deal in pipeline 1 stage 1 (or something else entirely) is YOUR business policy, and that policy lives inside your CRM in the receiving flow we wire up for you at onboarding. Every Person-create and every Activity-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 stage, which Lead Source, which workflow trigger. 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 website form / LeadBooster chat) flows through a single conversion pipe. It lands in your CRM 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. Web forms / LeadBooster chats AND the AI Receptionist produce the same lead-event shape with the same source taxonomy. They land in the same place in your CRM, 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 Pipedrive?",
"a": "Most teams are live the same afternoon. The OAuth grant takes a minute. The team roster and Activity-types import is automatic. We wire up the lead-receiving flow inside your CRM during onboarding. The phone integration is usually under an hour. Web chat is faster."
}
]
}