AI agents and chatbots
Botpress consultant: AI support agents that can act on a ticket.
SBD builds and supports Botpress agents that answer from your own content, take actions in your order and account systems, and hand over to a person with the history attached, for teams of 5 to 1,000 people. Workflow automation builds start at $1,500, with the fixed price set after a $500 Automation Audit that is credited to the build.
- Tool
- botpress.com
- Usually paired with
- Zendesk, Intercom, WhatsApp Business API, HubSpot
- Timeline
- Most builds live in 3 to 5 business days from scope
- Owned by
- You, with accounts, credentials and code in your name.
What we build on Botpress
- Build support agents in Botpress Studio with escalation rules
- Connect agents to your helpdesk, CRM and order systems
- Load and maintain the knowledge base agents answer from
- Test against real tickets before customers see the agent
What we sync
Workflows we are asked for
- Botpress support agent on top of Zendesk or Intercom
- Botpress WhatsApp agent with human handoff
- Botpress order status and refund workflows
- Botpress lead qualification into HubSpot
- Botpress knowledge base from your help centre
Documented in depth
Full write-ups of Botpress integrations.
Often paired with
Tools Botpress usually needs to talk to.
-

Botpress and Zendesk
The helpdesk most support teams of 10 to 1,000 run on.
-

Botpress and Intercom
Messaging and support with Fin, its AI agent, for product companies.
-

Botpress and WhatsApp Business API
The channel customers in most markets reply on, with templates, sessions and consent rules.
-

