Setting up WhatsApp for a practice: ownership, access and what it costs

Most guides to this treat it as a configuration exercise: get a number, connect an API, write some templates. The configuration is the easy part and takes an afternoon. The decisions that cause trouble two years later are about ownership, access and money, and they are all easier to make now than to unpick later.

This is the setup as a practice decision. Who the account belongs to, who can see what, what happens on somebody's last day, how Meta's rules and pricing actually work, and what to change before 1 October 2026.

What we'll cover

• Decide who owns it before anything else
• The number, and the one-way door
• Access, and the last-day problem
• Templates and what Meta will approve
• Building it with CodeWords
• The 24-hour window and what it governs
• How the money works, including October 2026
• Quality rating and sending limits
• Telling clients, and the first fortnight
• Making it survive
• Limits worth knowing about
• What to set up first
• Frequently asked questions

Decide who owns it before anything else

The account structure sits under a Meta business portfolio, and the portfolio is the thing with real consequences. It holds the WhatsApp accounts, the numbers, the billing and the permissions, and volume-based pricing is aggregated across everything inside it.

Two rules save a great deal of pain.

The portfolio belongs to the practice. Not to a partner's personal Facebook account, not to a former marketing contractor, not to whoever happened to set it up. Recovering an account from somebody who has left is possible and it is nobody's idea of a good week.

More than one person has administrative access. A single administrator is a single point of failure, and it fails at precisely the moment you need it.

Write down who holds which role and review it when people join or leave, in the same place you review everything else with a login attached.

The number, and the one-way door

The number is a decision you make once.

It has to be a number you control and can receive a verification code on, and it cannot be in active use on the consumer WhatsApp app. Registering it on the platform means removing it there first, and the history on the consumer account does not come across. A landline works, since verification can arrive by voice call.

Reusing a partner's personal number, already saved in hundreds of clients' phones, looks like a shortcut and is the variant to avoid: it pulls personal history into a practice asset and makes the eventual separation worse. Take a fresh number, and keep the old one answering for a while.

Access, and the last-day problem

The main operational reason to be on a business platform rather than the consumer app is that several people can work the same number and the practice can see the history.

That only holds if access is administered: granted per person, removed on departure, reviewed periodically. When somebody leaves, their access goes and the conversations stay with the practice, which is exactly what does not happen with personal numbers.

Decide at the same time who covers a colleague's conversations during leave, and who owns the shared inbox when nobody is specifically assigned. Unowned inboxes fill up quietly.

Templates and what Meta will approve

Any message you send to somebody who has not messaged you recently has to use a template that Meta has approved in advance. Templates carry variables for the personal details and are categorised as utility, marketing or authentication, and the category affects both approval and cost.

For a practice, the useful ones are utility: a document request, a deadline notice, a status update, an appointment confirmation. These relate to a transaction or service the client has with you, which is what the utility category covers.

Anything promoting an additional service is marketing, and it is treated differently by Meta and by the marketing rules generally. Do not disguise one as the other. Miscategorisation gets corrected by Meta, and persistent miscategorisation affects standing.

Submit templates early, since approval takes time and is occasionally refused for reasons that need a rewrite. Write them so a client who has not thought about you for six months can tell who is messaging and why within the first line.

Building it with CodeWords

CodeWords connects to more than 3,000 integrations, and the connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: which clients get which message, what triggers each one, what stops it, and what has to reach a person.
3. Authorize the connections to your practice management or ledger system and your WhatsApp Business Platform account.
4. Describe the exceptions: a client who has replied, one who has asked not to be messaged, anything that reads like a complaint or a request for advice, anything about fees.
5. Run it on a small group of cooperative clients for a fortnight before extending it, and watch the quality rating while you do.

You describe the outcome; Cody builds it, connects it, and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows; details are on the pricing page.

The 24-hour window and what it governs

When a client messages you, a 24-hour window opens during which you can reply freely, without a template. Outside it, contact has to be by approved template.

This shapes how a practice plans its sending. Reactive support is straightforward, because the client started it. Proactive contact, which is most of what a practice wants to automate, is template territory and needs planning.

It also means the state of the window is a real variable. A reply drafted at 9am to a message received at 8am yesterday will not send in the form you wrote it, and an automation that does not check will either fail or quietly send something else.

How the money works, including October 2026

Pricing has been per message since conversation-based pricing was retired on 1 July 2025. Utility, marketing, authentication and service messages are priced by category and by market, and volume tiers are aggregated across every WhatsApp account in the business portfolio (Meta pricing documentation).

