GoHighLevel SMS That Actually Delivers: Templates, Compliance, and Workflow Triggers

Why Your HighLevel SMS Isn’t Delivering

You built the workflow. You wrote the message. You hit save. Then crickets. Your SMS sits in the HighLevel conversation log marked “sent,” but your contact never saw it. Or worse, it landed in carrier spam filters and now your entire phone number is throttled.

SMS failure in GoHighLevel subaccounts usually traces back to five operator mistakes: wrong phone field in the workflow action, missing or undocumented consent, spammy first-message copy, ignored quiet hours, and unregistered A2P 10DLC campaigns. Each mistake is fixable once you know where to look.

This guide walks you through the mental model, the templates, the consent tags, the compliance registration, and the workflow triggers that actually deliver. No invented stats. No fake case studies. Just the operator checklist for SMS that reaches the inbox this week.

The Mental Model: Templates, Workflows, Broadcasts, and Campaigns

HighLevel separates SMS into four buckets, and confusion between them causes most launch failures.

Message Templates live under Settings → Templates (or Marketing → Templates in some navigation versions). These are reusable text snippets with merge fields. You write the template once—”Hi {{contact.first_name}}, your appointment with {{custom_values.business_name}} is confirmed for {{appointment.start_time}}.”—then reference that template in workflows, campaigns, or manual conversations. Templates do not send anything by themselves. They are blueprints.

Workflows (Automations) are trigger-based. Form submitted, tag added, appointment booked, missed call—something happens, the workflow fires, and an SMS action inside the workflow sends a specific template to that one contact. Workflows are one-to-one, event-driven, and run continuously in the background.

Campaigns (sometimes labeled Broadcasts in older HighLevel UI) are one-time or scheduled bulk sends. You pick a segment or filter, choose a template, and send to everyone in that list at once. Campaigns are one-to-many, operator-initiated, and do not repeat unless you manually schedule again.

Conversations is the inbox where all SMS threads appear, whether sent by workflow, campaign, or manual reply. The conversation log shows delivery status, carrier errors, and opt-out keywords. When troubleshooting, Conversations is your first stop.

Operators often build a workflow, then wonder why the SMS sent to 500 contacts at once—they accidentally used a campaign. Or they create a beautiful template and expect it to send automatically—it won’t, until a workflow or campaign calls it. Keep the four buckets clear.

Why SMS Fails in Subaccounts: The Five Usual Suspects

Wrong Phone Field in the Workflow Action

HighLevel contact records store phone numbers in multiple places: the primary phone field, custom fields labeled “Mobile” or “Cell,” and sometimes in opportunity or appointment metadata. When you add an SMS action to a workflow, the action defaults to {{contact.phone}}—but if your form or import wrote the number to a custom field instead, the workflow sends to a blank or mismatched value.

Check the workflow SMS action. Click into the phone number field. Confirm it points to the field where your phone numbers actually live. If you use a custom field, replace {{contact.phone}} with {{contact.custom_fields.mobile}} or whatever your field name is. Test by triggering the workflow with your own contact record and watching the conversation log.

Missing or Undocumented Consent

US carriers and the Telephone Consumer Protection Act (TCPA) require prior express written consent before you send marketing or informational SMS. “Prior express written” means the contact explicitly agreed to receive texts from your business, usually via checkbox or keyword opt-in, before you send the first message.

If you import a list from a spreadsheet, buy a lead list, or scrape contacts from another platform without documented consent, you have no proof of opt-in. Carriers flag the first batch of messages as spam, your number gets filtered, and deliverability drops across the board.

Operators must capture consent at the point of entry—form checkbox, landing page disclosure, keyword reply—and tag the contact immediately. No consent tag, no SMS workflow. We will cover the tagging pattern in detail below.

Spammy First Message

Your first SMS to a new contact sets the tone for carrier filters and human perception. Messages that open with “CONGRATULATIONS!” or “LIMITED TIME OFFER” or a wall of text with five links trigger spam scores. Messages that omit your business name or fail to remind the contact why they are hearing from you get marked as unknown sender.

Keep first messages short, human, and contextual. Remind the contact where they opted in. Use their first name. Include your business name. One link maximum. Save the pitch for message two or three, after they reply.

Ignored Quiet Hours

