Customer Service & Helpdesk
Tidio
Provenance unknown Report an error0–5 in half steps. 5 means the rubric's top anchor is met on the evidence.
by Tidio · www.tidio.com
Report an error on this page Is this your product? →
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Tidio's strongest criterion is omnichannel, scoring 4 with no spread: chats and emails are stated to become tickets in one system, with a live visitor list and typing preview. Integrations score 3-4 on order management inside the conversation and a Shopify app rated 4.8; ticketing core scores 3-4 for priorities, tags, spam management and smart views, with no public information on routing rules, SLA timers or escalation chains. Knowledge and self-service scores 2-3, since deflection rests on Lyro's claimed 67% instant resolution rather than a customer help centre. Customer data protection scores 2-3: GDPR, CCPA and SOC 2 Type 2 are claimed, but we found no public information on retention periods, an executable deletion path or a signable DPA. Sovereignty is weakest at 1-2 — no sovereignty attributes are on record, and no public information exists on hosting location, contracting entity or subprocessors. Pricing transparency scores 2-3: a free plan forever and paid plans from $29/mo are public, with no tier names or per-agent basis stated. The persona-weighted totals range from 2.5 to 3.3, and no flagged splits were flagged.
Speaks for it
- Chats and emails are stated to become tickets in one system, earning omnichannel the top score of 4 with no spread.
- Order management, cart preview and discounts happen inside the conversation, alongside a Shopify app rated 4.8.
- Lyro is claimed to resolve 67% of conversations instantly, plus AI-driven email resolutions.
- A free plan forever and paid plans from $29/mo are published, with cancel anytime in two clicks.
- GDPR, CCPA, SOC 2 Type 2, an AI Pact and a Trust Center are claimed, with guardrails and audit logs named.
Held against it
- Sovereignty scores 1-2, with no public information on hosting location, contracting entity or subprocessors.
- We found no public information on routing rules, SLA timers or escalation chains in the ticketing.
- Knowledge and self-service scores 2-3, with deflection resting on the AI bot rather than a customer help centre.
- Customer data protection scores 2-3: we found no public information on retention periods, an executable deletion path or a signable DPA.
- Pricing transparency scores 2-3, with no tier names, per-agent basis or AI-usage pricing stated beside the $29/mo headline.
Best for
- You run an ecommerce store and want carts, order history and discounts handled inside the conversation.
- You want live chat and email arriving as tickets in one system.
- You want AI deflection of common questions and emails before adding agents.
- You want to start on a free plan forever before committing to paid plans.
Avoid if
- Your operation depends on SLA timers, routing rules and escalation chains, which the captured pages do not evidence.
- You need to verify where the ticket archive is hosted, the contracting entity, or the subprocessors before signing.
- You need a computable annual invoice with tier names and a per-agent basis.
- You need a customer-facing help centre with article workflow and versioning.
The scores
Ticketing, queues & SLA
Show reasoningHide reasoning
How this is scored
The engine: how work is routed, prioritised, escalated and measured — and whether an agent can find the ticket they need among ten thousand.
0 — A shared mailbox with labels; no ownership, no status model, no history beyond the thread.
3 — Tickets with assignment and open/closed status, but routing is manual, there are no SLA timers and search covers subject lines only.
5 — Queues with rules-based routing, priorities, a working status model, SLA timers with breach warnings, and full-text search across ticket bodies.
8 — Business-hours-aware SLA policies per queue or customer, escalation chains, macros and triggers, merge and split, and reporting on first-response and resolution time by agent and queue.
10 — The workload is managed rather than merely tracked: capacity-aware assignment, SLA per contract with reporting an account manager could show a customer, audit of every status change, and search that finds the ticket from a half-remembered phrase.
The Support Lead
Tickets with priorities, tags and smart views are confirmed, which is a real step above a labelled mailbox — but the word "smart" is on views, not on assignment. We found no public information on routing rules, SLA timers with breach warnings, escalation chains, or first-response and resolution reporting, which are the parts my twelve agents live and die by. 1
The Agent Advocate
Tickets from chats and emails with priorities, tags, spam management and smart views is the whole engine shown; we found no public information on SLA timers, routing rules, macros and triggers, merge and split, or how deep search goes. On the hundredth reply this looks like triage by hand rather than workload management. 1
The Data Protection Officer
Tickets are evidenced as a real model — chats and emails become tickets with priorities, tags, spam management and smart views. Beyond that we found no public information on SLA timers, routing rules, escalation chains, ticket search, or reporting on response and resolution times. 1
The Shop Operator
Tickets from chats and emails with priorities, tags, spam management and smart views is more than a shared mailbox, but I run peak season on SLA timers, routing rules and escalation chains, and none of that appears on the captured page. We found no public information on a status model, merge and split, or first-response and resolution reporting. 1
The Integrator
The captured page shows tickets with priorities, tags, spam management and smart views — that is the whole engine on display. We found no public information on routing rules, SLA timers, escalation chains or full-text search across ticket bodies, which sits just above manual assignment and well short of SLA-managed queues. 1
The Skeptic
The vendor states "ticketing workflows" with priorities, tags, spam management and smart views, but we found no public information on routing rules, SLA timers, escalation chains, or full-text search across ticket bodies. Smart views read as saved filters rather than SLA machinery, so what is evidenced sits just above basic assignment and status. 1
Channels in one queue
Show reasoningHide reasoning
How this is scored
Email, chat, phone, portal, messengers and social — judged on what actually lands in the same queue with the same history, not on how many channel logos the marketing page carries.
0 — Email only.
3 — Email plus one more channel, but the second lives in its own inbox: no shared history, and a customer who switches channel starts again.
5 — Email, a web form or portal and live chat all landing as tickets in one queue, with the customer's history visible whichever channel they used.
8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp, Signal or similar) with its consent handling stated, and a customer portal where a requester can see their own tickets.
10 — Channel is an implementation detail: every channel including voice and messengers writes to one conversation with one history, agents answer from one screen, and the customer can move between channels mid-issue without repeating themselves.
The Support Lead
Chats and emails are confirmed to land as tickets in one system, and the live-chat side is well evidenced (visitor list, typing preview, offline Flows), which is better than a second channel in its own inbox. We found no public information on telephony, messengers, a customer portal where requesters see their own tickets, or whether one history follows the customer across channels. 1
The Agent Advocate
Email and chat are stated to land as tickets in one system, which clears the separate-inbox problem. We found no public information on a customer portal, messengers with consent handling, telephony, or whether the requester's history follows them when they switch channels. 1
The Data Protection Officer
Live chat and email are shown converging into the same ticketing system, which is more than a chat inbox bolted beside a mailbox. We found no public information on telephony, messengers with consent handling, or a customer portal where a requester can see their own tickets. 1
The Shop Operator
Chat and email land as tickets in one system, which is the right foundation, and the live visitor list with typing preview are genuine chat-queue features. I judge this by whether WhatsApp and the shop land in that same queue, and we found no public information on messenger consent handling, telephony, or a customer portal where a requester sees their own tickets. 1
The Integrator
Chats and emails are stated to turn into tickets, with live visitor tracking and typing preview around the live chat, so two channels land in one ticket system. We found no public information on telephony, messengers with consent handling, or a customer portal where a requester sees their own tickets. 1
The Skeptic
Chats and emails are stated to become tickets together, which is more than two separate inboxes, but no other channel is named. We found no public information on telephony, messengers such as WhatsApp, a customer portal, or whether a single history follows the customer across channels. 1
Knowledge base & deflection
Show reasoningHide reasoning
How this is scored
Whether the product reduces the number of tickets as well as organising them: public help centre, article workflow, suggestions to agents and to customers.
0 — No knowledge base; answers live in agents' heads and old tickets.
3 — A basic article list, public or internal, with no editorial workflow, no versioning and no link between articles and tickets.
5 — A searchable public help centre with categories, draft and publish states, and agents able to insert an article into a reply.
8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates that flag stale content, and reporting on which articles deflect.
10 — Knowledge is a managed asset: gaps identified from unanswered tickets, article performance measured against ticket volume by topic, versioned content with approval, and deflection reported as a number the team can act on.
The Support Lead
What is evidenced is AI deflection — "Lyro resolves 67% of conversations instantly" is a number I would want checked against my own queue before banking on it — rather than a managed knowledge asset. We found no public information on an article-based help centre for customers, editorial workflow, versioning, review dates, or reporting on which articles deflect. 1
The Agent Advocate
Lyro's claimed instant resolution of 67% of conversations is deflection of a kind, and AI-driven email resolutions show self-service beyond the queue. But we found no public information on a public help centre for my customers, article workflow or versioning, or reporting on which content deflects — the Help Center named on the site is the vendor's own support page, not a product capability. 1
The Data Protection Officer
Deflection is claimed loudly — Lyro resolving 67 percent of conversations instantly and answering common emails on its own — but the deflection is AI, not articles. We found no public information on a publishable help centre, article workflow, versioning, or reporting on which content deflects. 1
The Shop Operator
Deflection is the strength: Lyro resolving 67% of conversations instantly plus AI-driven email resolutions is precisely the December ticket-count drop I buy for. But the knowledge base behind it is dark — we found no public information on article workflow, categories, versioning or suggestions to agents — and the help centre named on the page is the vendor's own support channel, not a feature for my customers. 1
The Integrator
Deflection is evidenced the AI way: Lyro resolves 67% of conversations instantly and scans incoming emails to solve common problems, and the AI Reply Assistant drafts agent answers. We found no public information on a public help centre as a product feature, article workflow, versioning, stale-content flags or deflection reporting, so the knowledge side rests on AI alone. 1
The Skeptic
The deflection story is the Lyro bot, with a claimed 67% instant resolution rate and AI-driven email resolutions, not a knowledge base. We found no public information on a public help centre, article workflow, versioning, or article suggestions to agents or customers. 1
Customer data protection
Show reasoningHide reasoning
How this is scored
A ticket archive is personal data written by the data subject. Retention, deletion, access control, subject rights, and what the vendor does with attachments — judged on what executes rather than what is promised.
0 — No retention policy stated, no deletion path, agents all see everything, and no DPA is published.
3 — A DPA on request and coarse roles; deletion is described as something the customer arranges, and there is no stated retention period.
5 — A signable DPA published, configurable agent roles and queue-level visibility, a stated retention period, and deletion of a requester's data that can actually be executed.
8 — Automatic retention rules per queue or data category, attachment handling stated, an audit log of who opened which ticket, documented support for access and erasure requests, and pseudonymisation or redaction of ticket content.
10 — Built for a data-protection audit: retention executed and evidenced per category, field-level redaction, full audit trail, subprocessor list published, and the vendor's own support access to customer instances documented and consent-gated.
The Support Lead
GDPR, CCPA and SOC 2 Type 2 claims are published alongside a Trust Center, and audit logs appear in the AI guardrails context. We found no public information on a stated retention period, an executable deletion path, agent role or queue-level visibility, or a signable DPA — certifications stated, execution unevidenced. 1
The Agent Advocate
SOC 2 Type 2, GDPR and CCPA badges plus guardrails and audit logs show a compliance posture, and the audit-log feature is one executing control we can actually see. We found no public information on a published DPA, a stated retention period, configurable agent roles, or an executable path to delete a requester's data. 1
The Data Protection Officer
GDPR, CCPA, SOC 2 Type 2 and a Trust Center are named, and guardrails and audit logs appear as a feature line in the AI context — that is where the evidence stops. We found no public information on a stated retention period, an executable deletion path, a published DPA, agent roles or queue-level visibility, redaction of ticket content, or whether the vendor's own support can open a ticket. 1
The Shop Operator
GDPR, CCPA, SOC 2 Type 2, an AI Pact and a Trust Center are programme badges, and guardrails with audit logs are stated for the AI, but we found no public information on a published DPA, a stated retention period, an executable deletion path for a requester's data, or agent roles and queue visibility. For a ticket archive full of names and order addresses, that is thin. 1
The Integrator
GDPR, CCPA and SOC 2 Type 2 compliance are claimed alongside a Trust Center, and "Guardrails and audit logs" is listed, which at least evidences an audit capability. We found no public information on retention periods, a deletion path a customer can execute, agent roles, queue-level visibility or attachment handling. 1
The Skeptic
GDPR, CCPA and SOC 2 Type 2 badges plus a "guardrails and audit logs" line are a compliance posture rather than an executing mechanism. We found no public information on stated retention periods, a signable DPA, agent roles or queue-level visibility, a deletion path that can be executed, or attachment handling. 1
Integrations & API
Show reasoningHide reasoning
How this is scored
The systems a helpdesk has to reach — CRM, shop, order management, identity — and whether the API is documented for building or gated behind a partner conversation.
0 — No API and no named integrations; context is copied in by hand.
3 — A handful of native integrations and a read-mostly API, with no webhooks and no documented rate limits.
5 — Named integrations for common CRM and shop systems, a documented REST API with keys, webhooks for the core ticket events, and SSO.
8 — Maintained bidirectional integrations, customer context from other systems shown inside the ticket, SCIM provisioning, documented rate limits and a sandbox.
10 — A component rather than a destination: versioned API with a deprecation policy, event streaming both directions, an app framework for in-ticket extensions, and integrations the vendor maintains rather than lists.
The Support Lead
A Shopify integration is evidenced by its 4.8 app-store rating, Smart Actions claim real-time writes to external systems for order updates and lead qualification, and a mobile SDK and a Developers section exist. We found no public information on a documented REST API, webhooks, SSO, SCIM or rate limits, and no CRM or identity system is named. 1
The Agent Advocate
The Shopify integration is evidenced by a 4.8 App Store rating, cart and order context lives inside the conversation, and Smart Actions write order updates back to external systems — real shop-stack reach in both directions. We found no public information on a documented REST API with keys, webhooks, SSO or SCIM, or on CRM integrations beyond the shop world, though a Developers channel and a mobile SDK are offered. 1
The Data Protection Officer
A Shopify App Store presence and smart actions writing order updates to external systems evidence live connections beyond chat, with order management shown inside the conversation. We found no public information on a documented REST API, webhooks, named CRM integrations, SCIM provisioning, rate limits or a sandbox — only a Developers link and a mobile SDK. 1
The Shop Operator
Order management inside the conversation — preview carts, check order history, manage orders and offer discounts without leaving the chat — is exactly the shop context I need without a second login, and Smart Actions reaching external systems for order updates points the right way. But the only named integration is the Shopify app at 4.8, and we found no public information on a documented REST API, webhooks, SCIM provisioning or rate limits beyond a Mobile SDK and a Developers section. 1
The Integrator
A Shopify integration is evidenced by a 4.8 App Store rating, and Lyro "integrates with your external systems" for order updates and lead qualification, though no other systems are named. A Developers section and a Mobile SDK hint at a documented developer side, but we found no public information on a REST API, webhooks, rate limits, SCIM provisioning or a sandbox — the exact things I need to wire in a CRM, a shop and an identity provider. 1
The Skeptic
Ecommerce context is on the page: order management inside the conversation, Smart Actions writing to external systems for order updates and lead qualification, a 4.8 Shopify App Store rating, and a developers area with a mobile SDK. We found no public information on a documented REST API, webhooks, SSO, or rate limits. 1
European sovereignty
panel opinion
Show reasoningHide reasoning
How this is scored
Where the ticket archive lives, who the contracting entity is, which subprocessors touch it, and whether vendor support can read customer data. Independently sourced by the sovereignty pipeline; scored here as this buyer weighs it.
0 — Non-EU vendor and contracting entity, hosting unstated or non-EU, subprocessors unnamed.
3 — EU hosting offered as an option while the contracting entity is non-EU, or the subprocessor list is absent.
5 — EU hosting as standard and an EU contracting entity, but parts of the chain — support tooling, analytics, AI features — are non-EU without an explained safeguard.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, full subprocessor list published, and any non-EU processing named with its legal basis.
10 — Sovereign end to end and evidenced: vendor, entity, hosting and every subprocessor in the EU, certification published, and a self-hosted or private-cloud option for buyers who need the archive on their own infrastructure.
The Support Lead
No sovereignty attributes are on record: we found no public information on where the ticket archive is hosted, the contracting entity, or the subprocessors who touch it. A GDPR badge is not a data-residency answer, and for a buyer weighing EU exposure this is unverifiable end to end. 1
The Agent Advocate
We found no public information on where the ticket archive is hosted, which entity contracts, or which subprocessors touch the data. GDPR and SOC 2 badges speak to compliance handling, not residency or vendor support access, so as this buyer weighs it there is nothing to hold onto. 1
The Data Protection Officer
No sovereignty attributes are on record: we found no public information on hosting location, contracting entity, data-centre provider or subprocessors, so nothing evidences where the ticket archive lives or who can touch it. A GDPR badge is a framework claim, not a location or a legal basis. 1
The Shop Operator
The sovereignty record came back empty: we found no public information on hosting location, contracting entity or subprocessors, and GDPR plus the AI Pact are commitments rather than an evidenced chain. For a European shop's archive of customer names and order history, I cannot confirm from these pages where the data lives or who touches it. 1
The Integrator
No sovereignty attributes are on record: we found no public information on hosting location, contracting entity, named data-centre provider, subprocessors or whether vendor support can read customer data, beyond a GDPR badge and a Trust Center link. For a buyer weighing where the ticket archive lives, that silence sits near the bottom of the scale. 1
The Skeptic
No sovereignty attributes are on record, and the captured page says nothing about hosting location, the contracting entity, or the subprocessor chain. A GDPR badge and a Trust Center link are not a data-centre address or a subprocessor list, so only the published compliance posture keeps this above the floor. 1
Pricing transparency
Show reasoningHide reasoning
How this is scored
Whether a support lead can compute the real annual invoice for their agent count — including the channels and features they actually need — from public pages alone.
0 — No public prices at all; every tier is a sales conversation.
3 — A per-agent headline exists, but the tier where the needed channel or SLA feature begins is unstated, or light-agent and contact limits are not mentioned.
5 — Per-agent prices public for the main tiers with billing period stated, but at least one commonly needed capability (telephony, messengers, SLA policies) sits in an unpriced bundle.
8 — Every tier and add-on priced publicly with per-agent maths, billing period, minimum term and VAT treatment stated; only genuinely custom enterprise work lacks a number.
10 — Complete price computability: a calculator or table producing the annual invoice for a given agent count and channel selection, including usage-metered channels and overage.
The Support Lead
A free plan and "Paid plans from $29/mo" are public, with cancel anytime in two clicks — a genuine headline. But no tier structure, per-agent basis, conversation or contact limits, VAT treatment or add-on prices are stated, so I cannot compute the annual invoice for twelve agents from the public page. 1
The Agent Advocate
A free-forever plan, a from $29/mo headline and two-click cancellation are public and friendly. But we found no per-agent tier table with billing period, no statement of which plan carries which channels or SLA features, and no price for the AI conversation usage — I cannot compute an annual invoice for my agent count from these pages. 1
The Data Protection Officer
A headline exists — paid plans from $29/mo with no surprise upgrades, a free plan forever, and cancel anytime in two clicks. We found no public information on tier boundaries, what the headline figure covers per agent, contact or AI-usage limits, annual billing, minimum term or VAT treatment, so the real annual invoice cannot be computed from the page. 1
The Shop Operator
A headline exists — free plan forever, paid plans from $29/mo, cancel anytime in two clicks — but computability stops there: we found no public information on tier boundaries, per-agent maths, billing periods, VAT treatment or what Lyro's conversation volumes add to the invoice. A support lead pricing twenty agents cannot build an annual number from this. 1
The Integrator
Public numbers exist — a "Free plan forever" and "Paid plans from $29/mo, no surprise upgrades" with cancel-anytime — but no tier breakdown appears alongside them. We found no public information on which plan carries the AI resolution and channels, conversation or contact limits, annual billing treatment or VAT, so the real annual invoice for a given agent count is not computable. 1
The Skeptic
Public pricing is a single headline — paid plans from $29/mo, a free plan forever, cancel anytime — with no tier names and no per-agent basis stated. We found no public information on what the Lyro AI resolution is metered at or at which tier channels and SLA features begin, so the annual invoice cannot be computed from the page. 1
European sovereignty — proven facts
0 of 4 dimensions provenBuilt only from facts shown on the vendor's own pages. A dimension we could not prove is left open, not scored as zero.
| Legal entity | Not determined ⚠ unverified | — | uncited Report an error |
|---|---|---|---|
| Ownership | Not determined | — | uncited Report an error |
| Data residency | Not determined ⚠ unverified | — | uncited Report an error |
| Subprocessors | Not determined | — | uncited Report an error |
Where this could be wrong
- Evidence ages. The oldest capture behind this page is from 22 Sep 2026. Vendors change pricing and policies without notice; every fact reflects its source as of the capture date shown in the registry.
- Weak sourcing — Legal entity, Data residency. Not confirmed on the vendor’s own pages as captured.
- AI can misread a source. Extraction and judgement are automated; a citation guarantees traceability, not infallibility. If something here is wrong, say so — no account needed, every report is decided within 5 business days, and accepted corrections are published.
What we left out
A claim that does not survive our checks costs us the claim, not the page. This is what was taken off this one.
- 21 product facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 20 integrations facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 16 compliance facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 13 pricing facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 12 legal facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 data facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 2 support facts could not be confirmed on the vendor’s page as captured and were left out of this page and of the panel’s material. Know more? Tell us
- 1 hosting fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 1 subprocessors fact could not be confirmed on the vendor’s page as captured and was left out of this page and of the panel’s material. Know more? Tell us
- 2 sovereignty dimensions could not be confirmed on the vendor’s own pages and are shown as unknown. Know more? Tell us
- 6 of the readings below were written against an earlier fact sheet — a fact has been corrected, added or pulled since. Until the panel next runs on this product you are reading the older judgement. Know more? Tell us
Sources (9)
The pages every claim on this page was read from — each one checked, dated, and kept verifiable.
- 1 Vendor page www.tidio.com Checked 22 Sep 2026 Details →
- 2 Terms of service — found from the homepage www.tidio.com Checked 30 Sep 2026 Details →
- 3 Privacy policy — found from the homepage www.tidio.com Checked 30 Sep 2026 Details →
- 4 Ticketing, queues & SLA — found from sitemap www.tidio.com Checked 1 Oct 2026 Details →
- 5 Ticketing, queues & SLA — found from sitemap developers.tidio.com Checked 1 Oct 2026 Details →
- 6 Channels in one queue — found from sitemap www.tidio.com Checked 1 Oct 2026 Details →
- 7 Channels in one queue — found from sitemap www.tidio.com Checked 1 Oct 2026 Details →
- 8 Integrations & API — found from sitemap www.tidio.com Checked 1 Oct 2026 Details →
- 9 Integrations & API — found from sitemap www.tidio.com Checked 1 Oct 2026 Details →