The questions your support assistant can't answer are your best to-do list

When an AI assistant can't answer a question, it's tempting to see that as a failure. It's more useful to see it as information. Every unanswered question is a customer telling you, in their own words, something they wanted to know and couldn't find.

Most businesses never see this. On a website without chat, a visitor who can't find the delivery cost just leaves. On the phone, the question gets answered and forgotten. A support assistant writes it down. That gives you something rare: a running list of the gaps in what you tell customers.

Here's how to use it.

Why "couldn't answer" is a good outcome

An assistant that says "I don't know" is doing its job. The alternative is an assistant that guesses, and a confident wrong answer about your returns policy or opening hours is much worse than an honest "let me get someone to help".

Chatzora answers from the information you've given it. When nothing in that information matches the question well enough, it sends your "doesn't know" message instead of guessing, and records the question. You can adjust how strict this is with the setting How sure your assistant must be before answering. Stricter means fewer wrong answers and more questions passed to you. Looser means more answers, with a higher chance of a weak one. Most businesses should start strict.

Where the questions end up

Questions the assistant couldn't answer, and ones where it answered but wasn't confident, go into the Review Queue in your dashboard. Each item shows the customer's question and what the assistant said.

For each one you have a few options:

• Add the correct answer. Write the answer the way you'd want a customer to see it. From then on, the assistant uses it when someone asks the same thing or something close to it.
• Use your team's reply. If someone on your team already answered the customer in that conversation, the Review Queue suggests that reply as the answer. Often you only need to tidy it up and save it. The answer you gave one customer by hand becomes the answer for everyone after them.
• Dismiss it. Some questions don't need an answer: test messages, spam, or things you'd never want the assistant to handle.

A 20-minute weekly routine

You don't need to watch the queue all day. Once a week is enough for most small businesses. Pick a quiet time, for example Monday morning, and do this:

1. Read the weekly email first. Chatzora sends a weekly summary for each assistant. It ranks the questions that went unanswered most often, so the ones asked five times appear above the ones asked once. Start with the top of that list. One answer there can cover dozens of future conversations.

2. Work through the queue, most common first. For each question, ask yourself: is this something customers should be able to find out without talking to me? If yes, add an answer. If it really needs a person, such as a complaint or an account problem, leave it to your team and dismiss it.

3. Write answers for customers, not for yourself. Include the actual detail. "We're closed on public holidays except Good Friday, when we open 10am to 2pm" is better than "see our holiday hours". If the answer depends on something, say what: "Delivery is next day for orders before 2pm, otherwise two days."

4. Fix the source, not just the assistant. If the same gap keeps appearing, the real problem may be your website or your price list. A bakery that keeps getting "do you have gluten-free options?" should probably say so on its menu page. Update the page, and if the assistant learns from your website, it will pick up the change the next time the site is refreshed.

5. Check one or two answers. After adding a few answers, open the test chat and ask the questions again, in slightly different words. Make sure the assistant now gives the answer you wrote.

What the list tells you about your business

After a month, step back and look at the kinds of questions that came up. Patterns are often more useful than any single question.

• Lots of questions about price may mean your prices are hard to find, or that customers want a rough idea before they call.
• Repeated questions about a product or service you don't offer may be worth thinking about. Ten people asking a clinic whether it does evening appointments is a signal.
• Confusion about a policy suggests the policy itself is unclear, not just the way it's explained.
• Questions in another language tell you something about your customers you may not have known.

These are things you'd normally only learn from a customer survey, and few small businesses run those. Your unanswered questions give you a version of that for free, every week.

Keep an eye on the "almost right" answers

Not every gap is a question the assistant refused to answer. Sometimes it answers, but the answer is incomplete or slightly off. Those are harder to spot, so use two other signals:

• Low-confidence answers also show up in the Review Queue. Read them, even if they look fine at first glance.
• Customer ratings. On the website chat, customers can say whether a conversation was helpful. A conversation marked "not helpful" is worth opening to see what went wrong.

How you know it's working

A healthy pattern looks like this: in the first few weeks, the queue fills up quickly as real customers ask things you didn't think of. You add answers. The weekly list of repeated unanswered questions gets shorter, and the same questions stop appearing at the top.

The queue will never be completely empty, and it shouldn't be. Customers will always ask new things, and some questions should always go to a person. The goal isn't zero. It's that the questions you see each week are new ones, not the same ones you saw last week.

Treated this way, the questions your assistant can't answer stop being a weakness. They become the most reliable to-do list you have for improving what you tell customers.