For businesses running ServiceM8

The call becomes a ServiceM8 job. Not a message.

An AI receptionist on your own number that says it is an AI, takes the job properly, and writes it into ServiceM8 while the caller is still on the line. Client matched by phone, address verified, one job and not two. Emergencies come straight to you.

Work out what missed calls cost you

Two minutes, your numbers, no email.

What lands in ServiceM8

During the call

ClientMatched on mobile
AddressVerified against Maps
JobHot water, no supply, house of four
TypeRoutine, same day
BookedTomorrow 7:30am

Texted to you with the transcript attached. A second call from the same number adds a note to this job instead of creating another.

The problems this is for

If three of these are a Tuesday you have had, the rest of the page is worth reading.

  • The after-hours call went to voicemail and the caller rang the next plumber on the list.
  • The answering service sent a message, and somebody still had to type the job into ServiceM8 on Monday.
  • The same customer rang twice and there are now two jobs for one hot water system.
  • The address in the job is what the caller said, not where the house is.
  • A burst pipe at 11pm waited in an inbox until 7am.
  • Every vendor says it integrates with ServiceM8 and none of them will say what that means.

Before it writes

The address is verified, the job type is from a list

The address is resolved against Maps before a job can exist, and the job type is chosen from your own fixed list: emergency, routine, or quote. The model talks; it does not get to invent either.

One job, not two

Second call, same number: a note, not a rival job

Before anything is created it checks our own call ledger and then ServiceM8 by phone number. A caller who rings back gets their existing job updated, with a note saying what changed.

After hours

Emergencies wake a person

Burst pipe, no power, gas smell: it stops, rings your on-call number, and sends the transcript. Everything else is a job on the board for the morning.

What it does inside ServiceM8, verb by verb

Connected by OAuth to your own ServiceM8 account, with webhooks for the return trip. No marketplace listing is needed and nothing is copied out of ServiceM8 into a database of ours.

On the callStateWhat that means
Find the client by phoneBuiltExisting ServiceM8 client matched on the caller's number, so a returning customer is not created twice.
Create the jobBuiltA real job against the right client, with the verified address and the job type on it. Written once, during the call.
Book the timeBuiltThe slot goes on the schedule if your calendar allows it, and can be moved on a later call.
Add the noteBuiltWhat the caller said, what was promised, and the reference texted to them, on the job where the tech will read it.
Update the statusBuiltJob status moved when the call changes it, so the board reflects the phone rather than lagging it.
Read quotes, invoices and historyBuiltAn existing customer asking about a job gets an answer from the record, not a guess.
Draft a quote from your material listNot yetServiceM8 exposes the material list, and we have not wired it to quoting. A quote request is captured as a job for a person to price. We will not price it ourselves.

Checked against the adapter as at 26 September 2026. The reason the table has a “not yet” row is that the table is worth nothing without one. Ask any provider you are comparing for theirs.

The rules under every call

How we build, not legal advice. The long version is the compliance paper.

  • Says it is an AI, first

    Every call opens with the AI identification and the recording notice before anything else is said.

  • Do Not Call Register

    Every outbound number is washed against the register before a call. If the register cannot be checked, the call is not made.

  • Calling hours, by state

    Outbound calls land inside the permitted hours in the customer's own state, public holidays included.

  • Consent to the strictest state

    Victoria, Tasmania and the ACT need every party to consent to recording. We cannot know where a caller is, so that is the standard on every call.

  • A record on every call

    Recording, transcript and what was written into your system, kept under a proof id you can pull up when a customer disputes it.

What stays with a person

  • Quoting a price on the phone, or agreeing to a variation.
  • Anything where the caller is upset, or the job already went wrong.
  • Safety advice, and anything implying a licence the agent does not hold.
  • Deciding whether to break tomorrow's schedule for tonight's emergency.

Build it, or point a number at us

The whole workflow is published as an open standard with a ServiceM8 stub to build against. You only pay us for the live number behind it.

Free

Build it yourself

The Booked After Hours standard: eight checks in order, the job taxonomy, the escalation rules, and a pass test you can stage on your own phone. The scaffold runs against a local mock and swaps to your ServiceM8 account when you are ready.

Open the standard →

Monthly

Point your after-hours number at us

Keep the number you advertise and forward it out of hours. We run the live line, the disclosure and consent, the ServiceM8 write-back and the log. Flat monthly, no call caps, no per-minute overage, 30-day free trial.

See what it costs →

ServiceM8 stays the source of truth. The phone stops being the place jobs get lost.

See what it costs
Using ServiceM8's own connector in Claude? What to set up first, and a standard for each job you automate.
Choosing between an AI, an answering service, and a person? The honest comparison, including where a human service still wins.
Comparing AI receptionists that work with ServiceM8? Twelve priced from their own pages, sorted by whether they write a real job.