Respond Instantly
There’s a stat that should terrify every business owner: responding to a new lead within 5 minutes makes you 21 times more likely to qualify that lead than responding in 30 minutes. Not twice as likely. Twenty-one times.
Most businesses don’t respond in 5 minutes. They don’t respond in 30 minutes. The average response time for a web form submission in most industries is somewhere between 8 and 48 hours. Some never respond at all. Every dollar they spent on ads, SEO, and marketing to generate that lead — wasted, because somebody else answered first.
Your AI Receptionist handles live interactions. Someone calls, the AI picks up. Someone opens the chat widget, the AI responds. That’s Pillar 3 — Never Miss a Call. This playbook is Pillar 4. This is what happens when a lead comes in through every other channel: form submissions, Facebook lead ads, landing page opt-ins, Google Ads conversions, Instagram DMs, email inquiries. The lead lands in the system and the automation takes over before any human has to think about it.
Step 1: Map Every Lead Source
Before you build any automation, you need to know where leads enter the system. Most businesses have more lead sources than they realize, and every one of them needs to be wired into the speed-to-lead workflow.
Website contact forms. Landing page opt-ins. Facebook lead ads. Google Ads click-to-call that went to voicemail. Instagram DM inquiries. Email inquiries. Third-party lead providers like HomeAdvisor or Thumbtack. Google Business Profile message requests. Yelp leads.
List them all. Every source that generates a new contact or inquiry is a trigger point for the workflow. If it creates a contact in GHL, it needs to fire the speed-to-lead sequence.
Where this connects:
- Forms & Surveys — website and landing page form submissions
- Facebook Ads Integration — lead ads syncing directly into GHL
- Triggers — the event that starts the workflow for each source
Step 2: The First 60 Seconds
The lead submits a form. Within 60 seconds, they should receive an SMS acknowledging their inquiry. Not a marketing message. Not a pitch. An acknowledgment that a human being is aware they reached out.
Something like: “Hey [name], thanks for reaching out to [business]. We got your message and someone will be in touch shortly. In the meantime, is there anything specific we can help with?”
That last question is intentional. It opens a two-way conversation. If the lead replies, they’re engaged. An engaged lead is exponentially more likely to convert than one sitting in a queue waiting for a callback.
The SMS goes out via workflow automation. No human has to see it, write it, or send it. It just fires.
Where this connects:
- SMS & MMS — the outbound text that fires immediately
- Workflow Builder — the automation engine
Step 3: The Email at Two Minutes
Two minutes after the form submission, send a confirmation email. This serves a different purpose than the text. The text is immediate engagement. The email is documentation and credibility.
The email confirms what they submitted, introduces the business, and includes a booking link so they can self-schedule if they don’t want to wait for a call. A professional email arriving two minutes after a form submission signals that this business has its act together. It builds trust before any human interaction.
Where this connects:
- Email Campaigns — the confirmation email template
- Calendar Booking — the self-scheduling link in the email
Step 4: Internal Notification and Task Assignment
Simultaneously with the outbound messages, the workflow notifies the team. This is the human layer. The automation buys you time, but a real person still needs to follow up.
Create an internal notification — SMS, email, or app push to the assigned sales rep or the business owner. Include the lead’s name, what they inquired about, and where they came from. Make it easy to act on: one tap to call, one tap to open the conversation.
If the client has multiple team members, use round-robin assignment so leads are distributed evenly. If it’s a solo operator, the notification goes to them directly.
The key metric: does a human attempt contact within 5 minutes of the lead arriving? If not, the escalation sequence (Step 5) takes over.
Where this connects:
- Contact Manager — the lead record with all submitted data
- Opportunities — automatically creating a pipeline opportunity from the new lead
Step 5: The Escalation Sequence
This is the safety net. If no human has responded to the lead within 5 minutes, the automation escalates.
Send a second SMS with a different angle. Maybe a booking link: “If you’d like to skip the wait, you can grab a time on our calendar here: [link].” Maybe a question that drives engagement: “Quick question — are you looking for [service A] or [service B]?”
At the 15-minute mark, if still no human engagement, send an internal alert — a more urgent notification to the team lead or the business owner. “New lead from [source] has been waiting 15 minutes with no response.”
At the 1-hour mark, trigger a voicemail drop or a ringless voicemail if the lead provided a phone number. “Hey [name], this is [person] from [business]. I saw you reached out earlier — just wanted to make sure you got taken care of. Call me back at [number] or just reply to the text we sent.”
The escalation sequence is a pressure valve. It keeps the lead warm while pushing the team to respond. Most leads that go cold do so because nobody followed up in time. This prevents that.
Where this connects:
- If/Else Branching — checking whether the lead has been contacted before escalating
- Drip Sequences — spacing the follow-up touches
Step 6: After-Hours Logic
Leads don’t stop at 5pm. A form submission at 9pm on a Saturday needs the same instant response as one at 10am on a Tuesday. The automation doesn’t care about business hours — it fires regardless.
But the after-hours message should acknowledge the timing. “Hey [name], thanks for reaching out. We’re closed for the day but we got your message and someone will follow up first thing tomorrow morning. If you’d like, you can book a time right now: [calendar link].”
The calendar link is the after-hours conversion tool. People filling out forms at 9pm are often in research mode. Give them the option to book while they’re thinking about it, and they will. If they have to wait for a callback the next day, they might have already called someone else by then.
Where this connects:
- If/Else Branching — checking time of day to adjust the message
- Calendar Booking — the self-scheduling fallback for after-hours leads
Step 7: Multi-Day Follow-Up
Not every lead converts on the first day. Some are comparison shopping. Some aren’t ready yet. Some got distracted. The speed-to-lead workflow handles the first hour. The multi-day follow-up handles the rest.
Day 1: The instant response sequence (Steps 2-5) handled this.
Day 2: A check-in SMS. “Hey [name], just following up on your inquiry from yesterday. Still looking for help with [service]?” Keep it short. Keep it human. One question.
Day 4: An email with value. Not a sales pitch. Something useful — a tip related to their inquiry, a link to a relevant resource, a case study. “Most [niche] businesses we work with don’t realize [useful insight]. Here’s what we recommend…”
Day 7: Final touch. “Hey [name], wanted to reach out one last time about your [service] inquiry. If the timing isn’t right, no worries at all. We’re here when you’re ready.” Then stop. Don’t chase. If seven days of multi-channel follow-up didn’t convert them, continued messages become noise.
Where this connects:
- Drip Sequences — the multi-day follow-up cadence
Step 8: Measure Response Time
You can’t improve what you don’t measure. Track two numbers: time to first automated response (should be under 60 seconds — this is system performance) and time to first human response (should be under 5 minutes — this is team performance).
If the automated response is slow, the workflow has a configuration issue. If the human response is slow, the team needs better notifications, better accountability, or a Conversation AI layer to handle the gap.
Build a simple dashboard that shows these metrics per lead source. When the client sees “average response time: 47 seconds” next to their old reality of “average response time: 14 hours,” the value of your service is undeniable.
Where this connects:
- Dashboards — tracking and displaying response time metrics
- Attribution Reporting — tying response speed to lead source and conversion outcomes
The Sequence at a Glance
| Step | What You Do |
|---|---|
| 1 | Map every lead source that creates contacts in the system |
| 2 | Fire an SMS within 60 seconds of form submission |
| 3 | Send a confirmation email at 2 minutes with a booking link |
| 4 | Notify the team internally and assign via round-robin |
| 5 | Escalate at 5 minutes, 15 minutes, and 1 hour if no human response |
| 6 | Adjust messaging for after-hours with calendar booking fallback |
| 7 | Run a 7-day multi-channel follow-up for unconverted leads |
| 8 | Track automated response time and human response time |
What This Playbook Does NOT Cover
- Live call and chat handling (see Your AI Receptionist — that’s Pillar 3: Never Miss a Call)
- Building the forms and landing pages that generate the leads (see Get Found First — Pillar 1)
- Review requests layered into the follow-up (see Setting Up Your First Review Engine — Pillar 2)
- Re-engaging old leads who went cold months ago (see The Database Reactivation — Pillar 5)
- Advanced Conversation AI handling the follow-up conversation automatically (future content)
This playbook covers the automation that sits between lead generation and human conversation. The prospect reaches out. The system responds in seconds. The team gets notified. The follow-up runs itself. Nobody falls through the cracks, and no lead waits long enough to call someone else.