AI Email for Brisbane Businesses

No. Yes AI is a Melbourne business, Australian owned and operated, and we deliver to Brisbane clients remotely. There is no Brisbane team and no local presence. On timezones: Queensland does not observe daylight saving, so we are in step with you for roughly half the year and an hour ahead of you for the other half — which means from October to April our 9am is your 8am, and we book around your day rather than ours. That is the entire practical difference, and we would rather state it plainly than let you find out when a meeting invite arrives an hour early.

Because in Queensland some of that email is not correspondence — it is a legal instrument with a clock attached. Under the Building Industry Fairness (Security of Payment) Act 2017 (Qld), a payment claim can arrive by email, and once it does, you have a statutory period in which to respond with a payment schedule. Miss that window and the consequence is not a stern letter: you can become liable for the full claimed amount and lose the ability to argue about it. Now consider what a generic AI email tool is built to do — triage, categorise, auto-acknowledge, tidy the inbox — and consider what happens when it confidently files a payment claim as a routine invoice query. The tool has not just wasted your time. It has cost you the right to dispute. That is the specific risk this page exists to name.

The rule is that the AI escalates, it never disposes. Anything that looks like it might be a payment claim, a payment schedule, a notice under the contract, or an RFI carrying a deadline gets flagged to a named human and stays flagged until that human clears it. It does not get an automated acknowledgement, it does not get auto-filed, and it does not get "handled". We deliberately tune this to over-flag: the cost of a person spending ten seconds deciding that something was not a payment claim is trivial, and the cost of the machine getting that call wrong once is the claimed amount. Where the AI genuinely earns its money is everything around those instruments — the supplier chasing, the document requests, the progress updates, the forty routine questions a week — none of which starts a clock.

It can be configured to, and in a construction chain we will argue against it for anything that commits you. Australian Consumer Law applies to what your business says regardless of who or what typed it — an automated misrepresentation is still a misrepresentation, and the liability is yours rather than the model provider's. A model will confidently agree to a variation, accept a program date, or say something about scope that reads as agreement, in your house style, which is exactly what makes it hard to catch on a skim. Where auto-send is genuinely safe is acknowledgement traffic that asserts nothing: "we have received this, your reference is X, a person will respond by Thursday". Everything that commits you waits for a person.

To a model provider, and you should know which one. For the AI to draft a reply it has to read the email, so the contents are sent to whichever provider runs the model. If that provider is overseas, that is a cross-border disclosure under Australian Privacy Principle 8 of the Privacy Act 1988, and you stay accountable for what the recipient does with it. We will tell you, per component, which provider processes what and where it runs. What we will not do is hand you a blanket "your data never leaves Australia" assurance, because for anything involving a large language model that claim needs examining rather than asserting.

For construction, the Building Industry Fairness (Security of Payment) Act 2017 (Qld) is the one that most shapes how the system should be designed, because it turns particular emails into deadline-bearing instruments. The Queensland Building and Construction Commission Act 1991 (Qld) governs licensing and conduct for the sector generally. On privacy, the federal Privacy Act 1988 and the Australian Privacy Principles are the baseline for private-sector businesses, and Australian Consumer Law applies to anything you say to a customer. The Information Privacy Act 2009 (Qld) covers Queensland public sector agencies and can reach private businesses through contracted service arrangements — relevant if you hold Queensland government work. We map the ones that actually apply to your correspondence rather than reciting the list.

Storage can be, and that is the easy half of the question. The half that matters is inference: the moment an email is sent to a model to be read and drafted against, the question becomes which provider runs that model and in which country. Some are hosted in Australia, some are not, and the ones that are not put you into APP 8 territory. We will show you, component by component, exactly where your correspondence goes rather than giving you a marketing answer that falls over the first time a head contractor sends you an assurance questionnaire.

Yes, and the reasoning is the same even where no statute is involved. A five-person accounting practice, a dental clinic or a tour operator gets the same repetitive correspondence a large firm does, without anyone spare to handle it. The value is in the routine layer: the same questions answered for the fortieth time, the booking confirmations, the follow-ups everyone intends to send. The test is the same one we would apply to a builder — is this email routine, or does it commit us to something? Routine gets drafted. Committing waits for a person. Plans start at $149 per month, so the arithmetic is simply whether the routine layer costs you more than that in someone's time.