> 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/setup-your-sagent.md).

# Setup your Sagent

## Set up and launch Sagent

Sagent is an AI-powered guided selling chatbot that uses your product catalog to help shoppers find the right product through natural conversation. It draws on your product data and category knowledge to ask the right questions, understand what a shopper is looking for, and surface the most relevant recommendations.

This guide walks you through everything you need to get Sagent live — from creating the experience and connecting your product data, to configuring how it behaves, what it says, and how your customers will access it.

### Before you begin

Make sure the following are in place before you start:

* Your product data is available in Crobox. If it isn't yet, set this up first:
  * [Setting up a Product Feed](/how-to-guides/product-data/setting-up-a-product-feed.md)
  * [Manage and Transform Product Properties](/how-to-guides/product-data/manage-and-transform-product-properties.md)
  * [AI Enricher Properties (text-based)](/how-to-guides/product-data/ai-enricher-properties-text-based.md)
* You have access to **Experiences** in the Crobox platform
* You know which export feed contains the product data Sagent should use

***

### Set up

Create the Sagent and connect it to your product catalog.

{% stepper %}
{% step %}

#### Open the creation flow

Go to **Experiences → Sagent → New Sagent**.
{% endstep %}

{% step %}

#### Set the basic details

Set the **Chatbot Name**, **Product Categories**, if relevant, and the **Chat Language**.
{% endstep %}

{% step %}

#### Save the Sagent

Click **Save**.
{% endstep %}

{% step %}

#### Connect the data source

Open the **Products** tab, select the export feed Sagent should use, and click **Sync**.

{% hint style="info" %}
Use **Product Categories** if your catalog contains distinct product groups — this helps Sagent stay focused on the right assortment rather than searching across unrelated products.
{% endhint %}
{% endstep %}

{% step %}

#### Test the data connection

Go to **Setup → General**, start a conversation in the preview panel, and confirm Sagent can access your product data before moving on.
{% endstep %}
{% endstepper %}

***

### Knowledge

Sagent's knowledge comes from the product data in your connected feed. The products that remain after your feed is synced are what Sagent draws on to answer questions and make recommendations.

{% stepper %}
{% step %}

#### Open the product catalog

Open the **Products** tab.
{% endstep %}

{% step %}

#### Review what Sagent can access

Use the search and filters to browse the catalog and confirm the right products are available to Sagent.

{% hint style="info" %}
The quality of Sagent's recommendations depends directly on the quality of your product data. Well-structured properties and complete descriptions give Sagent more to work with.
{% endhint %}
{% endstep %}

{% step %}

#### Fix data issues at the source

Check for missing products, incorrect values, or incomplete descriptions. Review your feed setup if something looks off, then update the source data and sync again if needed.
{% endstep %}
{% endstepper %}

