WhatsApp Business support from Meta: how to open a ticket and how long it takes to reply

Updated on October 28, 2026

Meta’s support for the WhatsApp Business API (WhatsApp Business Platform) runs through Direct Support tickets at business.facebook.com/direct-support, which is aimed mainly at enterprise developers and partners. Meta says it does its best to send a first reply within 24 hours on business days, but it offers no SLA. If you use the API through a provider, Meta’s own guidance is to contact that provider first.

This guide covers which channel to use for each problem, how to open a ticket, what to attach so you don’t lose days going back and forth, and the response times Meta actually publishes.

How long does WhatsApp Business support take to reply?

Short answer: Meta’s published target for the first reply to a Direct Support ticket is 24 hours on business days, on a best-effort basis. There is no published time to resolution, and no commercial SLA.

Situation	Published time	Source
First reply to a Direct Support ticket	Meta does “our best” to reply within 24 hours on business days	WhatsApp Business Platform support
Review of a policy violation on a WhatsApp account	Decision typically takes 24 to 48 hours	Policy enforcement
Review of a restricted ad account, Page or business account	Typically completed in 48 hours, sometimes longer	Ads review policy
Uptime or latency SLA for the API	Meta says it does not offer commercially available SLAs	WhatsApp Business Platform support

Three things to keep in mind:

• Business days are your country’s. Meta defines business days as Monday to Friday in the customer’s country set in the Business Account, excluding holidays. A ticket opened on a Friday evening may get its first reply on Monday.
• A first reply is not a fix. The 24-hour target covers the first response. Resolution depends on the issue and on how complete your information is.
• Nobody can promise a resolution date for Meta. Any “Meta fixes it in X days” claim does not come from an official source.

Which support channel to use

The WhatsApp Business Platform support page lists the official channels. Each one has a job:

Channel	Who it’s for	What for
Direct Support	Enterprise developers, such as partners and managed partners	API tickets: send failures, number registration, billing, feature requests
Meta developer support	All platform developers	General entry point for developer support
Developer Community Forum	All developers	Implementation questions answered by the community
Bug reports	All developers	API behavior that contradicts the documentation
Status page	Anyone	Check for a platform-wide incident before opening a ticket
Business Support Home	Business portfolio admins	See policy violations and request a review
Your provider’s support	Customers of partners or providers	First stop when you don’t integrate directly with Meta

One point that confuses people: on the same page, Meta says end clients of a Solution Partner or managed partner should contact that partner directly for support. That does not lock every client out. The support page for partners’ business customers says that clients onboarded by a partner who have registered as a Meta developer can open a Direct Support ticket with the Ask a Question button.

If the difference between partners, providers and direct integration is still fuzzy, see what a WhatsApp BSP and Tech Provider are and buying the API directly from Meta or through a provider.

Want to try it while you read? Create a Vectalk account and send your first message through the official API. Create free account →

How to open a Direct Support ticket

The process Meta describes on its Direct Support page is short:

1. Go to business.facebook.com/direct-support with a user who manages the business portfolio.
2. If you have more than one portfolio, select the right one. Meta calls this out explicitly; a ticket opened under the wrong portfolio cannot see the affected account.
3. Click Ask a Question and choose the question type that matches your issue. For billing, for example, the topic is Dev: Billing, Credit & Pricing with the request type Credit Card Billing.
4. Describe the problem using the details in the next section and submit.
5. Follow the replies in Direct Support.

If you don’t see the billing topic, Meta says to ask your Tech Provider or Tech Partner to open the ticket for you.

Severity: how Meta prioritizes your ticket

You don’t pick severity in a free field: Meta derives it from the issue type you select and the information you provide. That is why describing the impact accurately matters.

Level	Meta’s definition
1 – Critical	The API does not work at all: you cannot send messages or register phone numbers, and there is no workaround
2 – Urgent	Most message sends fail and there is no procedural workaround
3 – Standard	Minor or intermittent failures, or issues that don’t fit the levels above

When a Critical or Urgent ticket is resolved but requests are still outstanding, its status changes to Mitigated.

What to prepare before you open a ticket

