Most WhatsApp Business setup guides are written for the person who will administer the account, not for the person who has to answer the messages afterwards. That gap is where most of the trouble lives: the number is verified, the template is approved, the team is invited, and the operation still runs badly for reasons that had nothing to do with setup.
This is a checklist oriented toward the second person — the one who inherits the inbox.
Confirm what the number actually is before anything else
The most consequential field on a business profile is not the category. It is the phone number itself, and specifically whether it can receive a verification code by SMS.
Numbers that cannot — some VoIP routes, some newly ported ranges, some numbers already associated with an account that was closed rather than deleted — will complete profile setup and then fail at the first verification prompt, usually days later, when somebody tries to register a second device. Check this before anything else is configured, because every other step assumes it works.
The two limits that shape everything downstream
Template messages outside the 24-hour window. A business can only send free-form messages inside a customer-initiated window. Outside it, outbound messages must be approved templates. This is not a technicality; it is the constraint that determines whether your team is doing customer service or outbound prospecting, and the two have different workflows, different tooling, and different failure modes.
The quality rating attached to the number. Messaging quality is measured on the number, not the account, and it degrades when recipients report or block. A number that drops in quality gets its throughput reduced, which looks exactly like a platform problem and is not one. Teams that do outbound and support on the same number usually discover this during their busiest week.
Decide the inbox model before inviting anyone
There are two workable arrangements and one that causes problems:
- One shared queue, rotated by language. Works when the team is small and the languages are few. Requires a written routing rule from the start.
- One queue per agent, with a shared view. Works when reply quality varies a lot between agents, or when conversations need continuity.
The problematic arrangement is a shared inbox where nobody owns anything. Conversations become visible to everyone and assigned to no one, and the first time it visibly fails is the week somebody is on leave. For the ownership model that prevents this, see shared mailbox rules that survive a growing team.
Invite with roles, not with full access
Every messaging platform offers a role structure, and most teams skip it and give everyone administrator rights on day one. The cost shows up later, when somebody changes a setting that changes how the number is registered, or exports a conversation list for a report that nobody intended to be exportable. Set two roles before inviting anybody: one that can reply and one that can change settings. It takes five minutes and it removes an entire category of incident.
The template library is a product, not a folder
Approved templates accumulate. Most teams treat them as a flat list and rebuild phrases from scratch every time, which produces near-duplicates and eventually a library that nobody trusts because it is full of variations nobody remembers approving.
Three fields keep it usable: what it is for, which language it is in, and when it was last used successfully. A template that has not been used in six months is a candidate for review rather than a candidate for reuse, because the product or policy it referred to may have changed.
Verify before the team starts, not after
A ten-minute check on the day before go-live catches nearly everything that goes wrong later:
- Send a test message from a personal account and confirm it arrives and that the business profile name displays correctly.
- Confirm the team inbox shows the conversation within seconds rather than minutes.
- Confirm replies from the team inbox arrive at the customer's phone with correct sender identification.
- Confirm that a template sent outside the customer-initiated window is delivered, and that its variable fields render correctly.
Each of these fails differently and none of them is caught by a setup wizard.
What this does not cover
This checklist is about making the operation work after setup. It does not address the translation layer, which for cross-border teams is often where the real friction sits. For that, see chat translation quality for cross-border teams. If your issue is that the translate button is missing from WhatsApp itself rather than from your tooling, that is a different problem, covered in why the translate button disappears.
Source note: This article draws on LivePerson's customer documentation "WhatsApp Business Messaging Setup Guide" (https://community.liveperson.com/kb/articles/1570-whatsapp-business-messaging-setup-guide), which covers business account setup and messaging mechanics. The inherited-inbox framing, the role split, the template library fields, and the go-live verification list are our own operational recommendations. No vendor figures from the source are used as verified data here.