Channels
Start with the website widget and playground, then connect the same agent to team chat, Meta messaging, Telegram, Discord, SMS, RCS, iMessage, email, API, and voice channels when the implementation needs them.
01
Launch on a public site, test in the playground without consuming credits, and keep the experience close to your brand.
Install with a lightweight script or iframe.
Preview behavior before publishing.
Use custom colors, placement, greeting copy, and domain controls.
02
Bring AI support into the channels your team already watches.
Install Slack with OAuth when configured.
Choose Slack channels for threaded replies.
Use Teams app credentials for Microsoft Teams.
03
Meet customers in familiar chat apps while reusing the same knowledge, instructions, and approved Actions.
Use Meta setup for WhatsApp, Messenger, and Instagram.
Use manual credentials for Telegram and Discord.
Use Twilio-backed setup for WhatsApp, SMS, RCS, and iMessage where configured.
04
Support Instagram Direct conversations from the same agent used on the website and other Meta channels.
Handle common pre-sale questions.
Guide visitors to next steps.
Escalate when human help is needed.
05
Use the agent for asynchronous and phone-style support channels where concise, channel-aware answers matter.
Use IMAP/SMTP-style email credentials.
Connect SMS, RCS, and voice through Twilio credentials.
Apply channel-specific prompts for plain text or spoken responses.
06
Use the API channel for custom frontends, server-side workflows, and product-specific conversation surfaces.
Reuse the same agent logic.
Send webhook callbacks when configured.
Build channel-specific support flows.
Yes. The goal is one trained agent that can be deployed across multiple surfaces.
No. Most teams should launch the website widget first, then add channels where demand is clear.
No. Channel access depends on plan limits and integration availability.