Tidio: plan website support around three different workloads
Tidio is a candidate when website visitors need answers and the business wants to coordinate human support with automation. Its fit depends on the questions visitors ask, the quality of your knowledge and whether someone can handle the exceptions. A chat widget alone does not create live coverage.
Our editorial starting point is one support journey: a visitor asks a common question, receives a checked answer and reaches an accountable person if the question remains unresolved. This is more useful than evaluating every automation feature before the team can explain its service process.
Separate human support, Flows and Lyro
Tidio's upgrade documentation treats live customer support, Flows and Lyro as separate components. Flows allowance is based on visitors served, while support uses conversation allowances. Check which packages your quote includes rather than assuming one upgrade covers all activity. Tidio package guidance
| Workload | Planning question | Useful measure |
|---|---|---|
| Human support | Who handles the inquiry and when? | Open work, response time and completed next action |
| Flows | What defined branch should run? | Visitors entering and completing the intended path |
| Lyro | Which checked knowledge can answer the question? | Answer quality, handoff and billable conversation threads |
One customer journey may touch more than one component. Do not add these volumes together and call the result a single pool of conversations. Write the billing unit beside each allowance in the cost planner.
Lyro's free allowance is not a monthly service budget
Tidio documents an initial, non-renewable allowance of 50 Lyro conversations. Paid Lyro quotas renew monthly. The help article also describes thread accounting and an inactivity boundary, so a returning visitor can consume more than one thread. Lyro limit explanation
The practical implication is to observe actual thread usage during an evaluation instead of estimating it from unique customers alone. A business with many returning questions may have different consumption from one where every visitor asks a single question and leaves.
For an illustrative month, consider 300 support inquiries, 900 visitors served by defined Flows and 180 Lyro-counted threads. Those are three separate inputs. They do not imply a $ price or entitlement. Ask for the package combination and peak-month behavior that covers them, including what happens when an allowance is exhausted.
Prepare knowledge that can support a decision
Start with the ten recurring questions your team can answer confidently. For an online shop, delivery areas, order tracking, returns and product compatibility may be useful topics. Each answer needs an owner, an authoritative source and an exception route.
| Question type | Prepared response | Route to a person |
|---|---|---|
| Published policy | Explain the current policy and link the source | Customer asks for an exception |
| Order-specific issue | Explain how to use the approved order lookup | Identity or order cannot be confirmed |
| Ambiguous product question | Ask a short clarification | The available information is insufficient |
| Complaint | Acknowledge the request and preserve context | Owner must investigate or approve a remedy |
An automated answer should not invent an order status or grant an exception beyond the business's policy. Keep account-specific actions separate from general knowledge. Follow knowledge before AI to record what the system may answer and what it must escalate.
Design coverage before switching on the widget
Choose staffed hours, the owning role and the backup. Outside those hours, give a clear asynchronous expectation and capture a usable return channel. During coverage, a visitor asking for a human should reach a visible queue rather than another answer loop.
Tidio documents configurable Lyro handoff behavior. Check how it behaves when the visitor requests a person or the system cannot answer. Lyro overview
Before relying on the installation, walk through a known answer, an ambiguous question, a human request, an agent going offline and a visitor returning later. Record whether the previous exchange and open question remain available. Our website-chat-to-case workflow explains the handoff record to preserve.
Review success beyond automated replies
Use a weekly sample of unresolved and escalated conversations. Ask whether the answer was correct, whether the customer understood the next step and whether somebody accepted the remaining work. Track repeated contacts about the same issue separately from newly resolved requests.
If a hypothetical 50-question review contains 30 correct self-service answers, 12 useful human handoffs and eight unresolved questions, the eight deserve investigation. Calling all 50 handled because a message was sent would obscure the service gap. These figures illustrate a review method rather than Tidio performance.
Alternatives and the buying boundary
Crisp deserves consideration for website conversations and a shared support workspace. Help Scout or Freshdesk may fit better when the main challenge is an ongoing support queue. Manychat belongs in a separate comparison when inquiries primarily begin with social comments or messages.
Read Tidio vs Crisp for the billing and operational tradeoffs. Check the current Tidio pricing page against your actual package quote. Keep your existing helpdesk when the missing piece is knowledge quality or ownership that can be fixed without migration.
Research basis: official documentation checked October 7, 2026, with our editorial analysis. Worked examples are illustrative, not customer results or hands-on benchmarks. Confirm the applicable account, plan and channel before purchase.