Two-Way SMS Integration: Let Customers Reply, Not Call
Your ops or customer-service team still sends one-way SMS for confirmations, then fields phone calls for every YES, cancel, or question. Two-way SMS turns those replies into an SMS conversation that lands in the CRM or ticket queue automatically.
We build the SMS reply handling that cuts confirmation labour and call volume.
Sound Familiar?
These are the exact issues ops and CS leads face when SMS is still one-way only:
- Your team sends one-way appointment or delivery SMS, then spends the afternoon calling everyone who did not reply
- Customers who want to cancel or reschedule still phone the reception line because there is no SMS reply path
- YES, NO, and free-text replies land nowhere: nobody routes inbound SMS into the CRM or ticket queue
- STOP requests sit unread or get handled inconsistently, leaving you exposed under POPIA direct-marketing rules
- Confirmation labour eats ops capacity while call answer rates stay roughly half of SMS reply rates
POPIA expects a simple SMS opt-out. DMASA guidance is clear: for marketing SMS, recipients should be able to unsubscribe by sending STOP to a short code. If STOP replies are ignored or handled by hand, you are carrying avoidable compliance and reputation risk.
What Two-Way SMS Reply Handling Actually Does
Outbound SMS leaves your system. The customer replies. The reply writes itself into the CRM or ticket queue.
You Send the Prompt
Confirmation, feedback, or support invite goes out via Twilio, Clickatell, or your gateway
Customer Replies by SMS
YES, NO, STOP, a rating, or a free-text question on your shortcode or long number
Webhook Parses Intent
Keyword rules update status, suppress marketing, or open a ticket with full context
CRM & Queue Updated
Ops sees confirmed, cancelled, or opted-out without dialling. Exceptions reach a human fast.
Everything You Need for Reliable SMS Conversations
Inbound Reply Routing
Every reply on your shortcode or long number hits a webhook and lands on the right CRM contact or ticket queue within seconds.
Keyword Parsers (YES / NO / STOP)
Structured replies update appointment status, cancel bookings, or opt the contact out. Free text escalates to a human with full thread context.
Confirmation & Feedback Flows
Two-way SMS conversations for confirmations, NPS-style 1–5 ratings, and short feedback, without forcing customers onto a web form.
Support Tickets from SMS Replies
Unmatched replies open a ticket or chat task with the message body, sender number, and CRM match, so CS picks up where SMS left off.
Shortcode & Long-Number Setup
We help you choose: dedicated SA shortcodes for high-volume branded traffic, or long numbers for faster two-way chat at lower monthly rental.
POPIA STOP Handling
STOP (and common variants) immediately suppress marketing sends, log the objection on the contact, and keep an audit trail for POPIA section 69.
Gateways & Systems We've Connected
From 320 Confirmation Calls a Month to 70
How a Johannesburg outpatient clinic stopped dialling every patient who ignored a one-way SMS.
The Manual Process
- Clinic sent one-way appointment SMS the day before
- Reception called non-responders: roughly 320 confirmation calls a month
- Cancels and reschedules clogged the phone line every morning
- STOP and "who is this?" replies sat in a shared gateway inbox nobody owned
- No CRM field showed whether the patient had confirmed by text
The Automated Process
- Outbound SMS invites Reply YES to confirm or NO to cancel
- Keyword parsers update HubSpot appointment status within seconds
- Free-text questions open a Zendesk ticket with the full SMS thread
- STOP suppresses marketing and logs the objection for POPIA
- Reception only dials the residual ~70 cases that still need a human
Before vs After Two-Way SMS Integration
How It Works
From first conversation to live two-way SMS in 2–4 weeks.
Tell Us Your Setup
Gateway (Twilio, Clickatell, or other), shortcode vs long number, confirmation volume, and where replies should land.
Free Scoping Call
30-minute call to map keyword rules, CRM fields, ticket routing, and POPIA STOP behaviour before anything is built.
Build & Test
We wire inbound webhooks, parsers, and CRM write-back, then parallel-test with live traffic for a week before you retire confirmation calls.
Go Live & Monitor
Switch confirmations to two-way SMS. Dashboards show reply rates, STOP volume, and how many calls you no longer need to make.
Frequently Asked Questions
What is two-way SMS integration, and how is it different from a bulk blast?
One-way SMS is broadcast only: you send, the customer cannot usefully reply into your systems. Two-way SMS uses a shortcode or long number so replies come back on a webhook, get parsed (YES, NO, STOP, or free text), and update your CRM or ticket queue. That is the difference between a notification and an SMS conversation.
Should we use a shortcode or a long number in South Africa?
Dedicated SA shortcodes suit high-volume branded traffic (once-off application fee plus monthly rental; local providers quote around R1,000 setup and R750/month for a dedicated code). Long numbers provision faster and cost less, and work well for moderate two-way chat, confirmations, and surveys. We size the choice to your monthly send volume and brand needs.
How do keyword parsers handle YES, NO, and STOP?
Inbound messages are normalised and matched to rules you approve. YES can confirm an appointment, NO can cancel or open a reschedule path, and STOP suppresses marketing sends and logs the objection. Ambiguous or free-text replies route to an agent so nothing falls through.
What does POPIA require for SMS opt-outs?
For electronic direct marketing, POPIA section 69 requires a clear chance to object, free of unnecessary formality, including on each marketing communication. DMASA guidance expects SMS recipients to be able to unsubscribe by sending STOP to a short code. Our integrations process STOP immediately and keep an auditable record on the contact.
How is this different from WhatsApp?
WhatsApp is excellent where customers already chat on that app. Two-way SMS reaches every handset without an app install, works for customers who never opened WhatsApp Business threads, and pairs cleanly with existing SMS gateways you already pay for. Many ops teams run both: WhatsApp for rich support, SMS for confirmations and STOP-compliant marketing.
How much does a two-way SMS integration cost?
A focused inbound webhook plus keyword parsers and CRM write-back starts from around R15,000. Builds with ticket routing, multi-flow confirmation and feedback logic, shortcode provisioning support, and POPIA audit trails typically run R25,000–R60,000. Teams cutting hundreds of confirmation calls a month usually see payback inside 2–3 months.
Stop Calling Customers Who Could Have Replied by SMS
If your team still sends one-way blasts and then dials for every confirmation, you are paying call-centre rates for work a keyword parser can finish in seconds.
Tell us which gateway you use, whether you have a shortcode or long number, and where replies should land. We will show you exactly how two-way SMS reply handling would cut your confirmation labour.