A dead-end handoff
The customer was told to email.
Botpress human handoff for teams whose agent should know when to step back
Botpress human handoff automation that opens one ticket, passes the history and a summary and returns the user to the agent afterwards
Botpress starts a handoff with the Start HITL card, which needs a ticket title, the user ID and the conversation ID, and the legacy integration requires a Plus plan or higher, while new workspaces are pointed to Botpress Desk. BoldBellows records the conversation ID, the user and the reason for the handoff before a ticket is opened, passes the history and a short summary so the person never starts from nothing, then decides when the agent should hand over, whether that is a refund above a limit, a customer who asks for a person or two failed answers in a row, writes a ticket title and a short summary the person can read in ten seconds, assigns the ticket by topic and availability, and tells the user what happens next. When the person selects Resume Chatbot, the agent takes the conversation back without repeating itself.
View Pricing
From $875, paid once. Hand over with Botpress.
Four checks every Botpress human handoff run must pass
- One ticket per conversation never two
- History and summary passed nothing repeated
- Assigned by your rules topic and availability
- The agent resumes when the person is done
- Tested failure paths Duplicates, late events and permission loss are exercised before launch
- Nothing recurring your first payment of $875 is the last one we ask for, apart from extras you choose
01 · the cold-handoff problem
A bot that hands over badly makes the customer start again
The moment a bot hands over is when a customer is least patient. A handoff that says only please email us loses the conversation. One that opens a ticket with no history makes the person ask everything again, and one that fires too easily sends routine questions to staff who should be doing something else. Without a rule for when to step back, the agent either clings to conversations it cannot solve or gives up on ones it could have finished, and when the person is done there is no clear way back.
A ticket with no history
The person started from nothing.
Routine questions escalated
The rule was too loose.
- Notifications are forwarded without a check
- A handoff sends the customer away or loses the thread
- The person has to ask everything again
- Records are matched on the conversation ID and the handoff reason, not on names
- A handoff opens one ticket with history and a summary
- The agent resumes once the person is done
02 · how it works
How a stuck conversation becomes a ticket a person can pick up at once
Qualify first, match second, write last; that order is what stops duplicates.
- 01
Verify and decide
The incoming event is checked for authenticity, its identifiers are recorded, and the route decides whether the Botpress event qualifies.
- 02
Decide, summarize, open
The handoff rule is met, a summary is written, and one ticket is opened with the history.
- 03
Assign, tell, resume
The ticket is assigned, the user is told what happens, and the agent resumes afterwards.
Where Botpress draws the line for human handoff
A ticket returns the user to the agent
When a person finishes, Resume Chatbot removes them from the conversation and the user carries on with the agent, which is the step a handoff route has to expect.
Triggers wait for input
Triggers do not run while the bot is waiting on a Capture Information card, so handoff rules are placed where the conversation can actually reach them.
Recovery
Anything unclear is reconciled against the support desk through the conversation ID and the handoff reason, then repaired, closed or handed to an owner.
03 · what ships in the build
Component by component: the Botpress the support desk build
Three layers, in order: Capture for eligibility and identity, Coordinate for the ticket itself, Audit for drift and exceptions.
Searching for botpress human handoff automation cost? Also covered: botpress human handoff automation optimization and chatbot to human handoff botpress. Related searches include botpress start hitl, botpress human handoff duplicate prevention, botpress human handoff automation error handling, botpress support ticket handoff, botpress resume chatbot, botpress escalate to human, botpress hitl, botpress human handoff automation consultant, botpress human handoff implementation, botpress agent takeover, botpress live agent, botpress live chat handover, botpress human handoff error handling, botpress human handoff automation specialist, hire botpress human handoff automation expert, botpress human handoff automation developer, botpress botpress desk, botpress human handoff automation implementation, botpress human in the loop, botpress human handoff automation service, botpress human handoff historical migration, botpress human handoff consultant, botpress human handoff automation integration, botpress human handoff automation setup, botpress human handoff, botpress human handoff automation, botpress human handoff automation workflow and botpress human handoff automation agency.
Scope filter
Applies the in-scope list to every Botpress event, so the support desk sees only what you approved.
CaptureStable identity ledger
Keeps one entry for every Botpress item the human handoff route has handled, with the outcome beside it, so a repeat is recognized.
CaptureField-level filter
Drops, masks or transforms each Botpress value according to the rule written beside it.
CaptureHandoff rule engine
Decides when a conversation should go to a person.
CoordinateOpen-ticket matcher
Matches each event to its ticket by the conversation ID and the handoff reason and flags the ones it cannot place.
CoordinateRouting and priority matrix
Chooses who receives the ticket and how urgent it is.
CoordinateHandoff register
Holds every difference between Botpress and the support desk with its age and its owner.
AuditWait-time monitor
Flags tickets nobody has picked up.
AuditRepair workbench
Offers a safe next action for each stuck ticket instead of a blind retry.
Audit04 · who it's for
When agencies that build bots for clients also have to hand a Botpress conversation to a person at the right moment: open one ticket with the history and a summary, assign it and let the agent resume when the person is done
Customers want a person quickly when the bot cannot help, and staff want to arrive already knowing why.
Customer
"Don't make me repeat myself."
The person has the story.
Agent on duty
"What went before?"
I get the history and a summary.
Support lead
"Fewer needless escalations."
Rules decide when.
Owner
"Don't lose a conversation."
Every handoff opens a ticket.
Developer
"Keep it simple."
One card starts it.
Manager
"See the waiting time."
Unclaimed tickets are flagged.
Conversations, tickets and resumes decide the total
Work out the Botpress to the support desk price in minutes
How far should Botpress human handoff go? Each answer below moves the price from its opening $875.
View Pricing
- One setup fee
- Range shown first
- PDF handover included
05 · compare your options
Botpress into the support desk: a Botpress handoff with history and a summary, or the usual a bot that says please email us and zap
Each can say a person will reply. Only one passes the history, opens a single ticket and brings the agent back afterwards.
| What kicks it off | a bot that says please email us | A generic Botpress connector | BoldBellows, with a Botpress handoff route |
|---|---|---|---|
| What starts the work | Staff notice and act | The first matching notification | Events inside the agreed scope only |
| How identity is decided | A person recalls the customer | Nothing stored, so nothing to compare | One key: conversation ID and the handoff reason, with a summary |
| What reaches the support desk | A partial copy | One object, no relationships | One ticket with history and a summary, and a clean return to the agent |
| After an uncertain result | A manual clean-up later | It repeats the write | Compares what exists with what was intended |
The newer state is already there
When an older event shows up after a newer one, the route notes it and leaves the confirmed ticket alone.
A customer asks for a person twice in one minute
The second request finds the ticket already open, nothing new is created, and the customer is told where they are in the queue. The existing ticket, if any, is found by the conversation ID and the handoff reason and judged against the payload before the route decides what to do. Only a confirmed absence permits another ticket.
The first design choice is the conversation ID and the handoff reason; identity, replay and repair all follow from it.
Pricing
Build your Botpress to Human Handoff price
Pick a package, answer three short questions about how Botpress data should reach Human Handoff, and your price and turnaround move as you choose.
06 · process & getting started
Six steps from a dead-end handoff to a warm one
The route is built in six steps, and nothing moves on until the last one is signed.
- Step 01
Write the handoff rules
We list the situations that must reach a person, the ones that must not, and who owns each topic.
- Step 02
Approve access
Day one is practical: a restricted account in Botpress, narrow rights elsewhere, and a short list of keys that tie the records together.
- Step 03
Agree the ticket and the wording
The ticket title, the summary format and what the user is told are written out and approved first.
- Step 04
Prove the repairs
Each failure path, from a lost reply to a rejected value, is exercised in a test the support desk before the live switch.
- Step 05
Launch with notes
After the final test we enable the route and give you notes that name every owner and repair path.
- Step 06
Early-life support
Questions about how the route behaves in production are answered during the launch window, and the notes are updated.
07 · turnaround
Package timings at a glance
Days are counted once we can sign in to Botpress with the rights we asked for.
Capture
6 to 10 business days
Coordinate
10 to 16 business days
Audit
16 to 24 business days
08 · before we start
What to have ready
A Botpress connection you are happy for us to test with
A Botpress workspace and bot with a handoff tool available, the people or teams who take tickets and a list of handoff topics
Permission to subscribe to the Botpress events that start the route
Agreement on which Botpress events are in scope for the first release
A contact who can approve changes to the field map
Names of the people who will receive the handover notes
09 · security and ownership
Least access, allowlisted fields, and a clean handover
Reads are limited to the Botpress data the human handoff work needs, and every write lands in a place you approved in advance.
No changes to either product
Botpress and the support desk keep their own code and settings; the route sits between them and uses only what each platform documents.
Scoped, revocable access
Least-privilege access is the default, and it is documented.
A short list of fields
The mapping names every field that travels. Additions are agreed in writing, not picked up automatically.
No blind replays
The route never resends on hope. It checks the support desk for the ticket through the conversation ID and the handoff reason and decides from what it finds.
Minimal logging
The audit trail is made of IDs and decisions, not personal data.
Full handover
After handover you can maintain, change or retire the route on your own.
10 · verified reviews
What BoldBellows clients say
Verified reviews from business owners who use BoldBellows automations every day, from marketing and sales to support and operations.
AI Workflow Automation for Agencies
Running a digital agency with many clients was overwhelming. BoldBellows built one automation dashboard that tracks tasks, sends updates and creates client reports automatically.
Clients love the transparency and we love the time we get back. Productivity is up, and project delays have dropped to almost zero.
AI Customer Journey Automation
We wanted a smoother path from first contact to purchase. BoldBellows built an AI system that guides each customer there automatically.
It sends personalized messages, recommends products and follows up at just the right moment. Customer retention has improved dramatically.
AI Video & Voice Automation
We publish product videos every week, and BoldBellows introduced us to AI video automation. The system writes the script, voices it and produces the finished video in minutes.
The quality is remarkable: professional voiceovers, clean visuals and smooth editing. Production time went from three days to under 30 minutes, and we scaled our video marketing without adding cost.
AI Email & Smart Inbox Management
Our inbox used to be chaos. BoldBellows built an AI email system that sorts messages, drafts replies and flags anything urgent.
It learns how we write and gets better every week. We reply faster and no longer miss important messages. It feels like having a personal assistant working around the clock.
AI Booking & Scheduling Automation
Our coaching business needed a better way to schedule. BoldBellows automated all of it: bookings, reminders, cancellations and follow-ups.
No-shows fell by 60% and clients enjoy how smooth it is. It feels personal, not robotic. One of the best upgrades we’ve made.
AI Translation & Localisation
When we expanded abroad we needed fast, accurate translations. BoldBellows built an AI translation system that turns our content into several languages instantly.
The translations read naturally and suit each culture. We now serve customers in five new countries without hiring translators. BoldBellows helped us go global.
AI HR & Recruitment Automation
Our HR team was drowning in applications. BoldBellows automated screening, skills-based filtering and interview scheduling.
It saves us hours every week and means we only interview qualified people. Hiring is now faster, better organized and more professional.
AI Accounting & Invoice Automation
BoldBellows automated our whole invoicing process: creating invoices, sending reminders and tracking payments.
Late payments dropped sharply, and our accounting team finally has time for strategy instead of repetitive admin. Worth every penny.
AI Data Entry & Reporting Automation
We used to spend hours collecting data and building weekly reports by hand. BoldBellows automated all of it.
The reports are clean, visual and easy to read, and our managers rely on them for quick decisions. Human error is gone and our numbers are more accurate across the board.
AI Chatbot & Customer Support
BoldBellows built an AI support chatbot for our online boutique, and it has changed how we run the business. We used to have two full-time staff answering the same questions all day. Now the AI handles order tracking, product recommendations and even refund requests on its own.
What surprised me most is how natural it sounds. Customers compliment the ‘agent’ without realizing it’s AI. Our support workload dropped by 75% and customer satisfaction went up dramatically.
AI Content & Social Media Automation
Our marketing agency couldn’t keep up with content. BoldBellows set up an AI content engine that writes blog posts and captions and even designs our social media creatives.
It spots trends and suggests topics for us, so we stay ahead of competitors. We now produce three times the content with the same team, and engagement has soared. They didn’t just automate our workflow, they lifted our whole brand.
AI Lead Qualification & Sales Automation
Our sales team wasted hours chasing cold leads. BoldBellows built an AI lead-scoring system that reads behavior, email engagement and buying signals.
It filters out weak leads and sends personalized follow-ups automatically, so our team only talks to people who are ready to buy. Conversions rose 40% in the first month. It paid for itself straight away.
AI E-commerce Listings Automation
BoldBellows automated our product listings. The AI writes descriptions, organizes photos and publishes listings across several marketplaces.
It even answers customer questions instantly. Our store looks more professional and sales have noticeably increased.
AI Document & Contract Automation
Onboarding was slow because we wrote every contract by hand. BoldBellows automated the lot: contracts, welcome emails and client setup.
What took 48 hours now takes under 10 minutes, and clients regularly tell us how professional it feels.
AI Social Comment & DM Automation
We get thousands of comments and messages every week. BoldBellows built an AI system that replies instantly, filters spam and surfaces the important ones.
Engagement is up and our page looks active around the clock. It’s like having a full social media team that never stops.
AI CRM Automation
Our CRM was barely used because updating it by hand was tedious. BoldBellows automated data entry, tagging, segmentation and follow-ups.
Now the CRM is always up to date and our campaigns are far more accurate. It improved our whole sales pipeline.
AI Voice Assistant
BoldBellows built a custom AI voice assistant for our customer hotline. It answers questions, books appointments and handles simple requests.
Customers love how fast it is, and our call-centre workload dropped dramatically. One of the smartest upgrades we’ve made.
AI Automation Partner
BoldBellows is hands-down the best AI automation partner we’ve worked with. Their systems are fast, reliable and built around how our business actually works.
Every automation they’ve delivered, from customer service to content, runs flawlessly. We’ve saved time, cut costs and grown faster than we expected.
11 · questions
Handing over from Botpress: what support leaders ask
Short answers to what people ask before they book. Anything else can go in your quote request.
Could a no-code Botpress zap handle human handoff?
Need only a person in the conversation within minutes, with the full story in front of them? A zap handles that. It stops short of the work to open one ticket per conversation, pass the history or return the user to the agent afterwards. That missing layer is what you are paying for.
Which plan does handoff need?
The legacy HITL integration needs a Plus plan or higher; new workspaces use Botpress Desk.
What does the person see?
The whole conversation and a ten-second summary.
Can tickets be assigned by topic?
Yes, by topic, language or availability.
What happens when the person finishes?
Resume Chatbot returns the user to the agent.
Can the agent hand over automatically?
Yes, on rules you set, such as two failed answers or a refund above a limit.
Can we test it?
Yes, with the agent's built-in test chat before going live.
Which Botpress fields does human handoff read, and who approves them?
Yes, at no extra cost. A written map shows which Botpress fields feed human handoff and where each lands, and it is signed off first.
Will human handoff in Botpress respect our own conditions?
Yes. Tell us the rules and Botpress human handoff follows them; the entry package is $875.
Who keeps human handoff working when Botpress updates?
We write down what the route assumes. When an assumption stops being true, the route stops that step and says so, rather than improvising. It is also the answer to custom botpress human handoff automation.
Hand over with the story already told
Give your support team handoffs worth picking up
A fixed price for Botpress human handoff begins at $875.
If your process has extra branches, we will price them on their own line.