Your agent answers wherever your customers ask — embedded widget, support email, Slack workspace, or wherever you connect it next.
Your customers don't all come through the same door.
Some click the chat widget on your site. Others email support@yourcompany.com directly. Some are in your shared Slack Connect channel. Some message you on WhatsApp. Today, your AI agent only sees the chat widget — every other channel is handled manually by your team.
That means the same question gets answered fast in one channel and slowly in another. The same content powers chat but not email. Your team duplicates effort across surfaces, and your customers get inconsistent experiences depending on where they reached out.
Multi-channel ingest fixes that by letting the agent respond on any channel you connect.
Email channel. Forward support@yourcompany.com to a Companin address (or use direct connection). Incoming emails route to the AI for a first-pass response. The visitor gets a reply within minutes — your team only steps in when needed.
Slack Connect channel. A customer in a shared Slack channel asks a question. The AI replies in-thread, drawing on the same knowledge base it uses for the widget. Your team can chime in or take over at any time.
Discord, WhatsApp, SMS. Each one is a separate connector — pick the channels your customers actually use. The AI behaves consistently across all of them.
Single conversation history. No matter which channel a conversation starts on, it lives in your dashboard alongside everything else. The same analytics, the same audit trail, the same export tools.
Meet customers where they are. Asking customers to use your preferred channel is a friction point. Some customers strongly prefer email. Some prefer Slack because they're already there for other vendors. Forcing one channel costs you support efficiency and customer satisfaction. Multi-channel removes the choice.
Same quality everywhere. Your widget gets fast, on-brand AI responses. Your email queue today gets... whatever your team types when they get to it. Multi-channel ingest brings the email queue up to widget quality without growing the team.
Coverage without headcount. A small team can't monitor five channels twenty-four hours a day. The AI can. It handles the first wave on every channel and only escalates the conversations that need a human.
Consistency across customers. A customer who emails today and chats tomorrow shouldn't get two different versions of your product's capabilities. Same AI, same knowledge base, same answers — regardless of channel.
For each channel, you connect once and configure routing rules:
Inbound messages flow into the same conversation system as widget chats. The AI uses the same knowledge base, applies the same configuration, and produces responses in the same format adapted to the channel's constraints (plain text for email, threaded replies for Slack, short messages for SMS).
Outbound responses go back through the channel they came from — the customer never knows whether they're talking to a person or AI unless your configuration tells them.
A separate ticketing tool for email. A separate Slack bot. The "we'll get back to you within 24 hours" auto-responder. The team member who copy-pastes answers from your dashboard into emails.
This feature is planned and will roll out per channel:
Each connector ships with channel-specific configuration: how to authenticate, how to route, how to format responses. The underlying AI and knowledge base infrastructure is shared — adding a channel doesn't mean rebuilding the agent.