WhatsApp Customer Support

WhatsApp is not just another chat channel

In India, the UAE and much of Latin America and Southeast Asia, WhatsApp is where customers would rather contact you than anywhere else. Treating it as a secondary channel bolted onto a chat widget misses both the opportunity and the rules.

Because it is a messaging platform rather than a website widget, WhatsApp brings constraints no other support channel has: who may start a conversation, what may be sent outside a defined window, what has to be pre-approved, and what counts as consent. Getting those wrong risks your business account rather than just annoying a customer.

RHI provides dedicated agents handling WhatsApp support within those rules, integrated with the rest of your contact operation.

The rules that shape everything

Three platform mechanics drive the design of a WhatsApp support operation.

The customer service window. Once a customer messages you, there is a limited window during which your team can reply freely with any message. Outside it, you cannot simply send free-form text - you need a pre-approved template. In practice this makes response speed a structural requirement rather than a nicety: let the window lapse and re-engaging becomes harder and more restricted.

Template messages. Business-initiated messages, and replies outside the window, use templates submitted for approval in advance. Approval takes time and can be refused, so the template library is designed during implementation rather than assembled in a hurry after go-live.

Opt-in. Business-initiated messaging requires the customer to have opted in through a route you can evidence. We work to your instructions on how opt-in is captured and recorded, and we will flag it where what is described does not look evidenceable.

What the team handles

• Inbound support conversations - order status, account and billing queries, faults, general questions.
• Order and delivery updates - where the customer has opted in, via approved templates.
• Appointment reminders and confirmations - well suited to the channel, and effective at reducing no-shows.
• Document exchange - customers routinely send photographs of a fault, a receipt or a meter reading, which resolves cases faster than describing them.
• Voice note handling - common in several markets and often preferred to typing.
• Escalation to phone - where a conversation has outgrown messaging.

How WhatsApp support actually differs in practice

Four behavioural differences change how the team is trained and rostered.

Expectation of speed. WhatsApp is a personal messaging app, so customers expect the response rhythm they get from people, not from a support desk. A reply in an hour reads as slow even where an email reply in an hour would read as fast.

Conversations do not close. There is no natural end. A thread from three weeks ago gets a new message on top rather than becoming a new ticket, so agents must pick up context that may be weeks old.

Message length and register. Long formal paragraphs read wrongly here. Short, clear messages in sequence work better, and getting that tone right without becoming curt is a trained skill.

Voice notes and mixed scripts. Customers send voice notes, and they type in mixed languages and scripts. Hindi typed in Roman script with English mixed in is normal, and agents reply in whichever script the customer chose - see Hindi customer support.

Media, and what not to ask for

Photographs and documents resolve cases quickly, which creates a data protection trap. A customer will happily send an image of a full bank statement to prove one transaction.

Agents are trained to ask for the minimum needed and to say what to obscure. Retention of received media follows the same rules as the case record rather than sitting outside it, and payment details are never requested on the channel. See security and data protection.

Joined to your other channels

WhatsApp is most valuable when it is not a silo. A customer who messages on WhatsApp then rings should not have to re-explain, which means the conversation history sits with the customer record rather than in a separate inbox - see omnichannel support.

Click-to-chat entry points from your website and email put the channel where customers already are. Agents work in your platform wherever possible - see technology.

Coverage, quality and reporting

Because expectation of speed is high and messages arrive at all hours, WhatsApp benefits from extended coverage more than most channels. Coverage is built from shift units - eight hours is one, twelve is two, weekends need enhanced staffing, round-the-clock is three daily teams plus a holiday plan.

Reporting covers first response time, average response time within a conversation, resolution rate, conversations handled per agent, template usage and delivery, and opt-out rate. First response time carries more weight here than on other written channels because of the service window. Conversations are sampled and scored against an agreed scorecard - see quality assurance. Figures published elsewhere on this site are historical or representative and campaign-dependent.

Getting started, and what it costs

Implementation includes designing the template library and getting it approved, which is the step most likely to hold up a go-live date, so it starts early. See the implementation process.

Priced per dedicated agent per month with a five-agent minimum, in the same band as chat - published rates and what moves them. Note that platform messaging charges are usually separate and billed on usage; we itemise rather than absorb them into a headline rate.

Bring your current WhatsApp volume if you have any, or the proportion of customers in markets where WhatsApp dominates. Related: live chat support, social media support. Talk to us.