Melbourne Marketing Brief / #059 / NEWS & ANALYSIS
WhatsApp replies get a workflow routing fix
Published by Ajay Dabhi · · AI-assisted research and writing
11 November 2026 · VERIFIED SOURCE REPORTING · ACCOUNT ACCESS UNVERIFIED
A customer taps an appointment option in WhatsApp, but the workflow treats them as if they never replied. HighLevel says it has fixed a matching problem behind that situation. Two related maintenance updates also deserve a careful check: shared message content can update across workflows, and a new cleanup list flags automations for review.
These are HighLevel announcements dated 10 November 2026, checked on 11 November. HighLevel is the underlying platform relevant to Growthcenter; the source does not establish availability in every Growthcenter plan or Australian account. Verify the controls in the account you are authorised to manage.
Research and writing use AI assistance. No customer account or workflow was inspected, changed or tested. Examples are hypothetical, not client evidence or a claim that Ajay personally reviewed the products. Vendor statements about capability are separated below from analysis and suggested checks.
01 / WHATSAPP REPLIES
A selected option should reach the selected branch
Announced 10 November · Vendor reports automatic fix
What changed
HighLevel says replies to personalised WhatsApp buttons and list options now match the branch for the chosen option. Previously, some labels containing custom values were not matched and the contact reached the Timeout branch instead.
The vendor also says overlong labels are now shortened with an ellipsis rather than causing a send failure, while the option retains its routing. It says existing workflows receive the fix automatically without re-saving. These are the vendor’s claims; this edition does not independently confirm delivery, routing or booking results.
Published 10 November 2026. Source checked 11 November 2026.
Who this affects
Australian service businesses already using HighLevel-based WhatsApp buttons or lists for appointments and service choices. If you use only phone, email or SMS, this fix does not call for a channel change. Growthcenter account and WhatsApp eligibility were not verified.
Our analysis: what it means for your business
Our analysis: accepting an answer, selecting a branch and completing the next task are three different events. A routing fix may address the first handoff while a calendar conflict, missing field or downstream action still needs attention. Do not count the tap itself as a confirmed appointment or assume historical contacts were repaired.
Hypothetical example: a cleaning customer taps an option showing their proposed arrival time. The operator should be able to trace that choice to the intended branch and then to the actual confirmation or booking result. If the label is shortened, two nearby choices must remain distinguishable to the customer. This is a suggested check, not a test performed for this edition.
The source does not establish recovery of earlier unmatched replies. Review a specific affected contact’s current status before any authorised follow-up; blindly replaying an old path could duplicate a message or booking. No uplift in enquiries or bookings is established by the announcement.
What to do next
- Have the authorised operator verify one representative choice, branch and downstream result using an approved test contact.
- Inspect personalised and shortened labels for clarity; assess old exceptions individually before re-running anything.
03 / WORKFLOW MAPS
A cleanup candidate is not permission to delete
Announced 10 November · Confirmation and permissions apply
What changed
HighLevel’s new Cleanup view in Workflow Maps identifies workflows with default names, workflows with no enrollments in the last 60 days, and empty folders. The documented path is Automation → Workflows → Workflow Maps → Cleanup.
The vendor explicitly says a workflow with no recent enrollments may still serve a seasonal or occasional process. Cleanup identifies candidates for review; deletion requires confirmation and follows access permissions. It advises checking purpose and dependencies first.
Published 10 November 2026. Source checked 11 November 2026.
Who this affects
An authorised operator reviewing a growing HighLevel-based automation account. If there is little clutter or the feature is absent from your account, there is no reason to delete or rebuild working processes to use it. Growthcenter entitlement was not checked.
Our analysis: what it means for your business
Our analysis: inactivity describes recent enrollments, not business value. A workflow for an annual reminder, a rare escalation or a seasonal closure might correctly sit idle. Renaming an unclear workflow or documenting its owner can be a better outcome than removing it.
Hypothetical example: a garden-maintenance business has a winter-only follow-up workflow with no recent enrollments. Before deleting it, the operator checks its next intended use, connected triggers and the staff member responsible. The cleanup list is useful for finding the question; it does not supply the business answer.
Our recommendation is to review candidates in a small batch and record keep, rename or remove with a reason. Use the existing recovery and change-approval process before a permitted deletion. Neither an empty folder nor a quiet workflow establishes a fault, and no customer account was cleaned up for this edition.
What to do next
- Check purpose, seasonality, dependencies and owner for each candidate.
- Record the decision before any authorised removal; do not use 60 days as an automatic deletion rule.
ANALYSIS / BUSINESS CONTEXT
Where to spend your attention today
These updates address distinct failure points: recognising a customer’s choice, using the intended message content and understanding the workflows that remain in the account. The useful check is a small documented path from customer action to actual result, not a count of new features enabled. No ranking, revenue, lead-generation or customer-service improvement has been measured here.
Commercial context: Ajay Dabhi sells local SEO, website, advertising and automation services for Australian service businesses. Growthcenter branding does not replace attribution to HighLevel, and these announcements do not establish account access. The invitation below is separate from the reporting; an existing authorised operator may be able to complete the checks. Digital services are Australia-wide; on-site visits are available in Melbourne.
Practical checks
- Verify an actual WhatsApp selection and its downstream outcome.
- Review shared-content dependencies and the older snippet-step exception.
- Use workflow cleanup as a review queue, preserving seasonal processes.
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 →