Workflows run 24/7 unless you add time-based filters. A form submitted at 11pm triggers the workflow immediately, and your “Thanks for reaching out!” SMS wakes the contact at 11:01pm. They mark it spam or reply angry, and your sender reputation takes a hit.

HighLevel workflows support business-hours filters and wait-until steps. Add a condition before every SMS action: if current time is outside 8am–8pm in the contact’s timezone, wait until 8am the next day. Quiet hours are not optional—they are baseline professionalism.

Unregistered A2P 10DLC

Application-to-Person (A2P) 10-digit long code (10DLC) registration is the carrier-level compliance framework for business SMS in the United States. If you send marketing, alerts, or transactional messages from a standard local phone number without registering your brand and campaign with the Campaign Registry, carriers throttle or block your messages.

HighLevel integrates A2P 10DLC registration under Settings → Phone Numbers (or via the Twilio subaccount if you bring your own). You register your business (brand), describe your messaging use case (campaign), submit sample messages, and provide proof of opt-in. Approval takes a few days. Once approved, your messages carry a trust score, and deliverability improves.

Skipping A2P registration is the single largest deliverability mistake operators make. We will walk through the registration checklist later in this guide.

Building Reusable SMS Templates with Merge Fields

Templates turn repetitive messages into one-click sends. Instead of rewriting “Hi [Name], your appointment is confirmed” in every workflow, you write it once as a template, then reference that template by name.

Navigate to Settings → Templates (or Marketing → Templates). Click Create Template. Choose SMS as the type. Give the template a clear name—”Appointment Confirmation” or “Lead Welcome” or “Missed Call Follow-Up.” The name is internal; contacts never see it.

In the message body, write your text and insert merge fields where dynamic data belongs. Common merge fields:

• {{contact.first_name}} – the contact’s first name from the contact record.
• {{contact.full_name}} – first and last name together.
• {{contact.email}} – email address, useful in confirmation messages.
• {{appointment.start_time}} – the scheduled start time of the appointment that triggered the workflow.
• {{appointment.calendar_name}} – the name of the calendar (useful if you run multiple service calendars).
• {{custom_values.business_name}} – a custom value you define once per subaccount, so every template pulls the same business name without hardcoding.
• {{custom_values.support_phone}} – your support or main line, defined as a custom value.
• {{custom_values.booking_link}} – a short URL to your calendar or landing page, defined once and reused everywhere.

Custom values live under Settings → Custom Values. Create key-value pairs like business_name = Acme Plumbing or booking_link = https://acme.link/book. Then every template that references {{custom_values.business_name}} pulls “Acme Plumbing” automatically. When you rebrand or change the URL, update the custom value once, and every template updates.

Example appointment confirmation template:

Hi {{contact.first_name}}, your appointment with {{custom_values.business_name}} is confirmed for {{appointment.start_time}}. Reply STOP to opt out.

Example lead welcome template:

Hi {{contact.first_name}}, thanks for requesting info from {{custom_values.business_name}}. I’ll follow up shortly. Questions? Call {{custom_values.support_phone}}. Reply STOP to opt out.

Keep templates under 160 characters when possible to avoid multi-segment charges and carrier concatenation issues. If you must go longer, stay under 300 characters and test on multiple carriers.

Always include opt-out language—”Reply STOP to opt out” or “Text STOP to unsubscribe.” Carriers and TCPA require an easy opt-out mechanism in every marketing or promotional message. Transactional messages (appointment reminders, password resets) have more flexibility, but including opt-out language everywhere is safer and builds trust.

Save the template. Now it appears in the template dropdown inside workflow SMS actions and campaign builders. You never retype the message again.

Consent and Opt-In/Opt-Out Tags: The Operator Pattern

SMS consent is not a legal checkbox you ignore after launch—it is an operational filter you enforce in every workflow. The pattern: capture consent at entry, tag the contact, filter every SMS workflow on that tag, and remove the tag immediately when someone opts out.

Capturing Consent on Forms

When you build a form in HighLevel (or embed an external form that posts to HighLevel), add a checkbox field labeled “I agree to receive text messages from [Business Name]. Message and data rates may apply. Reply STOP to opt out.”

Make the checkbox required or leave it optional, depending on your offer and legal review. (This guide is operational orientation, not legal advice. Consult a lawyer for TCPA compliance specifics.)

