Tithi MondalBlog

Article6 min readUpdated

Notification UX: Push, SMS and WhatsApp for Your App

Notification UX for Indian products: when to send push, SMS or WhatsApp, how to word messages, how often to send, and how to let users choose.

Read inहिन्दीবাংলাमराठीதமிழ்తెలుగుગુજરાતી

Notification UX: Push, SMS and WhatsApp for Your App: cover illustration

A customer orders lunch from a small restaurant app. In 40 minutes she gets 6 messages: order placed, order accepted, a push to rate the app, an offer for tomorrow, a reminder that her cart is waiting, and an SMS with a coupon. She turns off notifications and never sees the one that matters: "Your rider has arrived." That is the cost of careless notification UX. Every message spends a little of the user's trust, and you only have so much.

Pick the channel by the job of the message

Push, SMS and WhatsApp are different tools. Each one fits a different job.

ChannelBest forWeak at
Push notificationEvents inside your app: order status, new message, class startingUsers who never installed the app, or turned push off
SMSOne time codes, payment confirmations, critical alertsLong or rich content, and anything marketing-heavy
WhatsAppUpdates and conversations people want to keep: bookings, invoices, supportMessages the user did not agree to receive
EmailReceipts, long records, account newsAnything urgent
In-app messageTips and offers while the user is already insidePeople who are not opening the app

A simple rule: use the quietest channel that still does the job. A payment confirmation can be a push and an SMS. A discount can be an in-app banner only.

Many Indian users trust SMS and WhatsApp more than app alerts, because they check them every day. Others turn off app alerts quickly. Plan for both, and never depend on a single channel for something critical.

Decide when to send which message

Sort your messages into 3 groups.

Group 1: Transactional. The user did something and expects a reply. Order confirmed, OTP (one time password), payment received, ticket booked. Send these at once. Users want them.

Group 2: Helpful alerts. Something changed that affects the user. Delivery delayed, class starts in 15 minutes, EMI (monthly instalment) due in 3 days. Send these at a time that is useful, with plenty of notice.

Group 3: Promotional. Offers, new features, reminders to return. These are the easiest to overuse. Send them rarely, and only to people who agreed.

On the StudySakha edtech app, live class and progress features create a natural set of Group 2 alerts: a class is about to begin, a report is ready. Those messages feel useful because they are tied to something the student already chose to do. See more about that sector in my edtech app design notes.

For payment events, the confirmation must be fast and clear. Read my notes on UPI payment UX and checkout design.

How to word a notification

A notification has about two lines to work with. People read it on a lock screen, often in a hurry, often after translating it.

Follow this order: what happened, then what to do.

Do not writeWrite instead
Update on your orderYour order #1204 is out for delivery. Arrives by 1:30 pm.
Hurry up, offer endingThe ₹100 off coupon ends tonight at 11:59 pm
Action needed on your accountUpload your Aadhaar and PAN images to finish verification
You have a new messageRina: Can you come at 5 pm instead?
Payment failed.₹499 was not paid. Your bank did not approve it. Try UPI again.

Rules that help:

  • Put the key fact in the first 40 characters, because many phones cut the rest.
  • Use the person's own name or the thing they bought, not a generic line.
  • Use one clear action. Tapping the notification should open exactly that screen, not the home screen.
  • Write in the language the user chose. A user who picked Bengali should not get English alerts.
  • Do not use false urgency such as "Last chance" when it is not true.
  • Do not use all capital letters or many symbols.

Good wording is the same craft as the rest of your interface text. I cover it in UX writing and microcopy for apps.

Frequency: fewer messages, better timed

There is no perfect number of messages per week, because it depends on your product. A ride app may send many messages during a trip and none otherwise. A savings app may send 1 or 2 per month. What matters is a rule you can defend.

A few working rules:

  • Count every message across channels. If the user gets the same news by push, SMS and WhatsApp, you are repeating yourself.
  • Do not send the same alert twice. If the app was opened after a push, cancel the matching SMS.
  • Group updates. One message saying "3 new classes this week" beats 3 separate pushes.
  • Respect time. Avoid late night and very early hours unless the message is urgent, such as a delivery or a security warning.
  • Respect festivals and local habits. A user in a small town may not want a sales push during a family occasion.
  • Stop when the user does not respond. If someone has ignored 5 promotional messages in a row, send fewer.

Ask for push permission at the right moment. Do not show the system permission box on the first screen. First show your own short screen: "Get order updates. We will tell you when your food is on its way." Then ask the system question. If a user says no on your screen, do not ask the system, so you keep the chance to ask later. My piece on app onboarding UX best practices shows where this fits in first use.

WhatsApp notifications for business

WhatsApp is how many small businesses in India already talk to customers, so it is a natural channel for bookings, invoices and support. It works well when the user started the conversation or clearly agreed to get updates.

Practical points:

  • Ask for consent on a clear screen: "Send my order updates on WhatsApp." Use a checkbox the user can tick, not one that is pre-ticked.
  • Keep messages short, with one action such as a button or a link.
  • Make it easy to stop. Tell people how to opt out.
  • Use WhatsApp for what is personal and useful. Do not turn it into a daily advert.
  • For the rules on business messaging, templates and what you may send, check the provider's current policy. Those rules can change, so do not rely on old advice.

The same care applies to SMS. Check the provider's current policy, and any rules in your country for sending commercial text messages, before you plan a campaign. For a website contact page and WhatsApp button, the key is to say clearly what will happen after the tap.

Design the notification settings screen

A settings screen turns a blunt choice, "all on or all off", into many small choices. People who can choose usually keep more channels open.

A good layout:

  1. A heading: "Notifications".
  2. Groups with plain names: "Orders and payments", "Reminders", "Offers and news".
  3. For each group, a toggle per channel: Push, SMS, WhatsApp, Email.
  4. Critical items shown as always on, with a short note: "We will always send security codes by SMS."
  5. A quiet hours option: "Do not send between 10 pm and 8 am."
  6. A language choice for messages.

Things to avoid:

  • A single master switch with nothing else.
  • Hiding the screen deep in a menu. Link to it from the first promotional message and from the profile screen.
  • Making "Unsubscribe" a hunt. One tap should work.

Let people change settings without losing the important messages. The settings screen is also a good place to test your wording with real users, using a small session like the ones in my usability testing guide.

If you are planning alerts for an app and want the messages, timing and settings screen designed together, that sits within my mobile app design service.

Frequently asked questions

When should an app use SMS instead of push?

+

Use SMS for one time codes, payment confirmations and critical alerts, because it works even when the app is closed or push is off. Use push for in-app events that are not critical.

How many push notifications are too many?

+

There is no fixed number. If users turn off notifications or stop opening them, you are sending too many. Combine updates and send fewer promotional messages.

Should a business send WhatsApp messages without consent?

+

No. Ask users clearly and let them opt out. For the rules on business messaging, check the provider's current policy.

What should a notification settings screen include?

+

Groups such as orders, reminders and offers, a toggle for each channel, quiet hours, a language choice and a note on messages that are always sent for security.

Working on something like this?

Tell Tithi what you are planning. You get a clear scope, a fixed price and a timeline before any work begins. I reply to every enquiry within 24 hours.

Your details go only to Tithi and are used only to reply to you. No newsletters, no sharing.