Coexistence for agencies: connecting several clients' WhatsApp

Connecting one number is a process. Connecting ten, from ten different companies, is a process plus a structure of accountability — and it is the second part that gets forgotten until it causes trouble.

The rule that solves half the problems

The asset belongs to the client. The access belongs to the agency.

In practice:

• the Meta business portfolio is the client's
• the WhatsApp account lives in that portfolio
• the number is the client's
• the agency comes in as a partner with access

It looks like bureaucratic detail and it decides what happens at the end of the contract. With the right structure, ending it means removing an access. With the wrong one, ending it becomes a negotiation over a number printed on all the client's material and registered in your portfolio.

The same logic already applies to ad accounts, for the same reason.

What changes at ten

The process repeats, the attention does not. On the first connection everyone watches. By the seventh, someone rushes it and does not check it completed. Build a checklist and always use it — the one in common coexistence mistakes works.

Each client needs an internal owner. With ten numbers, "the agency handles it" is not an answer. There has to be a name per account for when quality drops or a message goes out wrong.

Sending limits are per number. A high-volume client does not lend limit to another. Planning sends without checking each number's limit produces messages that do not go out on campaign day.

Quality is per number and the blame is yours. If the agency ran the send, the drop is the agency's responsibility regardless of who asked. Which is the reason for the next section.

The three mistakes that create legal exposure

1. Number in the wrong portfolio. Covered above, and the most expensive. Fixing it later requires cooperation from the party you are leaving.

2. Sending what the client asked without checking. The client sends a list and asks for a blast. The list is old, people do not remember them, quality collapses. The number is the client's, but you pressed the button.

The protection is simple and has to be written down: the agency does not send to lists not collected with consent, and that holds even when the client insists. The piece on WhatsApp number quality explains what a cold list does to a number.

3. Automated messages with no recorded approval. Automation answering wrongly in the client's name is the client's problem with their consumer — and becomes your problem in the next meeting. Get the text approved in writing before switching it on.

A structure that works

Client A portfolio
  └ WhatsApp account A
      └ Number A          ← advertised by the client
  └ Ad account A
  └ Page A
  Agency: partner access

Client B portfolio
  └ ... same structure

Agency portfolio
  └ app / tech provider
  └ no client assets

The agency portfolio holds the tooling, not the assets. That separation is what lets you grow without accumulating responsibility for things that are not yours.

What to automate first across a portfolio

With several clients, the temptation is to build different automation for each. Resist.

Start with what is identical everywhere. Receipt confirmations, status alerts, internal reports. What repeats across clients is what scales.

Leave the bespoke for later. Custom flows per client multiply maintenance by ten, and automation maintenance is a cost nobody puts in the proposal.

Reporting on WhatsApp across a portfolio

With ten clients, the daily exception report stops being a convenience and becomes the operation: you only hear about what left the band, instead of opening ten dashboards every morning.

Two rules keep it useful:

One channel per client, not one general channel. Alerts from ten accounts mixed together become noise within a week.

Thresholds per account. If one client generates five alerts a day, the problem is a wrong threshold, not a worse client.

The format is in campaign reports on WhatsApp.

Where to start with a portfolio

1. One pilot client. Preferably one with an organized WhatsApp and a good relationship — if something breaks, you want someone patient.
2. Portfolio structure before connecting. Fixing it later costs more.
3. What gets sent, in writing. One page, signed, before the first send.
4. Only then the second client. And from there, in series.

For the comparison against taking the number out of the app, which changes the design of the whole operation, see coexistence or migration.