Botpress for Customer Support: Desk, Zendesk and Handoff

Botpress suits a support team that wants an AI agent on first-line questions and a clean handoff to people, and it offers two ways to run that. You can keep Zendesk or Intercom and put Botpress on top through OAuth, with no migration, or you can move tickets into Botpress Desk, the helpdesk Botpress launched in June 2026 and includes on every plan. For a staffed support floor the plan that matters is Team: routing and assignment, roles and unlimited seats start there, at $750 a month billed annually or $939 a month billed monthly, with 1,500 conversations a month included.

Our read after going through the support pages, docs and changelog: the deflection and handoff tooling is deep, and the per-workspace bill is easy to price from the published list but hard to cap, because conversation packs, added automatically at 95% of the quota, and AI grants recharge on their own. The friction sits elsewhere. Seats stop at 3 below Team, voice is Enterprise-only, and every test chat in the emulator counts toward your quota. Know those three lines before you build.

Two setups: on top of your helpdesk, or inside Desk

The first route leaves your agents where they are. Botpress says it connects to Zendesk or Intercom through OAuth, syncs tickets, agents, teams and custom fields automatically, and hands escalations into the agent workspace your team already uses^[1]. On the Zendesk side, the integration ships prebuilt cards for creating and reading tickets, getting users, assigning agents, adding tags, starting and stopping a human session and syncing knowledge, so your Zendesk Help Center articles can feed the bot. Link one Zendesk account to one bot only. Zendesk Messaging through Sunshine Conversations is a separate path and needs a Zendesk Support Professional account. Intercom asks for Administrator or Developer access, an access token, an admin ID, a webhook and a default assignee.

Desk is the second route, and it is a full ticketing system rather than a bot inbox. It brings capacity-based routing with business hours, priorities, custom statuses, tags, custom fields, merging, snoozing, threaded replies, macros, saved views and a help center. Desk SLA timers start at escalation, and only human replies count toward first and follow-up response targets; you can scope an SLA to tickets from one bot. Since August 2026 the composer can draft AI replies for the agent. The AI agent also stays in the conversation after a ticket reaches a person, instead of dropping out.

Beyond Zendesk and Intercom, the Hub carries handoff integrations for Freshchat, HubSpot Help Desk, HubSpot Inbox, LiveChat, Chatwoot, Brevo and Zoho SalesIQ, and HubSpot Inbox needs HubSpot Sales Hub or Service Hub Professional or higher on HubSpot's side. Each of these passes the whole earlier conversation to the agent as history. One rule decides your default. Workspaces created now hand off to Desk, while older workspaces may keep the legacy HITL integration, which needs Plus or higher.

How the agent answers tier-one questions

Deflection runs on your existing material. Botpress says the agent answers from your knowledge base, help center or policy documents across webchat, email and WhatsApp from one setup, cites the source it used, and needs no reformatting of that content first^[2]. You set a confidence threshold: below it, the conversation goes to a person with the full thread attached instead of a guessed reply. The agent detects the customer's language, answers in it without per-language setup, and logs the exchange in the original language and in English.

How you build it depends on who builds. In Botpress Viber, a support lead describes behavior in plain language: Instructions always apply, Playbooks hold reusable procedures such as a returns policy, and Escalation defines when a human takes over. Escalation is off by default. Turn it on, or nothing reaches Desk. In Botpress Studio, the Knowledge Agent returns an answer plus its citations as variables, so a workflow can show sources or branch on a missing answer. Our Botpress knowledge base guide covers sources, file limits and recrawl schedules.

Before going live, Botpress Viber Simulations replay sample tickets as single questions or multi-turn flows and check which tools the agent called. Botpress also says you can roll the agent out one channel at a time rather than switching all traffic at once. For scale, one customer story: 24hassistance, an insurance assistance company in Milan, says its Botpress agent now handles roughly 87% of conversations without a human.

Triage and routing, and why Team is the real starting line

Incoming tickets get classified without a rule set to maintain. Botpress says each one is tagged by topic, such as billing, technical, onboarding, account or compliance, and given a category and priority. Routing reads team descriptions and instructions written in plain language, can assign every ticket to the bot first so agents see only what needs them, and can match tickets to agents by language. Enrichment pulls subscription status, plan tier and account health from a connected CRM, matches the ticket against similar resolved ones and summarizes earlier history for repeat contacts. The plan gates then follow the support org chart^[3].

