WhatsApp marketing: plan the 2027 migration

PLAN / MESSAGING CONTINUITY

1. WhatsApp marketing has two migration dates to plan around

HighLevel reminder: 19 October 2026 · Meta announcement: 13 October 2026

What changed

HighLevel has issued a reminder to move WhatsApp marketing to the Marketing Messages API, which it supports under the MM Lite name. Its notice describes activation through Settings → WhatsApp and an account access request. It says existing numbers and marketing templates can be used. This is the vendor’s documented path, not evidence that a particular Growthcenter account is enabled.

Meta independently confirms that new Messaging accounts created on or after 13 April 2027 cannot send marketing messages through Cloud API. Existing accounts have until the global marketing sunset on 13 October 2027, after which those Cloud API sends produce an error. Service, authentication and utility messaging remain supported on Cloud API.

Meta also says utility messages reclassified as marketing need the appropriate marketing route, and warns that some optimization features have geographic restrictions. These dates concern API marketing delivery; they are not an announcement that every WhatsApp message or the WhatsApp Business App is being shut down.

Who this affects

Australian service businesses whose provider sends WhatsApp marketing templates through an API, including relevant Growthcenter setups. If you do not send API marketing messages, you can skip this migration project. If your workflows only send utility messages, confirm their actual classification and reclassification handling before assuming nothing is affected.

Our analysis: what it means for your business

Our analysis: ask for a sender inventory before asking someone to click an activation banner. List the recurring campaigns, their template category, the integration that sends them and who owns that integration. An account setting can be enabled while an older custom workflow still uses the wrong sending route.

Hypothetical example: a Melbourne detailing business has appointment confirmations and a seasonal promotion. The operator should inspect the real categories and sending paths for both. If a new branch needs a new messaging account next April, the earlier new-account restriction matters even though the existing branch has a later deadline. This is an example, not a reported customer incident.

Allow time for access permissions, integration work and verification. HighLevel describes a short activation flow; that does not guarantee the entire business migration is finished in a few minutes. The useful completion evidence is a controlled test showing the intended template uses the correct route and that delivery or failure reaches the staff member responsible.

Do not use migration as a reason to increase message volume or assume better returns. Availability of individual optimization features, costs and results need their own account-specific checks. The practical aim is continuity of an existing, wanted communication process.

What to do next

1. Ask the current messaging operator to confirm the account creation date, which API sends marketing and whether the required terms and access permissions are in place.
2. Have that operator check how templates reclassified as marketing are routed and how failures are surfaced to staff. Keep an owner and review date against each affected workflow.
3. Agree on a small authorised test and a fallback before making a change. Verify the actual account’s feature availability; this report does not authorise a customer-account migration.

EVALUATE / PREVIEW ONLY

2. Clairic can structure inputs, but structure is not proof

Announced 19 October 2026 · Cloudflare Workers AI preview

What changed

Cloudflare has announced Clairic, an extraction-model preview hosted on Workers AI. It returns typed fields from inputs and supports extraction, computation, estimation and forecasting. Its model documentation includes confidence values and nullable answers. Open weights are planned; the announcement does not say they have been released.

Cloudflare explicitly cautions that well-formed answers are not necessarily correct. It identifies limits in longer arithmetic chains, calibration on unfamiliar inputs and forecasting. The hosted preview requires a developer integration; this is not a verified native feature in Growthcenter or a customer’s existing booking system.

Who this affects

Businesses with repeated manual copying of job details, dates or reference numbers from incoming material, and an operator able to evaluate a developer preview. Owners without a specific data-entry bottleneck can safely ignore it for now. A working form that already collects clean fields may be the simpler solution.

Our analysis: what it means for your business

Our analysis: distinguish a value copied from the customer’s message from a value estimated by a model. They may both look tidy in a CRM field, but they do not have the same evidential status. Keep that distinction visible wherever staff review or act on the result.

Hypothetical example: a plumbing office receives a message with a suburb, an appliance model and a preferred callback time. An evaluation could check whether those stated details are captured correctly. A repair-price estimate generated from the same message is a different task and should not silently become the amount in a customer quote. No such workflow was tested for this edition.

A useful trial includes missing details, conflicting dates and ambiguous wording, not just clean examples. Record incorrect fields and the time spent reviewing them. A faster model call would not establish a faster office process if staff must correct more records.

Start with non-sensitive sample material and a human approval step. Before considering real customer data, have the existing provider assess the proposed data handling and account terms. This announcement does not establish Australian data residency, a measured saving, production reliability or a suitable privacy arrangement for your business.

What to do next

1. Choose one narrow extraction task and define the correct answers for a small representative sample. Keep the original input available for comparison.
2. Separate extracted fields from estimates, preserve missing-value states and send uncertain or conflicting cases to review. Use ordinary code for calculations that must follow fixed rules.
3. Keep outbound quotes, booking changes and payments outside an initial preview trial. Decide whether the tool reduces total handling effort only after measuring accuracy and review time.