Tidio’s Lyro answers customers and can call your own MCP servers (order status, account lookups), escalating to a person when it can’t help.
Independent review. Unpaid; no partnership with the tools on this page. Based on public documentation and research. Trademarks identify their owners’ products. Disclosure.
Editorial shortlist
Compare your options.
For answering help questions with controlled escalation.
Action-taking requires separate identity and permission tests. Choose one for answering from approved help content; switching may need setup changes.
Editorial judgment, not a personal-use endorsement or performance score. These are alternatives for the named role, not three required stack components. Vendors did not pay for, request or approve these positions.
Grounding and escalation come before autonomous actions. A lower-ranked option may fit your constraints better; compare the conditions stated on each card before choosing.
Setup and portability: Test answers, identity checks and handoff. Review conversation exports and action permissions separately.
Reviewed 2026-10-21. This page applies a shared comparison for “answering from approved help content” to the stated task and constraints. It is documentation-based editorial guidance, not three new hands-on tests. We weigh value for the job, distinct capabilities, replacement limits, technical effort and interoperability. Check current plan terms before adopting or switching.
Set escalation rules and review transcripts weekly
Human stepConfirmed
Confirmed = vendor-documented, not Ion-tested. Human and AI-platform steps are proposed roles.
Human approval
People handle escalations and refunds.
Watch out for
People handle escalations and refunds. Review transcripts weekly for wrong answers, and limit what the connected MCP servers can change.
Starter prompt
Help me set up Lyro in Tidio: review our knowledge base for gaps, list the questions it cannot answer yet, and draft escalation rules for refunds, account changes and upset customers. I will set the rules in Tidio and review transcripts weekly.
Written for this workflow. Paste it into your AI platform and adjust it to your situation.
No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
Gemini
Confirmed
No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
No platform-specific connection: the steps run in the tools themselves (browser, upload or built-in), with documented capabilities and human review steps. This is not an end-to-end test.
What the platform statuses mean
Confirmed: documented access meets the recorded requirements. Inferred: a reviewed note describes a plausible, untested pairing. To verify: a connection or step is unresolved. MCP and API pairings need route-specific evidence; a plugin, CLI or API alone does not prove compatible access, credentials or permissions. These are documentation assessments, not IonBin runtime tests.
What we checked
Lyro answers from your knowledge base.Tidio says Lyro uses guardrails and your knowledge base for its answers, and you can set handoff and escalation rules so a person takes over high-value or difficult chats.
Lyro and MCP. This route uses Lyro as the client of your server; it does not establish that Claude or another assistant can connect to Tidio as an MCP server. Tidio’s September 21, 2026 release confirms that you connect an external MCP server, inspect its tools and select those Lyro may use. The detailed help article was inaccessible, so account-specific plan and authentication requirements still need checking.
Plans. The release does not specify plan eligibility. Check before you build on it.
A lower-risk default (added 2026-10-18). Start with an agent that only collects context, such as who is asking, what they need and their order number, then hands off to a person. Let it resolve issues only after you’ve read its transcripts. For phone intake, see the separately documented warm-transfer workflow.
Set it up
Load your FAQ and help articles into Lyro’s knowledge base first.
Connect one MCP server with read-only tools, such as order status.
Test with representative questions and failure cases. Add an action only after defining its permissions, approval requirement and recovery procedure.
Keep refunds and account changes with people, and review transcripts weekly.
Verification limits and implementation checks
The page is documentation-reviewed; the complete workflow has not been run by IonBin.
Check Lyro plan eligibility, authentication and selected tools in your account before implementation.