Read receipts in WhatsApp are the two blue ticks that tell you a message was read: one grey tick means your message reached WhatsApp's server, two grey ticks mean it was delivered to the recipient's phone, and two blue ticks mean it was read. A clock or pending icon means the message has not yet left your device, usually because you are offline; on the Business API, the same states arrive as sent, delivered and read webhook events you can track at scale.
Disclosure: this guide is published by RichAutomate, a WhatsApp Business API platform. API status meanings were checked against Meta's Cloud API status-webhook reference, and read-receipt settings against WhatsApp's Help Center, on 30 October 2026.
That three-state signal, sent, delivered, read, is the single most misread part of WhatsApp for Indian businesses in 2026. With an estimated 535-550 million WhatsApp users in India and business messaging now the default channel for order updates, OTPs, and support, knowing exactly what each tick means saves hours of guesswork about whether a customer actually saw your message. This guide decodes every tick on both the WhatsApp Business App and the WhatsApp Business API, and explains why the read receipt you expect sometimes never turns blue.
What each WhatsApp tick means
WhatsApp shows a small icon next to every message you send. That icon moves through a fixed sequence as the message travels from your phone to WhatsApp's servers and finally to the person you are messaging. Here is the complete meaning of every state.
| Icon | Name | What it means |
|---|---|---|
| Clock / pending | Not sent | The message has not yet left your device. You are offline, on a weak network, or WhatsApp cannot reach the server. |
| One grey tick | Sent | The message reached the WhatsApp server. It has left your phone but has not yet arrived on the recipient's device. |
| Two grey ticks | Delivered | The message was delivered to the recipient's phone. Their device received it, but they may not have opened the chat. |
| Two blue ticks | Read | The recipient opened the chat and the message was displayed. In one-to-one chats this only appears when both of you have read receipts switched on. |
| Blue microphone | Played | A voice message has been played. Play receipts for voice messages cannot be turned off. |
The key mental model: grey is about delivery to a device, blue is about a human actually seeing the message. A message can sit at two grey ticks for hours if the phone is on but the chat is never opened. For a deeper walkthrough of why messages get stuck between these states, see our guide on WhatsApp message delivery troubleshooting.
Why a single grey tick stalls
A message stuck on one grey tick means it left your phone but never reached the recipient's device. Four causes explain almost every stalled single tick in India.
- Recipient is offline. Their phone is switched off, out of network, or has no data. The message queues on WhatsApp's server and delivers the moment they reconnect.
- You have been blocked. If someone blocks you, your messages stay on one grey tick indefinitely. WhatsApp deliberately never confirms a block, so a permanent single tick to one contact while others deliver normally is the strongest signal.
- Invalid or non-WhatsApp number. The number is wrong, deactivated, or does not have WhatsApp installed. This is a common cause when businesses import old contact lists.
- Network or device problem on their side. A full storage, a very old WhatsApp version, or a regional outage can delay delivery.
For businesses sending at scale, a batch of messages stuck on a single tick usually points to a data-quality problem in the contact list, not a WhatsApp fault. If your sends are stalling before delivery, our breakdown of WhatsApp status stuck on sent not delivered covers the fixes step by step.
Do read receipts work differently on WhatsApp Business App vs the API?
Yes, and the difference matters a lot for how you track engagement. The WhatsApp Business App behaves like the personal app with visible ticks, while the WhatsApp Business API reports status through webhook events instead of on-screen icons.
| Feature | Business App | Business API |
|---|---|---|
| Where you see status | Coloured ticks inside the chat | Webhook status events sent to your server |
| Read receipt visibility | Blue ticks, if recipient has them on | A read status event, if recipient has them on |
| Best for | Small teams, manual replies | Automation, bulk sends, analytics |
| Read-rate reporting | Manual, per chat | Aggregated across every message automatically |
Read receipts are a privacy setting under Settings, Privacy, and the rule works both ways: if you turn yours off, you also stop seeing other people's blue ticks in one-to-one chats. That matters for a business team on the Business App, because switching receipts off to look less pushy also blinds you to whether customers read your replies. The API does not draw ticks at all; instead it fires a stream of status updates your platform records. If you are still deciding between the two, our comparison of the WhatsApp Business App vs API lays out which fits your volume.
How do businesses track read status on the WhatsApp API?
On the API, every message you send generates a lifecycle of webhook status events, and read tracking works by listening for the read event. Instead of watching ticks, your system receives a callback each time the message changes state.
Send these messages on WhatsApp, from your own number
We get your templates approved on the official WhatsApp API and set up your first broadcast with you. ₹0 platform fee, you pay only Meta's per-message rate.
| Webhook status | Tick equivalent | Meaning |
|---|---|---|
sent | One grey tick | Accepted by WhatsApp and on its way. |
delivered | Two grey ticks | Delivered to the recipient's device. |
read | Two blue ticks | Recipient opened and viewed the message. |
played | Blue microphone | First time a voice message is played on the recipient's device. |
failed | Red error triangle | Could not be sent or delivered. The payload includes an errors array with the code, title and details. |
Each event arrives with a timestamp (when the webhook was triggered) and the message ID, so your platform can calculate how long delivery and reading took. One detail trips up many dashboards: Meta treats a message as read only after it is delivered, and if delivery and read happen at the same moment it sends only the read event, with no separate delivered event. Count every read message as delivered too, or your delivery rate will look lower than it is. A good analytics layer stores every one of these events. To wire this up correctly, follow our WhatsApp Business API webhook setup guide, which walks through the status payloads in detail.
What a failed status tells you
The failed event is the most actionable. Its error code separates a genuinely bad number from a policy or window issue, for example a message sent outside the 24-hour customer service window that needed an approved template. Reading these codes turns a vague delivery problem into a specific fix.
Why read receipts are sometimes off, and what that does to your read rate
Read receipts are a per-user privacy setting, and when a recipient turns them off, you will never see the blue ticks or receive a read webhook event from them. The message still delivers normally; you simply lose visibility into whether it was opened.
This creates a real measurement gap for Indian businesses. A meaningful share of users keep read receipts off, so your reported read rate is always a floor, not the true number. If a message shows two grey ticks forever but you know from a reply or a click that the customer engaged, read receipts were almost certainly off on their side.
- Delivered is the reliable metric. Delivery does not depend on the recipient's privacy settings, so delivery rate is the trustworthy denominator for most reporting.
- Read rate is directional. Treat it as a lower bound and watch the trend rather than the absolute figure.
- Replies and clicks fill the gap. For campaigns, response and link-click rates often measure real engagement better than the read event alone.
There is no reliable public benchmark for read rates in India, so be wary of anyone quoting one as fact. What does hold everywhere: utility messages a customer is waiting for (an OTP, a delivery update) tend to be read more than marketing messages, and because some of your audience has receipts off, the true open rate always sits above the reported read rate. Benchmark against your own history, by template and by category.
Two exceptions to the privacy setting are worth knowing. According to WhatsApp's Help Center, turning off read receipts does not disable read receipts in group chats or play receipts for voice messages; there is no way to turn those off.
How WhatsApp ticks work in groups
In a group chat, ticks follow the whole group, not any single person. Two grey ticks appear only once the message is delivered to every member's device, and two blue ticks appear only once every member has read it.
Because of that all-or-nothing rule, group ticks can lag well behind individual chats. If you tap and hold a message and open its info screen, WhatsApp shows a per-member breakdown of who received and who read it, which is far more useful than the summary ticks. Meta's Cloud API does offer a Groups feature, but it is limited to small groups (8 participants) and to Official Business Accounts, so it is not a broadcast channel; most Indian businesses use individual template sends for outreach, tracked through WhatsApp broadcast limits and messaging tiers.
How read-rate analytics actually work on the API
API read-rate analytics are built entirely from the webhook status stream, not from anything visible in a chat. Your platform counts read events against delivered events over a time window to produce a read rate, and against sent events to produce a delivery rate.
The quality of your analytics depends on capturing and storing every status event reliably, including duplicates and out-of-order arrivals, which webhooks can produce. Platforms that drop events under-report reads. A dashboard should reconcile events by message ID and keep the latest state per message. For a fuller picture of what to measure, our overview of WhatsApp API analytics and metrics dashboards covers delivery, read, and failure reporting together.
Reading the numbers honestly
Because read receipts can be off and webhooks can arrive late, a single day's read rate is noisy. The reliable practice is to track delivery rate as your health metric, read rate as a trend, and failure codes as your fix list. Read together, those three tell you whether a campaign is genuinely reaching and engaging people.
Blue ticks can now be paired with a "typing…" bubble. See our WhatsApp typing indicator API guide for how to show customers a reply is on its way.
Get accurate read and delivery tracking
Understanding ticks is the first step; capturing every status event automatically is what turns them into reliable analytics. RichAutomate records the sent, delivered, read and failed status for every campaign message, stores the Meta error code and reason on failures, and rolls them into campaign stats. Pricing is usage-based with ₹0 setup: Client Pay is Meta's rate plus ₹0.10 per message, SaaS Pay is ₹1.50 per marketing and ₹0.50 per utility message, and monthly plans (from ₹499) are optional. See pricing. Create your free RichAutomate account to start tracking real delivery and read rates on the WhatsApp Business API.