Missed Call Text Back in GHL: HighLevel Setup

Quick answer: in HighLevel (GHL), either tick “Enable Missed Call Text Back” under Settings → Phone System → Voice → Voicemail & Missed Call Text Back, or build a workflow: a Call Details trigger (Call Direction = Incoming; Call Status = busy, no-answer, voicemail) followed by Send SMS. Set the Incoming Call Timeout to about 20 seconds. US local numbers need a linked A2P 10DLC campaign (HighLevel says allow up to 24 hours after approval, and that carriers may take several business days); Australian numbers need a linked Regulatory Bundle.

Covered on this page: HighLevel’s Missed Call Text Back setting, the Call Details workflow trigger and its five filters, the Send SMS, Wait, If/Else, Add Contact Tag and Send Internal Notification actions, LeadConnector (LC) Phone numbers, the Trust Center’s A2P 10DLC brand and campaign registration, toll-free verification, Call Connect, Australian Regulatory Bundles, Twilio’s Australian SMS guidelines and the ACMA’s Spam Act guidance. Every HighLevel name below was copied from HighLevel’s own help centre on 20 October 2026.

Where Zian fits: answering the call instead of texting after it

Missed call text back limits the damage after a call is lost; an AI receptionist stops the call being lost. Zian AI’s AI Receptionist answers inbound calls 24/7, qualifies the caller, books the appointment, transfers or takes a message, and then follows up by SMS, WhatsApp, email or voice. Zian’s features and integrations page lists HighLevel as a CRM integration alongside HubSpot and Salesforce, and Zian also lists Zapier among its integrations. It also handles answering machines and voicemail on calls, in 30+ languages. If you would rather have the whole thing run for you, LeadsNow.ai is the done-for-you option. It is a managed, pay-per-result AI appointment-setting service that runs on Zian and answers leads in under 60 seconds, 24/7 (leadsnow.ai).

To be fair to HighLevel, it has a native version of the same idea. Its routing guide lets a Voice AI agent “Use as backup” after the Incoming Call Timeout, or “Answer calls directly”. If you want everything inside one HighLevel sub-account, test that too. Either way, keep the text-back workflow on this page as the fallback for callers who hang up before anything answers. Zian is in a partnership-application beta and does not publish prices.

How do I set up missed call text back in GHL? Two routes

HighLevel documents the feature in one sentence: “Missed Call Text Back is a feature that automatically sends a text message to a caller when their inbound call is missed” (HighLevel Support Portal, modified 7 September 2026). You can switch that feature on, or you can build the same behaviour as a workflow and control every step. The table compares the two using HighLevel’s own descriptions.

Question	Route A: Settings toggle	Route B: Call Details workflow
Where it lives	Settings → Phone System → Voice → Voicemail & Missed Call Text Back → Missed Call Text Back	Automation → Workflows → Create Workflow → Start from Scratch → Add New Trigger → Call Details
What fires it	An inbound call that “goes unanswered past your ring timeout”	A call log that matches your filters: Call Direction, Call Status, In Number Pool, Custom Disposition, In Phone Number
Repeat callers	Texts “every missed call — even if the same caller tries multiple times within a brief timeframe”	You decide, with a tag check, a Wait step and the Allow Re-entry setting
Which number sends	The number called if it can send SMS; otherwise a number that has messaged the contact before, then the default outbound number, then any other eligible number	The sending number set on your Send SMS action and messaging configuration
What happens after the text	The article describes no follow-up steps; your team handles the reply	Anything in the workflow: wait for a reply, notify a user, add a task, escalate
Setup effort	Five steps in HighLevel’s guide	About 14 steps in our checklist below
Best for	One main number, low call volume, nobody needs alerting	Several numbers, number pools, staff alerts, or repeat callers you do not want to text twice

