What channels and integrations does Botpress support for customer support?

Botpress supports two categories of connections for customer support: deployment channels where your AI agent talks to end users, and system integrations that let the agent read and act inside your existing support stack. According to Botpress's own platform page, the named channels are Webchat, WhatsApp, and Slack, and the named integrations are Intercom, Zendesk, Hubspot, and Salesforce. If your stack is built on those tools, Botpress is designed to sit on top of them rather than replace them.

Deployment channels

These are the surfaces where an end user actually interacts with the agent:

The platform page lists these under "All channels and integrations," implying the list shown is a subset rather than the full catalog. If you need a channel not named here, treat it as unconfirmed and check the docs before assuming coverage.

System integrations

Botpress names four integrations that connect the agent to existing support and CRM systems:

• Intercom — support and messaging platform
• Zendesk — ticketing and helpdesk
• Hubspot — CRM
• Salesforce — CRM

The point of these integrations is not just answering questions. The platform's stated positioning is that agents "take real action on refunds, account updates, and multi-step workflows" — meaning the integration layer is what lets the agent update a record, change a plan, or trigger a next step inside the connected system rather than just replying with text.

Botpress Desk

Botpress also offers Botpress Desk, described as "the AI helpdesk built for complex support." This is a separate product surface from the integrations above — it's positioned as a helpdesk where the AI agent operates, rather than a connector into a third-party helpdesk. If your goal is to keep your existing Zendesk or Intercom setup, the integration path is the relevant one; if you want a helpdesk built around the agent, Desk is the relevant one.

Support use cases the integrations enable

The platform maps its integrations and channels to these customer support scenarios:

• Ticket deflection — resolving tickets before they reach a human
• Ticket management — handling tickets end-to-end
• Escalation & handoff — passing a ticket to a human with conversation history, account details, and troubleshooting steps already attempted
• Ticket enrichment — adding context to tickets
• AI actions — performing concrete operations like refunds or account updates

The escalation path is worth noting for stack planning: the handoff carries context forward, so the human agent picks up mid-conversation rather than starting over.

How to decide if this fits your stack

Use these conditions:

• If you run Zendesk, Intercom, Hubspot, or Salesforce — Botpress names direct integrations for all four, so it's built to layer onto your existing stack.
• If you need Webchat, WhatsApp, or Slack as a customer-facing surface — all three are named deployment channels.
• If your channels or helpdesk are something else — the page shows a partial list, so verify against the docs rather than assuming support.
• If you want the agent to take actions, not just answer — the integrations are the mechanism; confirm the specific action you need (refund, plan change, record update) is supported for your connected system.

One caveat on scope: the platform page presents these as headline capabilities, not a full compatibility matrix. Before committing, confirm the exact channel or integration version you depend on, since "supports Zendesk" can mean different depths of access depending on the API surface involved.