WhatsApp customer service: how a team runs it

WhatsApp customer service is customer support delivered on a WhatsApp Business number, where customers write to the business and a team answers from that number. A team of two or three can run it on the free WhatsApp Business app. A team that needs assignment, a record of who replied, or more than four linked devices runs it on the WhatsApp Business Platform through a shared inbox. The rest is a reply time the team can keep, approved templates for messages outside the 24-hour window, and a few measures that show whether the channel is working.

What customer service on WhatsApp involves

Customers treat WhatsApp as a conversation rather than a ticket, so they write short messages, send photos and expect an answer within hours. A support team therefore needs three things it may not need on email. It needs a way for several people to answer one number and a rule about who owns each conversation. It also needs a plan for what happens 24 hours after the customer's last message. WhatsApp's own rules shape the last of those, because a business may send free-form messages only within 24 hours of the customer's last message. Outside that window the business can send only a message template that Meta has approved in advance.

The channel also has an identity layer that email does not. A business shows a display name that Meta reviews, and on the Business Platform the number is registered to a Meta business account. Customers see the name and the profile, and they read the number as the company rather than as a person. That identity is worth protecting with a policy on what the team sends, since marketing messages on a support number lead to blocks and a lower quality rating.

WhatsApp Business app vs the WhatsApp Business Platform

The WhatsApp Business app is the free app on a phone, with a business profile, quick replies, labels, and greeting and away messages. It can be opened on the phone and up to four linked devices, and every reply goes out as the business with no record of who typed it. The WhatsApp Business Platform, also called the API, runs the number on Meta's Cloud API through a provider or an inbox tool. Any number of teammates can then answer, and each conversation can carry an owner and notes. The platform charges Meta's per-message fees for templates, plus whatever the provider or inbox charges.

The four routes for sharing one number, including a shared handset and connecting the Cloud API directly, are compared in how to use WhatsApp Business with multiple users. This guide assumes the team has chosen one of them and concentrates on running the service from day to day.

Who answers the number and how conversations are assigned

On the app, whoever sees the message first answers it, and the team relies on memory to avoid two people replying to the same customer. That works at low volume and fails on the first busy afternoon, when two teammates send different answers to one question. On the platform, an inbox gives each conversation an owner, and the rule for choosing the owner is the first decision to make. A round-robin rotation suits a support queue where any teammate can answer, while named ownership suits accounts where one person knows the history.

Handoffs need a written step so the customer does not repeat the story. The teammate handing over leaves an internal note with the state of the conversation, reassigns it, and tells the customer who will reply next. A team across shifts does this at the shift change for every open conversation, and a team across time zones does it at the end of each person's day. WhatsApp shared inbox for client teams covers the version of this for teams that answer named clients rather than a queue.

Templates and the 24-hour customer service window

WhatsApp opens a 24-hour customer service window each time the customer sends a message, and within it the business can send any text, photo, document or voice note. Once the window has closed, the business can send only a template that Meta approved in advance, with placeholders for the customer's name and the details that change. A support team therefore keeps a small set of utility templates. Typical ones are an update on an open request, a request for information the customer still owes, and a note that the matter is resolved. Each takes time to approve, so the set is written before it is needed.

The window also decides how the team reads silence. A customer who asked a question on Monday morning and heard nothing is still inside the window on Monday evening and outside it by Tuesday afternoon. An inbox that shows the window on each conversation, as WhatsApp in Sektra does, lets the person replying see whether a free-form message is still allowed. The approval process and the categories of template are described in templates and the 24-hour window.

Response time expectations on WhatsApp

Customers who message on WhatsApp expect a faster reply than they would from email, because the channel is the one they use with friends and family. A workable policy is a first reply within two working hours and a full answer the same day, the WhatsApp line in email response time benchmarks and policy. The first reply can be a one-line acknowledgment that names when the answer will follow, and it counts for the measure. Outside working hours an away message states when the team returns, and the inbox's working hours stop the service level clock until then.

The policy is only as good as the staffing behind it. A number answered by one person will miss two hours whenever that person is in a meeting, so the rota needs a second person who can see the queue. The inbox's unassigned view shows what has no owner, and a service level warning tells the owner before the target is missed rather than after.

How to measure WhatsApp customer service

Four measures cover the channel for a small team. First response time is the interval from the customer's message to the first reply from the team, reported as a median and a 90th percentile. Reply coverage is the share of new conversations that received any reply, which catches the ones that fell through. Resolution time runs from the first message to the close, and a satisfaction rating asked after the close shows how the answer landed. Each of these is defined in customer service KPIs, with the formula and how to collect it.

On the app none of these can be measured without exporting conversations by hand, because the app keeps no record of who replied or when a conversation was resolved. On the platform the inbox records each event, so the figures can be read per teammate and per inbox. A team moving from the app to the platform often finds that its real first response time is slower than it believed, since the misses were invisible before.

What WhatsApp customer service costs

Meta charges for template messages that are delivered, priced by category and by the customer's country, and it charges nothing for free-form replies inside the 24-hour window. In the United States a utility template costs $0.0034 and a marketing template $0.0250, and the rates in other markets are listed in WhatsApp Business API pricing. That post works through a month for a five-person team that answers 400 conversations inside the window and sends 250 templates, which comes to $5.36 paid to Meta. The provider's platform fee and the inbox's seat price are therefore the larger lines for a service team.

The app itself is free, which is why it is the right start for a very small team. The platform's cost is the inbox or provider subscription, which runs per seat or per workspace depending on the vendor. A team comparing inbox tools should put the Meta line aside and compare the seat prices, the channels included, and whether assistant features are in the price or metered.

Where a shared inbox fits

A shared inbox is the piece that turns a WhatsApp number into a service the whole team can run. It connects the number through the Business Platform, gives each conversation an owner and notes, shows the 24-hour window, holds the approved templates, and reports response times. Sektra does this for a WhatsApp Business number beside the team's Gmail, Outlook and IMAP mailboxes and its website chat. A customer who emails on Monday and messages on Wednesday is then one record. The assistant drafts replies that a person sends, rules route and tag conversations as they arrive, and service levels count in the inbox's working hours. Other inbox tools cover the channel as well, and the right one depends on the mailboxes the team already uses.

How to set up WhatsApp customer support for a team

• Decide the route. Two to four people in one place can use the app with linked devices, and a team that needs owners, notes or handoffs connects the number to a shared inbox through the Business Platform.
• Write the policy. State the first response target, the working hours, who covers the number on each shift, and what the away message says outside hours.
• Prepare the templates. Draft the three or four utility templates the team will need outside the window and submit them for approval before the number goes live.
• Set the assignment rule. Choose round-robin for a queue or named ownership for accounts, and write down the handoff step for shift changes.
• Measure from the first week. Read first response time, reply coverage and resolution time every week, and compare them with the policy.

The channel rewards a plain start more than an elaborate one. A number answered within the promised time, with an owner on each conversation and templates ready for the day after, covers most of what customers expect from it. The rest, such as surveys and rules, can be added once the volume justifies the setup time.