QuoteBack and ServiceM8
Missed calls become ServiceM8 jobs.
You already run the jobs through ServiceM8. The gap is the enquiry that never becomes one, because it arrived while your hands were full and nobody wrote it down. This closes that gap and puts the result where you already look.
What happens between the missed call and the work order
- 01
The call rings out
A missed call on your business number is ruled missed and queued. Nothing is sent from a rule you did not set.
- 02
It texts them back
In seconds, in your business name, asking what they need and where they are. Most people answer a text they would never have left a voicemail on.
- 03
It works out the job
It reads what they wrote, matches it against your price book, reads the address back to confirm it, and asks for anything still missing.
- 04
It prices it from your book, or it does not
Under your limit and matched to a line you set, it quotes and books. Over your limit, complex, or a job you named as always-yours, it collects everything and hands it to you instead.
- 05
It creates or matches the client
Your existing client is found rather than duplicated. A new one is created with the contact details from the conversation.
- 06
It writes the job in, with the conversation attached
A work order against that client, and the whole exchange added as a note, so whoever opens the job can read exactly what the customer said and what was promised.
What it touches in your account
- Client record
- Found and matched if they already exist, created if they do not.
- Job
- Created as a work order with the address, the job description and the quoted total.
- Note
- The full conversation, added against the job.
- Reschedule
- Moves the date and leaves the status alone.
- Cancel
- Maps to Unsuccessful and reads back as cancelled.
- Nothing else
- No invoices, no staff, no settings, no pricing in your account is touched or changed.
What has actually been run against a real account
- 13 August 2026
Work order #10
A messy six-message conversation produced a work order in a real ServiceM8 account, with the qualification note attached and the client record created. Booking reference REL-0003. Thirteen assertions checked, including that a retry created no duplicate and that no call was made to ServiceM8 on the customer's own request path.
- 16 August 2026
Work order #11, end to end
A signed missed-call webhook, ruled missed, turned into a text back, followed through six customer messages to a quote, a booking, and work order #11 with its note attached. The SMS sender was simulated in that run; everything else was real.
- 23 August 2026
The job lifecycle
Rescheduling and cancelling had been declared capabilities that nothing had ever exercised against a live account. Both were run: the reschedule moved the date without touching the status, the cancel mapped to Unsuccessful and read back as cancelled, and an empty change correctly made no request at all.
The day it could not write to ServiceM8
On 28 August the whole chain ran on deployed infrastructure in Sydney and the ServiceM8 write failed with an HTTP 402: the trial account had lapsed two days earlier. The customer still got their price and their booking reference. The conversation was recorded as integration=failed with the reason attached, so a person could see exactly what had and had not happened. That is the designed behaviour under a provider outage, and it is the only way anybody ever gets to watch it: by having one.
Where it stands today
The API-key path is built and verified against a real account on the dates above. The trial it was verified in expired on 26 August 2026 and ServiceM8 confirmed on the 29th that partner status survives a paid subscription, which is the path being taken. If you run ServiceM8 and want this pointed at your account, that is a conversation worth having now rather than later, because your price book and your rules take longer to get right than the integration does.
Not on ServiceM8?
Then the finished job arrives as a text on your phone with everything in it, and the last line of that message tells you plainly that there is no job system holding it. The integration is a convenience for people who already have one, not the thing that makes this work.
Run ServiceM8? Let's put your own rates in it.
Bring your price list and your ServiceM8 account. Thirty minutes is enough to see it write a job you recognise.
Talk to me about it