Omnichannel AI chatbot platform for web & messaging
Ship an AI chatbot for website, WhatsApp, Slack, Teams, email, SMS, Messenger, and Instagram—AI customer service across chat, email, and messaging from one assistant. Start web-only, then add 9+ integrations; logos match live connector pickers.
Web stacks & messaging apps (18)
Third-party marks belong to their owners; colors come from our proxied brand logo endpoint.
- Web deployment ships as an embeddable script plus an optional hosted chat or help URL with your branding, layout, and accessibility controls
- Messaging mirrors the deployment selector in the product: Slack, Discord, Teams, Telegram, WhatsApp, Messenger, Instagram DM, Twilio SMS, and email routing
- Lower plans can be limited to the web widget only; upgrading unlocks OAuth and API-key connections for the rest of the directory
- The same agent configuration, knowledge bases, and models power every surface—including API consumers
In the app, open an agent and use the Deployment tab to add surfaces.
On your site
Widget script and hosted page—two web fronts, one assistant
Most teams start from the Deployment tab: copy a snippet for any HTML surface or publish a standalone page that already matches your theme tokens.
Embeddable widget
Drop a script tag (or the installer helpers we document) next to your existing stack. The bubble, drawer, or inline frame pulls the live agent you selected.
- Works beside SPAs as long as the mount node loads after your bundle
- Conversation state follows the visitor until you clear storage or they leave
- Upgrade flows can deep-link to human handoff URLs when you configure them
Hosted chat or help URL
Need a shareable link for email signatures, QR codes, or support portals? Spin up the hosted surface with the same branding controls as the widget.
- Optional custom paths or subdomains depending on your deployment settings
- Accessibility toggles stay aligned with the widget configuration
- Ideal when you do not want to touch production HTML on day one
Branding, layout, and accessibility
Color, typography, launcher icons, and contrast choices live next to deployment settings so marketing and support can iterate without redeploying servers.
- Dark mode, reduced motion, and high-contrast presets where enabled
- Launcher placement and greeting copy tuned per agent
- Widget appearance can differ per environment when you use staging agents
Publish anywhere you already build
Below is a representative list of stacks teams mention in rollout plans—logos use the same color pipeline as connectors so previews match the dashboard.
- Commerce platforms, site builders, and hand-rolled React or Next.js apps
- Same snippet for marketing microsites and authenticated app shells
- Pair with our API when you need a fully custom canvas
Popular site builders & stacks
Paste the same embed snippet into these environments—logos reflect the stacks we document most often alongside the widget.
WordPress
Shopify
WooCommerce
BigCommerce
Webflow
Wix
Squarespace
React
Next.js
Off the web
Every messaging platform in the deployment selector
Connections are created per agent inside Automations, then surfaced again when you add a deployment. OAuth covers Slack, Discord, Microsoft Teams, Meta apps, and several storage-backed flows; API keys cover Telegram, WhatsApp Business, Twilio, SendGrid, and similar vendors.
Team chat and communities
Slack workspaces, Discord servers, Microsoft Teams, and Telegram bots each get their own deployment row with status, reinstall, and error visibility.
- OAuth redirects return you to the same agent deployment screen you started from
- Channel or workspace IDs are stored so rerouting survives token rotation
- Great for internal copilots as well as customer-facing community moderators
WhatsApp, SMS, and email
WhatsApp Business and Twilio SMS rely on vendor-specific credentials; email can ingest inbound threads via webhook-style routing so tickets stay in FlexyAgents.
- Twilio numbers map cleanly to the SMS deployment type
- SendGrid and other mail providers align with transactional and inbound automations
- Ideal when your customers already expect async replies on mobile
Meta surfaces
Facebook Messenger and Instagram DM deployments share Meta OAuth when you connect the business assets that should receive automated replies.
- Respects page-level permissions you grant during OAuth
- Pairs with the same moderation settings you use natively in Meta
- Keep human reviewers in the loop with handoff URLs from the agent
Same brain as the widget
Model selection, knowledge bases, tools, and automations do not fork per channel—you configure once and let deployment records decide where conversations land.
- Analytics roll up per deployment so you can compare web vs Slack volume
- Rate limits still apply per vendor API even when FlexyAgents batches work
- Pause a deployment without deleting the underlying connection
Messaging & delivery connectors
Connect from Automations, then attach a deployment row for each channel—these names match the connection catalog.
Slack
Discord
Microsoft Teams
Telegram
WhatsApp Business
Facebook Messenger
Instagram
Twilio SMS
SendGrid
Plans & roadmap
Widget-only tiers, full omnichannel upgrades, honest gaps
Plans can ship with web-widget-only channel access. When that limit is on, the product blocks OAuth for Slack, Discord, WhatsApp, and the rest until you upgrade—matching what deployment APIs enforce.
Web widget on every plan
Free and entry hosted tiers still ship the script and hosted page so you can prove value before expanding into paid messaging connectors.
- Messaging grid stays visible in marketing so buyers know what unlocks later
- Upgrade copy in-product points at Starter and above—align sales decks with that story
- No fake “connected” state: APIs block OAuth until the flag flips
Operational visibility
Each deployment shows active, pending setup, or error states so support teams know whether a channel is healthy without digging through raw logs.
- Reconnect flows reuse the same OAuth or API key modals
- Great for regulated teams that need evidence a channel was deliberately paused
- Pairs with analytics retention windows from your subscription
LinkedIn is not wired up yet
The selector lists LinkedIn as “coming soon” on purpose—do not promise parity with Meta or email until the integration ships.
- Use this page with sales to set expectations during enterprise rollouts
- Watch release notes when LinkedIn messaging leaves the placeholder state
- Other channels above are live connection targets today
Same connectors power knowledge sync on Connectors, models on Hosted vs BYOK, and the full capability map on Features.
Next step
Publish one agent everywhere it matters
Drop in the widget, share a hosted URL, then layer Slack or WhatsApp when your plan unlocks full messaging. APIs stay available for anything custom.