GoHighLevel can send an SMS after an inbound call goes unanswered. The built-in setting is the shortest path when every missed call should receive the same acknowledgement. A custom workflow is the safer choice when repeat calls, business hours, routing, ownership, or different call outcomes need different treatment.
The text is only the acknowledgement. A complete missed-call recovery path also decides which number sends it, when repeated calls should be suppressed, who owns the callback, what stops automation, and how the team will prove the setup works.
Choose the built-in feature or a workflow first
HighLevel’s current built-in setting sends a text for every missed call, including repeated missed calls from the same caller in a short period. HighLevel therefore recommends a customized workflow when a business needs waits or tag-based repeat-call control. That distinction should be made before either option is enabled, because running both for the same call can create duplicate messages.
| Decision | Built-in missed-call text back | Custom workflow |
|---|---|---|
| Message rule | The same acknowledgement for each missed call | Conditions, branches, waits, business hours, and different messages |
| Repeat callers | Sends for every missed call | Can suppress or change the response during a defined window |
| Ownership | Must be handled outside the setting | Can create a task, assign an owner, or notify staff |
| Troubleshooting | Check phone settings and the conversation record | Also check the trigger, enrollment history, and execution logs |
| Best fit | One simple acknowledgement with a clear manual callback process | A lifecycle-aware missed-call process with exceptions |
Our decision rule is simple: use the native feature only when the business truly wants one message after every missed call and already has a reliable callback owner. Use a workflow when the response depends on context. We would not activate the native setting and a missed-call workflow together without an explicit reason and a test proving only one customer-facing SMS is produced.
Set up the current built-in feature
HighLevel’s support article, last modified September 7, 2026, gives this current path: Settings → Phone System → Voice → Voicemail & Missed Call Text Back → Missed Call Text Back. Enable the feature, select Customize, write the acknowledgement, send a test, and save. Older instructions that point to Business Profile or a different phone menu should be treated as stale unless that is what the account actually shows. See HighLevel’s Missed Call Text Back setup guide.
Keep the message factual. State that the call was missed, identify the business, and explain what the caller can do next. Do not imply that a technician is already dispatched, that an appointment is confirmed, or that an emergency response is underway unless the business has actually made that commitment.
Merge fields need a known contact record to populate reliably. Test the message with both a recognized contact and a genuinely new caller. A raw placeholder in a text is a setup failure, not a harmless cosmetic issue.
Treat call routing and the timeout as part of the trigger
The feature fires only after an inbound call remains unanswered past the incoming-call timeout. Answered calls do not trigger it. HighLevel currently documents an adjustable voicemail timeout and notes that a very short timeout can classify a call as missed before a person has a reasonable chance to answer, while a long timeout delays the acknowledgement.
That means the test cannot begin with the SMS. Start with the call path:
- Confirm the public number reaches the intended HighLevel number and routing rule.
- Confirm the assigned user, forwarding destination, or ring group can actually receive the call.
- Record the configured timeout and the expected voicemail behavior.
- Call from an external number and let the full timeout expire.
- Repeat the test with a staff member answering before the timeout.
The missed-call text should appear only in the first case. If forwarding sends the call somewhere that answers automatically, or a carrier voicemail intercepts it differently, the result may not match a simple test inside the message editor.
Understand which number sends the SMS
HighLevel no longer always depends on the number the customer called. Its current documented selection order is:
- the called number, if it is eligible to send SMS;
- a number that has successfully messaged the contact before;
- the location’s default outbound number;
- another eligible messaging number in the location.
This fallback helps when the called number is voice-only, part of a number pool, or otherwise unable to send. It can also surprise a customer who receives the reply from a different number. If no eligible number exists, HighLevel says the failed attempt and reason appear in the conversation record.
An eligible local sending number needs the applicable A2P 10DLC registration, while a toll-free sending number needs toll-free verification. The feature respects the contact’s DND and communication preferences. Those are platform safeguards, not substitutes for a business’s own consent records, message purpose, and legal review. A missed call does not authorize unrelated promotional messaging.
Design repeat-call control deliberately
A caller may ring twice because the first attempt dropped, voicemail was confusing, or the need is urgent. Sending the same automated text after every attempt can feel careless. Suppressing everything after the first attempt can also hide a meaningful escalation.
Use a defined repeat window and outcome, not an indefinite “already texted” tag. For example:
| Observed event | Example rule | Human action |
|---|---|---|
| First missed call | Send one acknowledgement and mark the recovery window | Create or expose the callback task |
| Second miss inside the window | Do not repeat the same SMS | Raise the callback priority or notify the owner |
| New miss after the window | Reassess as a new contact attempt | Create a new callback obligation if appropriate |
| Caller replies by text | Stop generic missed-call messaging | Route the conversation to the responsible person |
| Staff returns the call | Close or update the callback state | Record the disposition |
The exact window is a business decision. It should reflect staffing, after-hours coverage, and how quickly a callback can realistically happen. We would not copy a generic 20-minute wait into every account without deciding what that period means operationally.
Give the callback a named owner
An immediate text can make the system look responsive while the actual callback remains unowned. Decide who watches the inbox, who calls back, and what happens when that person is unavailable. The assignment should survive shift changes and after-hours calls.
A practical workflow can create an internal task, apply a short-lived state tag, assign the contact when appropriate, and notify the responsible queue. The customer-facing message should not promise a response time that the team cannot consistently meet.
This is the same broader principle used in GoHighLevel lead follow-up for home services: every automated step needs a current state, an owner, a next action, and an exit. If the workflow does not enroll or takes the wrong branch, use the evidence order in GoHighLevel workflow not triggering? before rebuilding it.
Test the feature as a system
Use external phones and fresh test contacts. A send-test button proves message rendering and basic delivery, but not the inbound call classification, repeat-call rule, ownership, or stop behavior.
| Test | Expected customer result | Expected system evidence | Expected staff result |
|---|---|---|---|
| New caller, no answer | One SMS after the timeout | Missed call and SMS in the same conversation | Callback owner or queue is visible |
| Known caller, no answer | Personalization resolves correctly | Existing contact is updated, not duplicated | Existing ownership rule is respected |
| Answer before timeout | No missed-call SMS | Answered call recorded | No callback task created |
| Two misses inside repeat window | Only the designed repeat behavior occurs | One or two executions exactly as specified | Escalation rule is visible |
| DND contact calls | No SMS | Suppression is observable | Staff can still see the missed call |
| Called number cannot send SMS | Message uses the documented fallback, if available | Actual sending number is visible | Team understands why it differs |
| No eligible sending number | No customer message | Failure reason appears in the conversation | Owner has a manual recovery path |
| Caller replies | Generic automation stops or changes state | Reply and exit are recorded | A person owns the conversation |
Capture the source number, called number, time, timeout, message received, sending number, contact record, workflow execution, and staff notification. The pre-launch workflow testing guide explains how to turn those observations into pass or fail evidence.
Common mistakes to avoid
- Enabling the native feature and a workflow that both answer the same missed call.
- Testing only the message preview instead of making a real inbound call.
- Treating every repeat call as a new reason to send the same text.
- Ignoring the incoming-call timeout and routing path.
- Assuming the called number will always be the sending number.
- Leaving a fallback sender unverified or ineligible for SMS.
- Using a missed call as consent for promotional follow-up.
- Sending an acknowledgement without assigning the callback.
- Letting a customer reply while the system continues a generic sequence.
- Declaring success because an SMS sent, without checking the contact, ownership, and exit state.
Edex has implemented multi-workflow lead lifecycles with explicit pipeline and tag state, but this article does not claim a deployed client result for missed-call recovery. The setup and test rules above combine current platform documentation with Edex’s operating principles for ownership, suppression, and acceptance evidence.