In the form settings, configure the submission workflow or automation to check: if the SMS consent checkbox is checked, add the tag SMS Opted In to the contact. If unchecked, do not add the tag. No tag, no SMS.

Some operators use a single tag (SMS Opted In). Others use two tags (SMS Opted In and DND – Unsubscribed SMS) to distinguish active consent from explicit opt-out. The two-tag pattern is cleaner for reporting: you can count how many contacts are opted in, how many opted out, and how many never consented.

Filtering Workflows on Consent Tags

Every workflow that sends SMS must include a filter step before the SMS action. Add a Condition or Filter element: if contact has tag SMS Opted In, continue; else, end workflow for this contact.

In HighLevel workflow builder, this looks like:

1. Trigger: Form Submitted (or Tag Added, Appointment Booked, etc.)
2. Condition: Contact has tag “SMS Opted In”
3. If Yes → SMS Action (send template)
4. If No → End or route to email-only path

This filter prevents accidental SMS to contacts who never consented, imported lists without opt-in, or contacts who previously opted out and still carry the DND tag.

Handling STOP, HELP, and Opt-Out Keywords

US carriers require that STOP, UNSUBSCRIBE, CANCEL, QUIT, and similar keywords immediately opt the contact out of future messages. HighLevel has built-in keyword handling: when a contact replies STOP, the platform automatically adds the contact to the Do Not Disturb (DND) list for SMS and stops sending.

As an operator, you should also tag the contact DND – Unsubscribed SMS when they reply STOP, and remove the SMS Opted In tag. This makes reporting clearer and ensures your workflow filters catch the opt-out even if the built-in DND list has a delay.

Set up a workflow:

1. Trigger: Inbound Message Received
2. Condition: Message body contains “STOP” or “UNSUBSCRIBE” (case-insensitive)
3. Action: Remove tag “SMS Opted In”
4. Action: Add tag “DND – Unsubscribed SMS”
5. Action: Send SMS reply: “You have been unsubscribed from {{custom_values.business_name}} messages. Reply START to opt back in.”

HELP keyword replies should send a short message with your business name and support contact: “This is {{custom_values.business_name}}. Questions? Call {{custom_values.support_phone}} or reply here.”

START keyword replies should reverse the opt-out: remove DND tag, add SMS Opted In tag, send confirmation: “You are now subscribed to {{custom_values.business_name}} messages. Reply STOP to opt out anytime.”

These workflows are not automatic in every HighLevel subaccount—you must build them. They take ten minutes and prevent compliance headaches for the next ten years.

Quiet Hours and Business Hours in Workflows

Workflows fire the instant their trigger condition is met. A form submitted at 2am triggers the workflow at 2am. Without a time filter, your SMS sends at 2am.

HighLevel workflows support time-based conditions and wait steps. Add a condition before every SMS action:

If current time is between 8:00 AM and 8:00 PM (contact’s timezone), send SMS immediately. Else, wait until 8:00 AM the next day, then send.

In the workflow builder:

1. Add a Condition element.
2. Choose “Current Time” or “Business Hours” (depending on your HighLevel version).
3. Set start time 8:00 AM, end time 8:00 PM.
4. Choose timezone: contact’s timezone (if you collect it) or subaccount default timezone.
5. If condition is true (inside business hours), route to SMS action.
6. If condition is false (outside business hours), route to a Wait Until step: wait until 8:00 AM, then send SMS.

Some operators set quiet hours 9am–9pm. Others use 8am–8pm. Choose based on your audience and industry. Do not skip this step. Texting at 2am is the fastest way to get marked spam and burn your sender reputation.

For appointment reminders, you may want a tighter window—send reminders only between 9am and 6pm, so a 7am appointment does not trigger a 6am reminder. Adjust the condition to match your calendar and customer expectations.

A2P 10DLC Registration: The Operator Checklist

A2P 10DLC registration is the carrier-mandated compliance framework for business SMS sent from standard 10-digit local phone numbers in the United States. If you send SMS from a HighLevel phone number (or a Twilio number behind HighLevel), you must register your brand and campaign with the Campaign Registry. Unregistered numbers face severe throttling—sometimes as low as one message per minute—or outright blocking by major carriers.

