WhatsApp Direct Send: utility messages without templates, for the largest senders first

WhatsApp Direct Send is Meta’s way of letting a business send a utility message, such as an order update or an appointment reminder, without creating a template and waiting for it to be reviewed. It exists, the utility part is out of beta, and most Indian small businesses can’t use it yet.

That last point belongs on the first screen, so here is the status exactly as Meta’s Direct Send page states it (the page shows “Updated: Oct 8, 2026”, and we read it on 13 October 2026):

• “Direct Send is a premium solution for businesses that meet the prerequisites. It supports utility and authentication (Beta) messaging and is rolling out in phases.”
• “Business portfolios with a messaging limit of 100,000 or unlimited are generally eligible for Direct Send utility messaging.”
• “Direct Send for authentication messages is in beta. To be considered, express your interest.”

Nothing on any of the Direct Send pages names a country. Meta’s page does not say India is included, and it does not say India is excluded.

What is WhatsApp Direct Send?

Direct Send is a mode of the ordinary send-message API in which you send the final text of a utility message and Meta builds the template for you. In Meta’s words, “you send business-initiated messages directly and Meta auto-generates the matching templates behind the scenes.”

There is no new endpoint. Your developer calls the same messages endpoint described in our guide to sending a message through the API and adds one field, category, to the request body. Without that field the request is treated as a normal free-form message, which only works inside the 24-hour customer service window. (Terms like “customer service window” and “utility template” are defined in our glossary.)

The changelog gives the timeline. Documentation for an open beta appeared on 15 June 2026. On 31 July 2026 Meta wrote that “Direct Send utility messaging is now generally available” and that authentication “remains in beta”. On 8 October 2026 it added the 100,000 eligibility line quoted above.

What problem does it solve?

It removes template management for transactional messages. Meta says Direct Send “eliminates template creation complexity” and lets businesses “accelerate time-to-market for utility and authentication messaging.”

Think about who feels that pain. Urvashi Parmar runs operations for a diagnostics lab chain in Ahmedabad (an invented example). Her team sends “sample collected”, “report ready” and “home visit confirmed” messages. That is five or six templates, written once, approved once, and left alone for a year. For her, template creation is an afternoon of work.

A logistics company with forty client brands, each wanting its own wording in six languages, is in a different position. It is managing hundreds of templates, and every wording change is a new submission. Meta’s template review page says an approval decision “can take up to 24 hours”. Direct Send is aimed at that second business.

How is it different from the normal template flow?

In the normal flow you write the template first and Meta reviews it before you can send. With Direct Send you send first, and the template and the category check follow.

Step	Normal template flow	Direct Send
Before the first message	Create a template with a name, category, language and sample values, then submit it	Nothing to create
Review	Meta’s page says a decision can take up to 24 hours	No waiting step is described. The message is sent using a matching template or a fallback one
What you send	The template name plus values for each placeholder such as {{1}}	The finished message text plus "category": "utility"
Who owns the template	You do. You can edit or delete it	Meta generates it. You cannot edit or delete it
Category check	Before approval, and again later if content drifts	After sending, by Meta’s monitoring
Categories	Marketing, utility, authentication	Utility, and authentication in beta. Marketing is not supported

Meta describes the mechanics in four steps. When a message arrives with a category field, Direct Send checks whether it matches an existing template. If it does, that template is used. If it doesn’t, the message goes out on a fallback “onboarding” template that Meta adds to your account when you are onboarded, and a new template is created in the background from your message, with personal details redacted and the language detected, so the next similar message matches.

Generated templates appear in WhatsApp Manager with an indicator that Meta created them, and their names start with auto_generated. If your reporting depends on knowing which template a message used, you can pass your own name in direct_send_config.template_name (lowercase letters, digits and underscores only), and all messages with that name are attributed to it. Meta’s FAQ says generated templates that are never used are deleted after 24 hours.

Which messages does it cover?

Utility messages are supported, authentication is supported in beta, and marketing is not supported. Meta’s “Supported features and limits” page, updated 31 July 2026, lists:

• Utility: text messages, call-to-action URL buttons, reply buttons, a mix of the two (up to 10 buttons, at most 2 with URLs), image, video and document headers, a custom time-to-live, and a “Call on WhatsApp” voice call button sent on its own.
• Authentication (beta): text messages and a copy code button, in English only.
• Not supported: marketing messages, phone number call buttons, and address, audio, contacts, location, sticker and reaction messages.

Length limits match templates: 1,024 characters for the body, 60 for a header or footer, 20 for button text. All Cloud API languages are supported. Two details will catch developers out. Link previews don’t render on Direct Send text messages, and a customer’s tap on a reply button arrives in the template format ("type": "button"), not the interactive format your code may expect.

If you send one-time passwords, our OTP guide covers the regular authentication templates, which remain the route open to everyone.

Who can use it, and is India included?

