AI Receptionist Costs in Australia: What Should Be in the Quote?

An AI receptionist quote should separate the initial build, ongoing platform fees, call usage and support. It should also explain what happens when a caller needs a person, a booking fails or your business changes its opening hours. Those details make two quotes comparable.

A monthly headline price tells you little about the service your callers will receive. A message-taking assistant and a receptionist that checks availability, books appointments and updates a customer record have different setup and maintenance requirements. Start by giving suppliers the same call-handling brief.

This guide provides a worksheet for that brief. It does not give a Grendigital price list or assume a single market rate applies to every business.

In this article

Start with calls and minutes from your own phone records

Ask your phone provider for recent inbound call records covering ordinary weeks and a busy period. Record how many calls arrive, how long they last and when they arrive. Separate the calls you want the receptionist to answer: all calls, overflow calls or after-hours calls.

An average can hide a difficult peak. A business receiving several calls at opening time needs to ask about simultaneous calls, even if its monthly total is modest. Also check whether a campaign or seasonal rush changes the mix of enquiries.

Use the following planning example with your own figures. A hypothetical repairs business routes 500 calls a month to an assistant. At an assumed average of three minutes, that means 1,500 assistant minutes. If 100 calls also need a two-minute onward telephone connection, ask how those 200 connection minutes are charged. They may sit outside the assistant allowance; the supplier should state the treatment explicitly.

Treat the example as a way to expose charging units. It is not a usage forecast or a supplier quote.

Ask for an itemised setup scope

Setup includes decisions your business must make before anyone connects a phone number. Which questions can the receptionist answer? Who gets an urgent message? Can it confirm an appointment, or only request one? What should it say when the caller interrupts or asks for a person?

An itemised proposal should identify the call flows, approved information, integrations and testing included in the build. Ask whether the supplier will help organise your information or expects a finished knowledge base from you. Confirm how many rounds of changes are included and what counts as a change in scope.

For a repairs business, “book a service” needs a precise meaning. A confirmed appointment may depend on service area, equipment type, technician availability and travel time. A simpler first release might collect those details and send a booking request for staff approval. Either can be useful; the quote must describe the promised behaviour accurately.

Ask for sample acceptance tests with expected results. One should cover an ordinary enquiry, another an unsupported request, and another a failed connection to your booking system. Include testing and staff handover in the setup price so they do not become surprises at launch.

Separate subscriptions from usage charges

Depending on the arrangement, your ongoing bill may combine a platform subscription, AI conversation usage, phone number rental, telephone minutes and messages. Some suppliers bundle these components; others pass through separate vendor charges.

Twilio’s Australian voice pricing illustrates why the telephone component needs its own explanation: it lists different charges for calls and phone numbers. Those telecommunications charges do not establish the total price of a configured AI receptionist. Voice-agent platforms add their own service capabilities and commercial terms.

Check the currency for each component. If a supplier pays an underlying service in US dollars, ask whether your Australian-dollar fee is fixed or changes with exchange rates. Have the proposal state whether GST is included, where applicable, and who receives each vendor invoice.

Also ask how unused minutes, rounded billing increments and overages work. A large allowance is useful only if it covers the calls you intend to route. Request a worked invoice using your expected volume and a second one using your busiest realistic month.

Put the integration work in writing

“Connects to your CRM” can describe several different jobs. The assistant might create a new lead, find an existing customer, attach a call summary or update an appointment. Each needs rules for matching records, permissions and failures.

ElevenLabs’ agent documentation distinguishes knowledge, tools, deployment and monitoring. That is a useful reminder when scoping a project: answering from approved information and taking an action in another system are separate capabilities. The precise functions available depend on the implementation.

For each connection, write down the information read, the fields written and the result a staff member should see. Include a duplicate-customer example. If a caller changes their phone number, the assistant should not silently attach their enquiry to somebody else’s record.

Confirm whether API access or a higher subscription tier is needed in your existing software. Ask who owns the connection and how expiring credentials or changed fields will be handled. Your supplier should identify these dependencies before calling an integration complete.

Budget for the work after launch

Your business will change. Staff leave, services change and public holidays affect opening hours. Agree who updates the receptionist, how a change is checked and what turnaround the support agreement provides. “Support included” needs a boundary: fault correction, content updates and a new call flow are different types of work.

Discuss operational failures as well. What happens if the assistant cannot reach the booking system? Where does a failed transfer go? Who notices if summaries stop arriving? The proposal should name the fallback and the person responsible for following it up.

Ask which records your team can review and export. Set appropriate access and retention requirements with the supplier before launch. Do not assume every plan includes the same recording, transcript or reporting features, or that every available feature needs to be enabled.

Compare quotes against the same monthly scenario

Put the commercial details beside the service behaviour. A comparison sheet is most helpful when it records both the price and what that price buys.

Estimate a normal month and a busy month using the quoted units, then add any one-off setup charges separately. Keep internal staff time visible too: someone must answer escalations, review exceptions and maintain the approved information.

Finish with a short demonstration using your own anonymised call scenarios. Ask the supplier to show the resulting appointment, message or customer record. A clear quote and a checked outcome give you a much firmer basis for choosing an AI phone receptionist than a monthly price on its own.