How do you respond to a lead in under 2 minutes?
The short answer
By automating what happens right after the form: the lead is saved in your CRM, your team is notified and the prospect gets a first message, with no human intervention. At Fastlane Rent a Car in Dubai, three Make scenarios cut the response time from over an hour to under 2 minutes.
Why does response speed matter so much?
Because a prospect who fills in one form often fills in several. Whoever answers first has a head start, and after an hour most enquiries have already gone cold.
The most quoted study on the subject was published in the Harvard Business Review in 2011. The authors sent a test lead to 2,241 US companies and measured how long each took to respond:
- 37% responded within an hour;
- 24% took more than 24 hours;
- 23% never responded at all.
In their data, companies that tried to reach the prospect within an hour were nearly 7 times more likely to have a meaningful conversation with a decision-maker than those that waited even an hour longer. You'll find far more spectacular figures elsewhere, wrongly credited to the same study: this one can be checked.
What happens to a lead without automation?
At Fastlane Rent a Car, a car rental agency in Dubai, leads arrived by email, with no CRM. Follow-up was manual, whenever someone saw the message. The result: an average response time of over an hour.
In car rental, an hour is enough for the customer to book elsewhere. Speed there is the competitive advantage, plain and simple.
What does lead automation look like?
The principle fits in one sentence: as soon as the form is submitted, a scenario runs and does three things in parallel. For Fastlane:
- The lead goes into the CRM (a Notion database), with its source and details, no retyping.
- The team is notified by email, with a summary of the request.
- The prospect gets a WhatsApp message through SendPulse, confirming the request is being handled.
- TriggerLead received
- MakeInternational number normalised
- NotionLead added to the CRM
- EmailTeam notified
- WhatsAppMessage sent (SendPulse)
< 2 min
between the lead and the WhatsApp notification
Source: 3 Make scenarios in production
The three branches run in parallel on Make. If one fails, the other two still go through: a lead is never lost because one service is down.
What are the technical pitfalls?
The big steps are rarely the problem. It's the details that fail silently:
- Phone numbers. One customer types "050 123 4567", another "+971 50 123 4567". The WhatsApp Business API expects the international format. Without normalising it upstream, some messages never go out, and nobody notices.
- The 24-hour window. WhatsApp Business only allows free-form messages within 24 hours of the customer's last message. After that, you need a message template approved by Meta.
- Duplicates. An impatient prospect submits the form twice: the scenario must recognise they're already in the CRM.
- Consent. The form must say the person will be contacted, and through which channel.
How do you connect these leads to your campaigns?
Once every lead is properly recorded, you can send the ones that become real customers back to Google Ads with offline conversion imports. Campaigns then optimise on actual sales, not just on submitted forms.
That's what I set up for a premium residence in Mauritius, using Make and the Google click identifier (GCLID): sales closed offline, at €490,000 per unit, feed back into the campaigns. More on the Ads campaigns page.
Frequently asked questions
Make, Zapier or n8n: which tool should I choose?
All three can handle this kind of scenario. I use Make for its visual scenarios and parallel branches, which stay easy to read when they need to evolve. The right choice depends mostly on the tools you need to connect and your lead volume.
Do I need a CRM?
You need at least one single place where every lead is saved with its source and status. That can be a proper CRM, or a Notion database as at Fastlane. Without it, leads stay scattered across inboxes.
Is an automatic WhatsApp message GDPR-compliant?
Yes, if the prospect expects it: the form must say clearly that they'll be contacted, and through which channel. The message should then answer their request, not enrol them in an advertising sequence.
What happens in the evening and at weekends?
That's exactly when automation pays off most: the prospect gets an instant answer and the team finds the qualified lead in the CRM as soon as they're back. The first message can state the real call-back time.
Sources
- The Short Life of Online Sales Leads (2011) · Harvard Business Review
- About offline conversion imports · Google Ads Help