The change to plan for is dated. From 1 October 2026, service messages become chargeable at the same rates as utility and authentication by market, with a free tier of 1,000 delivered service messages per business phone number per month. Utility messages sent in reply within the 24-hour window, which have been free since July 2025, also become chargeable (upcoming pricing updates).

For a small practice the absolute sums are modest. The reason to know it is that a design which assumed free in-window replies now has a running cost, and conversational back-and-forth that felt free will appear on a bill. Meta changes pricing only at the start of a quarter, so the sensible habit is a quarterly check rather than an annual one.

Quality rating and sending limits

Meta scores each number on how recipients respond to it, and blocks and reports move that score. A falling rating restricts how many people you can message, and the restriction arrives when you are mid-season and least able to absorb it.

Practices usually sit comfortably here, because clients expect to hear from their accountant and a document request is wanted rather than intrusive. The ways firms lose it are avoidable: messaging people who never opted in, sending too much too fast from a new number, ignoring anyone who asks you to stop, and promoting services to clients who only wanted their accounts done.

Sending limits step up as you demonstrate quality and volume, so starting small is both the enforced path and the sensible one. Limits apply across the portfolio rather than to one number, which matters if the practice runs more than one.

Telling clients, and the first fortnight

Tell them before the first automated message arrives, from a channel they already recognise.

Say what the number is, what it will be used for, what it will not be used for, and how to opt out. Ask them to save it, because a message from an unsaved number reads as spam regardless of its content.

Then start with a small group. A fortnight with twenty willing clients surfaces everything that is wrong with the wording, the timing and the exceptions, and does it at a scale where you can simply ring anybody who is confused. Rolling out to the whole book on day one removes that option.

Making it survive

Keep the portfolio in the practice's name with at least two administrators.

Review access when anybody joins or leaves, alongside every other system.

Check the quality rating regularly, and treat a drop as something to investigate that week.

Re-read the pricing page quarterly, since changes land on quarter boundaries.

Honour opt-outs immediately and permanently, across every automation rather than the one that sent the message.

Limits worth knowing about

No group messaging. Every message on the platform goes to one recipient.

Unofficial tools violate the terms and put the number at risk of being cut off, which during January would be a serious problem.

Templates constrain proactive contact. Anything you might need to send has to have been approved before you need it.

Rules and pricing change. Two significant changes have landed since mid-2025, so treat any setup as something to review rather than finish.

The platform cannot fix the message. A badly worded request sent reliably is still a badly worded request.

What to set up first

The portfolio, in the practice's name, with two administrators and a fresh number. Before any template, any automation and any client contact. It is half an hour of work and it is the part that is expensive to change afterwards.

Two habits make the difference. Administer access the way you administer every other system, since the whole argument for being on a business platform is that the conversations belong to the practice rather than to a phone. And check the pricing and rules each quarter, because this is a platform that has changed its charging model twice inside eighteen months and will do it again.

Frequently asked questions

Who should own the WhatsApp Business account?

The practice, through a business portfolio held in its name with at least two administrators. Accounts created under a personal profile become difficult to recover when that person leaves.

Can we use a number that is already on WhatsApp?

It has to be removed from the consumer app first, and the history there does not transfer. Using a partner's existing personal number is possible and inadvisable, because it merges personal history into a practice asset.

What is the 24-hour window?

When a client messages you, a 24-hour window opens in which you can reply freely. Outside it, contact must use a template Meta has approved in advance.

What templates does a practice need?

Utility templates covering document requests, deadline notices, status updates and confirmations. Anything promoting an additional service is marketing and is treated differently, so do not categorise it as utility.

What is changing on 1 October 2026?

Service messages become chargeable at utility and authentication rates by market, with a free tier of 1,000 delivered service messages per business number per month, and utility messages sent within the 24-hour window stop being free.

What is the quality rating?

A score based on how recipients react to your messages. Blocks and reports lower it, and a low rating restricts how many people you can message. Limits apply across the portfolio rather than per number.

What happens when a member of staff leaves?

On a practice-owned account their access is revoked and the conversations remain. On a personal number the relationship and the history leave with them, which is the main reason to be on the platform at all.

How should we roll it out to clients?

Tell them first through a channel they recognise, say what it will and will not be used for, ask them to save the number, then start with twenty willing clients for a fortnight before extending it.

Related reading

• Which channel is the client file
• Making a document request land
• Tax season as a queueing problem