> 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/deploy.md). # Deploy Publish Sagent through website widgets, QR codes, and other entry points. A deploy is the entry point that lets shoppers open Sagent. It connects the published experience to a website widget, QR code, or another customer-facing location. Use **Deploy** to choose where Sagent appears and how conversations begin. Enable only the entry points you are ready to make available. Sagent includes a default website entry. Open **Deploy** and select the **Default website entry** card to review it. {% hint style="info" %} You need at least one enabled deploy before publishing Sagent. {% endhint %} ### Create and configure a deploy {% stepper %} {% step %} #### Click + New Deploy Select a deploy type from the default options: * **QR Code:** Generates a QR code that opens Sagent. * **Chat Widget:** Adds an icon or styled button that opens Sagent. * **Inline Chat:** Displays the chat inside a selected website placeholder. Each default deploy type has its own settings. Select the type, then configure its tab-specific options. {% tabs %} {% tab title="QR Code" %} Use a QR Code deploy for printed or digital touchpoints. Save the deploy to activate its QR code. The **QR Code Preview** then provides these actions: * **Copy Link** copies the Sagent URL. * **Download PNG** downloads the QR code image. * **Copy preview link** copies a preview URL. You can manage the QR code later. This lets you update its destination without replacing the published asset. {% endtab %} {% tab title="Chat Widget" %} Use a Chat Widget deploy to add a Sagent launcher to supported website pages. Place the icon in a page corner, such as the bottom-right corner. You can also style it as a button to match your website.
Configure the launcher in **Design Preview**: * **Title** provides the accessibility label for the chat activation button. * **Page Position** places the launcher in a page corner. * **Label** adds optional text beside the icon, creating a labelled badge. * **Shadow** sets the launcher elevation. You can also set an icon, background colour, border radius, and custom CSS. Set **Chat frame title** to an accessible title for the chat window. Screen readers announce it when focus enters the chat. Enable **Allow camera access** when the chat needs photo capture. The browser asks the visitor before the chat accesses their camera. Set **Chat opened announcement** to the message screen readers announce when the chat opens. {% endtab %} {% tab title="Inline Chat" %} Use an Inline Chat deploy to display Sagent inside a website placeholder. Select the intended placeholder in **Locations**. When the selected flow is **Ask about a product**, choose the **Product source**. Use **Dynamic** when the page supplies the product context. Configure these settings in **Design Preview**: * **Title** provides the accessible title for the embedded chat. Screen readers announce it when focus enters the chat. * **Reserved height (px)** holds space until the chat reports its own height. This prevents the page from shifting as the chat appears. The value only needs to be approximate. * **Maximum width (px)** optionally caps the chat width. By default, the chat fills its placeholder. Set a cap when the page column needs one. * **Full screen on mobile** opens the chat across the mobile screen. The visitor returns to the page when they close it. Disable this for an in-page conversation in a short section, where less space is available for replies. You can also add custom CSS. {% endtab %} {% endtabs %} {% endstep %} {% step %} #### Choose a Sagent flow Choose how this deploy starts a conversation: * **Product discovery** starts the Guided Flow with the full catalogue. * **Ask about a product** starts the Product Flow with a product in context. Search for and select the product that shoppers should discuss. {% endstep %} {% step %} #### Name the deploy Add a clear name that identifies the deploy's purpose or placement. Add a description when your team needs more context. {% endstep %} {% step %} #### Set targeting Choose who can see the deploy. Add a condition or condition group, then select a filter type. Use presets for common product and cart audiences. You can also target page, product, product-engagement, visitor, referrer, region, or session data. Use **Locations** to limit the deploy to selected page types and apply the placeholder where it should appear (if required). {% endstep %} {% step %} #### Configure content The **Content** tab is available only for deploy types with editable content. Use it to localise available text and accessibility labels for each locale. * **Generate Content** drafts the available fields, if relevant. * **Generate Translations** creates translations for selected locales. {% endstep %} {% step %} #### Save, enable, and publish Click **Save** to store the deploy configuration. On the **Deploy** overview: * Use the **Enabled** toggle to choose whether the deploy is available in the next published version. * Use the deploy menu to **Edit**, **Duplicate**, or **Remove** it. After saving, navigate to the **Versions** tab and publish a new Sagent version. Deploy changes become live only when that version is published. {% endstep %} {% endstepper %} {% hint style="info" %} Chat widget deploys require the `@crobox/chat-activations` dependency. {% endhint %} ### Deploy best practices

QR code deploy

Use a QR code deploy on in-store signage, product packaging, or promotional materials. It gives customers a direct path to Sagent when they need help choosing a product. Place the code near the relevant product category or decision point.

Chat widget deploy

Place a chat widget deploy where shoppers may need advice, such as product listing pages or product detail pages. It keeps Sagent available without interrupting the browsing journey. Position the widget consistently so customers can find it easily.

Custom deploys

Create tailored entry points that fit your visitors guided shopping journey, using Crobox's existing components and placeholders. Explore possibilities with your Customer Success Manager during onboarding.

Start with focused targeting

Start with a limited audience and selected locations. Test the deploy before expanding its reach.
### Frequently asked questions
What is the difference between Product Flow and Guided Flow? Product Flow starts with a specific product in context. Guided Flow starts with the full catalog.
Can I remove certain entry points periodically? Yes. Disable specific deploys by toggling the enabled indicator off, and then publish a new version of Sagent within the **Versions tab.** You can re-enable it later without recreating the deploy. If you'd like to completely unpublish the Sagent periodically rather than a single entry point, you can head straight to the **Versions tab** and un-publish the Sagent. This can easily be re-published when ready.
Why is my deploy not visible? Confirm the deploy is enabled in the version you plan to publish. Check that its targeting conditions and locations match the page and visitor. Publish a new Sagent version after saving. Deploy changes become live only in a published version.
--- # 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/deploy.md?ask=&goal= ``` `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.