Overview
Lyro AI is Tidio's customer-service agent, trained on a company's support content to answer questions, perform supported actions and hand complex cases to people. It can reduce repetitive tickets, but knowledge quality, integration access, per-conversation pricing and escalation design determine results.Best for
Automated customer support, knowledge-base answers, ecommerce questions, lead qualification, order workflows and human-agent handoffPricing and availability
Tidio accounts can test Lyro with a limited number of free conversations. Continued use is priced by conversation or bundled into paid plans, while Premium and custom deployments add integrations, actions, limits and service commitments.Platforms and integrations
Available through: web, api.Lyro works in Tidio and can connect to existing support stacks including Zendesk, Intercom and Salesforce through eligible plans. Smart Actions, MCP-related workflows and custom integrations extend supported tasks.
Privacy and security
Support conversations and connected actions can expose customer and order data. Organizations should restrict knowledge sources, validate identity before sensitive actions and configure clear escalation, access and retention controls.Key strengths
- Answers are grounded in the support content supplied by the business
- Human handoff rules keep complex or sensitive cases in scope
- Connections to existing support platforms can reduce migration effort
Key limitations
- Incomplete or outdated knowledge produces weak answers
- Per-conversation pricing can grow with support volume
- Automated actions require authentication, monitoring and safe escalation
Editorial note
CoinBotLab independently maintains this record using current provider documentation and independent sources. Features, pricing, availability and policies can change.- Best for
- Automated customer support, knowledge-base answers, ecommerce questions, lead qualification, order workflows and human-agent handoff
- Supported languages
- Lyro supports customer conversations in multiple languages, while knowledge quality, integrations and available channels can vary by language and plan