For businesses running Simpro
The call becomes a Simpro 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 Simpro while the caller is still on the line. Customer matched by phone, site from a verified address, one job and not two. Emergencies come straight to you.
Two minutes, your numbers, no email.
What lands in Simpro
During the call
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 electrician on the list.
- The answering service sent a message, and somebody still had to key the customer, the site and the job into Simpro on Monday.
- The same customer rang twice and there are now two jobs for one switchboard.
- The site on the job is what the caller said, not where the building is.
- A no-power call at 11pm waited in an inbox until 7am.
- Every vendor says it integrates with Simpro 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 Simpro by phone number. A caller who rings back gets a note on their existing job saying what changed.
After hours
Emergencies wake a person
No power, burst pipe, gas smell: it stops, rings your on-call number, and sends the transcript. Everything else is a job in Simpro for the morning.
What it does inside Simpro, verb by verb
Connected by OAuth to your own Simpro build, with webhooks for the return trip. It sees what the Simpro employee who authorises it can see, so a dedicated integration user is the tidy way to connect. No marketplace listing is needed.
| On the call | State | What that means |
|---|---|---|
| Find the customer by phone | Built | An existing Simpro customer matched on the caller's number, so a returning customer is not created twice. |
| Set up a new caller | Built | A caller Simpro has never seen is created as a customer with their mobile, and given a site from the verified address, because a Simpro job cannot exist without one. |
| Create the job | Built | A real service job against the right customer and site, with what the caller described on it. Written once, during the call. |
| Book the time | Built | The slot goes on the Simpro schedule against a tech qualified for the trade, if your calendar allows it. It can be moved or cancelled on a later call, with a note saying why. |
| Add the note | Built | What the caller said and what was promised, on the job where the tech will read it. |
| Update the stage | Built | The job stage moved when the call changes it, and stage changes made in Simpro come back to us by webhook. |
| Read quotes, invoices and history | Built | An existing customer asking about a job, a quote or what they owe gets an answer from the record, not a guess. |
| Draft a quote from your catalogue | Not yet | Simpro's API exposes catalogue parts but not how your prebuilds are priced, which is how most Simpro businesses quote. A quote request is captured as a job for a person to price. We will not price it ourselves. |
| Text a pay link for an invoice | Not available | Simpro's API does not expose the invoice pay link, so there is nothing for us to send. We can read the balance, the due date and whether it is paid; the invoice with its link still goes out from Simpro. |
Checked against the adapter as at 30 September 2026. The table has two rows that are not “built” because a table without them is worth nothing. Ask any provider you are comparing for theirs. On ServiceM8 instead? The ServiceM8 verbs are here.
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 you can build against a local stub. 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 the live step connects to your Simpro build by OAuth 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 Simpro write-back and the log. Flat monthly, no call caps, no per-minute overage, 30-day free trial.
See what it costs →Simpro stays the source of truth. The phone stops being the place jobs get lost.
See what it costs