Why the first minute matters
When someone fills in a form or calls after hours, they are usually doing the same thing with two or three of your competitors at once. Whoever replies first sets the tone for the whole conversation, and often books the appointment before anyone else has even seen the enquiry.
We track first-response time on every account we manage. The pattern is consistent across industries: enquiries answered inside a minute book at roughly double the rate of those answered after an hour. After a day, most are cold. The good news is that "inside a minute" does not require staff watching a screen. It requires three automations that take an afternoon to build properly.
The three parts
1. The instant acknowledgement
The moment a lead is created from a form, chat widget, ad or missed call, GoHighLevel sends a short reply on the same channel the lead used. A form submission with a mobile number gets an SMS. An email-only enquiry gets an email. The message is personal, asks one question, and gives the lead a way to book straight away.
Hi Sarah, it's Emily from BrightSmile. Thanks for reaching out about a check-up. Is this week or next better for you? You can also grab a slot here: [booking link]Instant SMS, sent within 10 seconds
2. The human hand-off
At the same time, the workflow creates a task for the right team member, assigns the contact as the owner, and sends an internal notification with the lead's details and the message they received. During business hours that person follows up by phone within fifteen minutes. Out of hours, the task waits for the morning and the lead already has a booking link in hand.
3. The short nurture
If there is no reply and no booking, a second message goes out the next morning, a third two days later, and a final one after a week. Each is shorter than the last. The sequence stops the moment the lead replies, books, or is moved to a later pipeline stage. That stop condition is the difference between helpful and annoying.
One workflow with the trigger "Contact Created" (filtered by source), an "If/Else" branch on channel, "Send SMS" and "Send Email" actions, an "Assign to User" step, an "Add Task" step, an internal notification, then "Wait" steps with the goal event set to "Appointment booked" or "Replied".
Copy that gets replies
The first message has one job: get a response. Not to sell, not to explain the service. A few rules we follow on every account:
- First name only, and a real person's name as the sender. "Hi Sarah, it's Emily" beats "Dear Customer" every time.
- One question, ideally with an easy answer. "This week or next?" gets replies. "What are your goals?" does not.
- Under 160 characters for SMS so it arrives as one bubble.
- The booking link is optional, not the whole message. People reply to people.
The follow-ups get shorter, never longer. By the last one, we are at a single line: "Still want that check-up sorted, Sarah? Just reply yes and I'll call you."
Missed calls count too
For local service businesses, the biggest source of lost leads is not the website form. It is the phone ringing out while everyone is on a job. GoHighLevel's missed-call text-back turns that into a conversation.
Sorry we missed your call! This is James at RoofRight. How can we help? Reply here or book a free inspection: [link]Missed-call text-back, sent within 5 seconds
Two details matter. First, the text should come from the same number the caller just dialled, so it feels like a continuation. Second, the reply lands in the GoHighLevel conversation view where whoever is free can pick it up, instead of one person's mobile.
Two mistakes to avoid
Sending the same message to every source. Someone who booked a demo from a pricing page needs a different first line than someone who downloaded a checklist. Branch on the source field and write two or three variants. It takes an hour and removes the "mass message" feel.
Forgetting the stop conditions. A nurture that keeps firing after the lead has replied or booked is worse than no nurture at all. Every wait step should have a goal event, and the workflow should remove the contact when they reach a later pipeline stage.
How to measure it
GoHighLevel reports first-response time per conversation. We look at the median, not the average, every Monday. A healthy account sits under a minute for automated first replies and under fifteen minutes for the human follow-up during business hours. If the human number creeps up, the fix is usually the task assignment, not the people.
Set it up once, test it with a real form submission and a real missed call from your own phone, and watch it work. Then leave it running. This is the automation clients thank us for most, because it is the one they notice on their calendar.
Key takeaways
- Reply to every new lead within 60 seconds, on the channel they used, day or night.
- Three parts: instant acknowledgement, a task and alert for a human, and a short nurture that stops on reply.
- Write the first message like a person typed it: one line, one question, first name only.
- Missed calls are leads. Text back within seconds and the phone call becomes a conversation.
- Measure median first-response time in GoHighLevel every week. Under a minute is the target.