Transactional SMS and automated customer notifications
Keep customers informed the moment something happens. DARSMS sends receipts, order updates, account alerts and service notifications from your own systems through a simple SMS API, or from the dashboard when you need to notify a group.
Overview
Transactional messages are the updates customers expect: a payment was received, an order has shipped, an account has changed, a service is interrupted. They build trust when they arrive promptly and contain exactly the information the customer needs.
Most transactional SMS are sent automatically. Your application calls the DARSMS SMS API with the recipient, your Sender ID and the message text, stores the returned message ID and can check the delivery status later. For one-off notices to many customers, such as a service interruption, use a dashboard campaign to a contact group.
Common uses
- Payment and deposit receipts.
- Order confirmations and delivery tracking updates.
- Account changes, balance and security alerts.
- Loan disbursement and policy issuance notices.
- Service interruption and maintenance notices.
- Booking and registration confirmations.
How it works with DARSMS
- 01
Create an API key
Generate a key in the API Keys section of your DARSMS dashboard and store it securely on your server.
- 02
Use your Sender ID
Send from an approved Sender ID with your business name so customers know the notification is genuine.
- 03
Trigger from your system
Call the send endpoint when the event happens, such as when a payment is posted or an order changes status.
- 04
Track delivery
Store the returned message ID and query the status endpoint to confirm the notification was delivered.
Example messages
Payment received: TZS 150,000 for invoice INV-2291 on 04/06 at 10:42. Thank you for your business. - Kilimo Supplies
116 characters
Dear customer, water supply in Mikocheni B will be interrupted on 12/06 from 09:00 to 15:00 for maintenance. We apologise for the inconvenience.
144 characters
Best practices
- Send the notification immediately after the event; late receipts cause support calls.
- Include a reference number the customer can quote if they contact you.
- Keep marketing out of transactional messages so important updates stay clear.
- Validate phone numbers in your system to avoid failed deliveries.
- Keep your API key on the server; never embed it in a mobile app or web page.
Frequently asked questions
What is the difference between transactional and promotional SMS?
Transactional SMS are triggered by a customer's own activity, such as a payment or order, and are expected. Promotional SMS are marketing offers. Keep the two separate so important notifications are never mistaken for advertising.
Can our system send notifications automatically?
Yes. Any system that can make an HTTPS request can call the DARSMS SMS API with an API key. The API responds with a message ID that you can use to check delivery status.
How do we know a notification was delivered?
Each message has a delivery status of queued, sent, delivered, failed or rejected. Check it in the dashboard reports or through the message status API endpoint.
Related pages
Ready to get started?
Create a free account with 5 SMS credits to test, then buy credits with mobile money as you grow.