When you are under a house, your phone is still selling the next job.
A managed AI receptionist for plumbing businesses that answers calls while you are on site, captures the details needed for a callback or booking and routes exceptions to the named person.
- Job type
- Hot water system, no hot water
- Location
- Fictional Hills, inside service area
- Urgency
- Same day, not a gas or safety hazard
- Next step
- Photos requested by SMS, callback booked
Count the jobs your voicemail never shows you
How many calls arrive in a typical week? How many are missed while you are on a job? What percentage normally becomes a booked job, and what is an average job worth?
When the phone rings during a job, what happens now: voicemail, a callback later, a text, or nobody is sure? Which of those calls are worth interrupting a job for, and which are not? Use that answer to set the routing rule, not to assume every missed call is valuable.
This is not a promise that every missed call becomes a job. It is the number worth investigating before deciding that voicemail is free.
Treat the booking-rate input as a clearly labelled scenario assumption, ideally grounded in your own job data. It is not a Taachi performance claim.
The customer does not know you are busy. They only know you did not answer.
A homeowner has water coming through the ceiling. A landlord needs a repair before the tenant moves in. A builder wants a reliable subcontractor for the next stage. They call while you are carrying gear, driving between jobs or explaining a quote.
You mean to call back. Then the next job starts.
By the time you return the call, the customer may already have spoken to the next business. You never see that loss in your job-management system, because the job never entered it.
The phone is not an admin problem. It is the first stage of the next sale.
Turn a ringing phone into a usable callback or booking request
Taachi does not pretend to be the tradie. It does the work that gets lost between the ring and your first callback: answer, listen, capture and route.
The result is a cleaner handoff to the person who can price, diagnose or attend the job. The receptionist does not quote work it is not authorised to quote, promise an arrival time it cannot verify or give technical advice outside its approved script.
Taachi does not assess danger. If a caller describes immediate danger or a medical emergency, approved emergency-services wording takes precedence immediately, and the call follows your on-call path from there.
The receptionist does not quote prices, hourly rates or job durations beyond wording you approve, and does not promise a technician will attend at a time your calendar has not confirmed.
Three calls worth testing
Each one runs on the rules your business approves, tested before a live caller ever reaches them.
For a plumbing quote, booking or callback request, the minimum record captures service type, the caller's description of the job, suburb or service address, property context, urgency, preferred timing, caller name, callback number and call timestamp, plus recording or consent status where the approved workflow requires it. The record lands in the agreed job-management system or callback queue, and the named follow-up owner is the plumbing office or on-call contact. If no authorised destination or follow-up owner is available, the receptionist must not imply that a request was handed over. Electrical, HVAC and building need their own scripts and evidence before this page claims them.
Failure paths worth inspecting
- Out of area
- The caller receives the approved service-area response and is routed only if a named destination has been configured.
- Human unavailable
- The receptionist states that no authorised person is available, records a callback only when an owner and next step exist, and makes no attendance promise.
- System outage
- The workflow uses the documented backup number or callback path. If the backup is unavailable, it says the request could not be captured and gives the approved contact instruction rather than implying success.
Do not show a generic AI demo. Show the call you actually miss.
- 01A real trade scriptA plumbing job call for the first proof workflow. Electrical, HVAC and building claims require their own scripts and evidence.
- 02A clear call outcomeCallback request, booking request, transfer or disqualification, tested in the open.
- 03A job recordThe details captured on the call, and where they land for your team.
- 04A failure pathWhat happens when the caller is unclear, outside your service area, or the on-call person is unavailable.
- 05Pilot scoreboardAnswered calls, qualified requests, booked jobs, transfers, failed calls and opt-outs.
Customer proof requires a measured pilot, a named trade and owner, a verified before-state, a defined pilot period and attributable operational outcomes. An outcome appears only after the underlying call records and follow-up data have been checked.
Worth asking before you buy.
Some do. Give them a direct path to you. The receptionist exists so every caller gets a useful next step, not so every caller is forced through automation.
It should not guess. Start with the calls and questions your business can define, then test the boundary. Technical diagnosis, pricing and exceptions stay with the person qualified to handle them.
That is the status quo to measure. How many calls do you return, how quickly, and how many callers still answer? Put your own numbers into the calculator before calling the process good enough.
You should not have to. The managed-service promise is that Taachi maps the workflow, configures the receptionist, tests it and manages agreed changes. Confirm the scope before you commit.
Service areas, job types, availability and escalation rules need to be explicit. A call outside the rules is routed or declined, not invented into a booking.
Let the call decide. Test the greeting, interruptions, trade vocabulary and handoff. If the experience does not match the standard you want customers to feel, do not launch it.
Built around the way you actually run jobs
- 01Review the callsReview the calls that arrive while you are on the tools, driving or quoting.
- 02Sort the call typesSeparate urgent, quote, booking, supplier and out-of-area calls.
- 03Write the rulesWrite the approved questions and handoff rules for each call type.
- 04Connect the workflowConnect the agreed phone and job workflow.
- 05Test the callsTest normal and awkward calls with you or your office team.
- 06Launch with monitoringLaunch with monitoring and a named change process.
Bring your service area, common job types, usual call questions and fallback contact. Do not submit customer details, passwords or credentials.
Where Taachi fits, and where it does not
- You regularly miss calls while on site, driving or quoting.
- A typical call can be captured with a repeatable set of questions.
- You have a person or process that can handle qualified follow-up.
- Job type, location and urgency rules can be written down.
- The value of one attended job makes the phone workflow worth measuring.
- Almost every call requires immediate specialist judgement.
- You have very low call volume, or a genuinely full order book.
- There is no one to action the captured request.
- You want a self-serve trade knowledge app rather than phone coverage.
- You cannot approve or test what the receptionist is allowed to say.
Your next job is already calling. Decide whether it gets voicemail.
Hear a realistic call, push it outside the rules and inspect the handoff. If it does not save you from the exact phone problem you have, do not proceed.
Hear one plumbing call, inspect the captured job record and test an out-of-area and unavailable-human path.
Managed AI reception for Australian trade businesses. The receptionist works within your approved rules. Technical advice, pricing authority and exceptions stay with your team.