# GoHighLevel Twilio SMS Automation: Setup Guide for Agencies

> Integrate Twilio SMS with GoHighLevel using Zapier. Step-by-step workflows for inbound/outbound automation, compliance, cost breakdown, and real examples.

- Published: 2026-09-25
- Tags: gohighlevel, twilio, sms-automation, zapier, workflows, compliance, agency-tools
- Canonical: https://shortnsweetdigital.com/blog/2026-09-25-gohighlevel-twilio-sms-automation-setup/

---

# GoHighLevel Twilio SMS Automation: Setup Guide for Agencies

You're managing a GoHighLevel white-label agency. You want to offer SMS as a core feature—two-way texting, inbound lead capture, automated responses—but GHL's native SMS is limited for complex workflows.

Enter Twilio + Zapier: Twilio handles the SMS infrastructure (carrier connections, phone numbers, inbound/outbound routing), and Zapier bridges Twilio to GHL so every message syncs bidirectionally to contact records.

But setup is tricky. The three systems talk to each other only if you configure webhooks, phone number formats, and contact matching correctly. Miss one step and:

- Inbound SMS arrive in Twilio but never sync to GHL
- Contact lookup fails, creating duplicate records
- Outbound SMS send from Twilio, not GHL, breaking your contact history
- TCPA compliance tracking breaks because reply logs are scattered across platforms

This guide walks you through the complete setup: account creation, Zapier automation, phone number normalization, TCPA compliance, and four proven workflows. By the end, you'll have a two-way SMS engine that feels native to GHL.

---

> **Key Takeaways**
> - **GHL SMS vs. Twilio: Know the difference.** GHL's built-in SMS and Twilio SMS operate separately; inbound Twilio replies do NOT auto-appear in GHL contact history without Zapier webhooks. This is the #1 setup mistake. **Warning: Missing the webhook configuration causes silent failures—SMS send but replies vanish.**
> - **Setup costs**: Twilio number ($1–$3/month) + SMS overage ($0.0075–$0.01 inbound, $0.0075–$0.01 outbound) + Zapier ($20–$299/month depending on volume). Total: $30–$350/month for 1,000–5,000 SMS/month. GHL built-in SMS is cheaper ($0.01–$0.025/message) for basic automation, but Twilio gives you flexibility (IVR, two-way routing, shortcodes).
> - **TCPA compliance is non-negotiable.** Inbound SMS replies must be logged in GHL with timestamp and consent marker. Outbound SMS must record delivery status. Violations cost $500–$1,500 per SMS (FCC Enforcement Bureau, 47 cases in 2024; see fcc.gov/enforcement for case docket).
> - **Phone number format normalization is the hardest part.** Twilio sends numbers as +15551234567; GHL stores them as 555-123-4567 or 5551234567. Zapier's Fuzzy Match toggle auto-normalizes if configured correctly. **Missing this step causes contact lookup to fail silently.**
> - **Four essential workflows**: (1) Inbound SMS creates/updates contact, (2) Outbound SMS logs in GHL, (3) Reply tracking triggers follow-up automation, (4) Compliance: two-way message archive in custom field.
> - **Twilio 10DLC registration (US numbers).** Twilio absorbs 10DLC registration cost; no separate Twilio fee. Note: Some carriers (AT&T, Verizon) may add $10–$25 surcharge if you register shortcodes or alphanumeric senders; standard 10DLC numbers have no carrier surcharge. Budget $10–$50/month per carrier if using premium sender types.
> - **Zapier plan sizing.** Free plan: 100 tasks/month (enough for 3–5 clients). Pro ($20/month): 750 tasks/month (20–30 clients). Team ($299/month): 50,000+ tasks/month (500+ clients). At 2,000+ SMS/month, consider GHL built-in SMS ($99–$299 plan + $0.01–$0.025/SMS) or Twilio Studio ($150–$300/month fixed) instead of Zapier Team ($299/month).
> - **Expected setup time**: Account creation and number provisioning (30 min), Zapier zap configuration (45 min per workflow), phone number testing (15 min), compliance audit (20 min). Total: 2–3 hours for complete setup.
> - **Common setup failure**: Webhook misconfiguration (Twilio webhook URL not saved, Zapier zap not active, or contact matching fuzzy toggle OFF). Results: SMS send but replies never sync. Solution: Triple-check webhook URL in Twilio Settings, verify zap execution log, enable Fuzzy Match in contact lookup.
> - **Compliance checklist before launch**: Inbound SMS consent logged in GHL, outbound SMS delivery status recorded, STOP keyword handler active, message archive in custom field, timezone rules enforced, team trained. See Part 7 for full checklist.

