Skip to main content
Choose your deployment channel before planning the launch. A channel shown in the interface may be stable, beta, or planned, and each supported connection has its own setup requirements. The table below reflects the currently reviewed Builder guides and configuration sources. Confirm the available controls in the workspace and release you intend to use before committing to a customer rollout.

​
Compare the documented deployment options

​
Understand what the status means

Stable identifies the established deployment path described in the current guides. It does not remove the need to configure the agent, connect the channel, and test the customer experience. Beta means you should evaluate the connection against the needs of your particular workflow. Confirm provider requirements and the behavior your team depends on before using it for a wider rollout. Coming soon means the visible integration should not be treated as available for that launch. A card or brand logo alone is not evidence that the connection can be enabled.

​
Distinguish a native connector from an embed

A planned native WordPress or Shopify connection does not by itself answer whether a generic website embed can be installed on your site. That depends on the site’s embedding capabilities and configuration. Similarly, a custom API workflow is different from a ready-made native connector. Ask which operation is supported and what must be configured rather than relying on the integration name alone.

​
Start with one channel

A fictional retailer might first test policy answers in its web widget. It can evaluate WhatsApp separately after completing the provider connection and checking how identity and handoff work there. This approach makes it easier to isolate a problem. If the behavior changes between Playground and the live channel, you can inspect that specific path before expanding.

​
Verify the customer-facing experience

After releasing the reviewed agent to Production, test a normal request, a failed lookup where relevant, and a handoff. Check what the customer sees and what your team receives. Follow the deployment guide for configuration details after selecting your first channel.