To set up AI live chat, limit it to questions you already answer in public, tell the visitor they are talking to an AI, and send everything else to a named person. You do not need a custom-built chatbot to start.
This sits under what to automate first. For the service itself, see website chat support. To plan the workflow, discuss an automation project.
Key facts
- business.gov.au says AI can answer questions through a chatbot on your website, and can refer a customer to a person when it cannot solve the query. business.gov.au, accessed 10 November 2026.
- The same guidance says customers want to know when they are talking to an AI rather than a person for customer support.
- It also says a chatbot that talks directly to customers is riskier than using AI to draft a social media post, and that generative AI can present false or misleading information as fact.
- The OAIC recommends that organisations do not enter personal information, particularly sensitive information, into publicly available generative AI tools. OAIC guidance, published 21 October 2024, updated 17 January 2025.
What should the chat be allowed to answer?
Limit it to questions you already answer on the site, and name a person for everything else.
Write two lists before you install anything. The first is what the chat may say: services, opening hours, service area, and how to ask for a quote. The second is what a person must handle: complaints, custom prices, refunds, urgent jobs and anything not on the first list.
| The chat may | A person handles |
|---|---|
| Repeat a published service, hour or suburb | A price that is not on the page |
| Explain how to request a quote | A complaint or a refund |
| Collect a name and a contact method the visitor offers | A booking you have not checked |
| Say it does not know, and pass the chat on | Sensitive or health information |
Keep the allowed answers in one place a person updates when the business changes. If the hours on the site and the hours in the chat differ, fix that before launch. For how to choose the first task, use what to automate first. For the limits in more detail, read planning a useful website chatbot.
Where should the chat sit?
Put it on the pages where people already look for help, and check it on a phone.
A chat button on every page is not required. Start with the contact page and the service pages where the questions on your list actually arise. Read the welcome line out loud: it should say what the chat can help with, and that a person is available for anything else.
Open the page on a phone before you call it done. The button should not cover the phone number, the form or the booking link. If you also reply to enquiries by email, keep that path. Our lead response guide covers enquiries that arrive outside the chat window.
How do you hand a conversation to a person?
Decide the handoff before a customer uses the chat, including what happens when nobody is free.
Write four lines and keep them next to the allowed answers:
- The sentence the visitor sees when the chat stops.
- The person or shared inbox that receives the conversation.
- What you collect, and only that: usually a name, a contact method and the question.
- What the visitor is told if that person is unavailable.
business.gov.au says a customer-facing chatbot is a higher-risk use than drafting a social post, and that your business is responsible for what its AI tools do. A handoff is part of that, not an extra. Do not promise an instant transfer unless someone is actually there to take it.
What should you test before a customer sees it?
Test with fictional questions, including one the chat must refuse.
Use made-up names and a question from each row of the table above. Then ask for a price you have not published, a booking at a time you have not checked, and a complaint. The safe result is a handoff, not a confident guess. business.gov.au says generative AI can present false information as fact, so compare every answer with the page it came from.
Ask the supplier, in writing, where transcripts are stored, who can read them, and how you turn the chat off. The OAIC recommends not putting personal information into publicly available generative AI tools. A chat product that pastes customer messages into a public tool is a different risk from one that runs on an account your business controls. If you need a short rule for staff, see how to write an AI policy.
Frequently asked questions
How do I set up AI live chat on my small-business website?
Choose the questions it may answer from information you keep current, tell visitors they are talking to an AI, and send every other question to a named person.
Do I need a custom-built chatbot?
Not to start. business.gov.au says many tools you already use include AI features, and that a chatbot talking to customers is riskier than drafting a social post. Start narrow.
Can the chat confirm a price or a booking?
Only from information you keep up to date. business.gov.au says generative AI can present false information as fact, so check those answers before customers rely on them.
Should I paste customer chats into a public AI tool?
The OAIC recommends that organisations do not enter personal information into publicly available generative AI tools. Check what your chat product does with transcripts first.
Do I have to say the chat is an AI?
business.gov.au says customers want to know when they are talking to an AI rather than a person for customer support. Say so in the chat.
Ready to scope a chat that knows when to stop? Discuss an automation project.