This section is operational orientation, not legal advice. Consult a lawyer or compliance specialist for TCPA, CTIA, and carrier-specific requirements. The goal here is to give you the operator checklist so you know what to gather and where to click.

Brand Registration

Your brand is your business entity—LLC, corporation, sole proprietorship. You register the brand once, then create one or more campaigns under that brand.

In HighLevel, navigate to Settings → Phone Numbers (or Settings → Integrations → Twilio if you manage your own Twilio subaccount). Look for the A2P 10DLC or Brand Registration section. The exact UI varies by HighLevel release, but the flow is similar.

You will need:

• Legal business name – exactly as registered with your state or country.
• Business type – sole proprietor, LLC, corporation, non-profit.
• EIN or Tax ID – for US businesses, your Employer Identification Number.
• Business address – physical address, not a PO box.
• Business phone – a contact number for your business (does not have to be the SMS number).
• Business website – a live URL where carriers can verify your business exists.
• Vertical or industry – select from the dropdown (e.g., professional services, retail, healthcare, real estate).

Submit the brand registration. The Campaign Registry reviews and assigns a trust score. High-trust brands (public companies, established businesses with strong online presence) get higher throughput. Low-trust brands (new LLCs, sole proprietors, businesses with thin web presence) get lower throughput but still far better than unregistered.

Brand registration costs around fifteen dollars (one-time or annual, depending on the registry tier) and takes one to three business days.

Campaign Registration

A campaign describes your specific SMS use case. You might have one campaign for appointment reminders, another for marketing promotions, another for two-factor authentication. Each campaign must match the actual messages you send.

After brand approval, create a campaign. You will need:

• Campaign use case – select from the dropdown: marketing, customer care, account notifications, two-factor authentication, etc. Choose the category that best matches your primary message type. If you send mixed messages (reminders and promotions), choose “Mixed” or register separate campaigns.
• Sample messages – provide two to five example SMS messages exactly as they will appear to contacts, including merge fields replaced with realistic values. Carriers review these samples to confirm they match the declared use case. Do not submit generic placeholders—write real examples.
• Opt-in workflow description – explain how contacts consent to receive messages. Example: “Contacts check a box on our web form agreeing to receive SMS. The form disclosure states: ‘I agree to receive text messages from [Business Name]. Message and data rates may apply. Reply STOP to opt out.'”
• Opt-in proof – some campaigns require a screenshot of your form or landing page showing the consent language. Have this ready.
• Opt-out workflow description – explain how contacts can opt out. Example: “Contacts reply STOP, UNSUBSCRIBE, or CANCEL. Our system immediately stops sending messages and confirms opt-out.”
• Help workflow description – explain what happens when contacts reply HELP. Example: “Contacts receive a message with our business name and support phone number.”

Submit the campaign. Review takes one to three business days. Once approved, associate your HighLevel phone number(s) with the campaign. Messages sent from those numbers now carry the campaign trust score, and carriers allow higher throughput.

For detailed registration steps inside HighLevel, see the official A2P 10DLC brand and campaign registration in HighLevel support article. For deeper technical and compliance context, review the Twilio A2P 10DLC documentation, which explains carrier requirements and trust scores.

Why Registration Matters for Deliverability

Unregistered 10DLC numbers are treated as consumer peer-to-peer lines. Carriers throttle them to one message per minute or less and apply aggressive spam filters. Registered campaigns get throughput of hundreds or thousands of messages per minute, depending on trust score, and bypass many spam filters.

If you send SMS to more than a handful of contacts per day, A2P 10DLC registration is not optional—it is the difference between messages that deliver and messages that vanish.

Workflow Triggers That Send SMS Well

SMS works best as a response to a specific contact action or milestone. Broadcast SMS (bulk sends to a static list) has its place, but workflow-triggered SMS delivers higher engagement and better deliverability because the message is timely and contextual.

Form Submitted

Trigger: Contact submits a form (lead form, contact form, quote request). Workflow sends an immediate SMS acknowledging receipt and setting expectations.

Example: “Hi {{contact.first_name}}, thanks for reaching out to {{custom_values.business_name}}. I’ll follow up within 2 hours. Questions? Call {{custom_values.support_phone}}. Reply STOP to opt out.”

