Utility and Telecom Customer Notifications: SMS and WhatsApp

What do telecoms send for top-ups and data bundles?

Telecoms send balance, top-up confirmation, bundle usage and expiry alerts. These are triggered by the customer's own account activity, which keeps them service messages.

Najm Mobile: you now have 5 GB until 30 Nov. Dial *100# to check. Reply STOP for no alerts.

That is 91 characters in GSM-7, one segment. Include an opt-out for non-essential alerts, and offer preferences so customers choose which thresholds notify them.

If the same message also says "Buy a bigger bundle at a discount", it becomes promotion. Send it as a separate marketing message with marketing consent, a registered sender where required and, in markets with quiet hours for promotions, inside the permitted window. Check each country on the sender ID checker and SMS marketing rules by country.

How should fraud warnings be written?

Fraud warnings should tell customers what you will never ask for and how to report a suspicious message. Keep them short, specific and from your usual sender.

Najm Mobile: we never ask for your PIN or OTP by SMS or call. Report scams at najm.example/report

That is 97 characters in GSM-7. Avoid links to login pages in a fraud warning, since scammers copy that pattern and customers are trained to distrust links. The GSMA's work on interworking security describes the threats operators face from A2P fraud, and your own anti-fraud team knows which scams are current. Our guides on SMS pumping fraud and why SMS messages are blocked explain the filtering side. Registered sender IDs also help customers recognise the real sender.

How do you handle Arabic and English?

Store the customer's preferred language and send one language per message. Plan for Unicode in Arabic.

An Arabic version of the first outage alert:

وادي للكهرباء: انقطاع في المنطقة 3. التحديث القادم 15:30.

That is 57 characters, one Unicode segment. If copy runs over 70 characters it splits into several parts and costs more, so write tight and check each variant in the SMS character counter. Our guide on SMS character limits and Unicode for Arabic explains why, and Arabic customer messaging best practices covers tone.

How do you send millions of notifications reliably?

Separate traffic types, queue by priority and monitor delivery by operator. Incident alerts must not wait behind a marketing blast.

Read high-volume SMS sending for throughput planning, queueing and delivery-report handling. A bill run that sends everything at the same minute can overload payment pages and contact centres, so spread it across a window. Capacity is sized per account with your provider.

When should WhatsApp replace or back up SMS?

Use SMS where reach and urgency matter most and WhatsApp where richer content, buttons and replies help. Configure fallback so a failed WhatsApp delivery is followed by one SMS after a short timeout.

Facts to design around from Meta's documentation: WhatsApp requires opt-in; outside the 24-hour customer service window only approved templates can be sent; and a customer reply opens the window for free-form answers, including buttons and lists. That reply window is what lets a customer send "1" and get a human or an automated answer. Set preferences per customer in the Omni Inbox and see channel fallback strategy for the order and timing rules.

Worked example: a regional water and power company

"Wadi Utilities", a synthetic company, serves 400,000 accounts in two languages.

• Setup: customer records carry zone, language and consent. Templates for outage, restoration, maintenance and bills are approved in Arabic and English before the summer peak.
• Incident: a feeder fault affects Zone 3. Operations confirm it at 14:10 and the incident system triggers the first alert to Zone 3 accounts only, by SMS. Customers with WhatsApp consent also receive the utility template.
• Update: at 15:30 the second message goes out, then restoration at 16:45 with a "reply 1 if still off" path to the inbox.
• Afterwards: the team compares call volume during the incident to previous incidents, checks delivery by operator and reviews replies for zones that were mapped wrongly.

Measure delivery rate, time from confirmation to send, calls per incident, replies and payments received on time after bill reminders. Use these to refine content and timing.

What mistakes should you avoid?

• Mixing offers into alerts. It risks template recategorisation on WhatsApp and complaints on SMS.
• Sending to the whole base. Irrelevant alerts train customers to ignore you.
• Long Arabic messages. They split into multiple segments.
• No mapping tests. A wrong zone mapping sends the wrong alert.
• Silence after the first alert. Promise and send updates.
• Asking for data in the message. Never ask for passwords, PINs or codes in a notification.

This is general guidance, not legal advice. Check the rules for each country and regulator before launch.

How OmniChannels.ai helps

OmniChannels.ai, powered by BroadNet Technologies, sends SMS through direct operator connectivity, supports Unicode and Arabic, and runs WhatsApp utility, marketing and authentication templates. Channel fallback is configured per use case, delivery statuses arrive in a single webhook format, and campaigns support CSV upload, personalisation and scheduling. SMPP 3.4 is available for high-volume sending. For a notification design review, book a demo.