AI receptionist for Australian service businesses

What a missed call actually costs

Nobody invoices you for a call you did not answer, which is exactly why the number never appears on a profit and loss statement. The cost is real, it is just unrecorded. It sits in the gap between the enquiry that rang and the job that went to whoever rang back first.

You do not need a study to size it. You need three inputs from your own business: the average value of the work you actually want more of, the number of calls a week that ring out, and the share of those callers who ring a competitor instead of leaving a message. Multiply them and you have a monthly figure. Whether that figure is forty dollars or four thousand is the only question that matters, because it decides how much engineering the fix is worth. A business losing four hundred dollars a month should buy a better phone plan. A business losing four thousand a month should redesign how the phone is answered.

There is a second cost that rarely gets counted: the callback. A message left at nine at night, returned at seven the next morning, is a second sale where the first one was nearly closed. The caller has already cooled, already rung someone else, already had a night to think about whether the job is worth doing now. Callback debt is the most expensive inventory a service business carries, and it does not show up anywhere.

Worth checking before you buy anything: pull your own call log for the last month and look at when the misses happen. They will not be spread evenly across the week. They cluster in the two hours you are on site and in the evenings when the phone is the only way in. That pattern, not the total, tells you what the cover has to do.

Why voicemail and a contact form are not cover

Voicemail is a place where enquiries go to become apologies. A caller with a burst pipe or a dead fridge is not going to record a thoughtful message and wait. The contact form has the same flaw in a different shape: it only converts people who are at a desk, and it produces a queue that somebody has to work through during business hours, which is exactly when nobody has time.

The structural problem is that both options move the work to later without reducing it. The call still happened, the customer still needs an answer, and now there is an extra step and a delay attached. An AI receptionist is worth the money only when it removes the delay rather than rescheduling it.

What an AI receptionist should handle

The test is not whether it sounds human. It is whether the job ends up in your calendar with the right information attached, and whether the person who reads it in the morning can act without ringing anyone back to ask what the job actually was.

Answering, on the second or third ring

Days, nights, weekends, public holidays, and the ten minutes you are under a house. The agent answers with the business name, not a menu, and it does not ask the caller to press anything.

Capturing the six things you always need

Name, mobile number, suburb, what the job is, how urgent it is, and any access detail (dog, gate code, parking, which unit). The number gets read back to the caller. A job booked with a wrong number is worse than no booking, because it looks solved.

Answering the questions you are tired of answering

Do you cover my area, how soon can you get here, do you charge a callout, do you work weekends, do you handle insurance work, can you quote from a photo. These are the same six questions every week. If the caller can be answered now rather than promised an answer later, some of them book on the call.

Booking against real availability

Not "someone will call you back". A real slot in the real calendar, with the arrival window the business can actually keep. The agent should be given the same calendar constraints a good office administrator works within, including the jobs that need a longer window and the suburbs that need travel time.

Following up the ones that go quiet

A confirmation message straight away, a reminder the day before, and one follow up on the enquiry that never booked. This is the work that never gets done on a busy week, and it is the cheapest revenue in the business.

Handing over with context

When it does hand over, it hands over properly: a written summary, the number, the suburb, what was said, and what the caller expects next. A transfer that drops a caller into a cold "hello?" is worse than the voicemail it replaced.

What it should not handle

An agent that improvises is an agent that will eventually promise something the business cannot deliver, in writing, with a timestamp. The refusal list matters as much as the script, and it should be written down and reviewed, not left to the model's judgement on the night.

• Complaints about completed work. These go to a person immediately. A caller who is already unhappy and reaches a machine learns that the business does not care.
• Price negotiation. The agent can quote published callout fees and nothing else. The moment it starts discounting, the margin is being negotiated by software.
• Estimates on work nobody has seen. It books the site visit. It does not guess a number, and it never implies the visit is free unless that is the actual policy.
• Safety situations. Gas smell, smoke, burning plastic, a burst main, someone locked out in the heat. The script for these is written with the owner, kept short, and includes what the caller should do and who gets woken up. Improvised safety advice is a liability, not a feature.
• Anything licensed or regulated. Insurance liability, strata decisions, medical or legal questions, debt and payment disputes. Take the details, promise a window, escalate.
• Anyone who asks for a person. Transfer immediately, without a pitch and without three qualifying questions first. The refusal to transfer is the fastest way to lose a caller who was ready to buy.

One more rule belongs in the design rather than the script: the agent is a receptionist, never a replacement argument. If a caller works out that they are talking to software, the correct experience is still a booked job and a straight answer about what happens next.

After hours is the real test

Anyone can answer at ten on a Tuesday morning. The value shows up between seven at night and seven in the morning, on weekends, and on the days the whole country is at the beach. That is when the caller has no alternative except the next number on the list.

What good after hours cover actually looks like:

• The same script. The caller gets the same answers and the same booking path at 2am as at 2pm. A separate, thinner after hours experience is a downgrade dressed as a service.
• A quiet hours rule. Only a short, written list of situations wakes a human. Everything else waits for the morning list. An agent that wakes the owner for a wrong number gets switched off in week two.
• A morning handover. The day starts with a summary: what came in, what was booked, what needs a decision, who is still waiting. Not a voicemail box and a bad feeling.
• Promises the calendar can keep. If the agent says "first thing tomorrow", tomorrow has to have room in it. The promise comes from availability, not from optimism.

