What it supports
Keep customer messages flowing through supported connected channels.
Integration
Respond.io Handover
Use respond.io support for always-on messaging and handover workflows so customer messages can still be handled even when the seller is offline.
Connection path
The integration brings customer events into ZoliBot, keeps channel credentials private, and lets the seller decide when automation should reply.
Webhook
A focused part of the connection workflow.
Access token
A focused part of the connection workflow.
Inbox sync
A focused part of the connection workflow.
Human handover
A focused part of the connection workflow.
Offline does not have to mean unavailable
When the seller is away, respond.io can help keep the messaging channel connected while ZoliBot handles eligible automated replies.
What it supports
Allow ZoliBot to assist when automation is enabled and plan access is active.
What it supports
Let human agents continue conversations when the bot is paused or unavailable.
Clear handover boundaries
If the bot is paused, credits are exhausted, or the plan is expired, the customer message can still arrive while the seller continues manually.
1
Add respond.io token, channel, base URL, and webhook secret.
2
Confirm incoming messages reach the ZoliBot inbox.
3
Use human handover when the seller wants manual control.
What sellers should expect
This page is written for live businesses using ZoliBot with real customers, real stock, payment decisions, and support conversations that sometimes need a human handover.
Accurate context
The bot should use products, settings, payment choices, and order state from the seller dashboard before suggesting an answer.
Human escalation
Refunds, paid cancellations, fulfillment disputes, and sensitive issues should move to store review instead of unsafe automatic action.
Customer language
Replies should follow the language or informal style the customer is using while keeping prices, links, product names, and order IDs exact.
