Why we don't do read receipts (and probably never will).

Every month, someone asks us when we're adding read receipts to Tawasel. The request makes sense on the surface. You want to know if your customer saw your message. You want your manager to see that the team is responding. You want accountability in the inbox.

We've thought about this carefully. We're not going to do it — at least not in the way most people expect. Here's the reasoning.

The problem with read receipts in business messaging

In personal WhatsApp, read receipts are a social signal between two people who have an ongoing relationship. The blue ticks create a small, shared understanding: I saw your message. We've both acknowledged that I saw it.

In business WhatsApp, the dynamic is completely different. Your customer isn't messaging a friend. They're messaging a company. And the moment they know a company can see exactly when they read something, the power dynamic shifts in a way that creates friction rather than trust.

"The seen-zone is not a bug in WhatsApp — it's a very human response to feeling watched by an institution."

We've spoken to teams across UAE and the Gulf — clinics in Abu Dhabi, retailers in Dubai, real-estate offices in Sharjah — and the pattern is consistent. When customers know their messages are being tracked for read status, two things happen:

• Customers who haven't replied yet feel pressure they didn't ask for. They avoid opening messages they're not ready to respond to.
• Teams start gaming the metric. Agents mark things as read to show responsiveness in dashboards, even when the conversation hasn't actually been handled.

Neither outcome serves the customer. And serving the customer is the only thing that keeps your number from getting ignored.

What we track instead

We care about response time, not read time. The distinction matters.

Response time tells you something actionable: how long does it take your team to actually reply to a customer? That number drives satisfaction, conversion, and retention. It's a metric your team can actually improve.

Read time tells you something passive: when did the customer open the message you sent? You can't change that number. You can't act on it. You can only feel anxious about it.

In Tawasel, every conversation shows:

• First response time — how long from the customer's first message until your team replied
• Resolution time — how long the full conversation took from open to closed
• Unread conversation count — how many conversations are waiting for a reply, not how many the customer has "seen"
• Agent assignment and handoff time — when conversations were assigned, and whether they sat unassigned for too long

The Gulf context matters here

There's also a cultural dimension that's easy to miss if you're importing product assumptions from Western SaaS.

In the Gulf, business relationships — especially with SMEs — are built on a degree of patience and flexibility that doesn't exist in the same way in European or North American markets. A customer who hasn't replied for two days isn't necessarily disengaged. They might be busy with Ramadan obligations. They might be evaluating with someone senior. They might be waiting for a quote you haven't sent yet.

Chasing that customer with "we can see you read this" energy — even implicitly, through automated follow-ups triggered by read status — damages the relationship in ways that take months to repair.

The teams we've watched succeed on WhatsApp in the UAE share a common quality: they're responsive without being intrusive. They reply fast when customers reach out, and they give customers space when customers go quiet. Read receipts create pressure that makes that balance harder to maintain.

What about internal accountability?

This is the real ask behind most read receipt requests. Managers want to know their agents are actually reading conversations, not ignoring them.

We understand that. But read receipts are a proxy for the actual problem, which is: how do you know conversations aren't falling through the cracks?

The answer isn't read tracking. It's inbox structure. In Tawasel:

• Every unassigned conversation is visible in a shared queue — nothing is hidden in anyone's personal phone
• Conversations older than a threshold you set surface automatically as overdue
• Managers can see every agent's open conversations, response times, and resolution rates in one dashboard
• Internal notes let agents flag conversations for a colleague without the customer seeing anything

These tools give managers real accountability without putting customers in a panopticon. The difference is: the accountability is between the manager and the agent, not between the business and the customer.

The honest trade-off

We're not pretending read receipts have no value. If you're running a very high-volume outbound campaign — thousands of messages, fully templated — knowing delivery and read rates in aggregate can help you optimise message timing. WhatsApp's own API does expose message status at the aggregate level for templates, and we surface that.

What we don't do is show an agent that a specific customer read their specific message at 11:43pm and didn't reply. That information creates more problems than it solves.

If that's a dealbreaker for your team, Tawasel might not be the right fit. We'd rather be honest about that than ship a feature we think makes business messaging worse.

The principle underneath the decision

Most features in messaging products are built for the sender. Read receipts are for the sender — they relieve the sender's anxiety about whether their message landed.

We try to build for the relationship. A relationship where the customer feels comfortable messaging you, knows you'll respond, and doesn't feel tracked is worth more than knowing they read your message at 11pm.

That's the product philosophy. Some people disagree with it. That's fine. It's what we believe — and it's why we probably won't add read receipts in the way you're expecting.