Christchurch · Dunedin · Nationwide
AI Chatbot Services for Business
Exodesk scopes and builds AI chatbots for business across New Zealand. Our Christchurch and Dunedin teams agree the audience, sources, permissions and route to a person for selected website enquiries or internal staff questions.
We compare existing tools, a configured platform and custom development, then test one useful assistant before release and agree how it is maintained.
Supporting New Zealand businesses since 1989
The short answer
What are AI chatbots for business?
AI chatbots for business are conversational assistants that retrieve information, prepare answers or route requests for a defined set of customer or staff questions. They can combine AI, fixed responses and rules.
Company information improves relevance, but generated answers can still be wrong, so business chatbot solutions are built around approved sources, access controls, a clear route to a person and testing before and after release.
Exodesk has supported New Zealand businesses since 1989. Today, our Christchurch and Dunedin teams support businesses nationwide, and chatbot work sits within our wider AI solutions programme.
What we build
Business chatbot solutions for a defined job
AI chatbots for business work best with one audience and a clear set of questions. These are the kinds of assistant we scope.
Website
Website assistant
Explains your services from approved public information and collects an enquiry for your team to follow up.
Internal
Staff assistant
Helps authorised staff find policies and procedures, for example inside Microsoft Teams, within their existing access.
Connected
Requests and bookings
Tickets, bookings, CRM updates and messaging channels are checked for feasibility and scoped separately.
Lead capture, a ticket, an available slot and a confirmed booking are different outcomes, and each needs live data, permissions, validation and confirmation where it applies.
Sources and access
Agree the information and who can use it
We identify approved sources, the person responsible for each one and how updates reach the assistant. Public information is kept separate from internal material.
Access is enforced in the application, not by instructions to the model. Internal users should only receive information they are already permitted to see, and uploaded copies or shared service accounts are tested because they may not inherit document permissions. OWASP lists prompt injection, including through retrieved content, among the main risks for these systems.
The design also covers collected information, provider terms, retention and transcript access. The Privacy Commissioner expects transparency about generative AI use and a privacy impact assessment before personal information is collected, so users are told they are speaking to an automated assistant. Our AI data security guide covers the wider handling questions.
Handover
Make the route to a person clear
Useful AI chatbots for business do not rely on recognising every difficult question. Users get a visible way to ask for a person, and the handover is designed rather than assumed.
- Subjects. Agree which topics go straight to a person, such as complaints, account changes or sensitive information.
- Destination. Choose live chat, a callback or a ticket, depending on what your team and platform support.
- Staffed hours. Outside those hours, a queued request with a clear response time may suit better than a live transfer.
- Identity. General enquiries are kept separate from authenticated access, so account details are not revealed because someone supplies a name.
- Actions. Bookings and account changes need suitable interfaces, permissions, validation and confirmation. Our AI workflow automation service covers wider steps and approvals.
Platform
Choose the platform before commissioning a build
Microsoft or other existing tools may fit. Microsoft’s agent options, including Copilot Studio, can suit internal or customer scenarios depending on the product, channel and licence.
We compare sources, controls, channels and full cost before choosing a platform, configuration or custom work. Our Microsoft Copilot guide explains how Copilot licences and agents relate to the tools your staff already use.
Once live, support covers agreed source updates, response reviews, platform changes and fault handling, with a fallback for unavailable information or connections. Your business keeps an owner for its content and decisions.
How it works
How a business chatbot is delivered
Each project starts with one audience and a defined set of questions.
Scope
Agree the audience, channel, questions, sources, permissions, handover and any connected actions.
Prepare sources
Confirm source owners, remove outdated or conflicting material and set how updates reach the assistant.
Build and test
Test supported answers, paraphrases, unanswered questions, access, attempts to override instructions and handover.
Pilot and release
Review a pilot against the agreed acceptance tests before wider release.
Support and review
Review responses, update sources and handle platform changes and faults under the agreed terms.
Success is measured against real enquiry volume and the effort needed to review and correct answers, rather than assumed from the number of conversations.
Cost
What affects the cost of AI chatbots for business?
Cost depends on sources, channels, authentication, integrations, testing and usage. Even a narrow scope can need substantial security or integration work.
- Setup. Scoping, source preparation, configuration and testing.
- Platform and usage. Licences, hosting and usage charges, listed separately.
- Integrations. Connections to bookings, tickets or business systems, quoted where required.
- Maintenance. Source updates, response reviews and changes under agreed terms.
Compare the complete cost with real enquiry volume. Sometimes a clearer FAQ page or an existing product feature answers the need without a chatbot.
Questions
AI chatbots for business questions
What is an AI chatbot for business?
It is a conversational assistant for selected customer or staff enquiries. It can retrieve information, prepare an answer or route a request using AI, rules and fixed responses. Its sources, audience, access and permitted actions are defined before release.
Can it answer accurately from our company information?
Approved sources can improve relevance, but they do not ensure a correct answer. Keep information current, test likely questions and define a fallback. Generated answers may still misread material or include unsupported details, so consequential decisions need appropriate checks.
Can a chatbot answer after hours?
It may be available outside office hours, depending on the platform and arrangement. That does not mean a staff member is available. Agree when escalated requests are answered, provide a suitable fallback and make any queued response clear to the user.
Will it replace our support team?
That is not the goal of the service. Start with selected questions and measure whether the assistant reduces work without adding correction effort. People stay responsible for sensitive enquiries, exceptions and decisions, and staffing remains a business decision.
What information does a chatbot need?
Start with approved, current material relevant to its job, such as public service information or internal procedures for authorised staff. Identify who owns each source and how updates reach the assistant. Adding more documents does not automatically improve answers, especially where information conflicts.
What happens when it cannot answer?
The design includes an unanswered-question response and a route to a person, such as live chat, a callback or a ticket where supported. Users can request that route themselves. AI may fail to recognise an uncertain question, so the fallback is tested before release.
How do we protect customer and internal information?
Limit sources and connected actions, authenticate users where needed and enforce access in the application. Check provider terms, processing, retention and transcript access. Prompt instructions alone do not secure data, so public and internal use need separate boundaries and testing.
How much does a business chatbot cost?
Cost depends on channels, sources, authentication, integrations, testing, usage and maintenance. The proposal separates setup from recurring platform or usage charges where applicable. Compare the complete cost with real enquiry volume and the effort needed to review and correct answers.
How does a chatbot differ from workflow automation or Copilot?
A chatbot is the conversational interface, while workflow automation coordinates steps and actions, and a conversation can trigger a workflow. Microsoft Copilot agent tools may provide the chatbot platform itself. The right option depends on audience, sources, permissions, channels and licensing.
How long does chatbot setup take?
Timing depends on content preparation, access, platform decisions, integrations and testing. Milestones are agreed once the first scope is understood. A focused pilot shows whether the assistant is useful, but a small question set does not mean a short project.
Next step
Tell us which questions keep coming back
Tell us who would use the assistant, where they would use it and three recurring questions, and we can discuss whether a FAQ, an existing feature or one of our AI chatbots for business suits the job. Please keep customer records, internal document archives and passwords out of the enquiry form.
Get in touch
Talk to us about a business chatbot
Tell us about the audience, the channel and the questions you want answered, and we will be in touch to arrange a time that suits.
Prefer to talk?
Christchurch
Level 1, 85 Riccarton Road
Christchurch 8011
03 343 3124
Dunedin
Level 3, Bartons Building
2 Stafford Street, Dunedin 9016
03 479 2941