Bulk SMS for insurance companies, brokers and agents
Reduce lapsed policies and keep clients informed at every stage. DARSMS helps insurers, brokers and independent agents in Tanzania send premium reminders, renewal notices and claim updates by SMS.
Why insurers use SMS
Missed premium payments and forgotten renewals are a major source of lapsed cover. A short, timely SMS a few days before a due date is one of the simplest ways to protect your book of business, especially for motor, medical and micro-insurance clients who may not read email.
DARSMS supports recurring reminder schedules: load your policyholders with their premium amount and due dates, choose weekly or monthly reminders and how many days before the due date to send them, and the platform sends each reminder automatically.
Brokers and agents use the same account to follow up on quotations, confirm payments received and share claim progress, all under a recognisable Sender ID so clients know the message is genuine.
What insurers send by SMS
- Premium due-date reminders before a policy lapses.
- Motor and medical policy renewal notices.
- Payment received confirmations with policy number.
- Claim registration acknowledgements and status updates.
- Quotation follow-ups for brokers and agents.
- New product announcements to existing clients.
When insurers should send
30 days before expiry
Renewal notice
Name the policy and, for motor cover, the vehicle registration, so clients with several policies know exactly which one is ending.
7 days and 1 day before the due date
Premium reminders
Include the amount and the official payment number. Remove clients who have already paid before each reminder goes out.
As soon as payment is recorded
Payment confirmation
Confirm the amount, the policy number and the new cover period. Sent through the API, it goes out the moment your system records the payment.
At registration and at each stage
Claims
Acknowledge the claim with its reference, then update the client when an assessor is assigned and when settlement is approved.
SMS templates for insurers
Dear Juma, your motor policy MTR-20418 for T 123 ABC expires on 30 Mar. Renew before expiry to stay covered. Call 0741 000 000. - Salama Brokers
144 characters
Payment of TZS 85,000 for policy MED-7731 received on 12 Mar. Your cover is active until 11 Apr. Thank you for choosing us.
123 characters
Claim CLM-5521 for T 456 DEF is registered. An assessor will call you within 48 hours. Quote CLM-5521 in all enquiries. - Salama Insurance
138 characters
Ndugu Ali, bima ya afya MED-7731 inaisha 30/04. Lipia TZS 85,000 kwa namba ya malipo 991234 ili huduma iendelee. - Salama Brokers
129 characters
How to get started with SMS for insurers
- 01
Export the policy book
Pull policyholders from your policy administration system: phone, name, policy number, premium and due date. Agents can start from their own client spreadsheet.
- 02
Create reminder schedules
Add policyholders to a monthly or weekly schedule with their amount and due date, and set how many days before each due date the reminder is sent.
- 03
Automate confirmations by API
Have your system call the SMS API when a payment or claim event is recorded, and keep the returned message ID to check delivery later.
What it costs: a worked example
A broker with 2,000 active policyholders
| Message | Credits |
|---|---|
| Premium reminders: 1 per client | 2,000 |
| Payment confirmations | 1,500 |
| Renewal notices and claim updates | 500 |
| Total per month | 4,000 |
A purchase of 4,000 credits falls in the Basic tier at TZS 25 per SMS, so this month costs about TZS 100,000 before VAT. Buying 5,000 credits instead costs TZS 100,000 at TZS 20 each: the same or less money for more credits, and unused credits never expire.
All messages are single-SMS notices of up to 160 characters.
How DARSMS helps insurers
Automatic premium reminders
Set weekly or monthly reminder schedules per policyholder, with the amount due and reminders sent a set number of days before the due date.
Integrate with your core system
Use the SMS API to send payment confirmations and claim updates the moment they are recorded in your policy administration system.
Proof of communication
Delivery reports record when each reminder was sent and whether it was delivered, useful when a client says they were never notified.
Mistakes to avoid
Reminding clients who already paid
A premium reminder after payment makes clients doubt your records. Reconcile payments before each scheduled send and take paid clients off the list.
No policy reference
"Your premium is due" is not enough for a client with motor and medical cover. Always include the policy number or vehicle registration.
Payment details that look like a scam
Clients are wary of SMS fraud. Send only from your registered Sender ID, always use the same official payment numbers, and never ask for PINs or passwords.
Questions from insurers
Can reminders be sent automatically every month?
Yes. Create a reminder schedule with a weekly or monthly frequency, add policyholders with their amounts and dates, and choose how many days before each due date the SMS should go out.
Is SMS suitable for independent insurance agents?
Yes. There is no minimum volume or monthly fee. An agent can buy a small bundle of credits, import client numbers from Excel and send renewal reminders from the dashboard.
Can we connect SMS to our policy system?
Yes. The DARSMS SMS API lets your system send a message over HTTPS with an API key, and returns a message ID you can use to check delivery status.
How do we stop clients confusing our SMS with fraud?
Send every message from your registered Sender ID, use the same official payment numbers in every reminder, and tell clients that you will never ask for a PIN or password by SMS.
Can a broker send for clients of several insurers?
Yes. Keep a contact group per insurer or product line and send under the broker's own Sender ID, naming the insurer and policy in each message.
Guides for insurers
Related solutions
Stop policies lapsing for want of a reminder
Register free, set up a premium reminder schedule with your first clients, and connect the API when you are ready to automate confirmations.
