Guide · Support · For the owner whose provider is not answering

Who do you call when WhatsApp breaks? Meta's Direct Support for businesses onboarded by a provider

When a business's WhatsApp was set up by a provider, the owner usually assumes the provider is the only door to Meta. That is mostly true, and Meta keeps a page for providers that says exactly where the exceptions are: which problems the business can raise with Meta directly, which ones only the provider can raise, what a billing ticket has to contain, and the handful of card errors Meta sees so often that it lists the fixes. Here is that page turned round to face the owner.

Published 2 October 2026 · Updated 8 October 2026

Two doors, and which one is yours

Meta's Direct Support: Meta's page says a business onboarded by a partner can open a Direct Support ticket itself, using the Ask a Question button, provided the business has registered as a Meta developer. That registration is a formality done once in the business's own Meta account; a business that never did it sees no ticket form and has only the provider to call.
Your provider: Everything about how the system behaves, what it sends, what it shows and why a particular message failed is the provider's to answer, because the provider built and runs the system. Meta's page is explicit about one case: if the billing topic does not appear in the business's own ticket form, the business asks its Tech Provider to open the ticket for it.
The payment method comes first: Meta's page states the rule plainly: a business onboarded by a Tech Provider must add a payment method to its own Messaging account before the provider's app can send or receive a single message. Its last line repeats the consequence: if templates will not send, the business most likely has no valid payment method on file.

Where this connects

Whose card is on file, and the difference between a provider's credit line and your own payment method, is set out in the payment guide. Whether a problem is Meta's at all is often answered first by the status page guide.

When the problem is Meta's AI agent

Meta has a separate support page for Meta Business Agent, its AI agent for business numbers. It sends a business that came through a Tech Provider to that provider, which holds the account relationship and can escalate for it. Providers open a Direct Support ticket themselves, on the right business account, because a ticket raised on the wrong one cannot be moved, and they include the identifier of the number the agent runs on, since the agent's setup, connections and conversation history are all tied to that number. Meta says it aims to reply first within 24 hours on business days, Monday to Friday in the country set on the account, excluding holidays. Our reading: when the agent misbehaves, tell your provider which number and roughly when, so the ticket can go in the same day.

A billing ticket that gets answered

Pick the right topic. Meta's page names the exact form selections for money questions: the topic called Dev: Billing, Credit & Pricing, and the request type called Credit Card Billing. Any other topic routes the ticket to a team that cannot see payments.
Find the transaction first. For a question about one charge, Meta says to open the Billing and payments panel in Meta Business Suite, find the transaction under the Messaging accounts tab or in the payment activity list, and copy the entire transaction identifier.
Put the identifier in the ticket. A ticket that says "we were charged twice last week" waits for a reply asking which charge. A ticket carrying the transaction identifier can be looked up at once. It is the one thing Meta's page asks the business to include.
If the topic is missing, hand it over. Meta's page says a business that cannot see the billing topic should ask its provider to open the ticket. Give the provider the same transaction identifier and the same one-line question, so nothing is lost in the relay.

The card errors Meta sees most

Meta's page lists the payment errors that come up often enough to deserve a standard answer. None of them is a WhatsApp problem; all of them are between the business and its bank or Meta's payment rules.

The card has not been verified: The bank's one-time code was not completed. Meta's advice: try again and make sure the code from the bank actually arrives; if it keeps failing, ask the issuing bank whether the card is blocked for this kind of charge, wait a few days, or use another card.
Already saved to the maximum number of accounts: One card can be attached to only so many Meta accounts, and Meta's page says the limit cannot be raised and has no exceptions. A business whose card already pays for several advertising accounts needs a different card for WhatsApp.
Request not completed, for security: Meta's fraud checks stopped the attempt. The page's advice is to try again later, ask the bank whether restrictions were placed on the card, or try another card.
Something went wrong: Meta's catch-all. Try again in a few days or try another card, and if neither works, open the billing ticket described above.

Two problems the page settles in passing

Switching providers while an old credit line is still attached produces an error. Meta's steps are to back up the business's messages, disconnect and reconnect the number in the WhatsApp Business app, and go through onboarding again with the new provider; the part that matters to the owner is that the old provider's credit line has to be released before the new set-up can take, which is worth asking for in writing when a provider relationship ends. And a display name that has already been reviewed can be changed by the business itself in WhatsApp Manager, under Account tools, Phone numbers, then the Profile tab; the new name goes through review again, as explained in the display name guide.

For a single message that failed rather than a card that will not save, the reason Meta gives is listed in the failure reasons guide, and that question goes to the provider first.

Questions

Who do we contact when Meta's AI agent on our WhatsApp number goes wrong?

Meta's Meta Business Agent support page says a business that came through a Tech Provider contacts that provider, which can escalate on its behalf. Meta aims to give a first reply within 24 hours on business days.

Our provider set everything up. Can we talk to Meta at all?

Yes, for some things. Meta's page says a business onboarded by a partner can open a Direct Support ticket itself once it has registered as a Meta developer. Billing is the clearest case. How the system behaves is still the provider's to answer.

Templates suddenly will not send. Who do we call?

Check the payment method before calling anyone. Meta's page says the usual cause for a provider-onboarded business is that no valid payment method is on the Messaging account. If a card is on file and valid, the provider looks at the failure reason Meta returned.

Our card works for ads but WhatsApp will not accept it. Why?

Most likely the card is already attached to the maximum number of Meta accounts. Meta's page says that limit cannot be increased and has no exceptions, so WhatsApp needs a different card.

We were charged and want it explained. What does Meta need?

The whole transaction identifier, copied from the Billing and payments panel in Meta Business Suite, inside a ticket filed under the billing topic. Without it the first reply will only ask for it.

Sources

Meta's developer documentation: Business customer support (for solution providers), read 2 October 2026.
Meta for Developers: Meta Business Agent support, read 8 October 2026.

More plain-language notes like this one are on the guides page.

Want a provider that tells you which door to knock on?

We set up a business's WhatsApp number on a proper system, put the business's own payment method on its own Messaging account from day one, register the business as a Meta developer so it can open its own tickets, and hand over the transaction identifier and the exact ticket topic whenever a charge needs explaining. A short call is the easiest way to see whether it fits your business.

Book a demo