Melbourne Marketing Brief / #018 / NEWS & ANALYSIS
Email preferences, WhatsApp setup and AI routing: three changes to check
Published by Ajay Dabhi · · AI-assisted research and writing
1 October 2026 · NEWS & ANALYSIS · Public beta and account limits identified
Today’s changes concern how customers control notifications, how businesses connect WhatsApp, and how custom AI systems choose a model. Each solves a different operational problem. Start by checking whether your business uses the affected part of the platform.
Three official announcements dated 30 September were checked on 1 October, Melbourne time. The recommendations and hypothetical examples below are original analysis, separate from reported platform facts.
Growthcenter’s community item is attributed to HighLevel, its underlying platform. Individual account access, regional eligibility and provider configurations have not been tested. This report does not claim that Ajay personally reviewed a client account or measured any gains.
CHECK / MEMBER COMMUNICATION
1. Growthcenter’s underlying platform narrows Community email opt-outs
Confirmed platform announcement · Growthcenter account access unverified
What changed
HighLevel announced more specific Community email unsubscribe controls on 30 September. An opt-out now applies to the community and notification type identified on the confirmation page, such as a comment mention, rather than potentially stopping all platform emails.
The announcement says other community and platform emails continue. Invalid or expired unsubscribe links do not change settings, and members can re-enable a disabled notification in their preferences. This concerns Community notifications; it is not an announcement of a new newsletter subscription integration.
Published 30 September 2026. Source checked 1 October 2026.
Who this affects
Australian businesses running member or client communities through Growthcenter, and the staff responsible for those communications. If the business does not use Communities, this release does not require changing its email process.
Our analysis: what it means for your business
A customer may want fewer discussion alerts while still wanting another community’s updates. More specific controls can make that distinction clearer, but the business needs to understand which message category it is sending. A setting that appears enabled does not prove a message reached the recipient.
Hypothetical example: a fitness studio has separate member communities for two programmes. A labelled test member could switch off comment notifications for one programme, then check that the preference shown matches that choice. The test should use an internal address and planned sample messages, not real members as test subjects.
My recommendation is to explain what each preference controls and make requests to staff easy to resolve. Do not use this narrower setting as a reason to restart marketing someone has asked to stop. Confirm the actual request and the systems affected before changing a record.
What to do next
- Ask the provider whether these controls are available in the relevant Growthcenter account and identify which emails are Community notifications.
- With an authorised internal test member, check the confirmation screen, saved preference and expected message categories. Record anything that behaves differently from the documentation.
- Keep newsletter and other marketing preferences clearly identified. This platform release does not configure email subscriptions on Ajay’s website.
CHECK / NEW SENDER SETUP
2. Twilio updates its WhatsApp sender onboarding flow
Confirmed Twilio release · Generally available · Provider setup matters
What changed
Twilio announced general availability of WhatsApp Embedded Signup Version 4 on 30 September. It updates the WhatsApp self-sign-up flow in the Twilio Console, changes phone-number setup and includes MM API terms acceptance within that flow.
Twilio links the update to WhatsApp’s planned retirement of older signup versions. That is Twilio’s explanation of the dependency, not independent confirmation here of a Meta deadline. The reported release concerns sender registration; it does not announce a new customer-messaging capability.
Published 30 September 2026. Source checked 1 October 2026.
Who this affects
Businesses and providers setting up WhatsApp senders through Twilio. A business using a different onboarding route should ask its own provider about that route. If there is no planned sender setup or provider migration, there is no immediate task established by this announcement.
Our analysis: what it means for your business
The practical risk is a setup project getting delayed because nobody knows who owns the business account, phone number or approval step. A new interface does not resolve those ownership questions. Confirming the responsible person before a planned launch can prevent avoidable hand-offs.
Hypothetical example: a Melbourne cleaning company plans to add a WhatsApp enquiry channel. Its owner and provider first map the intended sender, the account that will own it and who can complete the terms and verification steps. This is preparation for an approved setup, not a claim that the channel is already active or will generate enquiries.
I would ask the provider for a short readiness check before scheduling customer-facing communications. Keep registration, message handling and follow-up as separate checks. A successful signup screen alone is not evidence that incoming enquiries reach the right person.
What to do next
- Identify whether the actual setup uses Twilio Console self-sign-up, a provider’s embedded flow or another route. Ask the owner of that route to verify compatibility.
- Confirm the authorised account owner and phone-number setup requirements before changing anything. Do not replace a working sender merely because an onboarding update was announced.
- After an approved setup, arrange labelled internal checks of incoming messages and human follow-up. This briefing has not performed those tests or verified an Australian account.
EVALUATE / CUSTOM AI WORKFLOWS
3. Cloudflare puts automatic AI model selection into public beta
Confirmed release · Public beta · Planned controls remain unavailable
What changed
Cloudflare released Auto Router through AI Gateway on 30 September. Requests using cloudflare/auto can be routed to different eligible models. The selection accounts for factors including request support, credentials, billing, access policies and spending limits.
Cloudflare reports internal cost and performance results; those are vendor findings, not measured savings for a local business. Its announcement lists zero-data-retention filtering and full Responses API and WebSockets support as future work. Those planned capabilities must not be treated as present release features.
Published 30 September 2026. Source checked 1 October 2026.
Who this affects
The maintainer of a custom AI workflow already using, or actively evaluating, Cloudflare AI Gateway. Owners using a managed assistant can ask their provider whether it is relevant. This is not a general instruction to replace a model or upgrade an AI receptionist.
Our analysis: what it means for your business
Automatic routing changes an important assumption: the same workflow may be handled by different models. A lower model charge is useful only if the completed task still meets the business’s requirements. Corrections, missed details and delays belong in the comparison alongside API spend.
Hypothetical example: an electrical business uses AI to draft an internal enquiry summary. A maintainer could compare the current setup with the beta using fictional enquiries, including missing addresses and requests outside the service area. The review should check whether both preserve the same facts and leave unknown availability unconfirmed. No such comparison was run for this report.
My recommendation is to keep a fixed working setup available while evaluating a low-risk internal task. Ask the maintainer which providers could receive the information and whether the existing data-handling requirements can be met. Do not route sensitive records on the assumption that a planned retention filter is already in place.
What to do next
- Confirm actual model, provider, account and interface compatibility before considering a trial. The public-beta announcement does not verify an individual Australian configuration.
- Use approved non-sensitive sample material and compare complete outputs, correction time, delay and total cost. Avoid presenting the vendor’s internal savings as a forecast.
- Keep customer sending, bookings and account changes outside the initial evaluation. Expand only after the responsible person reviews the results and the provider requirements.
ANALYSIS / BUSINESS CONTEXT
Where to spend your attention today
For most local owners, these are checks to assign to the person who manages the affected system. Community preferences belong with the communication owner; WhatsApp onboarding belongs with the account owner and provider; model routing belongs with the AI maintainer.
There is no need to adopt all three. Identify an existing problem, confirm the relevant feature is available, and define what a correct outcome looks like before changing the setup.
Practical checks
- Using Growthcenter Communities? Check which notification a member is actually turning off.
- Planning WhatsApp onboarding through Twilio? Confirm the route, account owner and readiness before launch.
- Running custom AI through AI Gateway? Treat automatic routing as a controlled beta evaluation, with task quality and data handling checked first.
These checks are recommendations, not additional requirements announced by the platform. The appropriate work depends on your actual configuration.
Publisher and editorial information
Ajay Dabhi publishes this report and also sells marketing and automation services. The commercial invitation above is separate from the sourced reporting. No client account test or direct interview is claimed in this report.
Research and writing use AI assistance. Original documents are linked so readers can check the facts. Read our ownership, sourcing and corrections policy or report a correction to Ajay.
All Melbourne Marketing Brief editions →