Speed to lead: calling web leads back within seconds
Someone fills in the form on your website at 21:40. They are interested right now, phone in hand, probably with two other suppliers open in other tabs. By the time a salesperson sees the lead tomorrow morning, the moment has passed. "Speed to lead" is the name for closing that gap, and a voice agent is the simplest tool for it: the form is sent, and seconds later the phone rings.
Why the first minutes matter
You may have seen big claims about how much better fast replies convert. Do not take ours or anyone else's. Check your own numbers. Pull the last hundred leads from your CRM with two columns: how long until the first real contact, and whether they became customers. Sort by the first column. The pattern is usually visible without a chart.
The reason is simple. A lead who has just pressed "send" is still thinking about the problem. An hour later they are cooking dinner. A day later they have gone with whoever called first. Speed does not replace a good salesperson. It makes sure the salesperson gets the conversation at all.
What the agent should do on the call
The call has one purpose: turn a form into a conversation with the right person at the right time. It is not a sales call. Keep it to four steps.
- Say who is calling and that it is an AI, and name the form: "you just asked about solar panels on our site".
- Ask the two or three qualifying questions you would ask anyway: what, where, when.
- Offer the next step: a warm transfer to a salesperson who is free right now, or a booked call at a time the lead picks.
- Confirm what happens next and end the call. Aim for under three minutes.
The warm transfer is the strong move during office hours. The agent puts the lead on hold, dials a salesperson, briefs them in one sentence ("Anna, from the website, wants a quote for a roof system in Aarhus"), and connects. Outside office hours it books the callback and writes everything down.
The plumbing, step by step
This is where a developer comes in, and it is a small job. The pieces are your form, your server, the calling API, and a webhook back.
When the form is sent, your server (or your CRM's automation) calls the API with the lead's number, name and the form answers as variables. There are two ways to do that. Push the lead into a campaign, and the campaign's calling window and retries take care of timing. Or start a single call directly, which is right when "now" is the whole point and you handle the timing yourself. The agent is set to outbound or both.
When the call ends, a signed webhook (call.completed) posts the summary, the outcome and the answers the agent collected back to your server, which writes them to the CRM. From the lead's record you can then see: called at 21:41, reached, qualified, meeting booked Tuesday at ten.
Two practical notes. API keys have scopes, so give the form integration a key that can only create calls and leads. And each key is limited to sixty requests a minute, which is plenty for form traffic but worth knowing if you plan to replay a backlog. The endpoints and events are listed for developers, and the wider picture is in connecting a calendar and CRM.
Guard rails
Fast must not mean careless.
- Calling window: a lead who sends the form at two in the morning gets called at eight, not at 02:01. Set the window per weekday in the campaign.
- Duplicates: if the same person sends the form twice, do not call twice. Match on phone number before you fire.
- Do-not-call: the blacklist wins over everything, including a fresh form.
- "Not now": accept it the first time, offer a callback, and write the time down.
- Consent: the lead asked to be contacted, which is a different situation from a cold call, but your country's rules on recording and marketing calls still apply. Check with your adviser and set the recording option to match.
- Honesty: the agent must not quote prices or promise dates it has not been given. Put the facts it may use in its instructions or knowledge base, and nothing else.
What to measure
Time to first call: the seconds between the form and the phone ringing. This should be a boring, flat line.
Reach rate: leads who answered divided by leads called. Retry once after twenty minutes, then send a text, then hand the lead to a person.
Qualified rate and meetings booked: from the outcome the agent writes on each lead.
Won deals: from your CRM, a month later. That last number is the only one that matters, and it is the one to compare against the hundred old leads you pulled at the start.
Where NordTell fits
NordTell's API starts a call from a form submission, the agent qualifies the lead in its own language, warm-transfers to a free salesperson or books a callback, and a signed webhook returns the summary and outcome to your CRM. Calling windows, retries and the blacklist apply to these calls like any other.