What this enables
Most SMS-from-GHL setups require a third-party cloud provider — Twilio, LeadConnector, or similar — with separate accounts and per-message charges. SMSFORCRM takes a different approach: your Android phone becomes the SMS sender. Messages routed through GHL get sent from your phone's actual SIM, using your phone's actual SMS plan.
Useful when:
- You want SMS to come from your real phone number — clients who already have it saved recognise it instantly
- You'd rather pay your existing phone plan than per-message Twilio fees
- You want a self-contained SMS workflow that doesn't depend on a separate cloud provider
- You're sending modest SMS volumes where Twilio's scale isn't needed
SMSFORCRM uses an Android app installed on your phone to act as the SMS gateway. iPhone is not supported — Apple's iOS doesn't allow third-party apps to send SMS programmatically. If you only have iPhones, use Twilio fallback instead.
SMSFORCRM is a separate product
SMSFORCRM is one of our companion brands and has its own subscription, billed separately from your WAGHL plan. The two products work together but are independently subscribed.
Visit smsforcrm.com for current SMSFORCRM pricing and to start your subscription. Plans are separate from WAGHL — you'll need both an active WAGHL subscription and an active SMSFORCRM subscription to use this integration.
Five messaging modes
Once SMSFORCRM is connected, you choose how messages should route across WhatsApp and SMS. The five modes apply at the WAGHL routing layer — they work the same regardless of whether your SMS provider is SMSFORCRM, Twilio, or any other:
| Mode | Behavior |
|---|---|
| WhatsApp (default) | Messages send via WhatsApp only. |
| Only SMS | Messages send via SMS only — WhatsApp is bypassed entirely. |
| WhatsApp & SMS | Messages send via both channels at the same time. Maximum reach. |
| WhatsApp or SMS | WhatsApp first; if the contact's number isn't on WhatsApp, automatically falls back to SMS. Smart default. |
| Tag-based: "only sms" | Tag specific contacts with only sms. Tagged contacts receive SMS only; everyone else gets WhatsApp. |
Setting it up
The video walkthrough above covers the full setup. Here's the high-level flow:
Register on SMSFORCRM
Visit smsforcrm.com and create an account. Choose a plan that matches your monthly SMS volume. Once registered, you'll have access to the SMSFORCRM admin panel.
Set up the custom menu link in GHL
SMSFORCRM provides a custom menu link that connects your GHL sub-account to the SMS gateway. Add it to your sub-account's settings — this is what tells GHL where to route SMS sends.
The exact link will be available in your SMSFORCRM admin panel after registration.
Install the Android app & scan the QR code
Download the SMSFORCRM Android app to the phone you want to use as the SMS gateway. Open the app and scan the QR code from the SMSFORCRM admin panel — this pairs your phone with your account, just like scanning the WhatsApp QR for WAGHL.
Keep this Android device:
- Connected to a stable internet connection (Wi-Fi or mobile data)
- Plugged into power, or with battery management disabled for the app
- Ideally a dedicated phone — using your daily-driver phone works but isn't ideal for high SMS volumes
Choose your messaging mode
In your WAGHL admin panel, set the routing mode (the five options above). For most users, "WhatsApp or SMS" is the right default — try WhatsApp first, fall back to SMS when needed.
Send messages from GHL
You can now send SMS from two places:
- Conversation tab — type a message in any contact's conversation; GHL routes it to your phone via SMSFORCRM, your phone fires the SMS
- Workflow Automation — use SMS in any workflow action, the same routing applies
Test it
Send a test SMS to a number you control. Verify it arrives correctly and shows your phone's number as the sender. Then try the workflow path to confirm automation routing works end-to-end.
SMSFORCRM vs. Twilio fallback
WAGHL supports two SMS provider integrations. Pick whichever fits your operation:
| SMSFORCRM (this article) | Twilio (other article) |
|---|---|
| Uses your Android phone's SIM | Uses Twilio cloud |
| SMS comes from your real phone number | SMS comes from a Twilio number |
| Android only | Works regardless of phone OS |
| Limited by your phone plan / carrier | Scales to millions of SMS |
| SMSFORCRM subscription only | Twilio per-message + WAGHL plan |
| Personal-feel sending | Programmatic / business-feel sending |
Limitations to know
Carrier throttling. Phone carriers may rate-limit or block bulk SMS sending. If you're sending more than a few hundred SMS per day, your carrier might flag it. Twilio handles bulk sending more reliably.
Phone availability. The Android phone must stay online for SMS to send. If the phone runs out of battery, loses signal, or the app gets killed by Android's battery manager, sends pause until it reconnects.
Privacy. SMS sent via SMSFORCRM shows your real phone number to recipients. For brand-consistent business sending, a Twilio number gives you a separate business-only line.
iPhone not supported. Apple's iOS doesn't allow third-party SMS gateway apps. Android only.
What's next?
- Twilio SMS fallback — alternative SMS provider for high-volume or iOS scenarios
- Setup & configuration — admin panel basics
- FAQ — quick answers to common questions