Route A is enough for many single-location accounts; HighLevel calls it a “Simple setup”. For repeat callers, its Missed Call Text Back article recommends building on “the existing recipe in Workflows” and adding “a 20 +/− minute Wait step, or filter using tags such as 1st call, 2nd call”. We could not find a HighLevel help article that names that recipe or template, as at 20 October 2026, so the checklist below builds from scratch.

Run one route, not both. Neither HighLevel article says the Settings toggle and a Call Details workflow check each other for duplicates. If you build Route B, untick “Enable Missed Call Text Back” in Settings. Otherwise a missed caller may get two texts.

What must be in place before the first text sends

A workflow can run perfectly and still send nothing if the number is not allowed to send. Check these first.

Prerequisite	United States	Australia	Where to check in HighLevel
Calls ring a HighLevel (LC Phone) number	Customers dial the LC number, or your existing number forwards into it. HighLevel’s forwarding guide lists US carrier codes	Same principle; HighLevel’s guide lists US carriers only, so use your Australian carrier’s own forwarding instructions	Settings → Phone System → Phone Numbers
The sending number is SMS-capable	Filter on SMS capability when you purchase the number; a number that can make calls may still be voice-only	Same: check the capability column at purchase	Settings → Phone Numbers → open the number → Messaging enabled
Identity check at purchase	Persona verification when buying an eligible +1 number (US, Canada, Puerto Rico), if the sub-account has not completed it before	Not the Persona check; see the Regulatory Bundle row	Prompted in the purchase flow
Messaging registration	A2P 10DLC brand and campaign approved, and the number linked to the campaign (green “A2P Verified” label). Toll-free numbers use toll-free verification instead	An approved Business Regulatory Bundle linked to each AU local number (green “KYC Linked” tag). HighLevel says AU mobile and toll-free numbers “also require bundles”	Settings → Phone System → Trust Center (US); Settings → Phone System → Regulatory Bundles (AU)
Waiting time after approval	“Up to 24 hours” after A2P approval before the number is fully registered with carriers; HighLevel’s registration article adds that carrier systems “may also require several business days”	Bundle review “typically takes 1–3 business days”	Phone Numbers list labels
Sole Proprietor limit	Sole Proprietor brands are limited to “1 campaign and 1 phone number per campaign”. A second local number can hit error 30034	Not applicable	Trust Center → Brands and Campaigns

Two details from HighLevel’s A2P pages matter for a text-back campaign. First, the campaign registration guide says sample messages should “identify the sender, align with the selected use case, and include applicable opt-out language”, and adds: “Do not include custom fields or values in sample messages.” So register the text-back wording with your real business name typed in. Second, the registration asks how contacts opt in, and a caller who rang you has not ticked an SMS box; describe what really happens. If your campaign has already come back rejected, our guide to why A2P 10DLC campaigns get rejected and how to fix them maps the rejection codes. The US consent rules for texting a missed caller (TCPA, CTIA) are covered in the legal section of our missed call text back ROI calculator, which also does the cost arithmetic this page leaves out.

In Australia the deadline has already passed. HighLevel’s bundle article (modified 2 June 2026, before the deadline) says AU local numbers not linked to an approved bundle “will stop sending or receiving calls and messages” after 1 July 2026, with “no grace period”. On that wording, a text-back on an unlinked AU number fails along with the calls.

When does a call count as “missed” in HighLevel?

A call counts as missed when it rings past the Incoming Call Timeout without anyone answering. That one setting decides whether a text-back fires at all. HighLevel’s Missed Call Text Back article says the timeout “determines when a call counts as ‘missed’”, and that “10 to 20 seconds is typically recommended”. Its newer Incoming Call Settings article (modified 10 September 2026) is stricter. It recommends about 20 seconds. It warns that above about 20 seconds “calls may go to the carrier voicemail instead of CRM voicemail” and the call status “may be marked as “Completed” instead of “Voicemail””. Below about 15 seconds, callers “may not have enough time to answer”. A value of 15 to 20 seconds satisfies both articles; we use 20.