Eligibility is set account by account, and Meta’s pages name no countries. The page says portfolios with a messaging limit of 100,000 or unlimited are “generally eligible” for utility, and tells you to confirm in WhatsApp Manager, where “a banner tells you whether your account is eligible”. If it isn’t, there is a form to express interest.

A messaging limit of 100,000 means your business portfolio can start conversations with 100,000 different people in a rolling 24 hours. New portfolios start at 250 and move to 2,000, then 10,000, then 100,000, as our messaging limits guide explains. A clinic, a coaching centre or a 12-person D2C brand is usually nowhere near that tier.

The “prerequisites” link on Meta’s page leads to its Help Centre article on scaling a WhatsApp Business account, which describes business verification and the other scaling paths. It doesn’t add Direct Send conditions of its own.

For authentication the wording is tighter. The send page says the authentication category is “Access restricted” and to “contact your partner or client manager to get access.”

What happens if an ineligible account tries anyway? The API answers at once with error 100 and this detail: “The ‘category’ value requires Direct Send, which isn’t enabled for this account. Use an approved message template instead.”

What does a Direct Send request look like?

It is a normal send-message request with a category field at the end. This is Meta’s own example, with placeholder IDs:

POST /<WHATSAPP_BUSINESS_PHONE_NUMBER_ID>/messages

{
  "messaging_product": "whatsapp",
  "recipient_type": "individual",
  "to": "<WHATSAPP_USER_PHONE_NUMBER>",
  "type": "text",
  "text": {
    "body": "<BODY_TEXT>"
  },
  "category": "utility"
}

Authentication uses "category": "authentication" where access has been granted. An optional ttl_seconds field sets how long Meta keeps trying to deliver. For utility the minimum is 30 seconds and the maximum Meta lists is 43,200 seconds (12 hours); for authentication the default is 10 minutes and the maximum 15. A message that can’t be delivered inside its TTL is dropped.

What does it cost?

Meta says Direct Send messages are charged at the rate for their category. The table of category values reads: utility, “Charged at utility rates”; authentication, “Charged at authentication rates”.

On Meta’s India rate card both are ₹0.115 per delivered message before GST, the same figures in our October 2026 cost guide. Meta calls Direct Send “a premium solution” but its Direct Send pages list no separate fee. Whether a provider adds a charge of its own for the feature is a question for that provider.

One oddity: the Direct Send FAQ still explains billing in terms of 24-hour “utility conversations”, while the main pricing page describes per-message charges. Ask your provider or check your first invoice before you build a forecast on either reading.

What are the limits and risks?

The main risk is category misuse, because nobody reviews the wording before it goes out. Meta’s integrity page says it “actively monitors how messages are categorized”, and that the same integrity rules that apply to templates you create also apply to generated ones.

If Meta detects marketing content in a utility message sent through Direct Send, you are told by email and by webhook, and the generated template is flagged. You can request a review within 60 days, once per template; Meta says most reviews take a few days. Persistent misuse escalates:

Level	What Meta says happens	Duration
Warning	You are notified and can request a review	Ongoing
Rate limiting	Utility sends are capped; beyond the cap they fail with error 131064	Until volume falls under the cap or the window ends
Messaging restriction	The account can’t use Direct Send for utility or authentication	7 days
Extended restriction	Meta calls this the final warning	30 days
Permanent revocation	Direct Send access is removed	Permanent

A delivery update with “use code DIWALI10 on your next order” at the end is the kind of message that starts this ladder. The rules on what counts as utility are the same ones in our guide to message categories, and the wording habits that get ordinary templates turned down, covered in our template rejection fixes, matter just as much here.

Quality still applies too. Generated templates can be paused for low quality like any other, and a message that matches a paused template fails with error 132015. Meta’s advice is to send only to people who are expecting the message.

On per-user caps, Meta’s Direct Send pages are silent. WhatsApp’s per-user limit applies to marketing templates, which Direct Send doesn’t carry. Throughput is the standard Cloud API throughput.

Should you care yet?

For most small and mid-sized Indian businesses the answer today is to know it exists and keep using templates.

Your business	Should you act now?
Bank, NBFC, insurer, marketplace or logistics firm at the 100,000 or unlimited tier	Yes. Look for the banner in WhatsApp Manager, and ask your provider whether its API passes the category field through
D2C brand or chain with a handful of order and reminder templates	Not yet. Approved templates do the same job, and you keep control of the wording
App or website sending OTPs	Authentication is beta and access-restricted. Ask your partner; plan on regular authentication templates
Business on a 250, 2,000 or 10,000 limit	You are outside the “generally eligible” group. The interest form is the only route Meta lists
Anyone hoping to send offers without template review	No. Marketing isn’t supported, and trying it through the utility category risks the account

If you are a developer reading this for a client, the practical step is small. Open WhatsApp Manager, look for the Direct Send banner, and note the portfolio’s messaging limit. Those two facts decide whether the rest of Meta’s documentation applies to you this quarter.