Skip to content
RosettaChat

Test answers and troubleshoot

Use your own test page and synthetic visitor details. Save your settings and start fresh conversations so previous agent activity does not suppress AI replies. Ordinary test conversations may count toward usage; do not assume they are free. The separate developer sandbox has its own setup.

TestWhat to check
A question answered in a published documentFacts and conditions match the document.
A paraphrase of that questionThe assistant still finds the relevant information.
An unknown policy or productIt does not invent business facts; the configured fallback is appropriate.
Conflicting or outdated contentCorrect the source material and retest rather than accepting a guessed answer.
A question in another supported languageMeaning, names, amounts, and dates remain correct.
A request for a humanThe conversation is flagged for attention and an agent can take over.
An agent claims or replies to the conversationThe bot stops contributing further replies.

Record the question, expected answer, actual answer, and source entry. Repeat affected cases after changing instructions or knowledge content.

  1. Confirm Enable bot has been applied and settings are saved.
  2. Check that the conversation is open and has no assignment, human reply, or earlier AI handoff.
  3. Check Stay silent was not selected as the applicable fallback.
  4. Check available usage in the dashboard.
  5. For knowledge-base mode, test the saved connection, publication status, and folder scope.

Find the intended source entry and check that it is published, in scope, and unambiguous. Remove conflicting instructions or outdated facts, save or publish the changes, then retest in a new conversation.

If the problem persists, note the time, workspace, conversation, and visible error. Share a minimal example with support, excluding API keys and unnecessary customer information. A connection success alone cannot validate the complete AI reply flow.