Filter the workflow on the SMS Opted In tag. Add a business-hours condition so late-night form submissions wait until morning.

Missed Call

Trigger: Inbound call to your HighLevel phone number goes unanswered or to voicemail. Workflow sends SMS within seconds.

Example: “Hi, you just called {{custom_values.business_name}} and we missed you. Reply here or call back at {{custom_values.support_phone}}. We’ll respond ASAP.”

Missed-call SMS has high reply rates because the contact just tried to reach you. Keep the message short and helpful. Do not pitch. Do not link. Just acknowledge and invite reply.

Appointment Booked

Trigger: Contact books an appointment on your HighLevel calendar. Workflow sends immediate confirmation SMS.

Example: “Hi {{contact.first_name}}, your appointment with {{custom_values.business_name}} is confirmed for {{appointment.start_time}}. We’ll send a reminder 24 hours before. Reply STOP to opt out.”

Follow up with a reminder workflow: trigger on appointment start time minus 24 hours, send SMS reminder. Then another reminder at start time minus 1 hour if you want belt-and-suspenders.

Tag Added

Trigger: A specific tag is added to the contact record (manually by operator, by another workflow, or by form submission). Workflow sends SMS based on the tag.

Example: Tag “Hot Lead” added → send SMS: “Hi {{contact.first_name}}, I saw your interest in [service]. I have a few time slots open this week—reply with your availability and I’ll get you scheduled.”

Tag-based triggers let you build segmented follow-up sequences. A contact tagged “Quoted – Plumbing” gets a different SMS than a contact tagged “Quoted – HVAC.” Keep the tag taxonomy clean and the workflows will scale.

Opportunity Stage Changed

Trigger: Contact’s opportunity moves to a new pipeline stage (e.g., from “Lead” to “Qualified” or “Proposal Sent” to “Won”). Workflow sends SMS appropriate to the stage.

Example: Stage changed to “Proposal Sent” → send SMS: “Hi {{contact.first_name}}, I just sent your proposal. Let me know if you have questions—happy to walk through it anytime.”

Stage-change SMS keeps the conversation moving without manual operator intervention. Pair SMS with email for contacts who prefer email, using the same trigger and parallel actions.

Inbound Message Received

Trigger: Contact sends an inbound SMS to your HighLevel number. Workflow can auto-reply, tag the contact, or route the conversation to a specific user.

Example: Inbound message contains keyword “SCHEDULE” → send SMS: “Great! Book your appointment here: {{custom_values.booking_link}}” and tag contact “Requested Appointment.”

Keyword-based workflows turn SMS into an interactive channel. Keep the keyword list short and the responses helpful. Do not over-automate—sometimes a human reply is better.

Integrating SMS into Larger Follow-Up Systems

SMS is one channel in a multi-touch follow-up system. A contact who submits a form might receive an immediate SMS, a follow-up email 10 minutes later, a phone call from your team within two hours, and a second SMS the next day if no reply. SMS works best when it is part of a coordinated sequence, not a standalone blast.

For a deeper dive into designing multi-channel follow-up sequences—email, SMS, calls, tasks—see our guide on follow-up automations. That guide covers sequence timing, channel priority, and operator handoff patterns. This guide focuses on the SMS-specific mechanics: templates, consent, compliance, and triggers.

When you build a follow-up workflow, add SMS actions at the moments when speed and brevity matter—immediate acknowledgment, missed-call recovery, appointment reminders. Use email for longer explanations, attachments, and links. Use phone calls for high-value leads or complex questions. SMS is the glue that keeps the conversation alive between the other touches.

Testing Deliverability: The Operator Checklist

Before you launch a new SMS workflow to your full contact list, test it end-to-end with your own phone number and a handful of test contacts on different carriers (AT&T, Verizon, T-Mobile). Here is the checklist:

Send to Your Own Phone

Create a test contact in HighLevel with your mobile number. Trigger the workflow (submit the form, add the tag, book the appointment—whatever the trigger is). Confirm the SMS arrives on your phone within seconds. Check the message body: merge fields populated correctly, no blank {{fields}}, business name and opt-out language present, links work.

Check the Conversation Log

In HighLevel, open Conversations and find the thread with your test contact. The log shows “Delivered” or “Failed” status. If failed, click the error message. Common errors:

