Melbourne Marketing Brief / #008 / NEWS & ANALYSIS
Jotform workflows and chat spam controls: check what happens to the enquiry
Published by Ajay Dabhi · · AI-assisted research and writing
21 September 2026 · News and analysis · New Jotform announcement; older chat-widget update
A new Jotform integration can move an enquiry into a workflow. A separate chat-widget control can stop suspicious contacts receiving follow-up. Both deserve a check at the point where a software record turns into a promise to a customer.
The Jotform announcement appeared in the underlying platform’s official feed on 20 September. The chat-spam announcement is dated 18 September and is included as relevant background, not a launch today. Both original pages were checked on 21 September, Melbourne time.
These are HighLevel platform announcements relevant to Growthcenter users. Neither announcement is labelled beta or Labs, but access, permissions, charges and suitability in an individual Australian Growthcenter account have not been verified. No customer workflow was tested for this edition.
CHECK BEFORE AUTOMATING ONBOARDING
1. Jotform can start workflows, but a saved record can be incomplete
Confirmed platform announcement · 20 September 2026 · Growthcenter account availability unverified
What changed
The integration adds triggers for new form submissions and signed documents, plus an action that creates a Jotform submission. Signed-document detection checks every five minutes.
The creation action cannot fill certain fields, including signatures, payments, file uploads and appointments. The announcement warns that unsupported required fields can stay empty while the submission is accepted as active. A created submission does not itself collect payment or reserve an appointment.
Published 20 September 2026. Source checked 21 September 2026.
Who this affects
Service businesses already using Jotform for intake or agreements and considering a connection to Growthcenter. If neither tool is part of your process, this is not a reason to switch systems.
Our analysis: what it means for your business
My recommendation is to separate three decisions: whether the enquiry arrived, whether the customer accepted the work, and whether a booking or payment actually exists. A successful transfer answers only the first question unless the other evidence is explicitly checked.
Hypothetical example: a cleaning business records a phone enquiry in an intake form. Its coordinator can assign a callback, but should not send a paid-booking confirmation simply because the new record appears in the form report. This is an illustrative failure to prevent, not a reported client incident.
What to do next
- Choose one simple intake form and compare every required business detail with the available field mapping. Route missing details to a named person.
- With authorised synthetic records, check normal intake, a duplicate and an incomplete submission. Keep outgoing customer messages disabled during the test.
- Require the relevant payment receipt, signed agreement or calendar record before advancing that stage. Retain the existing connector until the replacement passes the actual business checks.
REVIEW THE FOLLOW-UP QUEUE
2. Chat spam protection needs a review owner
Older platform update · 18 September 2026 · Not newly announced today
What changed
The chat-widget feature retains suspicious contacts and applies the tag chat_widget_high_volume_flag. Each widget can tag only, pause SMS, pause email or pause both.
The announced defaults differ: protection is off for existing widgets, while new widgets start with protection on and both channels paused for flagged contacts. Existing do-not-disturb preferences and other channels are unchanged. The provider does not disclose its detection thresholds.
Published 18 September 2026. Source checked 21 September 2026.
Who this affects
Businesses using the affected chat widget with automated follow-up. Confirm the controls in your own Growthcenter account. A different website form or chat product is not established as covered by this announcement.
Our analysis: what it means for your business
A quieter inbox is not enough to judge this setting. The useful question is whether staff can find and resolve a genuine enquiry that was flagged. Assign responsibility for that queue before relying on automated pauses.
Hypothetical example: a local repair business receives a legitimate request that is flagged during a busy period. A coordinator checks the contact history and request, then uses an appropriate permitted response. The flag alone should not become a lost-lead label or an instruction to override the person’s contact preferences.
What to do next
- Inspect each active widget rather than assuming its protection follows the default for newly created widgets. Record the selected channels and who reviews flags.
- Use the documented tag and activity history to investigate a missed follow-up. Check the reason for any pause before changing a contact’s messaging state.
- Review confirmed spam and genuine flagged enquiries separately. Keep permission and opt-out choices intact; do not release an entire flagged queue just to clear a count.
ANALYSIS / BUSINESS CONTEXT
Where to spend your attention today
These updates address different parts of the same enquiry path. One moves information between tools; the other controls whether follow-up leaves the system. A small business benefits from knowing who owns the exceptions, not simply from adding another automation.
Start where a missing field or silent pause could affect a customer commitment. If the current process works reliably and neither change solves an observed problem, document that decision and leave it alone.
Practical checks
- Ask the administrator which announced capabilities are actually available, what they cost and which live processes would be affected.
- For one relevant process, write down the expected record, the person responsible and the evidence required before telling a customer the next step is confirmed.
- Keep a short test record and a way to restore the previous setup. Measure resolved enquiries and avoidable administration before claiming an improvement.
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 →