Guides & Blog · 2026-08-13 · eWEB TEC
Last reviewed: 13 Aug 2026
ServiceM8 + AI: What to Automate (and What Must Stay Human)
Use AI in front of ServiceM8, not instead of it. Let it capture the job and draft the quote from your price list. A human accepts anything with a dollar figure outside the band. Only then write the job into ServiceM8.
Most of the “AI for tradies” pitches we see skip the job system. That is backwards. If the office already runs ServiceM8, the agent has to speak ServiceM8 — job type, suburb, scheduled window — or you will retype everything after the call.
The rails, in one table
| Step | AI may do | Human must do |
|---|---|---|
| Missed call / web lead | Answer, take suburb and job type, SMS the office | Anything that sounds like a complaint |
| Quote | Draft from the written price list | Send if the figure is outside the band or the job is new-to-you |
| Follow-up | Day-2 and day-7 chase on unanswered quotes | Stop or change tone if the customer replied annoyed |
| Write to ServiceM8 | Create the job after accept, with mapped fields | First fortnight of write-backs, until the mapping is trusted |
| Invoice / Xero | Nothing on day one | Always, until you deliberately expand the rails |
Write the catalogue before you touch an API
ServiceM8 cannot save you from a price list that lives in the owner’s head. Spend a morning on standard jobs, inclusions, exclusions and travel zones. The quoting walkthrough is the long version of that step.
What a good ServiceM8 write-back looks like
- Job type matches a real ServiceM8 category, not a paragraph of waffle
- Suburb and site notes in the fields the field staff already read
- No second “AI jobs” pipeline that nobody opens
- A failed write-back emails the office instead of failing silently
Tradify, email, or “we’ll move later”
Same rails if you are on Tradify. If you are still on a shared inbox, do not buy ServiceM8 the same week you add an after-hours agent. Capture the lead cleanly first. You can write into a job system when the office is ready.
Privacy and recordings
Call audio and the customer’s name and suburb are personal information. Know where they sit and how you delete one. See AI agents on Australian soil. We will not pretend a US model is onshore because the van is in Dee Why.
How we scope this
Usually a narrow after-hours pilot, then quote drafts, then ServiceM8 write-back. That is the Workflow Build on AI workflows and the tradie vertical on AI for tradies. Discovery call only — no public package price.
Autonomy is optional after you have watched it for a fortnight.
FAQ
Does this replace ServiceM8?
No. ServiceM8 (or Tradify) stays the job system. AI drafts and captures. Replacing the job system in the same month you add AI is how both projects fail.
Can AI create the invoice in Xero by itself?
Not on day one, and not without a person if money is involved. Start with a draft quote. Invoice automation is a later Workflow Build with rails.
We use Tradify, not ServiceM8 — does this still apply?
Yes. Same rails: catalogue, approval on price, write-back after accept. The field names change; the discipline does not.
What if a caller asks for a job we do not do?
The agent should say no and offer a callback, not invent a scope. Write the three jobs you refuse into the script before you go live.
Is this only for Sydney tradies?
The workflow is Australia-wide. On-site IT from eWEB TEC stays Northern Beaches and North Shore.
Want this set up on your stack?