• “Invalid phone number” – the phone field was blank or malformed. Check your workflow SMS action phone field mapping.
• “Unsubscribed” or “DND” – the contact is on the Do Not Disturb list. Check your consent tag filters.
• “Carrier filter” or “Spam detected” – the message content or sender reputation triggered carrier filtering. Review your message copy, check A2P registration status, and test on a different carrier.
• “Throttled” – you are sending too many messages too fast from an unregistered number. Register A2P 10DLC or slow your send rate.

Test Merge Fields with Blank Data

Create a test contact with first name populated but last name blank, or appointment data missing. Trigger the workflow. Confirm the message does not render “Hi ,” or “Your appointment is confirmed for .” If merge fields are blank, the message looks broken.

In your templates, add fallback text: “Hi {{contact.first_name | default: ‘there’}}” so if first name is missing, the message reads “Hi there.” HighLevel supports Liquid-style filters in some merge fields; test your version.

Test Consent Tag Filters

Create a test contact without the SMS Opted In tag. Trigger the workflow. Confirm the SMS does not send. Check the workflow log—it should show the contact exited at the consent filter step. Then add the SMS Opted In tag and trigger again. Confirm the SMS sends.

Test Quiet Hours

Manually adjust your system clock or wait until after 8pm. Trigger the workflow. Confirm the SMS does not send immediately. Check the workflow log—it should show the contact waiting until 8am. The next morning, confirm the SMS sends at 8am.

Test on Multiple Carriers

Carrier filtering varies by network. A message that delivers fine on Verizon might get blocked on AT&T. If possible, test with phone numbers on AT&T, Verizon, and T-Mobile. If you see consistent delivery on all three, you are in good shape. If one carrier blocks or delays, review your A2P registration and message content.

Monitor for a Week

After launch, check the Conversations log daily for the first week. Look for patterns: high failure rate on a specific carrier, repeated “invalid number” errors (indicates bad data), spike in STOP replies (indicates message frequency or content issues). Adjust workflows, templates, or consent filters based on what you see.

Common Failures and Fixes Checklist

Here are the most frequent SMS failures operators report, with the fix for each:

• Message shows “Sent” but contact never received it. Check A2P 10DLC registration status. Unregistered numbers get silently filtered by carriers. Register brand and campaign, wait for approval, then test again.
• Merge field renders as blank or {{contact.first_name}}. The contact record is missing that field, or the field name in the template does not match the field name in the contact record. Check spelling, check custom field vs. standard field, add fallback text.
• Workflow sends SMS at 2am. No business-hours filter in the workflow. Add a time condition before the SMS action: if outside 8am–8pm, wait until 8am.
• Contact replies STOP but keeps receiving messages. The workflow is not filtering on the DND tag or SMS Opted In tag. Add a consent filter at the top of every SMS workflow. Also confirm the built-in STOP handling is active in HighLevel phone settings.
• SMS sends to the wrong number. The workflow SMS action is pulling from the wrong field (e.g., {{contact.phone}} when the number is in {{contact.custom_fields.mobile}}). Update the phone field mapping in the SMS action.
• High volume of “invalid number” errors. Your contact data has formatting issues—missing country code, letters in the phone field, extra spaces. Clean the data: bulk export contacts, fix phone formatting (US numbers should be +1XXXXXXXXXX or 10 digits), re-import.
• Carrier error “Spam detected.” Message content triggered spam filters. Shorten the message, remove multiple links, remove ALL CAPS and excessive punctuation, add your business name, ensure A2P campaign samples match the actual message.
• Messages deliver but reply rate is zero. The message is not engaging or not asking for a reply. Rewrite the template: ask a question, invite a reply, keep it conversational. Also check that replies are routing to the correct inbox and your team is responding.

Operator Launch Checklist for This Week

You have read the guide. Now build the system. Here is the step-by-step checklist to launch SMS in your HighLevel subaccount this week:

