Skip to content

A glossary story9 chapters · 5 min read

Meta Direct Support

Meta's ticketing channel where WhatsApp Business Platform partners and eligible developers raise technical, account and integration issues with Meta.

Also called: Direct Support · WhatsApp Business Platform support ticket · Meta support ticket

Reviewed

Follow along

Follow a ticket from draft to resolved

4 / 4
  • Draft to Submitted: Submit
  • Submitted to In progress: Assigned
  • In progress to Needs your response: More info needed
  • Needs your response to In progress: You reply
  • In progress to Resolved: Fixed
  • Resolved to Reopened: Issue returns
  • Reopened to In progress: Re-traced
  1. Draft
  2. Submitted
  3. In progress
  4. Resolved

Step 4 of 4 · end of walk

Resolved

Fix applied or answer given. Confirm with one test message.

Arrived from In progress via Fixed.

Can move to

  • Reopened · Issue returns
The life of a Direct Support case. Walk the happy path, then switch to the paths where Meta needs more information or the fix does not hold. State names are illustrative.

Happy path, step 4 of 4: Resolved (via Fixed). Fix applied or answer given. Confirm with one test message.

Chapter 1 · The scenario

Example: A Gurugram fintech's OTPs stop delivering

At 19:05 IST a Gurugram fintech's authentication templates start failing with error 131000 on one number. Its provider's support engineer reproduces the call, collects three fbtrace_id values with UTC timestamps, the phone number ID and WABA ID, and confirms other numbers are unaffected. The ticket, filed within 25 minutes under an API errors question type, shows that 3,200 logins are blocked. Meta's engineer finds a stuck registration state, asks for one test send after a fix, and the case is resolved the next morning. The fintech switches OTPs to a backup number in the meantime.

— A Gurugram fintech's OTPs stop delivering

Chapter 2 · What is Meta Direct Support?

Meta Direct Support is the case-management channel Meta provides for the WhatsApp Business Platform. An authorised person in a partner's or developer's business portfolio opens a ticket, picks a question type (for example an API error, phone number registration, account or billing issue), describes the problem and attaches evidence; a Meta support engineer then works the case, asks for more information if needed and closes it with an answer or a fix.

Access depends on your relationship with Meta. All three WhatsApp partner types, Solution Partners, Tech Providers and Tech Partners, have Direct Support. Businesses that onboarded through a partner normally go through that partner, which can see the same assets and file a better ticket, while direct developers should check the standard support channels Meta lists for their account. Meta also points API integrators at Direct Support for specific programmes: for the new account model rolling out since 23 September 2026, it asks for tickets with the question type "New Account Model on WhatsApp Business Platform".

Direct Support is not the place to contest enforcement. A restricted or banned account, a disabled number or a rejected template is reviewed through a Policy Appeal or a template appeal in WhatsApp Manager. It is also unrelated to a business's own customer support operations on WhatsApp, which is about answering customers, not Meta.

Key takeaways

  • Meta Direct Support is the ticket channel for WhatsApp Business Platform problems: API errors, onboarding, numbers, accounts and billing.
  • Solution Partners, Tech Providers and Tech Partners all have access; most client businesses raise issues through their partner.
  • A good ticket includes the fbtrace_id, WABA ID, phone number ID, exact UTC timestamps, the request and the full error response.
  • Enforcement decisions such as a restricted account or rejected template go through the appeal flows, not a Direct Support ticket.
  • Choose the closest question type; Meta asks for questions on the new account model to use its own dedicated type.

Chapter 3 · How it unfolds

How does Meta Direct Support work?

  1. Confirm it is a platform problem

    Check Meta's platform status page and your own logs first. Reproduce the failing call and capture the full error object, including code, error_subcode, message and fbtrace_id.

  2. Open a ticket with the right question type

    In Direct Support, select your business portfolio, the app or WABA affected and the closest question type. The wrong type sends the case to the wrong queue and costs days.

  3. Give Meta everything needed to trace it

    Include the WABA ID, phone number ID, app ID, Graph API version, the request (with tokens removed), the response, UTC timestamps and how many users or messages are affected.

  4. Answer follow-ups quickly

    When the ticket moves to "needs your response", reply within a day with exactly what was asked. Silent tickets are closed automatically after a while.

  5. Escalate with impact, not volume

    If a case stalls, update it with business impact (failed OTPs, revenue at risk) and, if you have one, contact your Meta partner manager with the ticket number. Opening duplicate tickets slows things down.