Desk roles (Admin, Support Agent, Manager, Developer, Viewer) arrived in September 2026 on Team and up. The seat cap is the deciding fact. With four or more people answering tickets inside Desk, Plus stops working on headcount alone. Plus still adds white-label webchat and a custom Help Center domain, which matter for a customer-facing brand.

What the human sees at handoff

Escalation triggers are configurable by topic, detected sentiment, customer tier, an explicit request for a person, or a confidence score. When a ticket lands, the agent receives the full conversation, any notes and an AI summary of what was asked, what was tried and a suggested next step. There is also an assisted mode. The AI stays beside the agent, suggesting replies and pulling data, and you choose which ticket types get full handoff and which get assistance. Handoff volume, reasons and agent response time show on the analytics dashboard.

Actions are where the agent stops being a FAQ. Botpress says its agents can issue refunds, process returns and update accounts after checking order date, refund policy and customer history against rules your team defines. Ambiguous or high-value cases can require an agent's approval first. In Studio, a workflow bypasses the model entirely for steps that move money, which is where most teams will want refunds. The three handoff routes, and the cards each one uses, are laid out in our Botpress human handoff guide.

Channels your queue will actually see

Webchat and WhatsApp are on every plan, Free included. WhatsApp needs Meta to verify your business before the bot can send anything, so plan that wait into the rollout. Replies sent from the WhatsApp Business phone app through Coexistence have appeared in the matching Desk ticket since October 2026. Email is a Desk channel, and Gmail can also be connected as one since August 2026; the connected Gmail address answers all incoming mail as the bot, and Botpress advises against personal Gmail accounts. The Desk page also lists Slack, Discord, Telegram, Instagram and Messenger. Voice is the exception. It is listed only on Enterprise.

What a support month costs on Plus and Team

Botpress bills the conversation, not the resolution or the seat. A conversation is any exchange with at least two messages from the end user in the billing month, and AI-only and human-assisted conversations count the same, so a handoff does not cost extra. Plus runs $150 a month billed annually or $189 a month billed monthly, with 250 conversations and $25 of AI usage included a month; Team includes $150 of AI usage a month.

Each extra pack of 100 conversations costs $65 per pack on Plus or $50 per pack on Team, billed each month the pack stays on, and is added automatically at 95% of the quota; this auto-recharge cannot be turned off. A pack stays on until you remove it in billing settings, and unused conversations in it expire at month end. AI usage has its own top-up: past 95% of the AI limit, Botpress buys a $10 credit grant at cost, again each time the limit is reached; unlike packs, unused grant balance carries over up to 12 months, and grants are not refundable.

By our arithmetic, a 1,000-conversation month on Plus billed monthly comes to $709 a month with eight packs, below the Team base of $939 a month billed monthly. The lines cross higher up: Team's base price beats Plus plus packs above 1,350 conversations a month billed monthly, and above 1,150 a month at the annual rate; by the FAQ's 95% rule, the real bill can be one pack higher. Most staffed teams will cross the seat line first. Emulator conversations count toward your quota like live ones, and the AI operations in those tests draw on your AI usage too; our Botpress pricing guide walks through packs, AI usage and refunds.

Two more limits matter to a support lead. The uptime SLA, a 99.8% monthly target, applies only to Enterprise. Plus and Team get live chat with Botpress support engineers, not a dedicated contact. Botpress says it does not train models on your conversation data, and keeps conversations for 90 days and logs for 30 by default. Custom retention and residency policies are Enterprise-only as well.

Which support teams should start on Botpress now

Start on Botpress if your queue is heavy on repeatable tier-one questions, your answers already live in a help center, and you want a human handoff that carries a summary rather than a cold transcript. Teams happy in Zendesk or Intercom can add the agent on top and judge it channel by channel. Teams without a helpdesk get Desk on the same price list. Budget for Team the moment more than three people work tickets in Desk. Look elsewhere if phone support is central and Enterprise is out of reach.