A call generated by paid acquisition is handled according to actual intent, not only its marketing source.
ANONYMIZED REAL-WORLD SPECIFICATION
AI voice agent for Google Ads phone leads
An anonymized real-world requirement: qualify Google Ads phone leads, separate hot prospects, support and FAQs, transfer sales calls and offer booking after hours.
AT A GLANCE
Turn an ad-driven phone call into a clear next action.
Purchase, subscription and B2B sales requests follow a priority commercial path.
Language is detected at the start of the conversation and the same operating logic is maintained in both languages.
When the sales team is unavailable, the flow switches to an appointment offer by SMS.
CALL FLOWS
Four call flows to avoid sending every Google Ads caller to sales.
The advertising line receives several types of calls. The specification therefore qualifies intent before deciding between sales transfer, support, direct answer or booking.
01
Prospect ready to buy
- Incoming request
- The caller mentions purchase, subscription, ordering or a B2B sales request.
- Decision
- The agent quickly confirms commercial intent and whether the lead should be treated as hot.
- Outcome
- If the team is available, the flow ends in a warm sales transfer.
- Fallback
- If the team is closed, the flow switches to an appointment offer by SMS.
02
Existing customer with an order issue
- Incoming request
- The caller needs parcel tracking, reports a delay, requests a return or has a delivery problem.
- Decision
- The agent classifies the request as support rather than a sales opportunity.
- Outcome
- The caller is informed and then rerouted to the Customer Care line, separate from sales.
03
Simple product question
- Incoming request
- The question concerns coffee origin, grind type, shipping costs or delivery timing.
- Decision
- The agent uses the FAQ to answer without immediately involving a human team.
- Outcome
- After answering, it can ask whether the caller wants to continue toward a purchase.
04
Hot lead after hours
- Incoming request
- Strong commercial intent is detected while the sales team is unavailable.
- Decision
- The agent explains that sales is closed, offers a booking and checks that the number can receive SMS.
- Outcome
- After consent, a booking link matching the caller’s language is sent.
CONTEXT
An international premium coffee e-commerce brand turning Google Ads into inbound phone calls.
The requirement comes from a growing coffee brand operated from Asia while serving buyers in the US and Europe. Google Ads generates inbound calls mixing sales prospects, information requests and support needs from existing customers.
Phone-based acquisition
The number displayed in paid campaigns becomes an acquisition channel that needs qualification just like a form or web lead.
Several intents on the same line
A ready-to-buy prospect, a customer tracking a delivery and a simple product question can all reach the same number.
International time-zone gap
Internal teams and US/EU markets do not always share the same availability windows, so the call flow needs an after-hours path.
QUALIFICATION
Separate sales, support and simple information requests quickly.
The core requirement is to qualify intent before involving a human team. The expected logic separates calls into three main families, each with a different next step.
Hot sales lead
Purchase, subscription or B2B sales intent triggers short qualification followed by a warm transfer to sales when the team is available.
Support request
Tracking, delays, returns or order problems are identified as customer-support requests and rerouted to the support line.
Simple question / FAQ
Coffee origin, grind type, shipping fees or delivery timing can receive a direct answer before the caller is invited back toward purchase when relevant.
WARM TRANSFER
Transfer to sales only when commercial intent is clear.
Transfer is not the default outcome. It happens after qualification when the call matches strong commercial intent and the team is available.
Qualification before handoff
The first exchange confirms intent and prevents support or FAQ calls from reaching the sales team.
Warm transfer
A qualified commercial request can be connected immediately to a sales representative when the availability window allows it.
Separate support routing
Post-purchase requests are identified as support issues and transferred to a dedicated line separate from sales.
ROUTING LOGIC
Clarify when needed. Transfer when the destination is clear.
The interesting part is not the number of rules. It is the ability to combine direct routing, clarification, fallback and escalation in one consistent flow.
AFTER HOURS
When sales is closed, preserve the caller’s purchase intent.
The expected behavior changes with the team’s real availability. After hours, the assistant does not attempt an impossible transfer: it offers a booking path and sends the scheduling link by SMS.
Offer a booking
The prospect can choose to continue later with the sales team instead of leaving an unstructured voicemail.
SMS in the right language
The scheduling link sent by SMS must match the language detected during the call: English or Spanish.
Consent before sending
The flow requires confirmation that the calling number can receive a text and the necessary consent before sending it.
CRM & WEBHOOK
Send the lead status and conversation context downstream.
The specification requires a detailed post-call summary to the CRM or through a webhook, so the team can immediately see the outcome of the interaction.
Lead status
The outcome should distinguish states such as hot lead, support, answered inquiry or booked appointment.
Contact details and context
Useful contact details, detected intent and the applied next step should remain available for human follow-up.
Transcript + summary
The requirement includes a text transcript and a short summary of the conversation in the post-call record.
TECHNICAL CONSTRAINTS
Call tracking, low latency and automated SMS.
The flow combines paid acquisition and telephony, so it needs to integrate with ad call-tracking numbers, preserve conversational responsiveness across regions and trigger off-call actions.
Google Ads numbers
Compatibility with call-tracking number management is part of the requested functional scope.
Intercontinental latency
The architecture must remain responsive enough for natural conversation across teams and markets in different regions.
SMS triggering
Sending the booking link requires an SMS integration that can be triggered automatically from the call flow.
OPERATIONAL PRINCIPLE
A useful phone system does not just answer. It knows what should happen next.
COMPLIANCE
Make the AI explicit and govern voice, phone and SMS data.
The specification explicitly requires the assistant to disclose that it is an AI and includes different constraints for European and US markets.
AI disclosure
The assistant must clearly disclose that it is an AI at the beginning of the call.
Voice and phone data
Data handling must account for European requirements around retention of voice data and phone numbers.
SMS opt-in
For SMS delivery in the US, the flow requires explicit verbal consent before the message is triggered.
HOW TO READ THIS CASE
This study describes a phone-conversion requirement, not a measured uplift.
Qualifying 100% of ad-driven calls, improving conversion or reducing sales-team load are stated objectives in the specification. No conversion rate or performance uplift is presented as an achieved result.
Documented objectives
The source makes the desired business logic clear without converting commercial ambitions into performance statistics.
Product performance stays separate
Kalyvox latency, intent accuracy, task completion and transfer measurements remain documented in the separate Voice Benchmark.
VALIDATE BEFORE GO-LIVE
Paid acquisition, telephony and compliance meet inside the same flow.
The specification does not only ask for a conversational agent. It also includes call-tracking, international latency, SMS and consent constraints.
Preserve Google Ads call tracking
Telephony integration must remain compatible with the numbers used in ads so the existing acquisition setup is not broken.
Keep cross-region conversation responsive
Teams are based in Asia while target callers include the US and Europe. The requirement therefore calls for low voice latency despite that geographic distribution.
Trigger SMS from the voice flow
The after-hours flow depends on an SMS integration that can automatically send the correct scheduling link.
Keep the same logic in EN and ES
Language detection must switch between English and Spanish without changing qualification and routing rules.
Clearly disclose AI use
The specification requires explicit disclosure at the start of the call that the assistant is automated AI.
Get consent before SMS
For the US flow, the source requires explicit verbal opt-in before sending the booking link by SMS.
This case shows that an ad-driven call needs to be treated as a lead to qualify, not just another inbound call.
Kalyvox reading of the specification: the lessons below are operational conclusions drawn from the requested workflow, not measured commercial results.
Traffic source does not reveal intent
Even when every call comes from paid acquisition, some callers need support or a simple answer. Qualification therefore needs to happen before sales transfer.
After-hours handling should preserve the next action
The specification replaces an impossible transfer with a booking offer. The flow does not merely answer the phone; it preserves a possible commercial next step.
The CRM needs an outcome, not only a transcript
The requirement calls for explicit outcomes—hot lead, support, answered inquiry or appointment—in addition to contact details, transcript and summary.
SOURCE FRAMEWORK
A real requirement, fully anonymized.
Names, companies, locations, phone numbers, email addresses and identifying details have been removed. Only operational elements useful for understanding the phone architecture are retained.
Browse other studies