Botpress and HubSpot
The CRM and marketing platform most B2B teams of 10 to 1,000 run on.
-
Botpress and Shopify
The storefront for most of the e-commerce businesses we work with.
What we build
What a Botpress expert from SBD builds
The work usually starts with a support queue full of questions someone answers the same way every day: where is my order, can I change this, can I get a refund. An agent can answer many of those, but the value comes from letting it act in the systems behind the answer, and from knowing when it should stop and pass the ticket on.
We build in Botpress Studio with your support lead. We read a sample of real tickets first, decide which types the agent should resolve and which it should escalate, then connect the systems it needs. Each action that changes data has limits, such as a refund ceiling, and anything outside them goes to a person.
We have not published a case study built on Botpress, so we will not point you to one. The closest published work is our property automations, which connect Zendesk, Claude and n8n with the same attention to checks and handover.
- Support agents on top of Zendesk or Intercom, with your team keeping its helpdesk.
- Order status, changes and refund workflows connected to Shopify and your back office.
- WhatsApp and website agents that hand over to a person with the history attached.
- Lead qualification that writes to HubSpot and alerts the right salesperson.
Fit
When Botpress is the right choice, and when it is not
Botpress suits support teams whose tickets need actions as well as answers, and teams that want to avoid per-seat pricing. It works on top of an existing helpdesk or as its own helpdesk through Botpress Desk, so you do not have to migrate first.
An agent is only as good as the content and systems behind it. If your help articles are out of date or your order data is spread across spreadsheets, fix that first or the agent will give confident wrong answers. We test on a set of real past tickets before any customer sees it, and we measure how many it resolves correctly.
- Your questions are simple and come from documents alone; Chatbase may be quicker and cheaper.
- Volume is very low; a good help centre and a shared inbox may be all you need.
- Most of your support is by phone; compare a voice agent, since the Botpress pricing page lists the voice channel on Enterprise only.
- The agent would give regulated advice; keep a person answering and use AI to draft.
Plans and limits
Botpress plans, conversations and AI usage
Botpress prices by conversation, with no per-seat cost on Team and above. Any exchange with at least two messages from the end user counts, and AI-only and human-assisted conversations count the same. Conversation packs are added automatically near your quota and cannot be switched off, so we size the plan from your real ticket volume.
From Botpress's pricing page in November 2026, with paid plans billed annually:
- Free: $0; 100 conversations; 3 seats; 3 AI agents; no top-ups.
- Plus: $150 a month; 250 conversations a month, then $65 per 100; $25 of AI usage; 3 seats; unlimited agents; white-label webchat.
- Team: $750 a month; 1,500 conversations a month, then $50 per 100; $150 of AI usage; unlimited seats; teams, routing and role-based access.
- Enterprise: priced on request; adds dedicated support, an uptime SLA, a security review, custom storage and the voice channel.
Engagement and cost
How hiring a Botpress consultant from SBD works
Every engagement starts with an Automation Audit at $500, credited in full to your build. For Botpress we go through a sample of your tickets, estimate how many an agent could resolve, check the state of your help content and work out your monthly conversations, so the plan is sized before anything is built.
Workflow automation builds start at $1,500, and the fixed price is set after the audit and agreed before work begins. Your Botpress subscription is paid by you to Botpress. We do not resell licences.
Handover
What you own, and how the agent stays accurate
The Botpress workspace, the agents and every connected account stay in your name. You receive a runbook covering what each agent can do, its limits, how escalation works and how to update its knowledge.
Agents drift as products and policies change, so we set up a regular review of escalated and low-rated conversations. Your team can update content directly, and we can look after the rest under a support plan.
Read next
In every build
Standards we apply to every build.
Under the hood
- Upserts keyed on the record
Each write is matched on the source ID, so a retry or a re-fired event updates the existing record.
- Retries with backoff
Rate limits and timeouts are retried with increasing delays. If they still fail, they are parked for review.
- Idempotent, loop-safe writes
Two-way flows carry a marker so a change written by the sync does not re-trigger the sync.
- Reconciliation
A nightly job compares counts and totals on both sides and lists any record that differs.
- Audit log
Each run records the input, the mapping result, the action taken and what triggered it. You can search it by record.
For the team
- Slack or email notifications
Alerts go to a named person on your team, by Slack, email or WhatsApp.
- A runbook
One document per integration: what it does, what each alert means, and what to do in the first ten minutes.
- Training
A live session with the people who will use the review queue, recorded for whoever joins later.
- Handover
Admin access, billing and code sit in accounts in your name from the start, so the build keeps running if we stop working together.
- Sixty days of hypercare
The engineers who built it stay on call after go-live, fix what breaks and tune what the team asks for.
Keys and data
- Keys are kept in a vault
API keys and tokens are stored in the orchestration layer's encrypted credential store or the platform's secret manager. None are written into workflows, repos, spreadsheets or chat.
- One credential per connection
Each integration gets its own key, scoped to the objects and actions it needs. A lead sync cannot read invoices. Revoking one key stops one thing.
- Service accounts for connections
Connections use a dedicated service user in your account, so nothing breaks when a person leaves and nothing runs under someone's name.
- Two-factor on every account
Each platform account we set up has two-factor authentication on, and the recovery codes are handed to you.
- Rotation on handover and on request
Keys are rotated when the build is handed over, when anyone with access leaves, and at any time you ask.
The offer
Connect Botpress to the rest of your stack.
We agree a fixed scope in a discovery call, and most builds go live in three to five business days. The accounts are in your name, and the engineers who built it stay on call for sixty days after.
- ScopeOne call to agree the workflows, the fields and the owner, written up the same day.
- BuildValidation, upserts, retries, reconciliation and an audit log, on n8n, Make or code.
- Go-liveWe test in a sandbox first, then switch over. It takes longer only where a vendor has to approve something.
- HandoverRunbook, training session, alerts to a named owner, admin access and code in your accounts.
- AfterSixty days of hypercare, then a care plan or run it yourself.
Questions
What people ask about Botpress.
What counts as a conversation on Botpress?
Botpress's pricing page counts any exchange with at least two messages from the end user in the billing month, and a conversation spanning two months counts in both. We estimate your volume before recommending a plan.
Does it replace our helpdesk?
It can, through Botpress Desk, but it also runs on top of an existing helpdesk. We usually keep the helpdesk your team knows unless there is a clear reason to move.
Botpress
Start with the one Botpress workflow your team still runs by hand.
Bring it to a discovery call. You leave with a yes or no on fit, an outline of the build and what we would do first.
Book the call












