Part of our guide to AI voice agents in Australia: an operator's guide to calls, SMS and the rules
On this page · 6 sections
At the end of a site visit, a tradesperson may have ten minutes to return calls. A transcript of six conversations is a poor starting point. Give them a queue that distinguishes a customer waiting at a gate from a new enquiry about work next month. Each item needs a clear next action and enough context for the caller to feel remembered when the business rings back.
Design the list backwards from the next call
Ask dispatch to sort a few ordinary missed calls into three piles: existing booking, new job and needs a person now. Define the business's own route for each. Do not ask a phone assistant to diagnose faults or improvise emergency advice. Give it an approved handover route and an explicit fallback if the intended person cannot pick up. Rehearse those paths with staff before using them with customers.
Collect the minimum detail for the next decision. For a new enquiry, suburb and broad job type may be enough to route a callback. For a customer meeting an installer, the job reference and access instructions may be more valuable. A caller asking whether the business covers their suburb should not have to dictate their full history before receiving a response.
Use a short opening and read back the fragile detail
Illustrative opening: “Thanks for calling. I'm the automated assistant taking messages for the team. Are you calling about a booked job or a new enquiry?” If the caller wants a person, capture that preference and follow the agreed route. The opening should set an accurate expectation about what the assistant can confirm during this call.
Suppose the caller says the crew needs the rear entrance at number eighteen, not number eighty. Read the critical detail back. “I've written rear entrance at number eighteen. Is that right?” Distinguish this from confirming the booking. The assistant can verify the message while leaving the arrival time for dispatch to confirm. A short confirmation of one fragile fact is often worth more than a word-for-word summary.
| Caller says | Queue entry | Dispatch action |
|---|---|---|
| “I am at the gate for today's job” | Existing job, access issue, customer waiting | Match job reference and ring assigned crew |
| “Can someone quote a bathroom repair?” | New enquiry, suburb, preferred callback window | Assign estimator to qualify scope |
| “Please use my work number before lunch” | Preferred number and contact window for this request | Read back number and flag the time for the return call |
| “I want to speak to a person” | Human callback requested | Use the agreed escalation route and record its outcome |
Handle weak signal, repeat callers and changed details
People call from worksites, noisy vehicles and places with poor reception. Test names, street numbers and callback numbers with realistic background noise. If a detail remains unclear after a sensible repeat, let the assistant mark it unresolved and hand off. A field containing a confident guess can be worse than an empty field because the dispatcher has no reason to check it.
Try a caller who rings twice. On the second call they offer a different time or say the gate has now opened. The queue should keep enough history for a dispatcher to reconcile the messages. Matching on a shared office phone number alone can accidentally merge two separate jobs. Use the business's normal identity and job checks before updating an existing booking.
If the caller hangs up during collection, distinguish an incomplete message from a qualified enquiry. A queue item might say that a caller mentioned a current job but provided no reference. The dispatcher can decide whether an authorised return call makes sense. Counting every interrupted call as a booked lead will make the pilot look productive while the office receives unusable work.
Keep customer promises visible to the human dispatcher
Write a list of phrases that make commitments. “The team will be there at three”, “that part is covered” and “we can do it for the same price” all change what the customer expects. Give the phone agent approved language for a callback request and require a person to confirm anything that depends on stock, travel, price or authority. Test the rule with a caller who pushes for a definite answer.
Agree what happens when the callback window cannot be met. Who sees the overdue item? Can they move it to a colleague? Does the customer receive an update only after somebody has accepted the work? A queue is reliable when staff can see what has gone stale. Calling it complete because a message was captured simply transfers the problem from the phone to the office.
Fulcrum Lyre describes its inbound voice and SMS capabilities. When testing any provider, demonstrate the handover with the dispatch tools your business uses. If you add promotional messages later, review ACMA's guidance on marketing messages and obtain appropriate advice for your use. Keep the immediate service callback distinct from a marketing campaign.
Measure what the crew can act on
For a short pilot, record how many inbound calls produced a callback item, how many items a dispatcher could act on without replaying the call and how many resulted in a customer actually reached. Keep a separate count for wrong numbers, duplicate messages and callers who wanted a human. These numbers answer different questions. A vendor reporting calls answered is measuring an earlier step than the business that wants jobs handled.
Listen to a sample using the business's approved process and privacy arrangements. Compare the queue entry with what the caller actually asked. Pay special attention to changes of date and words such as possibly, only and after. Missing one of those can turn “possibly after lunch” into an appointment the customer believes was locked in.
At the end of the trial, sit the dispatcher and one field worker together. Select a call that led to a clean handover and one that required chasing. Change the question that caused the unnecessary callback. Sometimes the best improvement is moving a short question earlier in the conversation, before a caller with weak reception drops out.
Related guides: AI voice agents in Australia: an operator's guide to calls, SMS and the rules · After-hours AI receptionist: what it should handle and when to hand over · Missed call text back: templates, timing and rules for tradies and clinics.
Frequently asked questions
Should an AI phone agent book every tradie enquiry?
Only confirm bookings when the business has established the required checks, current availability and explicit authority to commit a slot. For an initial callback pilot, ask for preferences and have dispatch confirm the appointment.
How do we cope with callers who prefer text?
Record the caller's preference for this request, read back the number and let the dispatcher choose the approved response. A preference for one service follow-up should not automatically enrol the caller in unrelated promotions.
What makes a useful end-of-day queue?
Each item has a reachable person, a reason to call, a job reference or clear qualification question, a due window and an owner. The dispatcher can see which items changed and which people are still waiting for an answer.
Sources
General information only, not legal, financial or professional advice. Check the source for your circumstances.


