SMS chatbots, SMS forms and bulk messaging
Moozy SMS is two-way text messaging for enterprise. Send campaigns and transactional messages, then handle the replies as conversations, forms and payment steps. It reaches any mobile phone, with no app and no data bundle.
Moozy Cover: P120 premium due 25 Oct. Reply 1 to pay, 2 to change date, 3 for a person. STOP to opt out.
2
Which day of the month suits you? Reply with a number from 1 to 28.
15
Done. From November your premium will be taken on the 15th.
Illustrative workflow.
Three things SMS does on Moozy
SMS is one channel of the Moozy messaging platform, alongside WhatsApp, USSD and web. Bulk SMS is part of it, not a separate product: every message you send can start a journey.
has my claim been paid yet
Hello Neo. Your claim was approved on 3 Oct and P2 400 was paid to your mobile wallet on 4 Oct.
SMS chatbot
Customers ask in their own words and get an answer drawn from your information and their own record.
Q3 of 6: which district do you live in? Reply with the name, e.g. KWENENG.
KWENENG
Q4 of 6: how many people live in your household?
SMS forms
A registration or survey asked one question at a time, with each answer validated and stored as structured data.
Moozy Cover: we received P120.00 on 15 Nov. Ref MC-20418-11. Your cover is active. Thank you.
Campaigns and transactional messages
Bulk sends to a segment, plus confirmations, receipts and reminders triggered by your systems.
Illustrative workflow.
A gateway sends. It does not listen.
A bulk SMS gateway delivers the message and stops. Replies often land in a shared inbox, consent is tracked separately, and the payment or registration happens somewhere else. Enterprise messaging needs the send and the response in one place.
| What a buyer checks | Bulk SMS gateway | Moozy |
|---|---|---|
| Sending in bulk | Yes | Yes, to segments built from your own customer data |
| Replies | Typically forwarded to an inbox | Handled as a conversation, a form answer or a menu choice |
| What happens next | Usually outside the tool | Form, identity check, payment step or handover in the same journey |
| Consent | Managed by you, separately | Opt-in and opt-out recorded per customer and applied to the next send |
| Other channels | SMS only | WhatsApp, USSD and web from the same service definition |
| Reporting | Delivery receipts | Delivery, failures, replies, completions, payments and cost per message |
Typical of each product category.
How a campaign becomes a completed journey
The message is the first step. What the customer does with it is the part worth measuring.
Your systems can also start a message through the API: a receipt after a payment, a reminder before a due date, a notice when a status changes.
Illustrative workflow.
Choose who receives it
Build the segment from customers who opted in, using the fields you already hold.
Send, in bulk or one at a time
A campaign to thousands, or a single transactional message raised by an event in your system.
The reply continues the journey
A number, a keyword or a free-text answer moves the customer to the next question, a payment step or an answer from the chatbot.
A person takes over when needed
Replies that need judgement go to your team, with the thread attached. How handover works
Reminders and follow-ups
Scheduled nudges for customers who started and did not finish, within the consent they gave.
Service stepFollow-up
Know what was delivered, answered and spent
SMS customer engagement is only worth the spend if you can see the response. Events are captured as they happen, so you can review a campaign while it is still running.
- Delivered, failed and pending messages
- Replies, and what each reply led to
- Form starts, completions and where people stop
- Successful and failed payment collections
- What your messaging is costing you, per message
- 8 412Delivered
- 1 137Replied
Illustrative figures.
Set up properly, governed throughout
Messaging at volume touches operators, regulators and your customers’ patience. The controls are part of the platform, not a policy document beside it.
Sender identity and short codes
Sender names, long numbers and short codes are arranged with mobile operators during setup. Availability and approval steps vary by market.
Opt-in and opt-out
Consent is recorded per customer and per channel. Customers reply STOP where the network supports it, and the preference applies to the next send.
Audit trail
Every message, reply and automated action is logged with its time, channel and actor, and can be exported for review.
Role-based access
Roles decide who can send a campaign, who can read replies and who can act on customer information.
One channel of the same service
A customer can register on USSD, get the reminder by SMS and finish on WhatsApp. Where customer matching is configured, the journey carries on across channels.
SMS and USSD reach customers without a data bundle. WhatsApp and web need internet access. Choose the channel for the task, not one channel for everything.
Connected to your systems
APIs and webhooks let your CRM, core banking or policy system trigger a message and receive the outcome: delivered, replied, completed, paid.
English and Setswana
Send in English or Setswana, and let the customer reply in either. Other languages are added by arrangement.
Where SMS does the most work
SMS suits short, time-bound steps for a wide audience, including customers on basic phones.
Financial services and insurance
Premium and repayment reminders with a reply-to-pay step, payment receipts and date changes.
Government and public services
Notices to citizens, application status updates and short surveys that reach every phone.
Health and social services
Appointment reminders, confirmations by reply and follow-up after a visit.
Enterprise customer operations
Service updates, outage notices and feedback requests, with replies routed instead of lost.
Frequently asked questions
Is Moozy a bulk SMS platform?
Moozy sends bulk SMS, and that is one capability of a wider messaging platform. The same platform handles the replies, runs forms and payment steps and records consent across SMS, WhatsApp, USSD and web, and reports on delivery, replies and cost per message.
What is an SMS chatbot?
It is a chatbot that holds a conversation by text message. The customer writes a question in their own words, and the reply comes from your approved information and, where connected, their own record. A person can take over at any point.
Can customers complete a form by SMS?
Yes. A form is asked one question at a time, each answer is validated, and the result is stored as structured data. The same form can also run on WhatsApp, on the web or as a USSD menu.
Do customers need a smartphone or data?
No. SMS works on any mobile phone and does not need a data bundle. Network coverage and operator charges still apply.
How do customers opt out?
They reply STOP where the network supports it, or use the instruction given in the message. The preference is recorded against the customer and applied before the next send.
Can our own systems send SMS through Moozy?
Yes. Your systems can trigger transactional messages through the API, such as confirmations, receipts and reminders, and receive delivery and reply events back through webhooks.
Related capabilities
SMS and bulk messaging is one capability of Moozy’s omnichannel customer engagement platform. See how it is used across industries.
Bring one message you already send
Show us a reminder, a notice or a campaign you run today. We will walk through what the reply could do next.