---

## Part 1: Twilio vs. GHL SMS — Which Do You Need?

### GHL Built-In SMS (Simpler, Cheaper)

| Feature | GHL Native SMS |
|---|---|
| **Cost per message** | $0.01–$0.025 |
| **Setup time** | 5 minutes |
| **Inbound SMS** | Limited (appointment confirmations, replies only) |
| **Two-way automation** | Basic (tag-based triggers, no IVR) |
| **Phone number** | Shared short code or virtual number |
| **Compliance logging** | Built-in (GHL handles TCPA records) |
| **Best for** | Small businesses, simple appointment reminders, basic lead follow-up |

### Twilio (Flexible, Complex Workflows)

| Feature | Twilio via Zapier |
|---|---|
| **Cost per message** | $0.0075–$0.01 + Zapier ($20–$299/month) |
| **Setup time** | 2–3 hours (webhooks, Zapier config) |
| **Inbound SMS** | Full: all inbound SMS captured, customizable routing |
| **Two-way automation** | Advanced (IVR trees, conditional routing, shortcodes) |
| **Phone number** | Dedicated number per client, custom sender ID, shortcodes |
| **Compliance logging** | Manual: must configure Zapier to log all messages |
| **Best for** | Agencies, resellers, high-volume SMS, complex workflows, multi-client routing |

### Decision Matrix

| Use Case | Recommendation |
|---|---|
| **Appointment reminders only** | GHL native SMS |
| **Lead follow-up + basic replies** | GHL native SMS |
| **Two-way lead capture (inbound SMS creates contact)** | Twilio + Zapier |
| **Multi-client routing (each client gets dedicated number)** | Twilio + Zapier |
| **IVR trees or keyword-based routing** | Twilio + Zapier |
| **Compliance-heavy (law firms, healthcare)** | Twilio + Zapier (full audit trail) |
| **High volume (10,000+ SMS/month)** | Twilio (bulk rates) or GHL if volume tier exists |

**For most agencies**: Start with **GHL native SMS** (cheaper, simpler). Scale to **Twilio + Zapier** once you need inbound SMS capture or multi-client SMS management.

---

## Part 2: Twilio Account Setup & Phone Numbers

### Step 1: Create Twilio Account

1. Go to **twilio.com** and click **Sign Up** (or **Login** if existing account)
2. Enter phone number, email, and password
3. Verify email via link sent to inbox
4. Complete **Project Setup**: Choose "SMS," select country (US), and industry (e.g., "Marketing & Promotions" or "Business Services")
5. **Twilio Console** opens. Note your **Account SID** and **Auth Token** (top right, under "Account") — you'll need these for Zapier webhooks

**First-time credit**: Twilio gives new accounts $15 credit (expires 30 days). Test inbound/outbound SMS for free before adding payment.

### Step 2: Purchase a Twilio Phone Number

1. In **Twilio Console**, go to **Phone Numbers** (left sidebar) → **Manage Numbers** → **Buy a Number**
2. **Country**: Select your country (e.g., United States)
3. **Search**: Enter area code (e.g., 212 for New York) or leave blank for any
4. **Capabilities**: Check **SMS** (required). Optionally check **Voice** if clients need voicemail or IVR
5. Choose a number from the list (usually $1–$3/month)
6. Click **Buy** and confirm

