Public website

Customer conversation platform

Every conversation. One clear next step.

DripTell brings WhatsApp, Instagram, Messenger, Telegram and web chat into one workspace, with shared ownership, customer context, automation and AI assistance.

You are viewing the compatibility version because this browser does not support the modern website presentation. This is the public DripTell website; no customer workspace or account data is shown.

DripTell

Messaging Operations

WhatsApp Marketing Messages Are Moving Off the Cloud API

Use the April and October 2027 deadlines to inventory marketing traffic, prevent duplicate sends and prove replies before cutover.

By DripTell EditorialPublished November 8, 2026Reading time 4 min read
Two operations specialists test one active marketing message route beside a closed former route

Meta will stop delivering WhatsApp marketing messages through the Cloud API on 13 October 2027. Six months earlier, on 13 April 2027, any new Messaging account will lose the option to send marketing messages through that route. Those accounts must use the Marketing Messages API for WhatsApp from the start.

This is not a complete Cloud API shutdown. Meta says service, authentication and utility messages will continue there. Existing phone numbers and marketing templates can be used with the successor API, but teams still need a controlled cutover.

Read the two deadlines correctly

Meta's current Marketing Messages API overview separates new accounts from existing ones. Do not reduce the plan to a single final deadline.

DateWho is affectedOperational result
13 April 2027New Messaging accounts created on or after this dateMarketing messages cannot start on the Cloud API
13 October 2027Every business still sending marketing through the Cloud APIMarketing sends through that route return an error
After migrationMarketing trafficSends use the Marketing Messages API while other supported message categories remain on the Cloud API

An account created before April can use the old route only until October. Record which account owns each number and which system submits its marketing templates.

Turn those facts into a migration ledger with an account owner, last old-route campaign, first new-route test, decision date and rollback owner. The ledger makes the deadline actionable without assuming every number, market or campaign can switch on the same day.

Audit the traffic that must move

Start with actual traffic, not a template list. Record the sending account, number, template, category returned by Meta, owner and reply destination. Link the inventory to your WhatsApp Cloud API setup so asset and webhook ownership stays visible.

Overhead migration workbench with account, template, route, recipient test and cutover groups
Account, traffic, route, recipient evidence and cutover each need an owner.
Five migration controlsMove one marketing route with evidence.
  1. 1Map accountsRecord number and owner.
  2. 2Classify trafficUse the returned category.
  3. 3Build the routeKeep one send authority.
  4. 4Test outcomesProve status and reply.
  5. 5Cut overClose the old sender.

Pay special attention to utility templates that Meta reclassifies as marketing. Those sends must use the Marketing Messages API, so route by the returned classification rather than an old label.

Authentication, service and genuine utility messages are not part of this sunset. Do not move them merely to make the architecture uniform. Use the template change control guide when content, category or ownership changes.

Move without creating duplicate sends

Meta's sunset announcement says to accept the new terms, confirm the new endpoint is live and check reclassified traffic. Its roughly two-week average is a planning reference, not a promise.

Build the new path in a controlled environment with one approved template and a small permitted audience. Capture the request identifier, status events and chosen route. The old and new senders must never act on the same campaign row; use one durable send key and switch authority deliberately.

Meta describes the schema and billing model as similar, not identical. Check current permissions, feature availability and geographic restrictions. Keep provider fees separate from Meta charges using the WhatsApp cost model.

Prove the complete customer path

An API response only proves that Meta accepted the request. Test delivery, failure, expiry and a real reply. Confirm it enters the intended campaign workspace with its source and one owner.

Reconcile accepted, sent, delivered, read, failed and replied states by recipient. The campaign reply measurement guide keeps replies, delivery and business outcomes separate.

Rehearse rollback. If the new route fails, pause marketing work and inspect the recorded request. Never resend the same audience automatically through the old path.

Give the cutover named owners

Name owners for Meta access, integration, template classification, campaign approval and replies. Store the route, evidence and stop rule in a release record. The shared inbox remains the reply workspace, not the API migration.

Cut over a low-risk campaign, close the old marketing route, monitor events and replies, then expand. The result should be one send authority, one evidence trail and one accountable reply path.

Frequently asked questions

Is the WhatsApp Cloud API shutting down

No. Meta says the October 2027 sunset applies to marketing messages sent through the Cloud API. Service, authentication and utility messages continue to be supported there.

Can existing phone numbers and templates move

Meta says the Marketing Messages API uses the same billing model and can use existing phone numbers and marketing templates. Teams must still verify terms, permissions, routing and live results for their own assets.

When should a business begin

Begin early enough to inventory traffic, test reclassification, prove replies and hold a controlled cutover. Meta says most integrations may take about two weeks on average, but business review and recovery testing can require more time.

Want help applying this guide?Ask the DripTell team

All fields are required.

+971

Your request goes to a person, not a mailing list.

By sending this, you agree to an acknowledgment and follow-ups about your request from DripTell on WhatsApp or email, including automated messages. You can ask us to stop at any time. See our privacy policy. Google Analytics counts each request. Depending on your cookie choice, Meta and OpenAI are also told, so we can measure our ads, and Meta receives your contact details in hashed form.

DT

DripTell Editorial

Practical guidance reviewed by the DripTell product and customer workflow team.

See how DripTell checks product claims, uses primary sources and handles corrections.

Editorial and source policy