This article is currently available in English while its SO translation is prepared or reviewed.
Operational software creates a steady flow of events: a job is assigned, a delivery is late, a renewal is due, a customer has paid. Each event matters only if the right person learns about it in time to act. Choosing how to notify people, by SMS, WhatsApp, email, in-app alert or a phone call, is a design decision that affects cost, reliability and whether people trust the system.
This guide compares the common channels and offers a practical way to decide which to use for each kind of message.
Start with the message, not the channel
List the notifications your system needs to send and, for each one, answer four questions:
- Who receives it? A driver in the field, a supervisor in the office, a customer, or a manager.
- How urgent is it? Does it need action within minutes, today, or this week?
- What must they do? Acknowledge it, open a record, call someone, or simply be informed.
- What happens if it is missed? A small inconvenience, a lost sale, a compliance issue or a safety risk.
The answers usually make the channel choice obvious. A safety-critical alert to a driver needs a different route than a weekly summary to a manager.
SMS
SMS reaches almost every mobile phone, including basic phones, and does not need mobile data or an app. That makes it dependable for short, important messages to people in the field and to customers whose phone types you do not control.
Things to plan for:
- Length: Messages are short. Keep them specific and include a reference or short link where more detail is needed.
- Sender identity: Sending from your business name normally requires a registered sender ID arranged through an SMS provider.
- Cost: Each message has a cost, so high-volume, low-value messages add up.
- Delivery reports: Use the provider's delivery reports to see which messages were not delivered, and decide when to retry or escalate.
WhatsApp is familiar and widely used for business communication, and it supports richer content such as images, documents and quick-reply buttons. For automated messages from a system, businesses typically use the WhatsApp Business Platform through an approved provider rather than a personal phone.
Things to plan for:
- Templates: Messages that a business starts generally need pre-approved templates. Free-form replies are usually limited to a window after the customer last messaged you.
- Opt-in: Collect clear consent before sending automated WhatsApp messages, and make it easy to stop them.
- Data dependence: The recipient needs a smartphone with mobile data or Wi-Fi.
- Shared phones: Avoid running operations from one person's phone. Use an account the business controls so messages and history are not lost when staff change.
Check the platform's current rules and pricing with your provider, because they change over time.
Email suits messages that are detailed, formal or need to be kept: invoices, statements, reports, approvals and documents. It is inexpensive to send and easy to archive, but people in the field often do not read email quickly, so it is a poor choice for urgent alerts.
Send from a properly configured business domain so messages are less likely to land in spam, and keep subject lines specific enough that people can find the message later.
In-app and push notifications
If your staff already use a mobile app or web system for their work, in-app notifications keep everything in one place. Push notifications can reach a phone even when the app is closed, and they cost little to send at scale.
They only work if people install the app, sign in and allow notifications. Push messages are also less reliable on phones with aggressive battery-saving settings. For critical alerts, pair them with a fallback such as SMS.
Phone calls and escalation
Some situations still need a person on the phone: a safety incident, a vehicle breakdown with goods on board, or a customer complaint that needs immediate handling. Automated systems can support this by creating a call task or escalating to a supervisor when an alert has not been acknowledged.
Design an escalation path
For important notifications, decide in advance what happens when nobody responds. A simple pattern works well:
- Send the first notification through the most convenient channel, such as in-app or WhatsApp.
- If it is not acknowledged within an agreed time, send an SMS.
- If there is still no response, alert a supervisor and record the escalation.
Record each step in the system so managers can see where notifications are not being acted on, and fix the cause rather than adding more messages.
Keep notifications useful
Too many notifications teach people to ignore them. A few habits help:
- Group low-urgency updates into a daily or weekly summary.
- Let people adjust non-critical notification settings themselves.
- Include enough context to act without opening three screens: what happened, which record, what to do next and by when.
- Review notification volumes and response times every month.
Protect personal data
Notifications often contain names, phone numbers, locations or payment details. Send only what the recipient needs, avoid sensitive details in SMS or WhatsApp previews, and make sure the business, not an individual's personal account, controls the channels and their history. Keep provider credentials on the server, never in a mobile app or shared document.
A quick decision guide
- Urgent alert to a driver or field worker: in-app or push, with SMS as the fallback.
- Delivery update to a customer: an SMS or WhatsApp template, with email as the fallback.
- Documents, invoices and statements: email, with a customer portal as the fallback.
- Task assigned to office staff: in-app, with an email summary as the fallback.
- Safety incident or breakdown: a phone call plus an in-app alert, with SMS to a supervisor as the fallback.
The right mix depends on your team, your customers and the cost of a missed message. For more on connecting payment events and notifications, see our guide to planning M-Pesa integration and our system integration service.