If something looks off, the issue is likely in your feed setup. Use the links in [Before you begin](#before-you-begin) to review your product data configuration.

***

### Behaviour

Control how Sagent conducts the conversation and when it shows recommendations.

{% stepper %}
{% step %}

#### Open the behavior settings

Go to **Setup → Behavior**.
{% endstep %}

{% step %}

#### Set recommendation thresholds

Set the **Recommendation Thresholds** to control when Sagent asks more questions versus showing results:

* **Maximum Matches** — ask again if too many products still match
* **Maximum Questions** — stop after a set number of questions
* **Minimum Details** — require enough user input before recommending
  {% endstep %}

{% step %}

#### Adjust tone and answer length

Adjust **Tone of voice** and answer length to match your brand.
{% endstep %}

{% step %}

#### Add guidance prompts

Add **Guidance Prompts** for any conversational behavior that standard settings don't cover.
{% endstep %}

{% step %}

#### Open the question flow

Open the **Guidance** tab.
{% endstep %}

{% step %}

#### Review suggested questions

Review the questions Sagent's algorithm has suggested, shown in priority order.
{% endstep %}

{% step %}

#### Reorder the questions

Drag and drop questions into the order you want Sagent to ask them.
{% endstep %}

{% step %}

#### Hide questions you don't want to ask

Use the **eye icon** to hide any questions Sagent shouldn't ask. Hidden questions can be restored at any time from the **Questions hidden by you** section at the bottom of the page.
{% endstep %}

{% step %}

#### Enable multi-select where needed

Enable **Multi Select** on any question where users should be able to choose more than one answer.

{% hint style="info" %}
Use the answer chips to simulate user selections and preview how Sagent responds. This is for testing only — it doesn't affect your configuration.
{% endhint %}
{% endstep %}
{% endstepper %}

***

### Content

Update the copy and visual design so Sagent feels like a natural part of your experience.

{% stepper %}
{% step %}

#### Open the content settings

Go to **Setup → Content**.
{% endstep %}

{% step %}

#### Review the prefilled copy

Review the prefilled copy across the experience.
{% endstep %}

{% step %}

#### Update the copy

Update any text to match your brand.
{% endstep %}

{% step %}

#### Complete the privacy policy content

Complete the **Privacy Policy Content** field before launch.

{% hint style="warning" %}
You must complete the **Privacy Policy Content** field before Sagent can go live. Don't leave this until launch day.
{% endhint %}
{% endstep %}

{% step %}

#### Save your content changes

Click **Save**.
{% endstep %}

{% step %}

#### Open the design settings

Go to **Setup → Design**.
{% endstep %}

{% step %}

#### Set theme colors

Under **Theme & Colors**, set your **Primary Color**, **Primary Text Color**, **Surface Color**, and **Secondary Text Color**.
{% endstep %}

{% step %}

#### Set the gradients

Set the **Aurora** and **Animation Shine** gradients — these control the animated gradient on the loading screen and the shimmer effect that plays as each question appears.
{% endstep %}

{% step %}

#### Update the appearance

Under **Appearance**, upload your **Top Bar Icon** and set a **Chat Background** image or color.
{% endstep %}

{% step %}

#### Adjust the roundness

Adjust **Button and Sagent Roundness** to match your brand's style. The default is 6px across all elements.
{% endstep %}

{% step %}

#### Apply advanced styling if needed

Under **Advanced**, use the pre-filled CSS selectors to apply any further custom styling.

{% hint style="warning" %}
Without brand colors and an icon, Sagent will launch with Crobox's default styling. It's strongly recommended to update the Design tab before any demo or client-facing launch.
{% endhint %}
{% endstep %}
{% endstepper %}

For a deeper look at every design option, see Configuring the Design tab.

***

### Translations

If your Sagent needs to support multiple languages, set up your translations before launch — this covers the static copy users see throughout the experience.

{% stepper %}
{% step %}

#### Open the translations tab

Go to the **Translations** tab.
{% endstep %}

{% step %}

#### Select a language

Select a language from the dropdown. The languages available reflect what's set up in your Crobox account.
{% endstep %}

{% step %}

#### Review the fields

Review each field — the original English copy is shown alongside for reference.
{% endstep %}

{% step %}

#### Add or generate translations

Update the translations as needed, or click **Generate Translations** to auto-fill using AI.
{% endstep %}

{% step %}

#### Save the translations

Click **Save**.

{% hint style="info" %}
Translations cover static interface copy such as the chat title, loading messages, and privacy policy text. Product content is drawn directly from your product feed and handled separately.
{% endhint %}
{% endstep %}
{% endstepper %}

***

### Deploy

A deploy is the entry point through which users open Sagent — whether that's a floating chat button on your website or a QR code in a physical store. Sagent comes with a default chat widget deploy already in place, so you're not starting from scratch.

{% stepper %}
{% step %}

#### Review the default deploy

Go to the **Deploy** tab. You'll see a **Default website entry** card already created — a floating chat button that appears bottom-right on the page. Click the card to review its settings and adjust if needed.

{% hint style="info" %}
You need at least one enabled deploy before Sagent can be published.
{% endhint %}
{% endstep %}

{% step %}

#### Create a new deploy

Click **+ New Deploy**.
{% endstep %}

{% step %}

#### Choose the deploy type

Set the **Deploy Type** — for example, a chat widget or a QR code.
{% endstep %}

{% step %}

#### Choose the Sagent flow

Set the **Sagent Flow** to control how the conversation starts:

* **Product discovery** — starts the Guided Flow, with the full catalog in scope
* **Ask about a product** — starts the Product Flow, with a specific product already in context
  {% endstep %}

{% step %}

#### Name and configure the deploy

Give the deploy a name and description so it's easy to identify later. Configure any type-specific settings, such as page position for a chat widget or generating and downloading the QR code image.
{% endstep %}

{% step %}

#### Save the deploy

Click **Save**.
{% endstep %}

{% step %}

#### Manage existing deploys

* **Enable or disable** a deploy using the toggle on its card. Disabling takes it offline immediately — useful if you need to pull it down temporarily without removing it entirely.
* **Duplicate** a deploy as a starting point for a similar one — for example, a second QR code for a different product or location.
* **Remove** a deploy to delete it permanently.
  {% endstep %}
  {% endstepper %}

For a full overview of deploy types and configuration options, see Configuring deploys.

***

### Validate before launch

Before going live, confirm that Sagent works correctly across the scenarios your users are likely to encounter.

{% stepper %}
{% step %}

#### Check catalog coverage

In the **Products** tab, use the search and filters to verify the right products appear for different property combinations.
{% endstep %}

{% step %}

#### Test Sagent in preview

In the **Setup** tab, chat in preview mode to test how Sagent responds to real queries.
{% endstep %}

{% step %}

#### Test the Product Flow

Open the chat with a specific product in context, as a user would from a product detail page or QR code.
{% endstep %}

{% step %}

#### Test the Guided Flow

Start from scratch with the full catalog in scope.
{% endstep %}

{% step %}

#### Test simple and complex queries

Test straightforward queries as well as ambiguous or complex ones.
{% endstep %}

{% step %}

#### Test additional capabilities

If you've configured additional capabilities such as the **Comparison** tool or **Review summarizer**, confirm these work as expected.
{% endstep %}
{% endstepper %}

**Why this matters:** Even a well-configured Sagent can misinterpret answers or surface the wrong products if the data or question logic has gaps. Testing both simple and complex scenarios is the best way to catch those issues before your users do.

***

### What's next

Once Sagent is live, you'll want to keep an eye on how it's performing:

* [Monitor Sagent conversations](/how-to-guides/sagent/how-to-use-the-monitoring-tab.md)
* [Understand Sagent analytics](/how-to-guides/sagent/how-to-use-analytics.md)
* [Update your product feed](/how-to-guides/product-data/setting-up-a-product-feed.md)

***

### Frequently asked questions

<details>

<summary>What makes Sagent's recommendations accurate?</summary>

Sagent draws on the product data in your connected feed and its built-in knowledge of your product category. The more complete and well-structured your product properties are, the better Sagent can match shoppers to the right products.

</details>

<details>

<summary>How do I know which export feed to use?</summary>

Use the feed that contains the product assortment you want Sagent to recommend from. If you're unsure which feed is correct, check with the person who manages your product data in Crobox.

</details>

<details>

<summary>What happens if I skip the Privacy Policy Content field?</summary>

You won't be able to take Sagent live. This field is required before launch, so it's worth filling it in during the Content step rather than at the last minute.

</details>

<details>

<summary>Can I change the data source after Sagent is live?</summary>

Yes. Go to the **Products** tab, select a different export feed, and click **Sync**. Be aware that switching feeds may affect the products Sagent recommends, so test after making the change.

</details>

<details>

<summary>What's the difference between the Product Flow and Guided Flow?</summary>

The Product Flow starts with a specific product already in context — for example, when a user opens Sagent from a product detail page or a QR code. The Guided Flow starts fresh, with the full catalog in scope. Both should be tested before launch to make sure Sagent handles each entry point correctly.

</details>

<details>

<summary>How many questions should Sagent ask before recommending products?</summary>

This depends on your catalog and your users. Use the **Maximum Questions** threshold in the **Behavior** settings to set a ceiling, and the **Minimum Details** threshold to ensure Sagent collects enough input first. A good starting point is to test with three to five questions and adjust based on how well the recommendations match what users are looking for.

</details>


---

# 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/setup-your-sagent.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.