A missed call to an Australian trades business usually becomes a job for the next name on the list. Before an AI phone agent is useful, four systems have to connect: job management, accounting, calendar and the phone line itself. ServiceM8 publishes a REST API, a Webhooks API and an add-on store. Tradify publishes no public developer API documentation — checked 2 September 2026.
That last sentence is the problem in miniature. The Australian AI-receptionist pitch names the same local stack every time — ServiceM8, Tradify, Xero, MYOB — but naming a product is not the same as connecting to it. Then there are the Australian bits: the Do Not Call Register Act 2006 for anything outbound, an ABN on every ATO tax invoice, an Australian caller ID and a Google Calendar the agent can read before it writes. Here is what a phone agent has to do for a trades business, and where the integration actually exists.
The first 30 seconds of a missed trades call
A customer with a blocked drain or a dead hot-water service is not shopping. They are working down a list of numbers until someone answers. Voicemail is a decision to lose that job.
In the first 30 seconds the agent has to answer, establish what has broken and where (trade type, symptom, suburb, property type, access), establish urgency honestly, and commit to something specific — a booked assessment window, a named callback time or a transfer. Never a vague promise that someone will be in touch.
An agent that takes a name and a number and stops has replaced voicemail with slower voicemail. The value is the structured job record landing where your scheduler can see it, which is an integration question, not a conversation-quality question. We have covered agents in field services and getting an inbound line ready separately.
Quoting versus booking: the line an agent must not cross
An agent can qualify a caller, capture the job details and book an assessment. It must not price a job it cannot see.
This is not caution for its own sake. A price given on the phone by something the customer reasonably believes speaks for your business is a representation your business made. For trades work the scope is unknown until someone is on site: what is behind the wall, whether the switchboard is compliant, whether the drain needs a camera, whether there is asbestos in the eaves. A number quoted blind is either one you lose money honouring or one you have to walk back in front of an annoyed customer.
Callers will push for a number anyway, and that moment has to be scripted rather than improvised. The workable answer is a real one: state the call-out or assessment fee if you publish one, say plainly that the job price depends on what the tradesperson finds, book the assessment, and hand to a human if the caller keeps pressing. Publishing the call-out fee removes most of this pressure, because the caller’s real question is usually what it costs to get you there.
What has to integrate before any of this is useful
Four systems, and each one has a different published integration surface. We checked every vendor’s own developer documentation on 2 September 2026. Where a vendor does not publish a capability, the table says so rather than guessing.
| System | What it is used for | Published integration surface (checked 2 September 2026) | What breaks if it is not connected |
|---|---|---|---|
| ServiceM8 | Job creation, dispatch, quotes, job cards, invoicing | REST API plus a Webhooks API; API key for private apps and OAuth 2.0 for public add-ons; public add-on directory that already lists Xero, QuickBooks Online, MYOB, Zapier and Office 365 | The agent takes a job nobody is dispatched to. Worst case two people are sent to the same address. |
| Tradify | Quoting, job tracking, timesheets, invoicing | Public developer API: not published. Tradify’s own site documents packaged integrations with Xero, QuickBooks and Stripe; there is no developer portal, no published webhook documentation and no API reference on tradifyhq.com | Nothing reaches the schedule automatically. Someone re-keys every call, which is the job you were trying to remove. |
| Xero | Invoicing, payments, GST, reconciliation | Accounting API v18 (base https://api.xero.com/api.xro/2.0) with OAuth 2.0 scopes, plus a Webhooks API — both specified in Xero’s own published OpenAPI descriptions. Webhook event categories are CONTACT, INVOICE, SUBSCRIPTION, CREDITNOTE, PREPAYMENT and OVERPAYMENT, with event types CREATE and UPDATE |
Nothing, immediately — Xero has no concept of your job. That is the point: Xero cannot be your scheduler, and there is no webhook that tells you a job was booked. |
| MYOB | Invoicing, payroll, GST, accounts | MYOB Business API, JSON, OAuth 2.0 for online company files and a token header for desktop files. Webhooks: not published on the MYOB Business API overview or its authentication documentation | No push notification of a paid invoice, so anything you build polls on a timer instead of reacting. |
| Calendar | Technician availability, assessment windows | Google Calendar API supports push notifications via watch channels on ACL, CalendarList, Events and Settings resources. Google states plainly: “Notifications are not 100% reliable.” | Double bookings. An agent that writes appointments without reading availability is a liability, not an assistant. |
| Phone service | Receiving the call at all | No common published surface — varies by carrier or SIP provider. Number porting, call forwarding and caller ID are configured with your provider, not through a vendor API | The agent never gets the call. This is the step people skip and then blame the agent for. |
What Zian actually integrates with today
Zian publishes integrations with HubSpot, Salesforce, HighLevel and Zapier. That is the list. We do not publish a ServiceM8 integration, a Tradify integration, a Xero integration or a MYOB integration, and you should not read this page as a claim that we do.
Connecting to any of those four would be bespoke work — scoped, built and tested — not a box ticked at signup. Treat it as a scoping conversation, not a feature. Our general write-up of CRM integration patterns covers the mechanics — field mapping, idempotency, sync direction — and applies here even though the products are different.
After-hours triage: emergency, or Monday morning?
An agent that cannot tell an emergency from a Tuesday job is worse than voicemail. Voicemail at least does not wake you for a dripping tap, and it does not tell a customer with water coming through a ceiling that someone will call in the morning.
The triage has to be written down by the business owner, not inferred by a model. A workable split:
- Wake the on-call tradesperson: gas smell, no power to the property, water actively entering the building, sewage overflow, anything involving a fault the caller describes as sparking, smoking or burning, and no hot water where the caller identifies a vulnerable occupant.
- Book first thing tomorrow: single dead appliance, one dead circuit with the rest of the property live, slow drain, no hot water in a household that can wait.
- Book normally: quotes, renovations, installations, maintenance, anything the caller describes as not urgent.
Two rules follow. The agent never talks a caller out of an emergency — if the caller insists it is urgent, it escalates, because the false-positive cost is one annoyed tradesperson and the false-negative cost is a flooded house. And the agent tells the caller which bucket they are in and what happens next, with a time. A vague promise to get back to them does not qualify.
What the agent must hand to a human, not answer
Three categories, hard-coded rather than left to judgement:
- Anything safety-related. Gas, electrical faults, structural concerns. The agent captures the address, gives your standard isolate-or-leave advice, and escalates to a licensed person. It does not diagnose.
- Anything that commits a price. Discounts, variations, warranty disputes and quote-matching requests belong to a human.
- Anything where the caller is distressed. Flooded home, a job gone wrong, a complaint. A distressed customer processed by a script is how a recoverable problem becomes a public one.
Handover only works if the context travels. A customer who has explained the fault twice will not explain it a third time, so the context transfer on handoff — what was said, the address, the urgency flag, the job type — is the difference between a warm transfer and starting over.
Australian rules: the Do Not Call Register, and your ABN
Inbound and outbound are governed differently. The Do Not Call Register Act 2006 governs telemarketing calls, which the Do Not Call Register defines as a voice call made to a number to offer, supply, provide, advertise or solicit goods or services, land or an interest in land, a business or investment opportunity, or donations. Answering a call your customer placed is not one — nobody rang them to offer anything. The register separately lists calls that are not considered telemarketing at all, and that list includes solicited calls about orders, requests or customer enquiries, as well as appointment reminders and rescheduling. That is not a blanket exemption. For genuine outbound — reactivating old customers, chasing cold quotes, ringing a purchased list — the register applies. The prohibition lifts where the account-holder consented, or where you washed the list against the register in the last 30 days and the number was not on it. Washing a list is not a licence to ring everyone on it. Checked 2 September 2026. Longer treatment in the Do Not Call Register and AI voice agents.
Identifiers matter downstream. The invoice at the end of this chain is a tax invoice, and the ATO requires the seller’s identity and ABN on it, with the buyer’s identity or ABN also required on sales of $1,000 or more. On commercial and strata work that threshold is routine, so the agent asking who the account is for is not admin — it decides whether the invoice is valid. Settle your caller ID before you go live too; we cover that in choosing an Australian phone number for a voice agent.
This is general information, not legal advice. The Do Not Call Register rules turn on the facts of each call — if you are unsure whether a call you plan to make is telemarketing, check the register’s own guidance or get advice.
Who should not buy this
A sole trader taking six calls a day should not buy an AI phone agent. At that volume you can return every missed call in the ute between jobs, the integration work costs more than the missed calls do, and a caller who reaches a machine instead of the person doing the work is a downgrade in a business where the relationship is the product.
The threshold is structural, not a call count. It starts to make sense when calls arrive faster than anyone can answer them, when they arrive outside rostered hours, when jobs already run through a scheduling system rather than a group chat, and when a missed call reliably becomes a lost job. The Australian Bureau of Statistics counted 2,814,778 actively trading businesses at 30 June 2026, of which 996,203 employed anyone at all; non-employing businesses grew fastest of any size band in 2025-26, up 4.8 per cent or 83,105. Most Australian businesses have no staff, and most of those should fix their voicemail greeting and call diversion before buying anything.
Frequently asked questions
Does Zian integrate with ServiceM8 or Tradify?
No. Zian’s published integrations are HubSpot, Salesforce, HighLevel and Zapier. We publish no ServiceM8 integration and no Tradify integration, and nothing on this page should be read as one. ServiceM8 does publish a REST API and a Webhooks API, so anything built against it would be built to that documentation. Tradify does not publish a public developer API, so any connection there would be bespoke. Either would be scoped work, not a setting.
Should an AI phone agent quote a price on a trades job?
No. It can state a published call-out or assessment fee and book the assessment. It should not price a job whose scope nobody has seen, because a price given on your line is a representation your business made. When a caller presses for a number, the agent states the assessment fee, explains that the job price depends on what the tradesperson finds, and hands over to a human if the caller keeps pushing.
Will bookings appear in Xero automatically?
No, and that is not a gap in Xero. Xero’s published webhook event categories are CONTACT, INVOICE, SUBSCRIPTION, CREDITNOTE, PREPAYMENT and OVERPAYMENT, with CREATE and UPDATE event types, per Xero’s own OpenAPI description of its Webhooks API. There is no job or scheduling event because Xero is an accounting ledger. The job has to live in your job management system, and the invoice flows to Xero afterwards.
Can an agent write into my calendar without double booking me?
Only if it reads availability before it writes, and only if you treat the calendar as advisory rather than authoritative. Google documents push notifications for the Calendar API on ACL, CalendarList, Events and Settings resources, and states in that same documentation that “Notifications are not 100% reliable” and to expect a small percentage of messages to be dropped. Build a reconciliation check; do not assume every event change reaches you.
Does the Do Not Call Register stop an agent returning a missed call?
Returning a call the customer made is not telemarketing. The Do Not Call Register defines a telemarketing call as a voice call made to a number to offer, supply, provide, advertise or solicit goods or services, and separately lists solicited calls about orders, requests or customer enquiries among the calls that are not considered telemarketing. Genuine outbound campaigns are a different matter: there the register applies, and the prohibition lifts where the account-holder consented, or where the list was washed against the register in the last 30 days and the number was not on it. Washing a list is not a licence to ring everyone on it. Checked 2 September 2026.
I am a sole trader taking six calls a day. Should I buy one?
Probably not. Return them yourself between jobs, fix your voicemail greeting and set up call diversion. An AI phone agent starts paying for itself when calls arrive faster than anyone can answer them, when they arrive outside rostered hours, and when your jobs already run through a scheduling system rather than a group chat.
Before you talk to any vendor
Ask which of your systems they have actually connected to, and ask them to name the API. If the answer is a logo wall rather than a documentation link, the integration does not exist yet. Then check from your own side — open ServiceM8’s developer docs, or ask Tradify directly what they will expose — before assuming the connection is somebody else’s problem.
Zian is in partner-application beta. If you run a trades or service business with real after-hours call volume and a job system worth connecting to, Apply For Partnership and tell us what you are running.