Your AI receptionist answers every call. Your ads still can't tell which ones booked.
Since the receptionist took over the phones, Google Ads shows more call conversions and your inbox fills with summaries, but the schedule looks the same. A summary describes a conversation; it doesn't prove a booking. We put a tracking number in front of the receptionist, match each answered call to the job it became, and send only booked and completed work back to Google and Meta.
Free30 minutesNo obligation
AI receptionist tracking · what breaks
What changed when the receptionist started answering
- 01
Conversions went up, booked jobs didn't
A call conversion set to a minimum call length counts every call that runs past it. With nothing going to voicemail, spam, vendors and existing customers clear that bar too, and bidding buys more of them.
- 02
The summary says 'booked'; the schedule doesn't
Callers say 'Thursday works' and never confirm, or a message goes unreturned. Counting summaries as jobs overstates every campaign.
- 03
The receptionist's number replaced your tracking number
Put the AI line on your Google Business Profile or website and calls skip tracking. Every booking arrives marked 'phone', so ads, Maps and referrals look identical.
- 04
Bookings live in a system your ads never see
The appointment lands in Jobber, a calendar or your CRM with no click ID, so the ad behind a large job gets the same credit as a hang-up.
AI receptionist tracking · the fix
What fixed looks like — AI receptionist tracking
Calls tied to the ad before the receptionist picks up
A tracking number rings through to the receptionist, recording source, caller ID and start time on every call.
Booked and completed jobs reported, not answered calls
Each call is joined to its outcome in your scheduling system; only real bookings, with job value, go to Google and Meta.
An honest line where visibility ends
Calls with no click or tracking match are reported as unattributed, not credited to the nearest campaign.
AI receptionist tracking · architecture
How the receptionist's records reach your ad accounts
Each receptionist exposes different data. We use the route its own documentation supports and say where it stops.
- 1
Call tracking in front of the receptionist (M5)
Your call tracking number takes the call and forwards it to the receptionist. Smith.ai documents answering calls forwarded from CallRail call flows or tracking numbers; Ruby, Goodcall and Jobber's dedicated number also accept forwarded calls.
- 2
Receptionist records through Zapier or API (M4)
Smith.ai's Zapier trigger can pass a tracking_id_number field to your CRM. Goodcall's Zapier app has Call Complete and Flow Complete triggers. Ruby connects through Zapier, which checks for new data every 1 to 15 minutes. Jobber webhooks can arrive more than once, so duplicates get filtered.
- 3
Bookings from the system of record (M4)
Jobber Receptionist submits requests and schedules jobs through Jobber's own forms, so the Jobber record is the source. For the others, the source is wherever the booking is written: calendar, CRM or field-service software.
- 4
Outcomes sent back (M6)
Google Ads imports call conversions by caller phone number and start time only when the call came through a Google forwarding number. For website calls, the tracking platform keeps the visitor's click ID and the job goes back as an offline click conversion. Meta's Conversions API takes it with action_source phone_call, up to seven days after the event.
- 5
CSV reconciliation where no route exists (M8)
Where no usable route exists, a weekly export is matched by hand. It is slower, and we say so.
AI receptionist tracking · diagnose
Where receptionist tracking breaks, in diagnostic order
Start with the phone path: a call that never touched a tracking number can't be attributed.
- 01
Call each advertised number
Note which ring the receptionist directly.
- 02
Check what Google Ads counts as a call conversion
If it is any call over a set length, spam is counted.
- 03
Compare summaries marked 'booked' with the schedule
Over one closed week, by caller and date.
- 04
Check whether the caller's number survives forwarding and transfers
Some transfers show the receptionist's number instead.
- 05
Check how the receptionist greets callers from call ads
Google requires the business name as it appears in the ad at the start of the call.
AI receptionist tracking · prove
The QA evidence — AI receptionist tracking
Run on real calls to your live advertised numbers, answered by your receptionist as configured.
Source of truth
Booked and completed jobs in your scheduling or field-service system, matched to call records by caller phone and start time
- A call from an ad-tagged session, with its source on both the call and receptionist records.
- Every answered call in a closed week marked booked, not booked or excluded, with a reason.
- Exactly one conversion per booked job in Google Ads and Meta Events Manager.
- A cancelled visit retracted where Google Ads allows it, and a rescheduled one left alone.
- Payloads confirmed free of transcript, summary or recording text.
- Rerun a month later, and again whenever the receptionist's script or call routing changes.
AI receptionist tracking · free audit
What we check in the free audit
- Call each advertised number
- Check what Google Ads counts as a call conversion
- Compare summaries marked 'booked' with the schedule
- Check whether the caller's number survives forwarding and transfers
- Check how the receptionist greets callers from call ads
Checked against
Booked and completed jobs in your scheduling or field-service system, matched to call records by caller phone and start time
Free30 minutesNo obligation
AI receptionist tracking · when not to buy
When you don't need this — AI receptionist tracking
Some receptionist setups need a settings change, not a build.
- If nearly all your calls come from Local Services Ads, Google shows each lead's charge status on its own Leads page. Matching those to jobs is reporting, not this build.
- At a handful of calls a week, asking each caller how they found you is cheaper and accurate.
- If the receptionist only takes messages and your team books later, fix follow-up first.
- Ruby's HIPAA-compliant service can't use its Zapier integration; for healthcare calls we keep reporting aggregate rather than route call content anywhere new.
AI receptionist tracking · what we deliver
What we build, rung by rung — AI receptionist tracking
Call connected
Tracking numbers in front of the receptionist, with forwarding tested so the caller's number survives.
Call matched to receptionist record
Each answered call joined to its Smith.ai, Ruby, Goodcall or Jobber record on caller phone and start time.
Qualified lead
Your rule (service area, service type, new customer) applied to the receptionist's fields.
Job booked
Taken from the visit or appointment record in your scheduling system, never from the wording of the summary.
Job completed and paid
Invoice value attached to the original call, so bidding learns from revenue.
Cancellations and noise removed
Spam, vendor and existing-customer calls excluded. Cancelled visits retracted in Google Ads when the job went back by click ID; imported calls and Meta don't take retractions, so those are corrected in your reporting.
Written guarantee
95%+ tracking accuracy
Measured against Booked and completed jobs in your scheduling or field-service system, matched to call records by caller phone and start time. Miss it and we keep working at no cost.
Pricing
Pick the package that fits your ad spend
Browser-side starter
$400One-time fee · lifetime ownership
Repairs and verifies the browser-side setup you already have, on a live conversion. Honest about its ceiling on this platform.
- Root cause fixed, not worked around
- Verified on a live conversion
- Reconciled against your own records
- Written handover
1st-party server-side
Recommended$800One-time fee · most popular
Money events sent from your own records through a first-party container on your subdomain, so the browser can no longer lose them.
- First-party server container on your own subdomain
- Money events from your records, not the browser
- Deduplicated on a shared event ID at every destination
- First-party cookies beyond Safari's 7-day cap
- 95%+ accuracy and 8+ Meta EMQ, guaranteed in writing
Full 1st-party stack
$1,800One-time fee · lifetime ownership
Every paid channel server-side plus the offline loop, with monitoring so the next break surfaces in days.
- Everything in 1st-party server-side
- Pinterest, Snapchat, Reddit and LinkedIn CAPI
- CRM and offline conversion loop
- Refunds and cancellations corrected wherever each platform allows it
- Monitoring on every destination
FAQ
AI receptionist tracking questions, answered
No. A summary can say booked when the caller never confirmed. Count the visit or appointment record in your scheduling system, and use the summary only to help match the call.
Because the log shows who called and what was said, not which ad sent them. A tracking number in front of the receptionist records the source before the call is answered.
No. Ad platforms receive the event name, time, value and, where allowed, a hashed phone number. Transcripts, recordings and summaries stay in your systems, and for health and legal businesses service details are excluded too.
Google decides whether an answered LSA call is a chargeable lead from the conversation itself, so a charged lead and a booked job are different counts. Google is moving LSA into Performance Max with pay-per-lead goals in phases, starting with select US home and storefront service advertisers in August 2026. We match LSA leads to jobs in reporting and don't claim click-level attribution for them.
It can. Google requires calls from call ads to open with your business name as it appears in the ad, so check the receptionist's greeting.
Jobber Receptionist, if Jobber already runs your schedule, because the booking is created where the job lives. Smith.ai, Ruby and Goodcall records have to be joined to wherever the booking ends up.
Free · 30 min
Find out which answered calls became jobs
WhatsAppFree30 minutesNo obligation