1. Register A2P 10DLC brand and campaign. Gather business info (legal name, EIN, address, website). Navigate to Settings → Phone Numbers in HighLevel. Submit brand registration. Wait for approval (1–3 days). Submit campaign registration with sample messages, opt-in description, opt-out description. Wait for approval. Associate your phone number with the approved campaign.
2. Create custom values. Settings → Custom Values. Add business_name, support_phone, booking_link. Save.
3. Build SMS templates. Settings → Templates. Create templates for: form submission acknowledgment, missed call reply, appointment confirmation, appointment reminder 24hr, appointment reminder 1hr. Use merge fields and custom values. Include opt-out language in every template. Save.
4. Set up consent tags. Settings → Tags (or wherever your HighLevel version manages tags). Create tags: “SMS Opted In” and “DND – Unsubscribed SMS.” Document the tag definitions in your internal wiki or SOP.
5. Update forms to capture consent. Edit your lead forms. Add a checkbox field: “I agree to receive text messages from [Business Name]. Message and data rates may apply. Reply STOP to opt out.” In the form submission workflow, add action: if checkbox is checked, add tag “SMS Opted In.”
6. Build opt-out workflow. Automations → Create Workflow. Trigger: Inbound Message Received. Condition: message body contains “STOP” (case-insensitive). Actions: remove tag “SMS Opted In,” add tag “DND – Unsubscribed SMS,” send SMS reply “You have been unsubscribed. Reply START to opt back in.” Save and activate.
7. Build HELP workflow. Trigger: Inbound Message Received. Condition: message body contains “HELP.” Action: send SMS “This is {{custom_values.business_name}}. Questions? Call {{custom_values.support_phone}} or reply here.” Save and activate.
8. Build START workflow. Trigger: Inbound Message Received. Condition: message body contains “START.” Actions: remove tag “DND – Unsubscribed SMS,” add tag “SMS Opted In,” send SMS “You are now subscribed to {{custom_values.business_name}} messages. Reply STOP to opt out anytime.” Save and activate.
9. Build form-submission SMS workflow. Trigger: Form Submitted (choose your lead form). Condition: contact has tag “SMS Opted In.” Condition: current time between 8am and 8pm (else wait until 8am). Action: send SMS using your form acknowledgment template. Save and activate.
10. Build missed-call SMS workflow. Trigger: Missed Call. Condition: contact has tag “SMS Opted In.” Condition: current time between 8am and 8pm (else wait until 8am). Action: send SMS using your missed-call template. Save and activate.
11. Build appointment-confirmation SMS workflow. Trigger: Appointment Booked. Condition: contact has tag “SMS Opted In.” Action: send SMS using your appointment confirmation template (no time filter needed—confirmations send immediately). Save and activate.
12. Build appointment-reminder workflows. Trigger: Appointment Start Time (minus 24 hours). Condition: contact has tag “SMS Opted In.” Condition: current time between 8am and 8pm (else wait until 8am). Action: send SMS using your 24hr reminder template. Save and activate. Repeat for 1hr reminder if desired.
13. Test end-to-end. Create a test contact with your phone number and the “SMS Opted In” tag. Submit the form, trigger a missed call, book an appointment. Confirm each SMS arrives, merge fields populate, opt-out language is present, links work. Check Conversations log for delivery status.
14. Test opt-out. Reply STOP to one of your test messages. Confirm you receive the unsubscribe confirmation. Trigger another workflow. Confirm no SMS sends (because the tag was removed). Check the workflow log to confirm the contact exited at the consent filter.
15. Launch to live contacts. Activate workflows for your real contact list. Monitor Conversations daily for the first week. Watch for delivery errors, STOP replies, and reply rates. Adjust templates and workflows based on feedback.
16. Document your system. Write a one-page SOP: which tags mean what, which workflows send which templates, how to handle STOP/HELP/START replies, where to check delivery logs. Share with your team. Update the SOP when you add new workflows or templates.

Final Operator Notes

SMS in HighLevel is not plug-and-play. It requires templates, consent tags, A2P registration, workflow filters, and ongoing monitoring. But once the system is built, it runs in the background and delivers messages that actually reach the inbox—because you registered your campaigns, captured consent, respected quiet hours, and wrote messages that sound human.

Do not skip A2P 10DLC registration. Do not skip consent filters. Do not skip quiet hours. These are not optional optimizations—they are the baseline for deliverability in 2025.

Start with one or two workflows this week—form submission and missed call are the highest ROI. Test thoroughly. Monitor for a week. Then add appointment reminders, tag-based follow-ups, and keyword replies. Build the system in layers, and you will have SMS that works for years.

by Darius Gaynor