Ary
A missed-call text can acknowledge a caller while the front desk is busy. Before enabling it, check the call route, texting permission, eligible sending number and the person responsible for
replies. A saved toggle alone does not prove that a caller receives a message.
What is missed call text back, and why does it matter for a med spa?
It is a configured response to an unanswered call. It gives an eligible caller another way to contact the practice; it does not guarantee a reply or booking.
The text can accompany the missed-call and voicemail process. Someone still needs to review replies and return calls that need a conversation.
Use your own call log to find the gap: how many calls were unanswered, which number they reached, and how quickly staff followed up. Generic vendor statistics across other industries
do not establish a med spa’s missed-call rate.
A prompt acknowledgement can clarify that the call was received. Measure actual replies and appointments in your own process; older sales-lead studies do not predict the booking lift from a
med-spa text.
Inbound call rings
The client dials your GoHighLevel number.
No answer after 10 to 20 seconds
GoHighLevel marks the call missed.
Check messaging eligibility
Check sender eligibility, consent and Do Not Disturb (DND).
Eligible sender
SMS can be attempted: an apology and a booking link.
Caller replies or books. Staff check the reply.
Review any failed sending attempt in Conversations.
Not eligible
SMS cannot be sent. Check the failure reason.
Caller gets nothing. Review Conversations.
How do you set up missed call text back in GoHighLevel?
First verify the permitted use, consent records and an eligible SMS sender. Then open Settings > Phone System > Voice > Voicemail & Missed Call Text Back in the correct
sub-account. Customize the message and call timeout, save, and run a controlled end-to-end test using a number whose owner has agreed to it.
Here's the path, per HighLevel's official docs (2026):
- Switch into the correct sub-account, not agency view.
- Go to Settings > Phone System > Voice > Voicemail & Missed Call Text Back.
- Tick the Missed Call Text Back checkbox.
- Write your message. There's a sample below.
- Set the incoming call timeout. HighLevel recommends 10 to 20 seconds. This is how long the call rings before it counts as missed.
- Send a test message to your own phone.
- Save.
Use an authorized test caller who is not already a contact to check the unknown-caller wording. Confirm the received text, sending number, reply destination and booking link. Also check DND
and repeat calls; one successful send does not prove every route.
Why is your missed call text back not sending?
Check sender eligibility, call routing, timeout settings, account configuration and message content. Also inspect DND, opt-outs, account limits and carrier errors. A blank merge field is a content problem; it
is not evidence that SMS delivery stopped.
| Error | What's happening | The fix |
|---|---|---|
| No A2P registration | A local number without the required approved campaign can fail with error 30034. Inspect the conversation failure details and confirm that the number is linked to the approved campaign. | Review the Trust Center and A2P 10DLC registration, monthly and carrier fees. Costs include initial brand/campaign registration and vetting, recurring campaign charges, and message/carrier usage. The listed initial bundle varies by registration tier; confirm the current quote before submitting. |
| Calls don't route through GHL | Your Google Business Profile or old ads still show your direct line. Those missed calls never touch GoHighLevel, so nothing fires. | Check the existing forwarding route and caller ID first. Preserve published numbers where possible; update listings only after the tested routing plan is agreed. |
| Timeout mismatch | If the timeout is longer than your actual ring-to-voicemail time, the call hits voicemail before GHL counts it as missed. | Time how long your line actually rings, then set the timeout a few seconds shorter. |
| Wrong account or unsaved config | The toggle was set in agency view, the wrong sub-account, or never saved. | Recheck in the sub-account and hit save. Run the test send. |
| Blank merge fields | Tags like first name only fill in when GHL already knows the contact. New callers get "Hi , sorry we missed you." | Write the message without merge fields, or with fallbacks. |
Test repeated calls explicitly. If you add a workflow to suppress duplicate responses, verify it alongside the built-in feature so two automations do not send the same acknowledgement.
Illustrative routing check: if a public listing points to a line that never reaches HighLevel, those missed calls may never create a HighLevel event. Verify forwarding and caller ID before
changing the number displayed to customers.
Read Missed Call Text Back: settings, fallback senders and failure visibility before diagnosing the sender. It may select an eligible fallback number when the dialed number cannot send SMS. If
none is eligible, the failure reason appears in the conversation. Use SMS delivery errors and troubleshooting to diagnose the cause instead of repeatedly resending.
What should the missed call text actually say?
Identify the practice, acknowledge the call and give a useful next step. Keep the message within the purpose the caller agreed to, provide opt-out instructions and avoid asking for health
details by ordinary SMS.
Hi, this is [Spa Name]. Sorry we missed your call. We will return it during [hours]. For scheduling: [booking link]. Please do not send medical details here. Reply STOP to
opt out.
Why this shape works:
- It explains the miss in a way clients respect. "We're with clients" tells them you'll treat their appointment the same way.
- It asks a question, which invites a reply and opens a two-way thread your front desk can answer between treatments.
- The booking link lets the ready-to-book caller finish the job at 9pm without anyone touching the phone.
Skip merge-field first names unless you've set fallbacks. New callers are unknown contacts, and a text that opens "Hi ," reads like a bot.
What I'd be careful about
A few honest caveats before you treat this as done.
Confirm permission before enabling the automation. A phone call or customer record is not blanket permission for promotional texts. Document the consent required for the intended message and provider, identify
the sender and honor opt-outs. Keep marketing enrollment separate from a response to an inquiry.
Check the number type. US local 10DLC messaging needs an approved brand and campaign; toll-free numbers use toll-free verification. Other countries have their own rules. Registration does not create consent
or guarantee delivery. Landlines and some other destinations cannot receive SMS. Delivery errors need a monitored response.
Protect health information. Keep clinical details out of the sample response. Where HIPAA applies, review PHI handling, vendor agreements and safeguards before using the messaging platform for patient communications.
Don't let it replace the call back. The text buys you time. Someone still has to answer the reply. A recovered lead who texts back into an unwatched inbox is
lost twice.
If you're not sure which of these problems you actually have, the System Snapshot shows you where things stand. The Setup Check is where we look at it together.
A quick last word
Check one complete path before trusting the feature: an eligible call reaches HighLevel, an expected message arrives, a reply reaches a person, and the booking link opens the right calendar.
Keep checking failed messages after launch.
Explore CRM and follow-up setup if you need help connecting that path. Bring the public number and a workflow description, without patient information.