That “Completed” warning is the quiet killer of text-back workflows. Suppose your HighLevel number forwards to a mobile and the mobile’s own voicemail picks up first. HighLevel can then see a completed call, and a workflow filtered on no-answer never runs. HighLevel’s Call Connect article explains why: “Twilio marks all calls as “Completed” once they finish routing—even if no one answers.” Its fix is Call Connect (Edit Configuration → Advanced Settings), which makes the person answering “press a key before being connected”. HighLevel says this is “one of the main use cases” when calls forward to a personal or external number. Calls answered in the HighLevel web or mobile app generally do not need it.

Routing order matters too. HighLevel’s inbound call routing guide evaluates IVR or workflow routing first, then a Voice AI set to answer directly, then owner-based routing, then team devices and up to six Ring More Team Members, then the forwarding number. After the timeout comes the backup, Voice AI or voicemail. HighLevel’s timeout guidance treats a call that reaches CRM voicemail as status “Voicemail”, not no-answer. That is why the trigger below includes voicemail.

The timing table: ring timeout → text → follow-up

Each row says what HighLevel documents and what we use as a default. Our defaults are our judgement, not HighLevel settings or measured results, so change them to fit how fast your team actually replies.

Stage	HighLevel setting	What HighLevel documents	Our default
Ring before the call counts as missed	Incoming Call Timeout (Edit Configuration)	10–20 s (Missed Call Text Back article); ~20 s recommended, warning outside ~15–20 s (Incoming Call Settings)	20 seconds
First text	Call Details trigger → Send SMS	Sent “when the workflow reaches the Send SMS action”	Immediately, no Wait before it
Repeat-call suppression	If/Else on a tag, or a Wait step	“a 20 +/− minute Wait step, or filter using tags such as 1st call, 2nd call”	Tag check; tag removed after 24 hours
Wait for the caller’s reply	Wait → The contact to reply (SMS), Timeout on	Timeout on/off with a duration you choose	15 minutes
Staff response deadline	Wait → A user to reply, Timeout on	Holds until a team member replies, “with an optional timeout so the workflow can escalate”	10 minutes in business hours
After-hours hold	Wait → A set period of time → Advance Window	“Resume on selected days, Resume between hours”	Hold the callback task until opening time

We suppress repeats with a tag rather than HighLevel’s suggested 20-minute Wait, because a Wait placed before the Send SMS delays every first text by 20 minutes.

The build checklist: missed call text back as a HighLevel workflow

The trigger, filter and action names below come from HighLevel’s Call Details trigger article (modified 4 September 2026), its list of workflow actions and its Wait action guide. Steps 1 to 3 happen outside the workflow.

1. Confirm the prerequisites. In Settings → Phone System → Phone Numbers, the number shows “A2P Verified” (US local), is toll-free verified (US toll-free), or shows “KYC Linked” (AU local).
2. Set the Incoming Call Timeout. Open Settings → Phone Numbers, the number’s three-dot menu → Edit Configuration → Call Forwarding, and set it to 20 seconds. Pick a backup (Voice AI or Voicemail). The Missed Call Text Back panel also shows an incoming call timeout slider under Voicemail Settings.
3. Turn on Call Connect if calls forward to a personal or external phone (Advanced Settings → Call Connect, with Play Whisper Message on).
4. Create the workflow. Automation → Workflows → Create Workflow → Start from Scratch. Name it “Missed call text back”.
5. Add the trigger. Add New Trigger → Call Details. Name it “Incoming missed call”.
6. Set the filters. Call Direction = Incoming. Call Status = busy, no-answer and voicemail (you can select several values in one filter). Add In Phone Number if only one line should text back, or In Number Pool for a tracking pool.
7. Gate repeat callers. Add If/Else with a condition on the contact’s tags (the tag filtering HighLevel’s article suggests): has mctb-recent → end that branch. The None branch continues.
8. Tag the caller. Add Contact Tag: mctb-recent.
9. Send the text. Send SMS with the template below, then send yourself a test from the Test Phone Number field.
10. Wait for a reply. Wait → The contact to reply, channel SMS, Timeout on, 15 minutes.
11. If they reply: Send Internal Notification to the assigned user (in-app plus SMS or email), then Wait → A user to reply with a 10-minute timeout. If that times out, add a second Send Internal Notification action for a manager.
12. If they do not reply: Add Task “Call back missed caller”, after a Wait → A set period of time (1 minute) with Advance Window → Resume between hours set to your opening hours, so the task lands when someone is there.
13. Clear the gate. On both branches, end with Wait → A set period of time, 24 hours → Remove Contact Tag: mctb-recent.
14. Settings and publish. In the workflow’s Settings tab turn on Allow Re-entry, so a caller who rings again next week is texted again. Untick the Settings toggle (Route A), switch the workflow from Draft to Publish, and place a test call from a phone that is not saved in the account.