Chapter 4 · In code

Meta Direct Support in code

Summary: Authentication template sends fail with 131000 on one number since 13:35 UTC
 
Impact: ~3,200 users cannot log in; other numbers on the same WABA unaffected
WABA ID: {WABA_ID}
Phone number ID: {PHONE_NUMBER_ID}
App ID: {APP_ID}
Graph API version: v26.0
First seen (UTC): 2026-10-19T13:35:00Z   Still failing: yes
 
Request (token removed):
POST https://graph.facebook.com/v26.0/{PHONE_NUMBER_ID}/messages
{ "messaging_product": "whatsapp", "to": "91XXXXXXXXXX", "type": "template", ... }
 
Response:
{ "error": { "message": "...", "code": 131000, "fbtrace_id": "AbC123xYz..." } }
 
Other fbtrace_ids: AbC124..., AbC125...
Already checked: platform status page, token valid (debug_token), template approved

One ticket, everything Meta needs to trace it. Never paste access tokens or customer message content.

Chapter 5 · Where it goes wrong

Common mistakes with Meta Direct Support

  • Filing without an fbtrace_id

    Without it Meta has to guess which request failed. Log the full error object for every failed Graph call so the trace ID is there when you need it.

  • Using a ticket to appeal a ban

    Support engineers cannot overturn enforcement through a technical ticket. Use the Policy Appeal flow in WhatsApp Manager or Business Support Home and keep the ticket for technical faults.

  • Pasting secrets

    Access tokens, app secrets and customer message content do not belong in a ticket. Redact them; IDs and trace IDs are enough.

  • Opening duplicates

    Several tickets for one problem split the history and reset queues. Update the original case and reference its number everywhere.

Chapter 6 · The facts

Meta Direct Support: key facts and limits

Who has accessSolution Partners, Tech Providers, Tech Partners
Opened fromDirect Support, in your business portfolio
Key trace fieldfbtrace_id from the error response
Must includeWABA ID, phone number ID, UTC timestamps, request, response
Not forEnforcement decisions (use policy or template appeals)
New account modelDedicated question type for API integrators

Chapter 7 · Why it matters

Why does Meta Direct Support matter?

When messages stop delivering or a number will not register, the time to resolution depends almost entirely on the first ticket. Meta engineers trace problems through internal logs, and they can find yours in minutes if you give them the fbtrace_id and IDs, or never if you write "messages not going". Knowing what Direct Support handles, what goes to appeals and what a partner should file on your behalf turns a week of back-and-forth into a one-day fix.

Chapter 8 · What good teams do

Best practices for Meta Direct Support

  • Keep a ticket template in your runbook so on-call engineers file the same complete format every time.
  • Record ticket numbers against incidents in your own tracker for post-mortems.
  • Test a fix with one message before telling Meta it worked or did not.

Chapter 9 · Meta Direct Support FAQs

Meta Direct Support FAQs

How do I contact Meta support for the WhatsApp Business API?+
Partners open a ticket in Meta Direct Support from their business portfolio. If you onboarded through a provider, raise the issue with them first; they can see your assets and file a complete ticket on your behalf.
What is fbtrace_id and why does Meta ask for it?+
It is a trace ID in every Graph API error response. Meta's engineers use it to find your exact request in their logs, so it is the most useful single item in a support ticket.
Can Direct Support restore a banned WhatsApp number?+
Not through a technical ticket. Bans and restrictions are reviewed through the policy appeal process; Direct Support handles technical faults such as API errors, registration problems and onboarding failures.
How long does Meta Direct Support take to respond?+
It varies with the question type, severity and queue, from hours to several days. Complete tickets with trace IDs and clear impact are consistently resolved faster.

See InfiQ pricing

From definition to your first message

InfiQ is an official Meta Business Partner. Start a 7-day free trial — no card needed — and see this running on your own number.

Start free trialBrowse all 550 terms