WhatsApp customer service: how to set up your company’s support

Why customer service moved to WhatsApp, and what goes wrong on a phone

Customer service went where customers are. In Brazil and much of Latin America, that means WhatsApp. Customers would rather send a message with a photo of the broken product than wait on hold listening to music, and businesses find that one person can handle several conversations at once, something a phone call never allows.

It usually starts the same way. Someone shares their own mobile number, or a company phone sits on the support desk with the WhatsApp Business app, and that gets you through the first month. The trouble comes with volume: two people answering the same customer, a conversation forgotten at the bottom of the list and nobody knowing who promised what.

Support that lives on a phone has predictable flaws. The history stays on the device and leaves with whoever leaves the company. There’s no queue, only a list in order of arrival. There’s no deadline, only the memory of whoever is answering. And the manager doesn’t know how many customers waited, for how long and how many gave up. Organizing WhatsApp customer service means fixing those four points.

WhatsApp Business app or official API

The WhatsApp Business app is fine for getting started: it has a business profile, catalog, labels, quick replies and greeting and away messages. For more than one person to answer, the WhatsApp Help Center says the main phone can link up to four devices. With a Meta Verified or Meta One subscription, the limit goes up by plan, to as many as ten, and you can name each device and assign conversations to agents.

The app’s limits show up quickly in support. The main phone is still required to register the number and link new devices, and the Help Center warns that linked devices are logged out if the main phone goes unused for more than 14 days. There’s no real queue, automatic assignment or reply deadline, and nobody measures how long the customer waited.

With the official API, the number is connected to a platform and messages come in and go out through the system, with no phone in the middle. The limit is no longer about devices: the whole team answers the same number, and the history stays on the server, tied to the customer profile, as in a WhatsApp CRM. If you don’t want to give up the app, coexistence lets you use the same number on the phone and on the API at the same time.

Official number, business hours and triage

Start with the number. Support needs a company number, not a person’s, published the same way on the website, invoices, packaging and email signatures. A single number makes life easier for customers and harder for scammers, because it’s easy to check whether a message came from the right place. Complete the profile with address, website and hours.

Then the hours. Say on the profile and in the first reply when people are available, and use WhatsApp Business automatic messages for anyone who writes outside them: say when someone will reply, ask for what can be shared in advance, such as the order number, and leave the conversation in the next shift’s queue. An away message that only says “we’re closed” wastes that chance.

Triage decides where the conversation goes. It can be a short menu with buttons, such as invoice copy, delivery and returns, or an AI agent that reads what the customer wrote, answers from the company’s knowledge base and hands off to a person when it isn’t sure or when the customer asks. The guide to the WhatsApp chatbot compares the two models.

Either way, the way out to an agent has to be in plain sight. WhatsApp’s messaging policy allows automation inside the 24-hour window as long as the business offers a prompt, clear and direct path to human support, such as a transfer to an agent in the chat, a phone number or an email.

One queue, transfers and internal deadlines

Once triaged, the conversation goes into a queue by topic, not onto the phone of whoever saw it first. Automatic assignment gives the next conversation to whoever has the lightest workload at that moment, skipping people on a break or off shift. Every conversation has an owner, and the customer doesn’t get two different answers from two people.

When a case needs another team, the transfer carries the whole conversation, with an internal note the customer doesn’t see: what has been checked, what’s missing and what was promised. Whoever picks it up doesn’t ask for the order number again. And with the history saved on the customer profile, their next conversation starts with the context of the last one.

Finally, internal deadlines. Set a maximum time for the first reply during business hours and a maximum time to resolve, by type of topic, and keep both visible in the queue, with a warning before they run out. A customer support platform for your team shows the supervisor what’s waiting, for how long and with whom, so they can reassign before the customer complains.

The 24-hour window in customer service

The Meta rule that weighs most on support is the customer service window. The Cloud API documentation says that when a customer messages or calls you, a 24-hour timer starts, and each new message from them resets it. Inside the window, the business can reply with text, photos, documents, buttons and lists, with no pre-approval. Outside it, only with an approved template. The guide to the WhatsApp 24-hour window has the details.