What a good call sounds like

The script is where most of the quality lives, and it is written by the business, not generated fresh each time. Six rules do most of the work:

1. Say the business name in the first sentence, then ask one question.
2. One question at a time. Two questions in a row and the caller answers the second and forgets the first.
3. Two sentences maximum before the agent asks something. A caller who is talked at stops listening.
4. Read the mobile number back, digit by digit, every time.
5. End every call with what happens next and when. "Someone will be in touch" is not a next step.
6. If the line goes quiet, ask once whether the caller is still there, then offer a callback rather than sitting in silence.

Australian detail matters more than most vendors admit. Place names get mangled: spell them back, offer a read back for anything phonetic, and keep a local list of the suburbs and towns customers actually say. Callers say "the Gong" and mean Wollongong. They give a mobile as oh-four-oh-two and mean a number with no spaces in it. Small things, but they are the difference between a booking and a complaint about a robot.

What to measure in the first thirty days

An AI receptionist is measurable in a way that most admin changes are not, which is the strongest argument for trying one. Six numbers, all available from the call log and the calendar:

• Answer rate. Calls answered as a share of calls received, including the ones that rang out before.
• Time to answer. Median seconds, not average. Averages hide the terrible ones.
• Booked share. Calls that became a calendar entry with a full address and job description.
• After hours volume. How much of the demand arrives outside business hours. This is usually the number that settles the argument.
• Handoff reasons. Every escalation, with the reason attached. That list is the roadmap for what to teach the agent next.
• Booked to attended. The only number that is actually revenue. An answer rate with a poor show rate is a scheduling problem wearing a phone costume.

Pick one of these to move first and give it a target you would be embarrassed to miss. Nine metrics on a dashboard is how a project avoids being judged.

The Australian details that break imported setups

Most of the voice agent software available here was built for a single time zone and a single phone format. Australia is neither.

Time zones and daylight saving

New South Wales, Victoria, Tasmania, the ACT and South Australia move their clocks. Queensland, Western Australia and the Northern Territory do not, and South Australia sits half an hour off the east coast. An agent that books "nine tomorrow" from a Sydney calendar for a Perth caller has booked the wrong time, and the customer finds out when nobody arrives. Availability, quiet hours and reminders all need to be resolved in the caller's time zone, not the server's.

Numbers and how people give them

Mobile first, 1300 and 1800 numbers in the mix, and a lot of callers who give a number with no spaces and then a second one "in case". Capture both, read back the primary, and store the digits in a format the CRM will not choke on.

Recording and privacy

Rules about recording calls, and about what you are allowed to do with a transcript, differ between states and depend on what the recording is used for. Get the consent line, the retention period and the access rules written by someone qualified before you switch recording on. A vendor who waves this away is telling you something useful about the rest of their advice.

How to buy one without a six month project

A receptionist agent is one workflow, not a transformation program. The version that works is a four week pilot on one phone number, with a written list of what the agent handles, what it escalates, and one number that has to move.

Questions worth asking any vendor before signing:

• Who writes the script, and can I edit it without a change request?
• What exactly happens on a handoff, and can I hear a recording of one?
• What does the agent do when it is not confident, rather than when it is wrong?
• Where do transcripts live, who can read them, and how do I delete them?
• What is the exit? Can I take the number and the call history with me?

Two things to refuse: an annual contract before a measured pilot, and any pricing that charges per minute with no integration into the calendar. Per minute pricing punishes you for the calls you most want answered, and a receptionist that cannot see the calendar is a message taker with a nicer voice.

If the honest answer is that you are not sure which workflow to fix first, start there instead of starting with the phone. DoubleKlick's AI automation practice maps the workflows before anything gets built, and the AI practice page covers how the pieces fit together.

Questions we get asked

Can an AI receptionist actually book jobs into my calendar?

Yes, if it is connected to the calendar the business already runs on and given the same constraints a person works within: job durations, travel time between suburbs, and the windows you can genuinely keep. Without that integration it is a message taker. The booking, not the conversation, is the product.

Will callers know they are not talking to a person?

Often, and it should not matter. The agent identifies the business, answers the question and books the job. What loses callers is pretending, or a script that stalls when asked something unexpected. Being straight about it and still solving the problem is the better experience, and it is the one that survives a bad review.

What happens when it does not know the answer?

It says so, takes the details, tells the caller when they will hear back, and writes the question into the escalation list so the answer gets added to the knowledge base. An agent that invents an answer to protect its own confidence is the single most expensive failure mode in this category.

What does an AI receptionist cost in Australia?

Two models dominate: per minute usage, and a managed monthly service that includes the setup, the script, the integrations and someone to fix it. Per minute looks cheaper in a spreadsheet and gets expensive exactly when the phone gets busy. The right comparison is cost per booked job, not cost per call. If you want the smallest setup that fixes the expensive problem first, that is what the twenty second start form is for.

---

Start with the call log, not with the software. Count the misses for one month, work out what they are worth, and decide whether the number justifies the work. If it does, the sequence is short: one number, one script, one measured pilot, and a refusal list that everyone has agreed to. If you would rather have that conversation before you buy anything, tell us what you would most like to stop doing manually and we will come back with the first workflow worth automating.