What an AI Chatbot Costs in New Zealand (2026 Pricing)

Nobody publishes real prices in this market, which is why every business owner I speak to arrives with a number somewhere between $49 and $50,000 and no way to tell which end applies to them.

The honest answer is that AI chatbot cost in NZ depends on three separate things that vendors often blend into one figure: what you pay to start, what you pay every month regardless of use, and what you pay per conversation. A quote that shows only one of those is hiding at least one of the others.

Prices in this article are bands based on what businesses are being quoted in New Zealand as of 2026, in NZD. They vary a great deal by vendor and by scope, so treat them as the range to sanity-check a quote against rather than a price list.

AI chatbot cost in NZ falls into three bands#

Self-serve tool#

You should expect to pay somewhere around $50 to $250 a month, usually billed in USD by an overseas vendor, so add GST and watch the exchange rate.

You get a chat widget for your website, a knowledge base you fill in yourself, and often a basic voice option at the higher tiers. Setup is your own weekend. Integrations are limited to whatever the vendor already supports, which typically covers the mainstream calendar and CRM products and nothing else.

This band suits a business with straightforward services, low call volume and someone in the office who enjoys fiddling with settings. It genuinely works for a lot of businesses, and anyone who tells you it never does is selling the next band up.

Configured system#

Expect roughly $400 to $1,500 a month, plus a setup fee that commonly lands between $2,000 and $8,000 depending on how much of your business has to be taught to it.

Here somebody else does the work. Your services, prices, service area and escalation rules are built in, your calendar and job management software are connected, and the phone number is routed properly. You get transcripts, reporting and someone who fixes it when a customer gets a wrong answer. The monthly fee usually covers a maintenance allowance for changes.

Most New Zealand service businesses with a steady flow of enquiries sit here. It is the band where the system starts booking work rather than just answering questions.

Custom build#

A genuine custom build starts around $8,000 as a project and climbs quickly from there, with running costs on top.

You are paying for this when your workflow is unusual, when the system has to talk to older job management software with no modern integration, or when your data cannot leave particular systems for compliance reasons. The rest of the time it is an expensive way to buy something that already exists.

Voice costs differently from chat, and it catches people out#

Website chat is cheap to run. A conversation costs the vendor a fraction of a cent in model usage, so pricing is usually a flat monthly fee with a conversation allowance, and overage rates that only bite at high volume.

Voice is a different economic animal. Every minute of every call is transcribed, processed and spoken back, and the call itself has to be carried over a telephony network. Vendors bill this per minute, and while the rate is measured in cents, the total scales directly with how much you talk.

Work out your own exposure before you sign. Take your monthly inbound call count, multiply by your average call length, and you have your minutes. A clinic taking 300 calls a month at three minutes each is buying 900 minutes. At a per-minute rate in the low tens of cents, that is a few hundred dollars on top of the platform fee. At a rate ten times higher, which some premium voice vendors charge, it is a problem.

Two things reduce the bill without reducing the service. Shorter calls, achieved by getting to the point rather than reading a long greeting, cut minutes directly. And routing enquiries into chat where the customer is already on your website means the conversation never becomes a voice minute at all, which is one reason adding AI chat to your website is usually the cheapest first step.

What actually drives your quote up#

Vendors rarely explain this, so ask about each one directly.

• The number of integrations. Connecting a calendar is routine. Connecting a twelve-year-old job management system with no public API is a development project, and it should be quoted as one.
• How many distinct things the agent must be able to do. An agent that answers questions is simple. One that answers questions, books, reschedules, takes a deposit and updates a customer record is five systems wearing one voice.
• Call and chat volume, through the usage tiers described above.
• How much of your information exists in writing. If your prices live in your head, someone has to spend hours extracting them, and that time appears in the setup fee whether it is itemised or not.
• Compliance requirements. Health and financial businesses need tighter data handling, which narrows the vendor list and raises the price.

The last one is worth preparing for rather than paying for. Turning up with a written service list, current prices and your twenty most common questions can take a meaningful chunk out of a setup fee, and it produces a better system regardless. The list of what to prepare is in how to train an AI agent on your business.

The fees that get left off the quote#

Ask for these in writing before you sign anything.

Setup and onboarding often sits in the contract rather than the proposal. Ask what it covers and what happens if the build takes longer than expected.

Integration charges hide behind the phrase "integrations included", which should always be followed by a list of which ones. The integration you actually need is often the exception.

Overage rates matter more than the included allowance. Find both, then check them against a busy month rather than an average one.

Change fees annoy people most. You launch, you learn from the transcripts, and you want to change how the agent answers three questions. Some vendors treat that as included maintenance and some bill it hourly. Ask in month zero, not month four.

Exit terms are worth reading while you still like the vendor. Find out whether you keep your conversation transcripts, whether your phone number routes back cleanly, and what notice period applies.

Also check where the data lives and who at the vendor can read your conversations. That is a cost question as well as a privacy one, because New Zealand-specific data handling requirements can move you to a more expensive plan. The practical version of that conversation is in the Privacy Act and AI for NZ businesses.

Whether the price is right depends on a number you own#

Any of these bands is cheap or expensive only relative to what the problem costs you now. A business losing $400 a month to unanswered enquiries should not be spending $1,200 a month solving it. A business losing $6,000 a month should stop reading price lists and get on with it.

Calculate your own figure before you compare vendors. Count last month's missed calls and unanswered messages, estimate what share were real enquiries, apply your close rate and your average job value. The method takes about twenty minutes and is laid out in what missed calls are really costing you.

Then compare the shortlist against the same figure rather than against each other. A more expensive system that books jobs beats a cheaper one that takes messages, and the gap between those two outcomes is much larger than the gap between their prices.

What to ask for next#

Get two quotes in the same shape. Ask each vendor for setup, monthly, per-minute or per-conversation usage, and the cost of changing the script after launch, as four separate numbers. Vendors who resist itemising are telling you something useful.

Then ask both to explain what happens when the agent cannot answer. The answer to that question predicts customer satisfaction better than any price comparison, and the full picture of how these systems fit together sits in the guide to an AI receptionist for small business.