It is 11pm. A customer is on your website trying to figure out why their account is locked. Your chat widget is not there. They send an email and wait. Another customer is in Slack asking your team a question that your agent could have answered in seconds. A third one gives up and opens a support ticket that will sit in a queue until Monday.

None of that has to happen. Outlearn lets you deploy the same agent across every channel your customers and team use - your website, your email inbox, your team chat tools, your helpdesk. Configure it once and it shows up everywhere it needs to be. This article gives you a full overview of every deployment option so you can decide where your agent should live first.

In this article, you'll learn:

• What the Deploy tab is and how it works
• Every channel your agent can be deployed to
• What each channel does and who it's for

The Deploy Tab

The Deploy tab is where you choose where your agent operates. You can deploy to as many channels as you need - each one is configured independently, and your agent runs on all active channels simultaneously.

Available Channels

Chat Widget

A branded chat bubble that lives on your website. Users click it to open a conversation with your agent. This is the most common deployment - it's what most customers will interact with.

Best for: Customer-facing support on your website or product.

Email

Your agent gets a dedicated inbound email address. When customers email it, the agent reads the message, drafts a response, and either sends it or hands it off to your team.

Best for: Teams that receive support requests by email and want to automate first responses.

Slack

Your agent lives inside your Slack workspace. Team members can mention it in any channel to get instant answers.

Best for: Internal agents for employee support — HR questions, IT help, internal documentation lookups.

Microsoft Teams

Your agent is available inside Microsoft Teams — no tab-switching or separate tools required.

Best for: Teams that work primarily in Microsoft Teams and want their agent accessible without leaving the platform.

Google Chat

Your agent is available in any Google Chat space. Questions get answered inline, instantly.

Best for: Teams that use Google Workspace and want the agent accessible within their existing chat environment.

Helpdesk Copilot - Zendesk

Your agent is installed inside Zendesk, where it reads every incoming ticket and drafts a suggested reply. Your agent reviews the draft and sends it with one click.

Best for: Support teams using Zendesk who want AI assistance without giving up human oversight.

Helpdesk Copilot - Intercom

Your agent works inside Intercom, drafting replies to conversations for your agents to review and send.

Best for: Support teams using Intercom who want AI to speed up response time while keeping humans in control.

Helpdesk Copilot - Freshdesk (Coming Soon)

Similar to Zendesk and Intercom - AI drafts replies inside Freshdesk for your agents to review and send.

Knowledge Base

If you're using Helpjuice, your agent can be embedded directly on your knowledge base - automatically, without any manual embed code. Users reading your articles can ask questions without leaving the page.

Best for: Helpjuice customers who want their agent available alongside their existing help content.

API (Developer)

Build custom integrations with your agent using API keys. For teams that want to embed or connect the agent in ways not covered by the standard deployment options.

Best for: Technical teams building custom integrations or embedding the agent in proprietary platforms.

Best Practices

• Start with one channel - usually the Chat Widget - and expand to others once your agent is performing well.
• Deploy to channels where your users and team actually spend time. Adding every channel at once isn't better if half of them go unused.
• Each channel is independent - you can turn any of them on or off at any time from the Deploy tab without affecting the others.