Why the tag gate in steps 7 and 13? A contact “cannot normally re-enter while still active in the same workflow”, which blocks some repeats already. But HighLevel’s older Call Details article warns that “the trigger activates for each status change” and advises “conditions or cooldown periods”. The tag is that condition, and staff can see it on the contact.

Finished state: one test call from an unknown mobile produces one text after the timeout. A second call within 24 hours produces no second text. A reply creates an alert, and the Enrollment History tab shows the contact passing every step. If any of those is missing, go to the troubleshooting table.

Missed call text back message template, with opt-out wording

Keep the first text to one segment and plain ASCII characters. Twilio’s Australian guidelines give the single-message length as “GSM 3.38=160, Unicode=70”, so one curly apostrophe or emoji cuts the limit from 160 characters to 70. Type these into HighLevel exactly as shown, with straight characters and no dashes:

Use	Text (type it exactly)	Characters
US first text (Send SMS action)	Hi, this is [Business name]. Sorry we missed your call. How can we help? You can reply to this text. Reply STOP to opt out.	108 plus your business name: names up to 52 characters keep it within 160
Australian first text	Hi, this is [Business name]. Sorry we missed your call. How can we help? Reply here or call [your number]. Reply STOP to opt out.	101 plus name and number: with a 12-character number such as 02 XXXX XXXX, names up to 47 characters fit in 160
A2P campaign sample message	Hi, this is [your legal business name]. Sorry we missed your call. How can we help? Reply STOP to opt out.	80 plus your legal name; type the real name, no custom fields

Why each part is there. The business name identifies the sender, which HighLevel’s A2P guide asks of sample messages and the ACMA asks of commercial messages. “Reply STOP to opt out” matches the “reply STOP to opt out” wording in HighLevel’s A2P opt-in examples, and it matches the ACMA’s own SMS example, “Reply STOP”. HighLevel’s error 21610 article lists STOP, STOPALL, UNSUBSCRIBE, CANCEL, END and QUIT as opt-out keywords, and START or YES to resubscribe. Ending on a question (“How can we help?”) gives the caller something to answer. Leave out offers and links. The text acknowledges a call; it is not a promotion. We type the business name rather than use a placeholder: HighLevel’s Missed Call Text Back article warns that placeholders such as the contact’s name only work if HighLevel already knows the contact from an earlier interaction, and a first-time caller is not known yet.

We counted all three templates with Python on 20 October 2026, with the bracketed placeholders removed. All three are plain ASCII.

Why didn’t my missed call text send? The three-gate test

The three-gate test: a missed-call text only goes out if three gates pass in order. Gate 1: HighLevel logged the call as busy, no-answer or voicemail. Gate 2: the sending number is allowed to send. Gate 3: the contact can receive it. Find the gate first, then the code. HighLevel shows errors in Conversations with a red status, on the contact timeline, and in workflow Execution Logs. LC Phone codes are explained in its error code and warning dictionary. Accounts on their own Twilio (BYOT) also have Twilio’s message logs.

