Common Meta access errors | Chatfuel for Agencies

Access is granted, the client’s company exists, you clicked Add number — and Meta said no. Connection-stage errors all feel the same in the moment (a client on the call, a QR code that won’t cooperate), but each has a specific cause and a known exit. Find your symptom below. If the problem is earlier — partner requests vanishing, assets not visible, nobody knowing who the admin is — that family lives in Troubleshooting access issues.

One thing to internalize before the fixes: most of these are resolved on the client’s side of Meta, not in Chatfuel. Your job is rarely to click the fix yourself — it’s to know exactly what to tell the client to click, which is what turns a two-day stall into a five-minute detour.

Roadblocks lifting one by one — every connection error has a known fix

You’re in the connection flow, the portfolio picker opens — and the client’s business isn’t in the list.

Cause: the Facebook account you’re logged in with doesn’t have Full control of the client’s business portfolio. Partner access that’s fine for running ads doesn’t clear this bar.

Fix: check who has Full control at business.facebook.com/settings/people. Either the client adds one person from your team with Full control, or you run the connection as a screen-share where the client logs in and clicks. Both routes are laid out in Partner access to the client’s portfolio. Whose move: client.

”Number is not associated with the selected business”

You entered the client’s number and Meta claims it belongs to some other business.

Cause: the number is already registered inside a different business portfolio — often an old agency’s, a freelancer’s, or a portfolio the client forgot exists.

Fix: open Phone numbers in WhatsApp Manager and check each portfolio in the left sidebar until you find where the number lives. Then either select that portfolio in the connection flow, or unlink the number from it and connect it to the current one. Whose move: client (it’s their portfolios you’re searching).

The QR code won’t scan (“Couldn’t scan code”)

You’re connecting an existing WhatsApp Business App number and the scan fails, again and again.

Cause: almost always unpaid Meta bills on the client’s account.

Fix: wait a few minutes and retry once. If it persists: open the Billing hub in Meta Business Suite, look for “Payment failed” notices next to the Ad and WhatsApp Business accounts, pay what’s outstanding, wait ~10 minutes, scan again. Whose move: client — it’s their card.

”Your account is using marketing messages”

Meta blocks the connection because the number has marketing messages set up in the WhatsApp Business app.

Fix: on the client’s phone, in the WhatsApp Business app: Tools → Marketing messages, delete everything listed there, then run the connection again. Whose move: client, with you on the call telling them where to tap.

The Facebook account is restricted

The person doing the connection can’t proceed because their personal Facebook account is restricted — a check at Ads Manager confirms it.

Fix, two options:

Appeal with Meta Support at Business Support Home and wait it out.
Route around it: another person with admin permissions on the business account runs the connection from their own Facebook account.

Never log in with someone else's credentials

The workaround is a colleague connecting from their own account — not you logging in as them. Meta’s systems flag shared logins, and the restriction spreads to the borrowed account. That’s how one restricted account becomes two.

Whose move: whoever owns the restricted account; the routing-around is on your side.

Meta rejects the setup itself: category or display name

Two quieter blockers that surface as failed or restricted connections:

Restricted business category — some business and WABA categories can’t use the WhatsApp Business platform at all. Check the client’s category against Meta’s restricted list before the kickoff call; this one has no workaround, only surprises.
Display name violations — the name customers see must be the client’s real business name: no stuffed keywords, no decorative punctuation, no “WhatsApp” or “Meta” in it. A rejected display name stalls the number until it’s changed and re-reviewed.

Whose move: yours — both are checks you run during onboarding, not fixes you apply after.

Still stuck?

If the symptom doesn’t match anything above, work the sequence support uses: confirm the client’s business verification status, then category, then display name, then billing — screenshotting each step. And if the connection succeeded but verification is what’s failing, that has its own troubleshooting table.