How to Set Up Missed-Call Text-Back (Step by Step)

A missed call from a customer with a leaking pipe is not a missed contact. It is a job that quietly walks across the street to the next number on the search results. The fix is not hiring an answering service. It is a five-line automation that sends a real, useful text within seconds of the call ending. Done right it recovers a meaningful fraction of the calls you would have lost.

This guide shows the exact build in GoHighLevel, the message template we use with our clients, the test pass that catches the mistakes, and the three settings most people get wrong on the first try.

The window of time a service-business prospect spends on your number is short. If they get voicemail, most of them keep dialing. The instant text-back reframes the moment: "We saw you call, we are with another customer, here is the fastest way to get on the schedule today." That message turns a dropped call into a thread, and a thread is much easier to convert.

It also captures the phone number into your CRM, which means the lead is now in your follow-up engine even if they never reply.

• A GoHighLevel sub-account with a verified phone number that can send SMS in the United States.
• Your call traffic routed through that number. If you currently use a different business line, you will need to either port the number into GoHighLevel or forward calls to it.
• Ten compliant SMS templates approved through your registered A2P 10DLC campaign. Without that, your carrier will quietly filter the messages and you will think the automation is broken.
• An owner-approved message body. Not a template grabbed off a forum.

1. Open Automation. In the left rail, click Automation, then Workflows. Click Create Workflow and start blank.
2. Add the trigger. Pick Call Status as the trigger. Set the filter to Status: Missed on the business number you want to monitor.
3. Add a wait step. A 30-second wait before sending the text reads as more human and avoids overlapping with voicemail prompts on some carriers.
4. Add the SMS action. From the caller's number, send your approved text body (see the next section). Use merge fields for first name only if you have high confidence the name is populated.
5. Add a CRM action. Create or update the contact, tag with missed-call, and assign to the right pipeline stage so the lead is visible in your daily list.
6. Add a notification. Push a notification to the on-call staff member by SMS or app notification. The text-back alone is not enough — your team should know a real human is waiting.
7. Publish. Switch the workflow to Published. Confirm the trigger filter shows the right number and the workflow is set to allow re-entry, so a repeat missed call within a day does not silently skip.

Use a body that is specific, polite, and asks for a single next action.

Hi, this is [Company Name]. Sorry we missed your call just now. We are with a customer. Reply here with your address and the issue and we will get you on today's schedule, or call us back at [main number]. — [Owner first name]

What makes that version work and most off-the-shelf templates fail:

• It identifies the business in the first three words so the recipient does not block it as spam.
• It explains why you missed the call without sounding evasive.
• It asks for exactly one thing — address and issue — instead of a list of questions.
• It signs with a human name. That alone lifts reply rates measurably.

1. Call the business number from a personal phone that is not already in your CRM. Let it ring until it goes to voicemail. Hang up.
2. Wait 60 seconds. Confirm the text arrived, the body is correct, and the sender ID shows the business number.
3. Reply to the text. Confirm the reply lands in the conversation inbox of the correct GoHighLevel sub-account.
4. Open the CRM and confirm a new contact was created with the right tag and pipeline stage.
5. Confirm the staff notification fired and reached the right phone.
6. Repeat once with a number that is already in the CRM. The workflow should still fire, the contact should not be duplicated, and the tag should be added.

• Skipping A2P 10DLC registration. The workflow will look like it is running but a meaningful share of messages will be filtered by carriers and never delivered. Register first.
• Using "we are sorry we missed your call" verbatim from a template pack. That exact phrase is filtered or de-prioritized by some carriers. Rewrite in your voice.
• Forgetting the human escalation. The text-back keeps the lead warm for a few minutes, not for an hour. Pair it with a staff notification so a real person follows up fast.
• No re-entry rule. If the same caller misses twice in a day, your workflow should send a fresh, shorter follow-up, not skip silently.

Missed-call text-back is the smallest, fastest win in a full speed-to-lead workflow. For the broader build, see our speed-to-lead guide and the full GoHighLevel setup checklist. If you want voice calls answered as well as missed-call recovery, our AI receptionist and voice agent service covers both. To have us build the whole stack with you, see the all-in-one CRM setup.