> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/how-to-guides/sagent/validate-before-launch.md).

# Validate before launch

Test Sagent's catalog, conversations, and entry points before publishing.

Testing confirms that Sagent works correctly before shoppers use it. It catches product data, conversation, and launch issues while they are safe to fix.

Use this checklist to test the tasks shoppers are most likely to complete. Fix unexpected results before publishing.

{% stepper %}
{% step %}

### Check product coverage

In **Products**, search and filter by different product attributes. Repeat this for every language and market you support.

Verify each result has the correct title, price, image, availability, and product link.
{% endstep %}

{% step %}

### Test conversations

Use preview mode in **Setup** to test real shopper questions. Test clear questions, unclear questions, and detailed questions.

Test both experiences:

* Start **Product Flow** from a product page.
* Start **Guided Flow** with the full product catalog available.

Test each enabled feature, including **Comparison** and **Review summarizer**.
{% endstep %}

{% step %}

### Record your test results

Create one row for each shopper task before testing. Record what should happen, what happened, the tester, device, language, and market.

| To check                  | Test                                                       | Expected outcome                                            |
| ------------------------- | ---------------------------------------------------------- | ----------------------------------------------------------- |
| Products and markets      | Search key attributes in each language and market.         | Only available products appear with translated information. |
| Guided Flow               | Test clear, unclear, and detailed questions.               | It asks useful questions and recommends suitable products.  |
| Product Flow              | Start from a product page.                                 | It uses the product shown on that page.                     |
| Enabled features          | Test each feature, such as comparison or review summaries. | Each feature opens and shows relevant information.          |
| Product links and buttons | Open every product link and button.                        | Links reach the correct page and buttons work.              |
| AI disclosure             | Start Sagent from every launch location.                   | The AI notice appears before the first message.             |
| Mobile and desktop        | Repeat key tasks on mobile and desktop.                    | Content is readable and controls are easy to use.           |

Test every place where shoppers can open Sagent. Include each page type, market, and language.
{% endstep %}

{% step %}

### Investigate failures

Do not publish while a key shopper task fails. Identify the area that needs fixing:

* **Products:** Product information is missing, incorrect, unavailable, or untranslated.
* **Knowledge or guidance:** Answers are incorrect, questions are weak, or recommendations do not fit.
* **Behavior or design:** Features, links, buttons, AI notices, or layouts do not work correctly.
* **Launch settings:** The wrong audience, language, version, or publishing settings apply.

Run the same test again after each fix. Publish only when every required test passes.
{% endstep %}

{% step %}

### Check AI and privacy notices

Open Sagent from every launch location. Confirm the AI notice appears before the first shopper message. Confirm privacy information and links are visible and correct.
{% endstep %}

{% step %}

### Monitor after launch

Review [Monitoring](/how-to-guides/sagent/monitoring.md) after major updates. Investigate flagged or unexpected conversations. Then improve the guidance or product information.
{% endstep %}
{% endstepper %}

### Frequently asked questions

<details>

<summary>Why should I test simple and complex queries?</summary>

Testing catches missing product information and conversation issues before shoppers encounter them. Detailed questions can also reveal unclear guidance and unexpected answers.

</details>

<details>

<summary>What should I check at every entry point?</summary>

Check that Sagent opens correctly. Confirm the AI notice is visible. Check that the right experience starts and uses the expected products.

</details>

### Why validation matters

Sagent can misunderstand shoppers or suggest unsuitable products when product information or guidance has gaps. Test clear and detailed questions to find issues before launch.

### What's next

* [Monitoring](/how-to-guides/sagent/monitoring.md)
* [Analytics](/how-to-guides/sagent/analytics.md)
* [Setting up a Product Feed](/how-to-guides/product-data/setting-up-a-product-feed.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.crobox.com/how-to-guides/sagent/validate-before-launch.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.