Skip to main content

Melbourne Marketing Brief / #005 / NEWS & ANALYSIS

Call recording bills, AI workflows and cleaner company records

Published by · · AI-assisted research and writing

18 September 2026 · News and analysis · Includes a Labs feature

Today’s useful changes sit behind the enquiry: how recorded calls are measured, how follow-up workflows are drafted, and how several contacts are connected to one business. Each needs a different check before it earns a place in your daily operations.

The three announcements below are dated 17 September and were checked on 18 September, Melbourne time. The Growthcenter items come from HighLevel’s underlying-platform changelog; availability, permissions and charges in an individual Growthcenter account have not been verified.

CHECK YOUR PHONE-SYSTEM REPORTING

1. Twilio changes how recording usage is measured

Confirmed operational change · Migration begins 17 September · Account migration not verified

What changed

Twilio says it began migrating accounts to an updated Voice Recording Storage billing system on 17 September. The announcement says recording-storage pricing is unchanged, but daily usage figures in the Console or Usage API may change because measurement is more accurate.

This is a storage-billing update. It is separate from the Functions Classic migration previously covered in this publication. Twilio does not give an Australian account-by-account migration schedule in this notice.

Twilio’s recording-storage billing announcement

Published 17 September 2026. Source checked 18 September 2026.

Who this affects

Businesses retaining call recordings in Twilio, including some custom AI receptionist installations. If a managed phone provider handles storage, ask whether this change reaches your reporting or bill. Businesses with no Twilio recording storage can leave this item alone.

Our analysis: what it means for your business

A changed usage chart can be easy to misread as a busier phone line. Storage usage, incoming calls and booked work answer different questions. Keep those reports separate when reviewing marketing performance. Unchanged pricing also does not establish that every customer’s billed total will remain identical.

Hypothetical example: a Melbourne plumbing office sees a different daily storage figure after its account migrates. Before attributing the movement to an advertising campaign, its administrator asks the phone provider to reconcile retained recordings, measurement and the relevant billing period. This is an example of a check, not a reported client result.

What to do next

  1. Ask your phone provider whether your account uses the affected storage and whether its billing migration has occurred.
  2. Keep comparable before-and-after usage and billing records, with the reporting period and units visible. Ask for an explanation of any discrepancy.
  3. Do not change call routing or delete retained recordings just to flatten a chart. Review any retention decision separately with the people responsible for those records.

TEST A USEFUL FOLLOW-UP PROCESS

2. Workflow AI gets another way to start a draft

Confirmed underlying-platform announcement · Growthcenter access and costs require checking

What changed

HighLevel has made its existing Workflow AI builder available through Ask AI, including the WhatsApp interface. Users can describe a workflow, inspect the generated steps and request changes in conversation.

The new part is access through Ask AI. Manual editing, final testing and publication still happen in the workflow builder. The announcement does not establish that this feature is enabled or free in every Growthcenter account.

HighLevel: Workflow AI inside Ask AI

Published 17 September 2026. Source checked 18 September 2026.

Who this affects

Owners or administrators who already manage enquiry and follow-up workflows in Growthcenter. This may be useful when a process needs a new draft; it is not a reason to replace an existing reliable workflow or adopt paid tooling without checking its cost.

Our analysis: what it means for your business

The hardest part of an enquiry workflow is often defining what should happen when the usual path fails. A natural-language request can leave that decision unstated. Before choosing how to build, specify the trigger, who should act, when follow-up stops and what happens if delivery fails.

Hypothetical example: a cleaning business wants an internal reminder for an unanswered quote. The draft should distinguish an open quote from one already accepted or declined. Its owner should see who receives the reminder and what happens if the same enquiry is submitted twice. A convincing-looking diagram is not evidence that these cases work.

What to do next

  1. Confirm feature access and usage charges with your administrator. Use the existing manual builder if that already meets the need.
  2. Write a short process specification with the trigger, required fields, assigned person, timing and stop conditions. Keep customer data out of an exploratory prompt.
  3. Test synthetic cases for a normal enquiry, a duplicate, an after-hours arrival and an already-booked customer. Inspect every recipient and action in the builder before deciding whether to publish.

CONSIDER FOR BUSINESS-TO-BUSINESS WORK

3. A Labs feature can connect contacts to companies

Confirmed Labs feature · Underlying platform only · Growthcenter account not inspected

What changed

HighLevel’s new domain-based company automation can associate a contact with an existing company or create a company record using the contact’s email domain. Optional enrichment supplies a company name and logo. The documented setup starts in Labs.

The platform says it respects existing associations, excludes common free-email providers and uses exact domain matching. A main domain and its subdomain are treated separately. Enrichment is best effort, so a completed record is not proof that all details are correct.

HighLevel: company creation and association by email domain

Published 17 September 2026. Source checked 18 September 2026.

Who this affects

Commercial cleaners, accountants, consultants and other providers dealing with several people at one customer business. It is less relevant to a household-service pipeline where most enquiries use personal email addresses.

Our analysis: what it means for your business

Grouping contacts can make a customer history easier to follow, but an email domain should not silently become a service address or an access decision. One organisation can have several sites, and the person requesting a quote may differ from the person approving it. Keep those distinctions explicit.

Hypothetical example: a commercial cleaner receives enquiries from two branches using the same corporate email domain. The contacts may belong to one company, while their site addresses, quotes and appointment instructions must remain distinct. Company-level organisation should help the office understand that relationship, not collapse two jobs into one.

What to do next

  1. Check whether the Labs option is available and identify who is responsible for reviewing company matches.
  2. Try a small set of synthetic contacts covering a main domain, subdomain, personal email and existing association. Inspect the results and exclusions.
  3. Keep job-site details and booking authority in their own fields. Review staff access and any downstream automation before using the new associations more widely.

ANALYSIS / BUSINESS CONTEXT

Where to spend your attention today

Give these checks to the people who own the affected work. A recording-usage question belongs with the phone-system provider and the person reviewing the bill. A workflow draft belongs with the person responsible for the follow-up. Company matching belongs with the person keeping customer records accurate.

For a small operator, the useful outcome may be deciding that no change is needed. If your business has no retained Twilio recordings, no workflow to improve and no company-level customer records, these launches need not become another project.

Practical checks

  1. Identify which of the three capabilities your business actually uses or needs. Record account availability before planning an implementation.
  2. Choose one small, reversible check with a named owner. Write down the expected result before testing, using synthetic records where possible.
  3. Keep the evidence: a usage reconciliation, a workflow test result or a reviewed contact-to-company match. A successful software action alone does not prove an enquiry became a booked or paid job.

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 →