Melbourne Marketing Brief / #040 / NEWS & ANALYSIS
HighLevel adds forms to manual bookings
Published by Ajay Dabhi · · AI-assisted research and writing
23 October 2026 · REPORTING + LOCAL BUSINESS ANALYSIS
A booking taken over the phone can lose useful details between the conversation and the calendar. HighLevel has announced a way to attach an intake form while staff create a service or rental booking. A separate update adds date filters before a HubSpot import. Both changes offer more control over what gets recorded, but neither removes the need to check the customer, the information and the next step.
Both underlying-platform announcements are dated 22 October 2026 and were checked on 23 October. They do not provide an Australian rollout schedule or a plan-by-plan availability table, and are not labelled beta in the retrieved posts. Growthcenter customers should verify their own account and configuration before relying on either feature.
This edition uses AI-assisted research and writing. Ajay is not claimed to have personally reviewed a customer account or tested these features. No booking, import, contact upload or customer-account change was performed. The business examples below are hypothetical.
CHECK / STAFF BOOKING FLOW
1. Put the intake details with the manual booking
Announced 22 October 2026 · Checked 23 October
What changed
HighLevel says staff can now attach a form while creating a service or rental booking in the in-app appointment modal. The configured form is selected initially, with an option to choose another. Name, email and phone fields are prefilled from the selected contact. Attaching a form is optional.
CAPTCHA, product-selling and payment elements are omitted from this staff flow. The submitted form can be viewed in appointment details, but forms cannot be attached or edited later for now. The announcement describes an in-app flow; it does not establish support in a particular mobile app.
Published 22 October 2026. Source checked 23 October 2026.
Who this affects
Australian service teams that manually create supported service or rental bookings, provided the feature is available in their actual account. Teams that use only another calendar or have no relevant manual-booking process can ignore this change. It is not evidence that every Growthcenter calendar or booking type has the feature.
Our analysis: what it means for your business
A useful operational test starts with what the person doing the job needs to know. For a service visit, that might be the access arrangement or the equipment involved. Recording those answers with the appointment could make the handover easier to follow. That is a possible process benefit, not a measured reduction in staff time or missed bookings.
Hypothetical example: a Melbourne equipment-hire business takes a phone booking. A staff member selects the customer, reads the prefilled details back, chooses the relevant intake form and records the pickup requirements. Before saving, they confirm those requirements with the caller. The team later checks that the appointment shows the submitted information. No real business test is implied.
The inability to edit the attached form later makes the correction process important. Decide where a changed access instruction or an incorrect answer will be recorded, who must see it and how the team will distinguish it from the original submission. Do not assume a second form can simply be attached afterward.
Keep three records conceptually separate: what the customer told staff, whether the appointment exists and whether any required payment has been received. Because payment elements are absent from this form flow, completing the intake does not establish payment. Use the business’s existing payment record and confirmation process.
What to do next
- Check the relevant service or rental booking type in the actual account. Confirm the configured form, fields and staff access rather than assuming a platform announcement applies.
- Use a labelled, authorised sample booking to check the selected contact, saved form and staff handover. Avoid putting real customer details into an unapproved test.
- Agree how corrections will reach the person delivering the service, and verify payment separately where it is required.
PLAN / MIGRATION SCOPE
2. Define the records you need before importing
Announced 22 October 2026 · Checked 23 October
What changed
HighLevel says its HubSpot importer now filters Contacts, Deals, Companies and Tasks in the Preview and import step using HubSpot Created Date or Last Modified Date. Conditions include relative periods and exact dates, with AND/OR combinations. Filters can differ by object or be applied across selected objects; preview counts update.
Filters are optional: leaving them empty imports everything. The vendor specifically says that “In the last” excludes today. The retrieved announcement limits supported fields to the two date fields; it does not describe a general filter for active customers or completed jobs.
Published 22 October 2026. Source checked 23 October 2026.
Who this affects
Businesses planning an authorised move from HubSpot into a HighLevel-based setup where this importer is available. Businesses staying in their current CRM, or using another migration method, need no action from this announcement. Growthcenter account availability has not been verified.
Our analysis: what it means for your business
A date rule is a selection mechanism, not a definition of business value. An older customer may still have an open job, while a recently modified record may be obsolete. Write the business question first—such as which work the new team must continue—then check whether the available date fields can select that population without losing necessary records.
Hypothetical example: an Australian maintenance business plans to move current work into a new CRM. A company record created years ago may be linked to a recent deal. Applying the same created-date cutoff to every object could select the deal while excluding the older company. This is a planning example, not a finding about how this importer handles that relationship; the announcement does not establish the outcome.
The preview count is useful for spotting a surprising selection, but it does not prove that contacts, companies, deals and tasks will be linked correctly after import. The migration owner should inspect representative relationships and account for records near the cutoff. Where today’s changes matter, review the exact displayed range instead of relying on the everyday meaning of “last month”.
Treat the import as a separate authorised change with its own owner and recovery plan. Confirm what downstream automations may run, retain an appropriate source record, and reconcile the result before staff depend on it. None of those checks was performed for this report, and a date filter is not evidence of marketing permission.
What to do next
- Define the required records and relationships for each object before choosing dates. Check older active customers as well as recent records.
- Review the exact displayed range and counts, including the exclusion of today for “In the last”. Do not leave filters empty unintentionally.
- Before a separately approved import, sample related records and confirm automation and recovery behaviour with the migration operator.
ANALYSIS / BUSINESS CONTEXT
Where to spend your attention today
The common decision is what staff should verify before saving. In the booking flow, it is the right customer and a usable intake record. In the import flow, it is the intended population and the relationships the business needs to continue its work. A new control is helpful only when the team knows what a correct result looks like.
Neither announcement establishes fewer errors, faster service or more enquiries for a particular business. Check the applicable workflow first, then measure any practical improvement against your own starting point.
Commercial context: Ajay Dabhi sells website and automation services, including Growthcenter-related work. The invitation below is separate from this reporting and analysis. Your existing booking administrator or migration operator may already be the right person to handle these checks.
Practical checks
- For manual service or rental bookings, confirm the actual form flow and a clear correction process.
- For a planned HubSpot migration, define the record selection per object and inspect boundary dates.
- Keep account availability, completed operational checks and business results as separate evidence.
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 →