Lead capture and sales follow-up
Receives leads from the authorised sources, drops the duplicates, assigns an owner, follows up by stage, and keeps the origin attached all the way to a won or lost outcome and its reason.
Google Ads — lead forms
A form filled inside the ad is written into Zenvox as a request to call back. Nothing is written on the advertising side: receiving a lead is not managing campaigns.
7 days, 20 answered calls, no card
Where your lead lands
The lead is written into Zenvox as a request worth qualifying: name, number, what they are after, the campaign it came from. The ad account stays yours, and nothing is written into it — receiving a lead is not managing campaigns, not creating an ad, not committing a budget. The receptionist calls while the subject is still fresh.
Access is granted through an authorisation you give from your own ad account: no key to create, no connector to program. Four tasks often travel under one name — receiving a lead, sending an outcome back, creating a campaign, launching it with a budget. This page covers the first only; the others carry their own authorisation and their own page.
A lead form opens inside the ad, and the person leaves a name, a number and what they need without ever leaving the search results. The trouble comes next: the form lands in an inbox and it sits there.
Read, create, update, cancel
This flow runs one way, and understanding that first saves you from expecting anything else of it. Only one of the four actions touches the ad side; the other three are settled on yours. No account has been configured yet and no live delivery has been received.
| Action | Status | What that means |
|---|---|---|
| Read | To qualify | The lead is delivered by a web post to an address you configure, protected by a validation key you choose. The fields delivered and the version of the format come from the implementation guide. Your account's eligibility and the exact list of fields it delivers still have to be checked on your own account. |
| Create | Zenvox native mode | Nothing is created on the ad side: an advertising platform does not hold appointments. The lead becomes a request in your workspace, with its campaign, its form, its timestamp and whatever consents were delivered with it — and that request is what the receptionist works from. |
| Update | Zenvox native mode | This incoming flow changes no state on the ad side. Where the lead stands — called back, qualified, booked, lost — lives in your workspace, and that is where an outcome sets off from when it travels back to advertising, through a different connection described on its own page. |
| Cancel | Zenvox native mode | This flow establishes no route for a withdrawal, a correction or a deletion. So a withdrawal of consent and a deletion request are recorded and honoured in your workspace, with the register that goes with them, and they do not depend on the advertising platform at all. |
What is included, what needs an add-on
Answering the phone, qualifying and passing the request along is in your base, and advertising changes none of that. Receiving a lead that came from an ad, handing it to the right person and following it through to its outcome is the work of an acquisition add-on. Preparing and launching the campaigns themselves is something else again, and it does not switch itself on because a lead arrived.
The authorisation, and what holds the truth
There is no password to hand over here: the setup is done inside your own ad account, and it comes down to one address and one key.
- You configure the form and the receiving address from your own ad account
- A validation key that you choose travels with every delivery, and a delivery that arrives without the right key is refused
- The origin is kept as delivered — campaign, form, timestamp, consents — because an outcome with no origin explains nothing
- The same lead sent twice creates one file: a replay is handled rather than endured
- Your ad budget stays with your ad platform; the connection does not touch it, and connecting adds no fee to your subscription
- The ad account holds the truth for delivery; your workspace holds the truth for how the request moves along
A roofer, two crews, autumn season. A search ad carries a lead form. The lead arrives while the person is still in front of their screen, and the receptionist calls back.
ReceptionistHello, I am calling you back about the roofing estimate you just asked for. Let me take your name and a callback number first, in case we get cut off.
CustomerYeah, hi. I have had a water stain on the ceiling since Saturday's storm.
ReceptionistI am logging that as an active leak. What is the address, with the postal code? And is it a sloped roof or a flat one?
ReceptionistThank you. I am marking the request as a priority and holding a slot for an estimate visit. The price of the repair comes from the roofer, once he has seen the roof.
The request reaches the owner with the campaign it came from, the address, the roof type and the active leak flagged. Nothing is written on the ad side, because there is nothing there to write to.
If the connection is not there
Without the connection, none of the receptionist's work is lost: the only thing that changes is the road the lead takes to get to you.
- The calls that the same ad produces are answered, qualified and passed along as usual
- The form on your own site drops the request straight into your workspace, with its origin
- A lead that reaches you by email can be entered by hand without losing its timestamp or its campaign
- The day receiving is qualified, it is added on top without changing your setup or your budget
Questions about this connection
Does Zenvox manage my campaigns?
No: receiving a lead is not managing campaigns, not creating an ad, not committing a budget. The ad account stays yours, and nothing is written into it.
How does the lead arrive?
By a web post to an address you configure from your own ad account, protected by a validation key you choose; a delivery that arrives without the right key is refused. Your account eligibility and the exact list of fields delivered still have to be checked on your own account.
What if the same lead arrives twice?
It creates one file: a replay is handled rather than endured. The origin is kept as delivered — campaign, form, timestamp, consents — because an outcome with no origin explains nothing.
Does connecting cost extra?
Your ad budget stays with your ad platform, the connection does not touch it, and connecting adds no fee to your subscription.
What about a withdrawal of consent?
It is recorded and honoured in your workspace, with the register that goes with it. This flow establishes no route for a withdrawal, a correction or a deletion on the ad side, so the request does not depend on the platform.
Where to next
See what sales follow-up does with the lead, how the outcome travels back to advertising, or open the full software list.
Google Ads — lead forms