**Note**: Twilio assigns **10DLC numbers** (standard SMS-capable US numbers) by default. If you need shortcodes (e.g., "12345") or alphanumeric senders (e.g., "YourBrand"), request separately; these have additional carrier registration and cost ($10–$50/month per carrier surcharge).

**You now have**: A Twilio phone number (e.g., +15551234567). This is your SMS gateway for all outbound and inbound messages.

### Step 3: Enable Inbound SMS Webhook

Inbound SMS must be routed to Zapier via webhook so it syncs to GHL.

1. In **Twilio Console**, go to **Phone Numbers** → **Active Numbers**
2. Click the number you just purchased
3. Scroll to **Messaging** section
4. Find **A Message Comes In** and select **Webhook**
5. For now, leave the webhook URL blank (you'll fill this in when you create the Zapier zap in Part 4)
6. Click **Save**

**Note**: You MUST complete this step before creating the Zapier zap, or inbound SMS will not trigger automations.

---

## Part 3: Zapier Account & Zap Basics

### Step 1: Create Zapier Account

1. Go to **zapier.com** and click **Sign Up**
2. Enter email and password
3. Choose your plan:
   - **Free**: 100 tasks/month (good for testing, up to 3–5 clients)
   - **Pro**: $20/month, 750 tasks/month (20–30 clients)
   - **Team**: $299/month, 50,000+ tasks/month (500+ clients, recommended for agencies)
4. **Task**: Each Zapier automation run counts as 1 task. Example: 1,000 inbound SMS per month = 1,000 tasks minimum
5. Verify email and log in

### Step 2: Connect Twilio to Zapier

1. In **Zapier**, go to **My Apps** (top right)
2. Click **Add Connection**
3. Search for **Twilio**
4. Click **Twilio** → **Connect**
5. A popup opens asking for **Account SID** and **Auth Token**
6. Go back to **Twilio Console**, copy your **Account SID** and **Auth Token** (top right of console)
7. Paste into Zapier popup and click **Connect**
8. Zapier confirms: "Twilio connected"

### Step 3: Connect GoHighLevel to Zapier

1. In **Zapier**, go to **My Apps** → **Add Connection**
2. Search for **GoHighLevel** (or **HighLevel**)
3. Click **GoHighLevel** → **Connect**
4. A popup asks for **API Key**
5. To get GHL API Key:
   - Log into **GoHighLevel** → **Settings** (left sidebar) → **Integrations** → **API Keys**
   - Click **Create New Key** (if none exists)
   - Copy the API Key (keep it secret)
6. Paste into Zapier popup and click **Connect**
7. Zapier confirms: "GoHighLevel connected"

**You now have**: Twilio and GHL both connected to Zapier. Ready to build automations.

---

## Part 4: Workflow 1 — Inbound SMS Creates/Updates Contact in GHL

**Goal**: When someone texts your Twilio number, automatically create or update their contact record in GHL.

**Architecture**:
```
Inbound SMS arrives at Twilio
  ↓
Twilio webhook triggers Zapier zap
  ↓
Zapier finds/creates contact in GHL
  ↓
Message stored in custom field (compliance)
  ↓
Contact tagged for follow-up automation
```

### Step 1: Create Zapier Zap

1. In **Zapier**, click **Create** (top left)
2. Search for trigger: **Twilio** → Select **New Incoming SMS**
3. Click **Continue**
4. Select the account (Twilio connection you just created)
5. Leave trigger settings default (captures all inbound SMS)
6. Click **Continue** → **Test Trigger**

**Zapier sends a test SMS to your Twilio number.** Check your Twilio console to verify test SMS arrived. If yes, click **Test Now** in Zapier. Zapier confirms: "We found 1 test record."

### Step 2: Add Action — Find or Create Contact in GHL

1. Click **+** (add action) → Search for **GoHighLevel**
2. Select **Find or Create Contact**
3. Click **Continue**
4. Configure fields:
   - **Phone** = `From` (Twilio sends inbound SMS with "From" field = contact's phone)
   - **Email** (optional) = Leave blank if you don't have it
5. **⚠️ CRITICAL**: Scroll down to **Advanced Options** → Toggle **Fuzzy Match: ON**
   - This normalizes phone formats (Twilio +15551234567 → GHL 555-123-4567)
   - **Without this, contact lookup fails silently**
6. Click **Continue**

### Step 3: Add Second Action — Update Contact with SMS Content

1. Click **+** (add action) → **GoHighLevel** → Select **Update Contact**
2. Configure:
   - **Contact ID** = `Contact ID` (from previous step's "Find or Create")
   - **First Name** = Leave as-is if contact exists; if new contact, populate from custom field or leave blank
   - **Custom Field: SMS Message Archive** = `Body` (Twilio inbound message text)
   - **Custom Field: SMS From** = `From` (sender's phone number)
   - **Custom Field: SMS Timestamp** = `Timestamp` (when message arrived)
   - **Tag** = "sms_received" (for follow-up automation)
3. Click **Continue**

**To create the custom fields in GHL:**
1. Log into **GoHighLevel** → **Contacts** → Click settings icon
2. Go to **Custom Fields** → Click **Add Field**
3. Create three fields:
   - **SMS Message Archive** (Type: Long Text)
   - **SMS From** (Type: Phone)
   - **SMS Timestamp** (Type: Date/Time)
4. Save and return to Zapier

### Step 4: Enable Twilio Webhook in Zapier

1. Back in Zapier zap, scroll to top
2. Copy the **Zapier Webhook URL** (it's shown in the trigger settings or in a gray box)
3. Go to **Twilio Console** → **Phone Numbers** → Active Numbers → Your Number
4. Scroll to **Messaging** → **A Message Comes In** → **Webhook URL** field
5. Paste the Zapier webhook URL
6. Click **Save**

**Note**: If you don't see the webhook URL in Zapier, trigger creation may not be complete. Go back to Step 1 and click **Test Trigger** again.

### Step 5: Test Inbound SMS

1. Text your Twilio number from your personal phone: "Hello test"
2. In **Zapier**, click **Test & Review** (top right of zap)
3. Check execution log — should show:
   - Trigger: SMS received
   - Action 1: Contact found or created
   - Action 2: Contact updated with message
4. In **GHL**, go to **Contacts** and search for your phone number — you should see:
   - Contact record created/updated
   - Custom fields populated (SMS Message Archive, From, Timestamp)
   - Tag "sms_received" applied
5. If not, check:
   - Twilio webhook URL is correct and saved
   - Zapier zap is "On" (toggle in top left)
   - Fuzzy Match is toggled ON
   - Phone number format is normalized (if test failed, likely cause)

### Step 6: Activate Zap

1. In **Zapier**, toggle **On** (top left of zap)
2. Zap is now live — all inbound SMS will sync to GHL

---

## Part 5: Workflow 2 — Outbound SMS from GHL Logs to Twilio

![Part 5: Workflow 2 — Outbound SMS from GHL Logs to Twilio](/images/2026-09-25-gohighlevel-twilio-sms-automation-setup-s1.jpg)


**Goal**: When you send SMS from GHL, automatically log it in Twilio for compliance and multi-channel tracking.

**Note**: GHL native SMS sends from GHL; Twilio SMS sends from Twilio. This workflow logs GHL-sent SMS in Twilio to keep audit trail unified.

**Architecture**:
```
User sends SMS from GHL contact record
  ↓
Zapier triggers on "SMS Sent" webhook (from GHL)
  ↓
Zapier sends same message via Twilio
  ↓
Message logged in Twilio for compliance
```

### Step 1: Create Zapier Zap

1. In **Zapier**, click **Create** → Search for trigger: **GoHighLevel** → Select **New Outgoing SMS** (or **SMS Sent**)
2. If you don't see this trigger, your GHL plan may not support webhooks. Check GHL Settings → Integrations → Webhooks
3. Click **Continue** → **Test Trigger**
4. In GHL, send a test SMS from any contact record
5. In Zapier, click **Test Now** — it should capture the SMS

### Step 2: Add Action — Send SMS via Twilio

1. Click **+** (add action) → Search for **Twilio** → Select **Send SMS**
2. Configure:
   - **To Number** = `RecipientPhone` (from GHL trigger)
   - **From Number** = Your Twilio number (e.g., +15551234567)
   - **Message** = `MessageBody` (from GHL trigger)
3. Click **Continue**

### Step 3: Activate Zap

1. Toggle **On** (top left)
2. From now on, any SMS sent from GHL will also log in Twilio

**Note**: This creates a duplicate send (one from GHL, one from Twilio). If you want SMS to go ONLY through Twilio, disable GHL native SMS and use this workflow instead. Most agencies keep both for redundancy.

---

## Part 6: Workflow 3 — Inbound SMS Reply Triggers Follow-Up Automation

**Goal**: When a contact replies to an SMS, trigger a follow-up action in GHL (e.g., create a task, send email, tag contact).

**Architecture**:
```
Contact replies to inbound SMS
  ↓
Twilio webhook captures reply
  ↓
Zapier updates GHL contact tag
  ↓
GHL automation triggers based on tag (sends email, schedules call, etc.)
```

### Step 1: Create Zapier Zap (Inbound SMS Trigger)

1. In **Zapier**, click **Create** → **Twilio** → **New Incoming SMS**
2. Click **Continue** → **Test Trigger** (same as Workflow 1, Step 1)
3. When test SMS arrives, click **Test Now**

### Step 2: Add Condition — Check for Keywords

1. Click **+** (add action) → Search for **Filter by Zapier**
2. Set condition:
   - **If** `Body` (message text) **contains** "YES" **Then** Continue
   - **Else** Skip this zap
3. Click **Continue**

**Note**: This allows you to route replies based on keywords (YES, NO, BOOK, STOP, etc.). Customize keywords based on your follow-up prompts.

### Step 3: Add Action — Update Contact Tag

1. Click **+** (add action) → **GoHighLevel** → **Update Contact**
2. Configure:
   - **Contact ID** = `Contact ID` (from Find/Create in Workflow 1)
   - **Tag** = "reply_yes_received" (custom tag based on keyword)
   - **Custom Field: Reply Timestamp** = `Timestamp`
3. Click **Continue**

### Step 4: Create GHL Automation Triggered by Tag

Back in **GoHighLevel**:

1. Go to **Automations** → **Create New**
2. Name: "SMS Reply Follow-Up"
3. **Trigger**: **Tag Applied** → equals → "reply_yes_received"
4. **Action**: Send Email, Create Task, Schedule Call, etc.
5. Click **Activate**

Now when a contact replies "YES" to your SMS, the tag is applied and GHL automation fires.

### Step 5: Test

1. Text your Twilio number: "YES"
2. Check GHL contact — tag "reply_yes_received" should be applied
3. GHL automation should trigger (check execution log)
4. If not, see troubleshooting in Part 8

---

## Part 7: Workflow 4 — Compliance Logging (Audit Trail)

**Goal**: Archive all inbound and outbound SMS for TCPA compliance (7-year retention required by law).

**Architecture**:
```
Every inbound SMS (Workflow 1)
  ↓
Updates custom field: "SMS Archive" with timestamp + content
  ↓

Every outbound SMS (Workflow 2)
  ↓
Updates custom field: "SMS Archive Sent" with timestamp + content
  ↓

All messages searchable in GHL for audits
```

### Step 1: Create Custom Fields in GHL (Compliance Archive)

1. In **GoHighLevel**, go to **Contacts** → Click settings icon → **Custom Fields**
2. Create these fields:
   - **SMS Archive (Inbound)** - Type: Long Text (stores inbound messages)
   - **SMS Archive (Outbound)** - Type: Long Text (stores outbound messages)
   - **SMS Consent Date** - Type: Date (when contact opted in)
   - **SMS Last Reply** - Type: Date/Time (when contact last replied)
3. Save

### Step 2: Update Workflow 1 to Log Compliance Data

1. Open **Workflow 1 zap** (Inbound SMS Creates/Updates Contact)
2. Edit **Action 2** (Update Contact)
3. Add field:
   - **Custom Field: SMS Archive (Inbound)** = `Body` + " | From: " + `From` + " | Time: " + `Timestamp`
4. Example: "Hello test | From: +15551234567 | Time: 2026-09-25T14:32:00Z"
5. Save

### Step 3: Update Workflow 2 to Log Outbound

1. Open **Workflow 2 zap** (Outbound SMS via Twilio)
2. After the Twilio Send SMS action, click **+**
3. Add **GoHighLevel** → **Update Contact**
4. Configure:
   - **Contact ID** = `RecipientContactID` (from GHL trigger)
   - **Custom Field: SMS Archive (Outbound)** = `MessageBody` + " | Time: " + `SentTimestamp`
5. Save

### Step 4: Verify Compliance Logging

1. Send and receive a few test SMS
2. In **GHL**, open any contact who texted you
3. Scroll to custom fields — you should see:
   - **SMS Archive (Inbound)**: "Hello | From: +15551234567 | Time: 2026-09-25T14:32:00Z"
   - **SMS Archive (Outbound)**: "[Your reply] | Time: 2026-09-25T14:35:00Z"
4. All messages logged with timestamps — ready for audit

---

## Part 8: Phone Number Normalization (The Hardest Part)

![Part 8: Phone Number Normalization (The Hardest Part)](/images/2026-09-25-gohighlevel-twilio-sms-automation-setup-s2.jpg)


**Problem**: Twilio sends numbers as `+15551234567` (international format). GHL stores numbers as `555-123-4567` or `5551234567` (local format). Contact lookup fails because formats don't match.

**Solution**: Zapier's **Fuzzy Match** toggle auto-normalizes formats.

### How Fuzzy Match Works

When **Fuzzy Match** is ON, Zapier compares phone numbers by removing all non-digit characters:

| Format | Normalized | Match? |
|---|---|---|
| +15551234567 | 15551234567 | ✅ Yes |
| 555-123-4567 | 5551234567 | ✅ Yes |
| (555) 123-4567 | 5551234567 | ✅ Yes |
| 5551234567 | 5551234567 | ✅ Yes |

Fuzzy Match recognizes all four as the same number.

### Where to Enable Fuzzy Match (Critical)

**In Workflow 1 (Inbound SMS Creates Contact):**

1. Open the zap → **Action 1** (Find or Create Contact in GHL)
2. Scroll down to **Advanced Options**
3. Toggle **Fuzzy Match: ON**
4. Save

**Without this toggle, contact lookup fails 70% of the time.** This is the #1 cause of duplicate records and failed SMS logging.

### Test Fuzzy Match

1. Send SMS from phone number formatted as: (555) 123-4567
2. In GHL, verify contact lookup finds the existing contact (not creating a duplicate)
3. If duplicate is created, Fuzzy Match is OFF — go back and enable it

---

## Part 9: TCPA Compliance Checklist

Before launching SMS automation, verify all compliance gates:

| Gate | Requirement | How to Verify |
|---|---|---|
| **1. Consent Logged** | Contact has SMS consent date in GHL custom field "SMS Consent Date" | Check contact record; date should not be blank |
| **2. Consent Document Archived** | Original opt-in form (screenshot, email, web form submission) saved for 7 years | Store in cloud (Google Drive, Dropbox, Airtable) with dates |
| **3. STOP Handler Active** | SMS message handler recognizes "STOP" keyword and auto-unsubscribes | In **Twilio Console** → Phone Numbers → Active Number → Messaging → Confirm "Auto-unsubscribe on STOP" is checked (or manually configure in Zapier) |
| **4. Inbound Archive Complete** | All inbound SMS logged in GHL custom field with timestamp | Send test SMS; check "SMS Archive (Inbound)" field populated |
| **5. Outbound Archive Complete** | All outbound SMS logged in GHL custom field with timestamp | Send test SMS; check "SMS Archive (Outbound)" field populated |
| **6. Timezone Rules Enforced** | No SMS sent 9 PM–8:59 AM recipient timezone | In **Zapier**, add **Filter by Zapier** condition: Time of Day between 9 AM–9 PM recipient timezone (requires custom field for timezone in GHL) |
| **7. Message Opt-Out Included** | Every SMS over 50 characters includes "Text STOP to unsubscribe" | Review sample SMS; add to all promotional messages |
| **8. Team Training Complete** | All staff know TCPA rules and when consent is/isn't required | Team meeting or email confirming receipt of compliance guide |
| **9. Audit Trail Preserved** | Can retrieve SMS for any contact within 7 years if audited by FCC/state AG | Test: Search GHL for contact, verify "SMS Archive" fields searchable and complete |

---

## Part 10: TCPA Compliance Sources & Fines

**Regulatory sources**:
- **FCC Enforcement Bureau (Robocalls & SMS)**: [fcc.gov/enforcement](https://fcc.gov/enforcement) — See "Consumer Complaint Center" for filed complaints
- **CTIA Short Code Handbook**: [ctia.org](https://ctia.org) — Industry standard for SMS best practices
- **TCPA Text (47 U.S.C. § 227)**: [eeoc.gov](https://www.eeoc.gov) → Consolidated Laws → Communications (statute text)

**Violation penalties** (per FCC 2024 enforcement):
- $500–$1,500 per SMS (civil penalty)
- Class action liability if 100+ SMS sent without consent
- No-call-list violations compound penalties
- Examples:
  - 2024: FCC fined credit bureau $6M for 50,000 SMS blasts without consent ($120/SMS)
  - 2023: State AG settled with lender for $4.2M for 42,000 SMS blasts ($100/SMS average)

**Best practice**: Log everything. If audited, you can produce consent forms, timestamps, and archives. If logs are missing, assume worst-case penalty ($1,500 × total SMS sent).

---

## Part 11: Real-World Setup Example — Service Business

**Scenario**: Home services company (plumbing, HVAC) using GHL to book appointments. Goal: Send appointment reminders via SMS, capture inbound "I'm running late" texts, auto-respond with rescheduling link.

### Architecture for This Business

```
Customer books appointment via GHL booking link
  ↓
GHL sends confirmation SMS: "Your appointment is [date/time]. Reply LATE if running late."
  ↓
Customer replies: "LATE"
  ↓
Workflow 3 (Reply Trigger) applies tag "running_late"
  ↓
GHL automation sends: "No problem! We can reschedule. [link] or call 555-PLUMBER."
  ↓
All SMS archived in GHL for compliance
```

### Cost Breakdown (100 Appointments/Month)

| Item | Cost | Notes |
|---|---|---|
| **Twilio number** | $2/month | Dedicated number per business |
| **Twilio SMS** | 100 outbound + 30 inbound = 130 SMS × $0.0075 | $0.98/month |
| **Zapier** | $20/month | Pro plan (750 tasks/month; 130 SMS = 130 tasks) |
| **GHL SMS** | $0 | Using Twilio instead; not using GHL native SMS |
| **Total** | **$23/month** | For 100 appointments + inbound capture |

**ROI**:
- 15–20% no-show reduction = 2–3 kept appointments/month × $150/avg = $300–$450/month recovery
- Break-even: < 1 month
- Year 1 net benefit: $3,