Gate	Symptom	Status or code (HighLevel’s wording)	Fix
1	Workflow never enrolled the caller	Call status “Completed” although nobody answered	Lower the Incoming Call Timeout to about 20 s; turn on Call Connect for forwarded calls
1	Workflow never enrolled the caller	Workflow still in Draft, or (for a repeat caller) Allow Re-entry off	Publish it; check the Enrollment History and Execution Logs tabs
1	Nothing for calls to your old number	No call log in HighLevel	The call never reached HighLevel; fix forwarding and avoid the redirect loop HighLevel warns about
1	Two texts for one call	Settings toggle and workflow both on	Untick “Enable Missed Call Text Back” when the workflow is live
2	Send rejected at once	21661 “’From’ number is not SMS-capable”; 21606 “not a valid message-capable phone number for this destination/account”	Use an SMS-capable number in this sub-account; finish any port first
2	US local number fails	30034 “Message from an Unregistered Number”	Link the number to the approved campaign (A2P Verified label); wait up to 24 hours after approval; one number only on Sole Proprietor
2	US number recently approved	30035 “Message from a number still being configured”	Wait; HighLevel says allow “up to approximately 24 hours”
2	US toll-free number fails	30032 “Toll-Free Number Has Not Been Verified”	Complete toll-free verification
2	Campaign stopped working	30033 “US A2P 10DLC - Campaign Suspended”	Contact HighLevel Support for the reason
2	Sending capped	30023 “Daily Message Cap Reached”	The cap is per Brand (per EIN) to T-Mobile; contact Support
2	Australian number dead for calls and texts	“Bundle required” tag on the number	Link an approved Business Regulatory Bundle
2	Text came from a different number	Not an error	Route A’s sending-number fallback: the dialled number could not send SMS
3	Caller opted out or is on DND	21610 “Attempt to send to unsubscribed recipient”	An opt-out is reversed only by the caller texting START or YES; DND is a separate toggle on the contact record
3	Caller rang from a landline	21614 “’To’ number is not a valid mobile number”; 21635 “The “To” number is a landline”; 30006 “Landline or unreachable carrier”	Nothing to fix; route landline callers to a callback task
3	Accepted, never delivered	30007 “Message filtered”	Review content and consent; send Support 3 or more examples
3	Handset unreachable	30003 “Number unreachable or out of service”; 30005 recipient number inactive	Retest once; repeated 30003 on long codes can be carrier filtering
3	International caller	21408 “not allowed to send SMS to this country or region”	Ask Support to enable the destination

You can automate the alert for Gates 2 and 3. HighLevel’s Messaging Error - SMS trigger enrols a contact when an SMS ends undelivered with a selected code. It lists 20 codes, including 30007, 30034, 21610 and 21661. Build a second small workflow on it that adds a callback task, so a failed text-back still produces a human call. If 30007 keeps showing up, our guide to carrier filtering and Twilio error 30007 covers the content checks. Before you escalate, HighLevel’s SMS troubleshooting guide asks for “the sending number, recipient number, timestamp, and error code”.

Setting up missed call text back in HighLevel from Australia

Three things change for Australian accounts. First, registration. Twilio’s Australian SMS guidelines list no registration step for domestic long codes (provisioning time “N/A”). The pre-registration they do list is for alphanumeric sender IDs, and unregistered ones are delivered as “Unverified”. HighLevel’s own requirement is the Regulatory Bundle described above. You create it once per sub-account, with the client’s business details rather than the agency’s, and one approved bundle can be linked to every AU local number in that sub-account.

Second, the sender type. A text-back exists to start a conversation, so send it from a phone number that can take replies, not an alphanumeric name. The ACMA notes that alphanumeric message headers “are generally not capable of receiving return messages”.

