WhatsApp Direct Send utility messages: who became eligible in October 2026?

Meta's 8 October changelog widened the general eligibility rule for Direct Send utility messaging to portfolios with a 100,000 or unlimited messaging limit. The Direct Send overview, updated the same day, says the solution remains a phased rollout and tells businesses to verify availability in WhatsApp Manager. An eligible-looking limit alone is therefore not an activation signal.

Direct Send itself predates this entry. Its purpose is to let an eligible business submit business-initiated utility content through the Cloud API without first creating the corresponding message template by hand. Meta matches the content to an existing template or uses an onboarding fallback and creates a new template asynchronously. This is a change in the integration path, not an exemption from category rules, recipient permission, message charges or delivery checks.

Find the portfolio's actual messaging limit and open WhatsApp Manager for the intended Messaging account. Meta says a banner there indicates whether Direct Send is enabled. Record the business, account, phone number and banner state. A portfolio at the threshold may be generally eligible yet still lack access during rollout or because another prerequisite is unmet.

If the feature is not enabled, keep using the approved-template path. Meta documents a synchronous code 100 response for a Direct Send category request from an ineligible account; its detail says the category requires Direct Send and recommends an approved template. Do not interpret that error as a temporary delivery delay and blindly retry customer traffic.

Direct Send uses the existing Cloud API messages endpoint with a category field. Meta's utility example sends ordinary text content with category set to utility; the platform then handles template matching or generation behind the scenes. This is different from submitting an approved template name and parameters. A developer should follow Meta's current request reference rather than adapting a live sender from this short explanation alone.

Omitting category follows the normal free-form Service flow. It is not a way to start a Direct Send utility message: outside an open service window, the usual 131047 error can apply. Marketing is not a supported Direct Send category. Authentication is documented as beta and access restricted, with its own category and conditions. A customer update belongs in Utility only when it satisfies Meta's category guidelines; writing marketing copy in an order notification does not make it Utility.

A useful first case is an order or delivery update tied to a real customer transaction, using a consented test recipient and a business account whose Direct Send banner shows access. Keep the content strictly informational. Before a live change, review how your system creates and displays templates, records message IDs, handles reclassification and processes later status webhooks.

Direct Send pilot

Check access, category and outcome

A messaging limit is only a starting signal. Confirm the account banner and test one suitable utility message.

01

Eligibility

Confirm the intended account's Direct Send banner in WhatsApp Manager.

02

Content

Use a permitted, genuinely transactional Utility message and supported format.

03

Outcome

Check the API response and later delivery evidence separately.

Send one controlled example using Meta's documented request format. Compare the synchronous API result, the actual template or fallback behavior, and later status events. Record any error and stop criteria. A successful request does not prove that the message arrived, that every future message will match the same template, or that Whats91's existing product interface exposes Direct Send.

Meta lists Direct Send Utility support for text, selected call-to-action URL and reply buttons, some media headers and a standalone voice-call button. Formats outside its supported list should not be assumed to work. The supported-features page says Direct Send follows standard Cloud API throughput eligibility; the 100,000 threshold here is a general eligibility criterion, not a promise of extra throughput or a quota of free messages.

Meta's sending guide identifies Utility Direct Send messages as charged at Utility rates. Use the rate applicable to the recipient market, date and account when budgeting. The October 2026 India pricing article covers the local rate schedule and separates Utility from Service allowances. No Direct Send-specific discount or Whats91 product support is established by this Meta update.

This guide was prepared on 13 October 2026 from Meta's WhatsApp Business Platform changelog and Direct Send documentation. The new fact is the 8 October portfolio-limit eligibility update. The Direct Send mechanics and supported-format pages describe the existing feature; their earlier update dates are not presented as October launches. Meta's overview calls Utility generally eligible at the threshold while also noting a phased rollout and account-level confirmation.

No Whats91 or customer Meta account, WhatsApp Manager banner, API send, generated template, delivery, charge or billing record was tested for this article. The checklist is for deciding whether a small, authorized pilot is sensible; it is not a statement that a particular business or Whats91 feature has been activated.