Oct 28, 2026
IN /
Guides
5 min read
Does your small business need an AI chatbot?
Before adding a chatbot, check which customer questions need clearer website answers, access to a record or a person. A practical small-business test.
Carbon Black Digital
If your team keeps answering questions already covered on your website, an AI chatbot may look worth trying. But an opening-hours question and a request to change a booking need different information and different permissions.
An online retailer, looking for help with WhatsApp and Messenger enquiries, raised a practical question on Reddit: could a bot answer repeated product questions, take orders and pass difficult enquiries back to the owner? Several replies were product pitches. The distinction in the original question is useful. The replies don't establish which product works.
Before choosing a chatbot, work out what the answer depends on.
Check whether the answer is settled
Take ten recent customer questions, with identifying details removed. Use fewer if that's all you have. This is a scoping exercise, not a statistical sample. On a simple worksheet, write each question, its approved answer and where that answer lives. Mark any question your team has not agreed how to answer.
If customers keep asking which suburbs you cover, check whether the service-area information is easy to find on the page where they enquire. Ask someone unfamiliar with the site to find it on their phone. If they struggle, fix the wording or placement and test again. Do that before asking a supplier to build an assistant around the same page.
A chatbot can help people find information across a larger set of useful pages. Give it a source your team can keep current. Microsoft's Copilot Studio documentation explains that generative answers search selected sources and summarise the results. It also warns that answers can contain mistakes and repeat inaccurate source material.
Treat an unanswered question in your worksheet as content work first. And don't ask the software to decide an unpublished policy for you.
Separate public answers from private records
These hypothetical questions show why one chat box may need several different routes:
“Do you work in Coomera?” needs an approved service-area answer.
“Is my booking confirmed?” needs the relevant booking record and a way to establish whose record the visitor can see.
“Can you squeeze me in tomorrow?” needs availability and a decision about what the business can commit to.
“Can I speak to someone?” needs a working way to reach the team.
A public website answer cannot establish a particular customer's booking status. If the assistant needs access to records, include that connection and its access rules in the scope. Microsoft's tool authentication guidance recommends user authentication when an agent must restrict data access to particular people or groups, such as retrieving a user's records or acting on their behalf. Other products need their own checks.
Original CBD decision aid. The examples are hypothetical, not results from a client project.
For each question, choose a route: show an agreed public answer, retrieve an authorised record, or pass the decision to a person. Some conversations will move between routes.
Reading a booking is also different from changing one. Write down which actions the assistant may take and which need a person to agree.
Test the handover before relying on it
Choose a question the assistant should not answer. Ask it for an exception to your normal terms, then ask for a person. Keep going until you can see what the team receives. Does the conversation arrive in the right place? Is someone responsible for replying, and can they understand the request without making the customer start again?
Then try the same thing when nobody is available. The customer needs an honest explanation of what happens next. Don't promise a callback time your team cannot keep.
Microsoft's fallback and handoff guidance recommends defining what the conversational experience can do and providing another route when it cannot help. The tests above are a practical way to check your own setup, not a claim that every chatbot includes a reliable handover.
Count the work left after the chat
Agree what a useful outcome looks like before starting a small trial.
Record the questions answered correctly and the answers that needed correction. Track requests passed to the team separately, including whether anyone followed up. Include the effort spent maintaining the source material and reviewing conversations.
Read the definitions behind a dashboard's numbers. In Copilot Studio's outcome reporting, a session can be recorded as resolved after the end-of-conversation topic is reached and the customer does not reply before the session times out. That is different from verifying that their request was completed.
If the main problem is website traffic without enquiries, start with the enquiry-path diagnostic. A new chat channel may be beside the point.
Use the questions to scope the work
Use the worksheet to write a smaller brief. If the answers are missing or hard to find, start with the pages. Once those answers are reliable, you can test whether an assistant helps people find them. Questions about a particular booking need a separate scope for the connection and its access rules.
For clearer service pages or a better enquiry form, see CBD's website design and care service. Scope any chatbot or booking-system connection separately.
Bring a few anonymised questions and the answers your team currently gives. Include one where the right answer is “someone needs to check”. That boundary belongs in the brief before the chatbot is built.
Oct 28, 2026
IN /
Guides
5 min read
Does your small business need an AI chatbot?
Before adding a chatbot, check which customer questions need clearer website answers, access to a record or a person. A practical small-business test.
Carbon Black Digital
If your team keeps answering questions already covered on your website, an AI chatbot may look worth trying. But an opening-hours question and a request to change a booking need different information and different permissions.
An online retailer, looking for help with WhatsApp and Messenger enquiries, raised a practical question on Reddit: could a bot answer repeated product questions, take orders and pass difficult enquiries back to the owner? Several replies were product pitches. The distinction in the original question is useful. The replies don't establish which product works.
Before choosing a chatbot, work out what the answer depends on.
Check whether the answer is settled
Take ten recent customer questions, with identifying details removed. Use fewer if that's all you have. This is a scoping exercise, not a statistical sample. On a simple worksheet, write each question, its approved answer and where that answer lives. Mark any question your team has not agreed how to answer.
If customers keep asking which suburbs you cover, check whether the service-area information is easy to find on the page where they enquire. Ask someone unfamiliar with the site to find it on their phone. If they struggle, fix the wording or placement and test again. Do that before asking a supplier to build an assistant around the same page.
A chatbot can help people find information across a larger set of useful pages. Give it a source your team can keep current. Microsoft's Copilot Studio documentation explains that generative answers search selected sources and summarise the results. It also warns that answers can contain mistakes and repeat inaccurate source material.
Treat an unanswered question in your worksheet as content work first. And don't ask the software to decide an unpublished policy for you.
Separate public answers from private records
These hypothetical questions show why one chat box may need several different routes:
“Do you work in Coomera?” needs an approved service-area answer.
“Is my booking confirmed?” needs the relevant booking record and a way to establish whose record the visitor can see.
“Can you squeeze me in tomorrow?” needs availability and a decision about what the business can commit to.
“Can I speak to someone?” needs a working way to reach the team.
A public website answer cannot establish a particular customer's booking status. If the assistant needs access to records, include that connection and its access rules in the scope. Microsoft's tool authentication guidance recommends user authentication when an agent must restrict data access to particular people or groups, such as retrieving a user's records or acting on their behalf. Other products need their own checks.
Original CBD decision aid. The examples are hypothetical, not results from a client project.
For each question, choose a route: show an agreed public answer, retrieve an authorised record, or pass the decision to a person. Some conversations will move between routes.
Reading a booking is also different from changing one. Write down which actions the assistant may take and which need a person to agree.
Test the handover before relying on it
Choose a question the assistant should not answer. Ask it for an exception to your normal terms, then ask for a person. Keep going until you can see what the team receives. Does the conversation arrive in the right place? Is someone responsible for replying, and can they understand the request without making the customer start again?
Then try the same thing when nobody is available. The customer needs an honest explanation of what happens next. Don't promise a callback time your team cannot keep.
Microsoft's fallback and handoff guidance recommends defining what the conversational experience can do and providing another route when it cannot help. The tests above are a practical way to check your own setup, not a claim that every chatbot includes a reliable handover.
Count the work left after the chat
Agree what a useful outcome looks like before starting a small trial.
Record the questions answered correctly and the answers that needed correction. Track requests passed to the team separately, including whether anyone followed up. Include the effort spent maintaining the source material and reviewing conversations.
Read the definitions behind a dashboard's numbers. In Copilot Studio's outcome reporting, a session can be recorded as resolved after the end-of-conversation topic is reached and the customer does not reply before the session times out. That is different from verifying that their request was completed.
If the main problem is website traffic without enquiries, start with the enquiry-path diagnostic. A new chat channel may be beside the point.
Use the questions to scope the work
Use the worksheet to write a smaller brief. If the answers are missing or hard to find, start with the pages. Once those answers are reliable, you can test whether an assistant helps people find them. Questions about a particular booking need a separate scope for the connection and its access rules.
For clearer service pages or a better enquiry form, see CBD's website design and care service. Scope any chatbot or booking-system connection separately.
Bring a few anonymised questions and the answers your team currently gives. Include one where the right answer is “someone needs to check”. That boundary belongs in the brief before the chatbot is built.
Oct 28, 2026
IN /
Guides
5 min read
Does your small business need an AI chatbot?
Before adding a chatbot, check which customer questions need clearer website answers, access to a record or a person. A practical small-business test.
Carbon Black Digital
If your team keeps answering questions already covered on your website, an AI chatbot may look worth trying. But an opening-hours question and a request to change a booking need different information and different permissions.
An online retailer, looking for help with WhatsApp and Messenger enquiries, raised a practical question on Reddit: could a bot answer repeated product questions, take orders and pass difficult enquiries back to the owner? Several replies were product pitches. The distinction in the original question is useful. The replies don't establish which product works.
Before choosing a chatbot, work out what the answer depends on.
Check whether the answer is settled
Take ten recent customer questions, with identifying details removed. Use fewer if that's all you have. This is a scoping exercise, not a statistical sample. On a simple worksheet, write each question, its approved answer and where that answer lives. Mark any question your team has not agreed how to answer.
If customers keep asking which suburbs you cover, check whether the service-area information is easy to find on the page where they enquire. Ask someone unfamiliar with the site to find it on their phone. If they struggle, fix the wording or placement and test again. Do that before asking a supplier to build an assistant around the same page.
A chatbot can help people find information across a larger set of useful pages. Give it a source your team can keep current. Microsoft's Copilot Studio documentation explains that generative answers search selected sources and summarise the results. It also warns that answers can contain mistakes and repeat inaccurate source material.
Treat an unanswered question in your worksheet as content work first. And don't ask the software to decide an unpublished policy for you.
Separate public answers from private records
These hypothetical questions show why one chat box may need several different routes:
“Do you work in Coomera?” needs an approved service-area answer.
“Is my booking confirmed?” needs the relevant booking record and a way to establish whose record the visitor can see.
“Can you squeeze me in tomorrow?” needs availability and a decision about what the business can commit to.
“Can I speak to someone?” needs a working way to reach the team.
A public website answer cannot establish a particular customer's booking status. If the assistant needs access to records, include that connection and its access rules in the scope. Microsoft's tool authentication guidance recommends user authentication when an agent must restrict data access to particular people or groups, such as retrieving a user's records or acting on their behalf. Other products need their own checks.
Original CBD decision aid. The examples are hypothetical, not results from a client project.
For each question, choose a route: show an agreed public answer, retrieve an authorised record, or pass the decision to a person. Some conversations will move between routes.
Reading a booking is also different from changing one. Write down which actions the assistant may take and which need a person to agree.
Test the handover before relying on it
Choose a question the assistant should not answer. Ask it for an exception to your normal terms, then ask for a person. Keep going until you can see what the team receives. Does the conversation arrive in the right place? Is someone responsible for replying, and can they understand the request without making the customer start again?
Then try the same thing when nobody is available. The customer needs an honest explanation of what happens next. Don't promise a callback time your team cannot keep.
Microsoft's fallback and handoff guidance recommends defining what the conversational experience can do and providing another route when it cannot help. The tests above are a practical way to check your own setup, not a claim that every chatbot includes a reliable handover.
Count the work left after the chat
Agree what a useful outcome looks like before starting a small trial.
Record the questions answered correctly and the answers that needed correction. Track requests passed to the team separately, including whether anyone followed up. Include the effort spent maintaining the source material and reviewing conversations.
Read the definitions behind a dashboard's numbers. In Copilot Studio's outcome reporting, a session can be recorded as resolved after the end-of-conversation topic is reached and the customer does not reply before the session times out. That is different from verifying that their request was completed.
If the main problem is website traffic without enquiries, start with the enquiry-path diagnostic. A new chat channel may be beside the point.
Use the questions to scope the work
Use the worksheet to write a smaller brief. If the answers are missing or hard to find, start with the pages. Once those answers are reliable, you can test whether an assistant helps people find them. Questions about a particular booking need a separate scope for the connection and its access rules.
For clearer service pages or a better enquiry form, see CBD's website design and care service. Scope any chatbot or booking-system connection separately.
Bring a few anonymised questions and the answers your team currently gives. Include one where the right answer is “someone needs to check”. That boundary belongs in the brief before the chatbot is built.
Oct 28, 2026
IN /
Guides
5 min read
Does your small business need an AI chatbot?
Before adding a chatbot, check which customer questions need clearer website answers, access to a record or a person. A practical small-business test.
Carbon Black Digital
If your team keeps answering questions already covered on your website, an AI chatbot may look worth trying. But an opening-hours question and a request to change a booking need different information and different permissions.
An online retailer, looking for help with WhatsApp and Messenger enquiries, raised a practical question on Reddit: could a bot answer repeated product questions, take orders and pass difficult enquiries back to the owner? Several replies were product pitches. The distinction in the original question is useful. The replies don't establish which product works.
Before choosing a chatbot, work out what the answer depends on.
Check whether the answer is settled
Take ten recent customer questions, with identifying details removed. Use fewer if that's all you have. This is a scoping exercise, not a statistical sample. On a simple worksheet, write each question, its approved answer and where that answer lives. Mark any question your team has not agreed how to answer.
If customers keep asking which suburbs you cover, check whether the service-area information is easy to find on the page where they enquire. Ask someone unfamiliar with the site to find it on their phone. If they struggle, fix the wording or placement and test again. Do that before asking a supplier to build an assistant around the same page.
A chatbot can help people find information across a larger set of useful pages. Give it a source your team can keep current. Microsoft's Copilot Studio documentation explains that generative answers search selected sources and summarise the results. It also warns that answers can contain mistakes and repeat inaccurate source material.
Treat an unanswered question in your worksheet as content work first. And don't ask the software to decide an unpublished policy for you.
Separate public answers from private records
These hypothetical questions show why one chat box may need several different routes:
“Do you work in Coomera?” needs an approved service-area answer.
“Is my booking confirmed?” needs the relevant booking record and a way to establish whose record the visitor can see.
“Can you squeeze me in tomorrow?” needs availability and a decision about what the business can commit to.
“Can I speak to someone?” needs a working way to reach the team.
A public website answer cannot establish a particular customer's booking status. If the assistant needs access to records, include that connection and its access rules in the scope. Microsoft's tool authentication guidance recommends user authentication when an agent must restrict data access to particular people or groups, such as retrieving a user's records or acting on their behalf. Other products need their own checks.
Original CBD decision aid. The examples are hypothetical, not results from a client project.
For each question, choose a route: show an agreed public answer, retrieve an authorised record, or pass the decision to a person. Some conversations will move between routes.
Reading a booking is also different from changing one. Write down which actions the assistant may take and which need a person to agree.
Test the handover before relying on it
Choose a question the assistant should not answer. Ask it for an exception to your normal terms, then ask for a person. Keep going until you can see what the team receives. Does the conversation arrive in the right place? Is someone responsible for replying, and can they understand the request without making the customer start again?
Then try the same thing when nobody is available. The customer needs an honest explanation of what happens next. Don't promise a callback time your team cannot keep.
Microsoft's fallback and handoff guidance recommends defining what the conversational experience can do and providing another route when it cannot help. The tests above are a practical way to check your own setup, not a claim that every chatbot includes a reliable handover.
Count the work left after the chat
Agree what a useful outcome looks like before starting a small trial.
Record the questions answered correctly and the answers that needed correction. Track requests passed to the team separately, including whether anyone followed up. Include the effort spent maintaining the source material and reviewing conversations.
Read the definitions behind a dashboard's numbers. In Copilot Studio's outcome reporting, a session can be recorded as resolved after the end-of-conversation topic is reached and the customer does not reply before the session times out. That is different from verifying that their request was completed.
If the main problem is website traffic without enquiries, start with the enquiry-path diagnostic. A new chat channel may be beside the point.
Use the questions to scope the work
Use the worksheet to write a smaller brief. If the answers are missing or hard to find, start with the pages. Once those answers are reliable, you can test whether an assistant helps people find them. Questions about a particular booking need a separate scope for the connection and its access rules.
For clearer service pages or a better enquiry form, see CBD's website design and care service. Scope any chatbot or booking-system connection separately.
Bring a few anonymised questions and the answers your team currently gives. Include one where the right answer is “someone needs to check”. That boundary belongs in the brief before the chatbot is built.
(CBD — 11)
Field notes
More articles
More articles
More articles
Plain-English notes on calls, admin
and websites — from real builds.
Plain English, no jargon
Fixed price before we build
You stay in control
Built on the Gold Coast
Most first builds live in 30 days

(CBD — 15)
NEXT STEP
Talk to
Josh
No call centre, no runaround —
you talk to the person who builds it.
No call centre, no runaround —
you talk to the person who builds it.
Let’s find the first
job to automate.
Tell us where the
work gets stuck and
we’ll map a first step.
Let’s find the first job to automate. Tell us where the work gets stuck and we’ll map a first step.
Let’s find the first job to automate. Tell us where the work gets stuck and
we’ll map a first step.
No preparation needed. Call 07 5690 5300
or send a quick message.