Third, the message rules. If your text-back is a commercial message, the ACMA’s guidance requires three things. You need consent. The message must identify you with correct contact details that stay valid for at least 30 days. And it needs an unsubscribe option that is clear, free or standard-rate to use, honoured within 5 working days, working for at least 30 days, and that does not ask for extra details or a login. Whether a reply to someone who just rang you is “commercial” depends on what you write, so keep the first text to an acknowledgement. Our analysis of after-hours enquiries in Australia shows how to count your real missed calls from call records first.

What the DIY build costs you to run

The workflow is about 14 steps. The waiting and the upkeep take longer. On HighLevel’s published timelines, a US local number is not ready until the A2P brand and campaign are approved, then linked, then given up to 24 hours (HighLevel’s registration article says carriers may take several business days). An Australian number needs a bundle reviewed in 1–3 business days, and a rejected bundle or campaign goes back for another review. After launch, someone has to watch the Messaging Error alerts, answer replies at 9pm, and re-test when HighLevel changes call routing; all three core articles above were revised in September 2026.

A text-back also only reaches people willing to text. A caller who does not reply is still a missed call, and so is one who replies at night and waits until morning.

Frequently asked questions

Does HighLevel have a built-in missed call text back?

Yes. In a sub-account go to Settings → Phone System → Voice → Voicemail & Missed Call Text Back, tick “Enable Missed Call Text Back”, write the message, send a test and save. HighLevel’s own article describes the five steps and says it texts every missed call, including repeat calls from the same person (HighLevel Support Portal, modified 7 September 2026).

Which workflow trigger fires on a missed call in GHL?

The Call Details trigger. Set Call Direction to Incoming and Call Status to busy, no-answer and voicemail. HighLevel lists five filters on that trigger: Call Direction, Call Status, In Number Pool, Custom Disposition and In Phone Number.

How long should the phone ring before the text-back sends?

About 20 seconds. HighLevel’s Missed Call Text Back article says 10 to 20 seconds is typically recommended. Its Incoming Call Settings article warns below about 15 seconds and above about 20, because a long timeout can let carrier voicemail answer and the call is then logged as Completed, not missed.

Why is my GHL missed call text back not sending?

Check three gates in order: the call was logged as busy, no-answer or voicemail; the sending number may send (no 21661, 30034, 30032 or 30033); the caller can receive (no 21610 opt-out, not a landline). The error code shows on the failed message in Conversations.

Do I need A2P 10DLC for missed call text back?

Yes, if you text US recipients from a US 10-digit local number. HighLevel requires an approved brand and campaign with the number linked (A2P Verified), and says to allow up to 24 hours after approval, though carrier systems may take several business days. Toll-free numbers need toll-free verification instead.

Can I use missed call text back in HighLevel in Australia?

Yes, once the sending number is SMS-capable and each AU local number is linked to an approved Business Regulatory Bundle. HighLevel’s bundle article (modified 2 June 2026) says unlinked numbers will stop sending or receiving calls and messages after 1 July 2026, with no grace period. Send from a number that can receive replies, and include your business name and a STOP option.

Can HighLevel send a WhatsApp message instead of an SMS after a missed call?

Yes. HighLevel has a separate Missed Call WhatsApp Back setting in the same Voicemail & Missed Call Text Back area. It needs a WhatsApp-enabled number connected to the sub-account (HighLevel Support Portal).

Where every figure on this page comes from

