AI Receptionists and Scheduling Agents: Ad Attribution
When an AI receptionist or scheduling agent books the visit, ads can lose credit. How to keep attribution and keep patient details out of ad platforms.
An AI receptionist or scheduling agent books the visit inside your phone line, text thread, calendar or EHR, so Meta and Google never see a website conversion unless the booking is sent back to them, which is what Curve Compliance does. It receives those bookings from booking systems, CRMs and call tracking through incoming webhooks and from EHR and intake tools through Keragon, credits each to the original ad click, and sends each ad platform only a fixed list of fields. It strips PHI before data reaches an ad platform.
Book a call. If bookings credited to your ads dropped in Meta or Google after an AI front desk went live, check whether the bookings are being sent back. Curve Compliance sends booked visits to your ad platforms server-side and signs a BAA on every plan. Book a call with Curve.
Where an AI front desk books the visit
AI front-desk tools now answer calls and texts and put visits straight on the calendar. Here is what three vendors say their products do, and what each vendor says about its BAA, checked October 26, 2026. Keragon labels its agents as new on its agents page.
| Product | What the vendor says it does | Where the booking lands | BAA, per the vendor | Source |
|---|---|---|---|---|
| Keragon New Patient Acquisition Agent | "Picks up inbound website leads, qualifies them, and books them straight onto a provider's calendar." | A provider's calendar; Keragon says Agents connect to "EHRs like Athenahealth, Elation, Healthie, DrChrono, and ModMed" | "A standard BAA is included on every paid plan" | Keragon Agents |
| Weave AI Receptionist | "Answer calls and texts, book appointments, capture appointment requests and more to care for patients and grow your practice 24/7." | Your calendar ("For qualified Dental PMS only"), or an appointment request your team reviews and schedules ("Available for everyone") | Weave publishes a Business Associate Addendum to its Terms of Service (BAA Directory) | Weave |
| CallRail Voice Assist | "the AI voice agent that answers every call, qualifies leads, and books appointments automatically" | Booked during a phone call | CallRail signs a BAA "with each of our Healthcare clients" (BAA Directory) | CallRail |
A vendor's BAA covers that vendor. Ask each one whether its BAA covers the AI product you use, and whether the product sends anything to ad platforms itself. The patient's side is changing too: on May 19, 2026, Google said its agentic booking and calling "will roll out to everyone in the U.S. this summer" (Google), and on October 6, 2026, Meta said its Muse agent "makes appointments" on business websites (Meta). Those agents have their own guide: AI agents booking appointments.
Why ad platforms lose the conversion
Ad platforms credit an ad when a conversion comes back tied to the click. Google provides "unique IDs, called Google Click ID (GCLID), for every click that comes to your website from an ad" (Google Ads Help). When an AI receptionist books by phone or text, no thank-you page loads and no pixel fires, so the click and the booking never meet. The same happens when an agent books a web lead hours later, or rebooks a missed visit.
Pixels are a poor fit for clinic pages anyway. Microsoft tells advertisers "Do not place UET tags on pages subject to HIPAA regulations" and says it "does not offer Business Associate Agreements (BAAs) for UET" (Microsoft Advertising). Meta's Business Tools Terms say you will not share data that "includes or is based on, directly or otherwise, health information" (Meta's BAA Directory entry). So the booking has to go back another way: from your systems, server-side, with nothing clinical in it.
Three ways to send the booking back
| Route | Use it when | What Curve Compliance does |
|---|---|---|
| Incoming webhook | Your booking system, CRM or call tracking tool can post an event when a visit is booked | Receives the outcome and credits it to the original ad click |
| Keragon | The visit lands in Healthie, Athenahealth, OptiMantra, IntakeQ or Jane | Receives those outcomes through Keragon and credits each to the original ad click |
| Offline conversion upload | Bookings sit in a CRM or EHR export | Takes the upload and credits each booking to the original ad click |
Google explains why this works: "By importing offline conversions, you can measure what happens in the offline world after your ad results in a click or call to your business" (Google Ads Help). For the webhook route, see how to webhook patient leads safely; for Google's side, offline conversion imports for clinics. The Healthie path has its own page: Healthie.
What never goes to Meta or Google
Treat the AI front desk as clinical intake. Call recordings, transcripts, the reason for the visit and the patient's answers belong in the receptionist and your EHR, not in anything sent to an ad platform. What leaves for advertising is a booked event and a short, fixed list of fields.
- Neutral names. Meta says the names you choose for events and conversions "must not reflect, imply or be based on" the sensitive categories in its terms, health information among them (Meta).
- A fixed field list. Curve sends each platform only the fields on a fixed list for that platform.
- Contact identifiers off. In Curve, contact identifiers are off by default on Meta, Google Ads and TikTok.
- PHI checks. Curve checks every event for PHI-like patterns, such as condition names, form answers and emails in URLs, and strips PHI before data reaches an ad platform. See the 18 HIPAA identifiers in website data.
BAAs: one for each vendor that touches PHI
Among its examples of business associates, HHS lists a "chatbot on a provider's patient portal that provides services involving the patient's PHI such as symptom assessment, medical reminders, and appointment scheduling" (HHS). An AI receptionist that schedules visits does similar work. HHS adds that "A business associate must establish a BAA with its subcontractor before disclosing PHI to the subcontractor for work to be done for a covered entity" (HHS).
Each BAA binds only the company that signs it. Curve Compliance signs a BAA on every plan for its own service; the receptionist vendor, the call tracking tool and the EHR each need their own. See what a business associate agreement is and HIPAA for healthcare chatbots. Which rules apply depends on your setup, so talk to your counsel.
Reading the results
Once bookings flow back, compare like with like. Curve's Campaign Reporting puts Meta and Google Ads spend next to Curve-tracked conversions per platform and campaign, with five attribution models, the list of conversions behind any number, and a single prospect's journey from ad click to booking. Compare the weeks before and after the AI front desk went live, and decide up front whether a rebooked missed visit counts as a new conversion. See platform ROAS versus real ROAS.
How Curve Compliance helps
Curve Compliance closes the gap between your AI front desk and your ads. It receives bookings from booking systems, CRMs and call tracking through incoming webhooks, from Healthie, Athenahealth, OptiMantra, IntakeQ and Jane through Keragon, and as offline conversion uploads from a CRM or EHR, and credits each to the original ad click. Bookings made days later still match, and when a visitor leaves your site to book in IntakeQ, Calendly, Acuity, Jane App or another supported scheduler, attribution comes along.
Curve sends conversions server-side to Meta's Conversions API, Google Ads, TikTok, Microsoft Advertising, LinkedIn and ChatGPT Ads, each with only a fixed list of fields. Event Logs show what Curve sent and what each platform accepted. Curve is SOC 2 Type II, signs a BAA on every plan, and its team does the setup, typically live in about a week. See booked appointment attribution.
Sources, checked October 26, 2026: Keragon Agents; Weave AI Receptionist; CallRail Voice Assist; HHS, Business Associates FAQs; Microsoft, UET safeguards for sensitive data; Google Ads, offline conversion imports; Google, automated calls to your business; Google I/O 2026; Meta, personal agents.
Frequently Asked Questions
Do AI receptionist bookings count as ad conversions?
Not on their own: a visit booked by phone, text or straight onto your calendar never fires a website pixel, so Meta and Google see nothing unless the booking is sent back. Curve Compliance sends it back server-side, credited to the original ad click.
Can an AI receptionist send conversions to Meta?
Ask the vendor first, because Meta's Business Tools Terms say you will not share data that "includes or is based on, directly or otherwise, health information" (Meta). The safer route is a neutral booked event with a fixed field list, sent from the booking record, which is what Curve Compliance does.
Does my AI receptionist need a BAA?
If it handles PHI for your practice, expect so: HHS lists a chatbot that provides "appointment scheduling" involving a patient's PHI among its examples of business associates (HHS). Check that the vendor's BAA covers the AI product itself; the BAA Directory has entries for Weave and CallRail.
How do I credit a phone booking to a Google ad?
Tie the booking to the click that started it and send it back as a conversion. Google says offline imports measure "what happens in the offline world after your ad results in a click or call to your business" (Google Ads Help), and Curve Compliance receives call tracking and booking outcomes by webhook and credits each to the original ad click.
What if the patient books days after the ad?
Bookings made days later still match in Curve Compliance, as long as the booking reaches Curve from your scheduler, CRM or EHR. Your attribution window decides how far back credit goes; see choosing an attribution window.
What if an AI agent books straight into my EHR?
Curve Compliance receives outcomes from Healthie, Athenahealth, OptiMantra, IntakeQ and Jane through Keragon and credits each to the original ad click, and Curve's team does the setup. Keragon, for one, says its New Patient Acquisition Agent "books them straight onto a provider's calendar" (Keragon).
Is Google's AI calling my clinic the same thing?
No. That is Google phoning your front desk for a customer: "Google calls your business to book the appointment" (Business Profile Help). See Google AI calling your clinic.
Talk to Curve Compliance
Book a call. Curve Compliance takes the visits your AI front desk books from your scheduler, CRM, call tracking or EHR and sends them to your ad platforms, credited to the original ad click, with PHI stripped before data reaches an ad platform and a BAA on every plan. Curve's team does the setup, typically live in about a week. Book a call with Curve.
Related articles
- GuideAI Agents Booking Appointments: Tracking and HIPAA
- GuideHIPAA Compliant Scheduling Software: BAAs and Ad Attribution
- GuideMed Spa Botox and Filler Ads on Meta: Campaign Structures That Book Consultations Without Violating HIPAA
- GuideTelehealth Attribution: Measuring Marketing ROI Across Virtual and In-Person Visits
Check your own site
See if your website is at risk. Enter your domain to scan it for tracking scripts that can expose patient data.
Stay Compliant. Scale Confidently.
Curve's team sets up HIPAA-compliant ad tracking for you, and most customers are live in about a week.
Book a free tracking audit