Meta does not publish a mandatory field list, but its error codes page says the fbtrace_id returned with each error is a trace ID you can include when contacting Direct Support. With that and your account IDs, the agent can find the request without asking you for more.

Checklist:

• Business portfolio ID and Messaging account ID (formerly the WABA ID).
• phone_number_id and the number in international format.
• The full error exactly as the API returned it, including code and fbtrace_id.
• Date and time of the failures, with time zone.
• Message IDs (wamid) for failed examples, when available.
• Since when it has been happening and what share of sends is affected.
• What changed around the time the problem started: a new template, a new token, a migration, a provider switch.
• For billing: the full transaction ID from the Billing & payments panel in Meta Business Suite.

The error object worth pasting into the ticket looks like this, according to the documentation:

{
  "error": {
    "message": "(#<CODE>) <TITLE>",
    "type": "<TYPE>",
    "code": <CODE>,
    "error_data": {
      "messaging_product": "whatsapp",
      "details": "<DESCRIPTION>"
    },
    "fbtrace_id": "<TRACE_ID>"
  }
}

The details field usually points to the likely cause and sometimes to the fix. Read it before opening a ticket. If you’re not sure what a code means, start with WhatsApp API error codes: many problems are solved without a ticket.

Before you open a ticket: five checks

Many tickets can be avoided with quick checks:

1. Status page. If there is a platform-wide incident on Meta Status, a ticket won’t speed anything up.
2. Payment method. According to Meta, if you can’t send template messages, you most likely haven’t added a valid payment method to the Messaging account. With Vectalk there is no card at Meta: messages are deducted from your prepaid balance, so check your balance in the dashboard.
3. Disabled account. A WhatsApp account can be disabled automatically after policy violations. The account_update webhook reports changes like this; the review process is covered in restricted or disabled Business Manager.
4. Right number. Make sure the number registered on the Cloud API is the one you are using. Registration and PIN issues are covered in how to register a number on the Cloud API.
5. Account structure changes. Since September 23, 2026, the WABA has been split into a WhatsApp account (the number) and a Messaging account (templates, billing, webhooks). If something stopped working after that date, see WhatsApp account vs Messaging account.

Feature requests and bug reports

Not every ticket is an incident. To request a new feature, Meta accepts either a Direct Support ticket or a platform bug report, and asks for a clear description, the intended use, use case examples and any supporting documents or images. For behavior that contradicts the documentation, file a bug report with a reproducible example.

How to do it with Vectalk

Vectalk is a proxy for the official Cloud API: your system talks to Vectalk, and Vectalk talks to Meta. When something goes wrong, your first contact is the contact page or the Help Center. Because error responses and webhooks follow Meta’s format, the code and fbtrace_id you receive are the same ones Meta uses to trace the issue; include them in your message. Technical docs are at docs.vectalk.com.br.

For the bigger picture of the platform, the WhatsApp Cloud API guide sums up requirements, limits and costs.

Frequently asked questions

Is there a phone number or live chat for Meta’s WhatsApp API support?

The official WhatsApp Business Platform support page lists Direct Support tickets, developer support, the community forum, bug reports and the status page. It does not list a phone line.

I can’t see Direct Support. What should I do?

Direct Support is aimed at enterprise developers and partners. If a partner onboarded you, register as a Meta developer to use the Ask a Question button, or ask your provider to open the ticket.

Does opening several tickets about the same issue get a faster reply?

Meta doesn’t say so anywhere. What it does say is that severity comes from the issue type and the information you provide. One well-documented ticket with IDs and fbtrace_id tends to be more useful than several incomplete ones.

My number was blocked. Is a ticket the right path?

For policy violations, the path is to request a review in Business Support Home, where Meta says decisions typically take 24 to 48 hours. The full process is in restricted or disabled Business Manager.

Can WhatsApp support help me if I use an unofficial API?

The support channels above are for the WhatsApp Business Platform. Libraries that emulate WhatsApp Web are not part of it, so there is no official channel for them; see official vs unofficial WhatsApp API.

---

Official sources checked on October 28, 2026: WhatsApp Business Platform support, Direct Support, Support for partners’ business customers, Support for solution providers, Error codes, Policy and spam enforcement, Ads review policy, Meta Status: WhatsApp Business API.