Figure	Who published it	Link	Date read
10–20 s ring timeout recommended; texts every missed call; 4-level sending-number fallback; 20 +/− minute Wait suggestion	HighLevel	help.gohighlevel.com/support/solutions/articles/48001239140-where-and-how-to-configure-the-missed-call-text-back-feature	20 October 2026
~20 s recommended timeout; warnings above ~20 s and below ~15 s; Completed vs Voicemail status	HighLevel	help.gohighlevel.com/support/solutions/articles/155000006881-phone-number-edit-configuration-incoming-calls-settings-	20 October 2026
Call Details trigger, its 5 filters and status values busy / no-answer / voicemail / completed; Allow Re-entry	HighLevel	help.gohighlevel.com/support/solutions/articles/48001212511-workflow-trigger-call-details	20 October 2026
“The trigger activates for each status change”	HighLevel	help.gohighlevel.com/support/solutions/articles/155000002552-workflow-trigger-call-details	20 October 2026
Routing order; up to 6 Ring More Team Members; Voice AI “Use as backup”	HighLevel	help.gohighlevel.com/support/solutions/articles/155000007498-inbound-calls-ivr-ai-routing-call-flow-explained	20 October 2026
Twilio marks calls “Completed” even if no one answers; Call Connect	HighLevel	help.gohighlevel.com/support/solutions/articles/48001181825-using-call-connect-to-ensure-accurate-call-status-tracking	20 October 2026
Wait action types, timeouts and Advance Window	HighLevel	help.gohighlevel.com/support/solutions/articles/155000002470-workflow-action-wait	20 October 2026
A2P 10DLC required for US recipients from 10-digit local numbers; toll-free uses separate verification; carriers may take several business days after approval	HighLevel	help.gohighlevel.com/support/solutions/articles/155000002380-what-is-a2p-10-dlc-brand-and-campaign-registration	20 October 2026
Sample messages: opt-out language, no custom fields	HighLevel	help.gohighlevel.com/support/solutions/articles/155000004539-a2p-campaign-registration-step-by-step-guide-and-faqs	20 October 2026
Sole Proprietor: 1 campaign and 1 phone number per campaign; A2P Verified label	HighLevel	help.gohighlevel.com/support/solutions/articles/155000008316-error-30034-linking-a-phone-number-to-an-approved-a2p-campaign	20 October 2026
Error codes 21408, 21606, 21614, 21635, 21661, 30003, 30005, 30006, 30007, 30023, 30032–30035, 21610; up to 24 hours after A2P approval; 3 or more examples for Support	HighLevel (LC Phone)	help.gohighlevel.com/support/solutions/articles/155000005526-lc-phone-system-error-code-and-warning-dictionary	20 October 2026
Messaging Error - SMS trigger lists 20 codes	HighLevel	help.gohighlevel.com/support/solutions/articles/155000003201-workflow-trigger-messaging-error-code-sms	20 October 2026
Where errors appear; what Support needs	HighLevel	help.gohighlevel.com/support/solutions/articles/48000981696-troubleshooting-sms-delivery-issues	20 October 2026
AU Regulatory Bundle; 1 July 2026 deadline; 1–3 business days review	HighLevel	help.gohighlevel.com/support/solutions/articles/155000008023-how-to-create-and-link-a-regulatory-bundle-for-australian-local-numbers	20 October 2026
Persona verification for eligible +1 and +972 numbers; SMS capability filter	HighLevel	help.gohighlevel.com/support/solutions/articles/155000003226-how-to-purchase-a-phone-number	20 October 2026
“reply STOP to opt out” consent wording	HighLevel	help.gohighlevel.com/support/solutions/articles/155000007237-how-to-get-your-phone-number-a2p-approved-in-2026	20 October 2026
Opt-out keywords STOP, STOPALL, UNSUBSCRIBE, CANCEL, END, QUIT; START / YES	HighLevel	help.gohighlevel.com/support/solutions/articles/48001186075-twilio-error-21610-recipient-unsubscribed-stop-when-sending-sms	20 October 2026
Single SMS length GSM 160 / Unicode 70; AU long codes provisioning “N/A”; alphanumeric pre-registration	Twilio	www.twilio.com/en-us/guidelines/au/sms	20 October 2026
Unsubscribe honoured within 5 working days; details valid at least 30 days; “Reply STOP” example	ACMA	www.acma.gov.au/avoid-sending-spam	20 October 2026
Template lengths 108 / 101 / 80 characters; 52 and 47-character name limits	Zian (our own count)	Counted with Python on this page’s template	20 October 2026
Timing defaults: 20 s, 15 min, 10 min, 24 h	Zian (our defaults, not measurements)	This page	20 October 2026