Skip to content

Turn a wrong answer into a useful correction.

Use the actual visitor question, confirm what should have been said, and check the result. This guide follows the correction from the inbox to your website assistant.

How do I correct an incorrect chatbot answer?

Find the original question, select its website, confirm the correct business information and save an approved correction through Ask Sairo or the knowledge controls. Test the original and related questions, and update any conflicting source page.

First-party product guidance. How we maintain these guides · Report a correction

1. Find the original question and choose the website.

Open the conversation in the inbox and choose “Review with Ask Sairo”, or open Ask Sairo and describe the exchange you want to find. Check the transcript before changing anything: a missing detail, a stale policy and a request for a person need different responses.

Select the website the answer belongs to. If you manage several clients, include the business or website name in your request and confirm the selected site in the proposed change.

2. Establish the correct information.

Ask Sairo to inspect the relevant saved answer and source information. Confirm the replacement with the person responsible for that policy. “This answer is wrong” does not tell the assistant whether the hours, location or booking conditions have changed.

For this example, imagine the assistant said appointments were unavailable at weekends. The business has confirmed that Saturday consultations are available from 10am to 2pm, by appointment. Include the condition as well as the hours.

Example correction to enter in Ask Sairo

Question: Do you offer weekend consultations? Answer: We offer Saturday consultations from 10am to 2pm, by appointment. We do not offer Sunday consultations.

3. Review and save the proposed answer.

Check the question, replacement text and website on the proposal. Apply the change when they match the approved information, or dismiss it and provide a clearer correction.

If automatic corrections are enabled, an explicit, unambiguous question-and-answer correction for one selected website can be saved directly. Turn that setting off when you want to review every correction. Either route records the completed change; a request that only reports an error should lead to clarification.

For a business fact such as a phone number or opening hours, ask for the specific fact to be updated as well when appropriate. A saved answer and a confirmed business detail are separate records, so check which record your request affects.

Walkthrough 021:10Captions and transcriptDownload MP4Captions (VTT)

Teach Sairo a better answer. Save confirmed information and check the next reply.

Before you start: Use an account with permission to edit website knowledge. The workspace, visitors and figures shown are fictional examples.

Read the transcript
  1. A better answer starts with you.

    A visitor asks about Sunday inspections. Here's how to give Sairo the confirmed answer your team wants to use.

  2. Open the library

    Open Knowledge library, then choose Add saved answer. Select the website that this information belongs to.

  3. Be specific

    Enter the exact question and a clear, verified answer. Here, the business confirms that Sunday inspections are unavailable and gives the visitor a useful next step.

  4. Save the answer

    Select Save new answer. Wait for confirmation. Saved answers take priority when a visitor asks a matching question.

  5. Check coverage

    In Check your knowledge, enter the same visitor question and select Check source coverage. This checks saved knowledge; it does not generate a live reply.

  6. Read the result

    Look for A saved answer is ready. Read the returned wording and confirm that it answers the question completely.

  7. Try the next reply

    Now ask the question in the website assistant. The visitor receives the saved answer, including the next step for arranging an inspection.

  8. Teach once. Help the next visitor.

    Repeat this whenever a policy changes or a visitor finds a gap. Keep the wording specific and confirmed.

All five walkthroughs

4. Check the original question and nearby questions.

Use the answer-check action, then test the visitor assistant with the original question. Exact saved-answer matching prioritises the approved wording, subject to handoff rules. Similar wording can use semantic retrieval, so a single passing question is not enough.

Try “Can I book a Saturday consultation?”, “Are you open on Sunday?” and a question about a weekday appointment. The Saturday correction should not invent Sunday availability or change unrelated weekday information.

A small correction test set
QuestionExpected result
Do you offer weekend consultations?The approved Saturday hours and appointment condition.
Are Sunday consultations available?No Sunday consultations, as confirmed in this example.
What does a consultation cost?Use a separate supported source or acknowledge that the price is unavailable.

5. Fix the source and keep the change reviewable.

If the website still publishes the old policy, update that page too and refresh the relevant content. Otherwise visitors reading the page and visitors using the assistant may see conflicting guidance.

Keep the original question in your review set and watch for related gaps. Use Undo on the recorded change if it should be reverted. When somebody has edited the same record since your change, review its current state and prepare a new correction instead of overwriting the newer work.

When the correction does not appear.

Confirm that the proposal says it was applied, belongs to the intended website and contains the question you tested. Check whether the original exchange triggered human handoff, whether a nearby question needs different wording, or whether another source still conflicts.

If your role cannot edit answers, ask an authorised teammate to review the correction. A disconnected model, missing embedding configuration or interrupted request can leave a proposal unfinished; inspect the recorded result before retrying. Report the question, website and change status to support without sending credentials.

See what your website can answer.

Try a sample, review the result, and decide what comes next.