For support, that has two consequences. The first is to reply inside the window: a conversation left unanswered until the next day can no longer be picked up with free text. The second is to have templates ready for what runs past the deadline, such as “your case has been resolved” or “we need one more detail to continue”, knowing that Meta charges per delivered template, by category and country.

In practice, the internal first-reply deadline should be much shorter than the window. A case that depends on another team and takes days should end with the customer updated while the window is open, or with a follow-up template built into the process, not with a message that won’t go out.

What Brazil’s customer service decree requires

In Brazil, the Consumer Protection Code applies to every business that serves consumers, and the customer service decree spells out the rules for part of the market. Decree 13.135 of October 9, 2026 revokes Decree 11.034/2022 and takes effect 20 days after publication. It covers products and services regulated by the federal government, under each regulator’s criteria, and digital financial services supervised by the Central Bank.

The text treats instant messaging as an electronic customer service channel. At least one electronic channel, widely publicized, must run 24 hours a day, seven days a week, with real-time service by a human from 8 a.m. to 8 p.m., every day. Automation and AI can handle triage, routing and resolution, as long as the consumer has the option to talk to a person. Phone service remains mandatory.

A request must be resolved within five levels of service, with the options to cancel and to talk to a person, during human service hours, available at every level, including the first, and with the estimated wait time shown. It’s prohibited to send advertising at any stage, to require data before handing off to a person and to ask the customer to repeat a request already logged, except for a justified technical reason.

Every request gets a protocol number, and the system must show the agent the customer’s request history. Non-urgent requests get an answer within seven calendar days, and the suspension of an improper charge must be completed within 48 hours. Messages are kept for at least 90 days, and each request’s history for six months, sent to the customer within five business days on request. Even for businesses outside the decree, it’s a good benchmark.

Scams, personal data and privacy law

Every WhatsApp support line becomes a target for scams using the company’s name: an unknown number with the logo on its profile offers a discounted invoice, asks to confirm details or sends a payment link. The WhatsApp Help Center lists the signs: requests for personal data, passwords or money, a link to tap or an app to download, pressure to hurry and someone pretending to be who they aren’t.

The defense starts with your own service. Never ask for a password, PIN or a code received by text message, and tell customers so in plain words, on the website and in the first message. Publish a single number and show where to check it. The WhatsApp Business verified badge, which Meta grants after verifying the account, helps customers recognize the official number.

Support conversations are full of personal data, and data protection law (LGPD in Brazil, GDPR in Europe) applies to them: collect only what the case needs, limit who on the team sees what and decide how long you keep it. WhatsApp’s messaging policy goes further and prohibits asking, in the chat, for full payment card numbers, financial account numbers, ID card numbers or other sensitive identifiers. To find the customer, the order number usually does the job.

What to measure, and the step to omnichannel

Seven numbers tell the story of your support. First response time, measured in business hours. Resolution time, from first contact to closed case. First contact resolution, the share of cases that end without the customer having to come back. And satisfaction, CSAT, asked at the end of the conversation on a scale of 1 to 5.

The other three catch what the first ones hide. How much the AI agent or bot resolves on its own, read together with the handoff rate, because a bot with no way out resolves everything on paper. Reopens, the customer who comes back for the same reason within a few days, show resolutions that didn’t resolve anything. And the count of conversations waiting right now, oldest first, is the number the supervisor checks every hour.

Customers don’t stay on WhatsApp. They ask through Instagram Direct, reply to an email and then write on WhatsApp, and expect the company to know all of it. When the channels land in the same queue and on the same customer profile, with the full history, support stops being multichannel and becomes omnichannel customer service, and the metrics start measuring the customer, not the channel.

Start with WhatsApp, where the volume is, with the official number, queue, deadlines and metrics working. Then bring the other channels into the same operation, one at a time, checking that customers never have to repeat what they already said somewhere else.