Deploy

The Deploy tab is where you turn an agent into a live front office. It shows your launch readiness, active channels, setup gaps, and the code or URLs you need to share the agent.

​

Launch readiness

Before you send traffic to an agent, check the readiness summary at the top of the Deploy page. Readiness is not only about whether a feature switch is on. For example, CRM capture needs pipeline/status setup, and workspace delivery needs an actual published workspace URL when you want to share generated files or pages.

​

Channel states

Each deploy card shows the current state of that channel.

​

Primary channels

​

Hosted agent page

Publish the agent page when you want a standalone public URL that customers can open directly. This is the fastest way to share a sales assistant, intake assistant, support front office, or booking agent. Use this when:

• you need a public link for prospects or customers
• you want a branded agent page without installing code
• you are testing the full conversation flow before embedding

​

Website widget

Enable the website widget when you want the agent to handle visitors on your site. The Deploy page gives you the install snippet and widget settings. Use this when:

• your website should capture, qualify, and book leads
• the agent should answer support questions without leaving the page
• you want CRM, calendar, workspace, and custom interfaces inside the widget

​

Agent email

Agent email lets people email your agent directly. Use it for support inboxes, lead intake, service requests, or follow-up conversations. The Deploy page shows:

• the agent email address
• whether inbound email is enabled
• whether auto-reply is enabled
• whether owner notifications are enabled

​

Inline embed

Use inline embed when you want the full agent experience inside a page instead of a floating widget. This is useful for:

• help centers
• booking pages
• client portals
• onboarding pages
• internal tools

​

Workspace publish

Workspace publish turns files or pages created by the agent into a shareable workspace URL. Use this when the agent produces deliverables, plans, pages, prototypes, documents, or reports. The channel is only launch-ready when a workspace is actually published.

​

Custom domain

Custom domains let you serve the hosted agent or workspace under your own domain. A domain can be:

• Active - ready to share
• Pending - DNS or verification still needs to finish
• Failed - DNS or ownership verification needs attention

​

Advanced channels

The Router SDK supports advanced messaging channels such as:

• Slack
• Discord
• Telegram
• WhatsApp
• Crisp

Use Router SDK channels when your front office should live inside a community, support inbox, or messaging platform.

​

Widget SSO

Widget SSO lets your site identify signed-in users before they chat with the agent. Use it when you need user-specific memory, workspace access, account context, or authenticated support flows. See Chat Widget SSO for the token flow.

​

Launch package

Before going live, collect the launch package from the Deploy page:

• hosted page URL
• widget snippet
• agent email address
• published workspace URL, if relevant
• custom domain, if active
• enabled channels
• remaining setup-required or plan-gated items
• one test prompt for a real visitor scenario

​

Next Steps