Panel rating · 6 judges · How to read the stars
Category median
Sovereignty: 3 of 6 dimensions proven
0–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? →
Link to this page
Add ?theme=dark to the image address for dark backgrounds.
The badge shows the category and the month of the latest evaluation, and EU-Made where
that is the product’s provenance. It never shows a score.
Tidio at a glance
- Vendor
- Tidio
- Headquarters
- Incorporated in the United States source, captured 16 Nov 2026
- Data hosting
- In the EU by default source, captured 16 Nov 2026
- Free plan
- Yes, per the vendor’s own page source, captured 26 Oct 2026
- Panel verdict
- The AI panel rates Tidio 2.5/5, the mean of 6 judges. Tidio, a customer service and helpdesk platform, scored highest on omnichannel and integrations, both at 6, and lowest on knowledge and self-service at 2 to 3, where self-service leans on AI bots rather than a knowledge base. how scores are made
- As of
- Vendor pages captured 22 Sep 2026 to 16 Nov 2026; evaluated by the panel 18 Nov 2026. all sources
Read this page as one judge. Each weighs the same scores by what they care about.
The panel's verdict
Tidio, a customer service and helpdesk platform, scored highest on omnichannel and integrations, both at 6, and lowest on knowledge and self-service at 2 to 3, where self-service leans on AI bots rather than a knowledge base. Its strength is the single inbox: WhatsApp, Messenger, Instagram, email and live chat land in one panel, forwarded email arrives as tickets, plus a documented ticket-data API beside Salesforce, Zendesk and Shopify integrations. Ticketing core settled at 4 — priorities, tags, departments and assignment are documented, while the captured ticketing page states no SLA or queue features. Customer data protection and sovereignty sit at 4: storage is stated as mainly in the EEA and Tidio Poland Sp. z o.o. is a joint controller, yet the contracting entity is Tidio LLC of San Francisco under California law, and some data may be transferred to and processed in the United States. Pricing transparency spread widest, from 4 to 6: five tiers from Free to Enterprise at $2,999, "Paid plans from $29/mo", but we found no public information on per-agent maths or add-on costs.
Speaks for it
- WhatsApp, Messenger, Instagram, email and live chat land in one panel, with returning WhatsApp customers recognised by phone number and their existing data shown to agents.
- Forwarded email from any provider arrives as a ticket, and a documented ticket-data endpoint exposes priority, status, tags, departments and custom fields with webhooks and keyset pagination.
- Lyro grounds answers in your website, help centre and product data, chatbots handle shipping, order and returns questions, and a 75% average resolution rate is claimed for Lyro.
- Salesforce, Zendesk and Shopify are named integrations, and Jira issues can be created from chats with custom field mapping and status tracking.
- Five tiers carry public prices — Free, Starter at $29, Growth at $59, Plus at $300 and Enterprise at $2,999 — with a free plan forever, no credit card required and cancellation in two clicks.
Held against it
- The captured ticketing page states no SLA or queue features, we found no public information on escalation or ticket search, and the API docs state that solving a ticket resets its assignment.
- We found no public information on a hosted knowledge base, article workflow or deflection reporting.
- The terms reserve the vendor's right to access your account for technical purposes without prior notice.
- The contracting entity is Tidio LLC of San Francisco under California law, subprocessors are disclosed as categories with a few named companies, and some data may be transferred to and processed in the United States.
- We found no public information on per-agent maths, add-on or AI usage costs, and the captured pages give different tier names, with the Jira page referencing Plus and Premium plans.
Best for
- You run an online shop and want WhatsApp, Instagram, Messenger, email and live chat handled in one panel, with carts, order history and discounts visible inside the conversation.
- You want AI to deflect shipping, order and returns questions using your existing website, help-centre and store content.
- You want to start at no cost before committing — the free plan is forever, no credit card is required and cancellation takes two clicks.
- You assign conversations to named operators and departments and need to see in real time who else has a ticket open.
Avoid if
- Your support operation runs on SLA targets, timers, breach warnings or first-response reporting — the captured ticketing page states no SLA or queue features.
- You rely on article-based self-service — the documented deflection path is AI bots grounded in content you already host elsewhere.
- You must contract under EU law end to end — the contracting party is Tidio LLC of San Francisco under California law, and some data may be transferred to and processed in the United States.
- You need a full-year cost figure before signing — the terms permit automatic upgrades when usage exceeds your plan, and we found no public information on per-agent maths or add-on costs.
The scores
| Criterion | Panel median |
|---|---|
| Ticketing, queues & SLA | 2 of 5 |
| Channels in one queue | 3 of 5 |
| Knowledge base & deflection | 1 of 5 |
| Customer data protection | 2 of 5 |
| Integrations & API | 3 of 5 |
| European sovereignty | 2 of 5 |
| Pricing transparency | 2.5 of 5 |
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 — Not a ticketing tool: requests stay in a shared mailbox or chat with no ticket, owner or status of their own.
3 — Tickets with assignment, a status and a conversation history, worked from a shared inbox with views or filters.
5 — Tickets routed by rules or automations to teams or agents, priorities and statuses, SLA targets or response-time reporting, and search across tickets.
8 — Business-hours-aware SLA policies per queue or customer with breach warnings and escalation, macros and triggers, merge and split, skills- or load-based assignment, 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 come with status, priority, tags, departments and a named operator, worked from a shared inbox with smart views and macros, and the export API is detailed enough to warn that solving a ticket resets its assignment — a level of care I respect. But my SLA is nowhere in it: we found no public information on SLA policies, timers, breach warnings, escalation or first-response reporting, so this is a well-organised inbox rather than a managed workload. 4 5 7 6 4
The Agent Advocate
Assignment to named operators, priorities, statuses, tags, notes, smart views and macros are all documented, and the ticket data endpoint exposes departments and custom fields — good bones for a working queue. But the ticketing page itself states no SLA or queue features, and we found no public information on ticket search or first-response and resolution reporting. The API docs quietly admit assignment resets to null the moment a ticket is solved, which is exactly the kind of quirk you feel at the hundredth reply. 4 5 7 1 4
The Data Protection Officer
Chats and emails become tickets with priorities, statuses, tags, departments, custom fields and assignment to named operators, worked from a shared inbox with smart views, macros and real-time visibility of who has a ticket open. The ticketing pages we read state prioritisation and assignment without stating SLA or queue features, and we found no public information on escalation, business-hours targets or search across tickets. 4 5 7 1 6 4
The Shop Operator
Tickets are real things here: assignment to operators and departments, status, priority, tags, custom fields, macros and smart views, and the ticket data API exposes the same fields for reporting. But the captured ticketing page itself states no SLA or queue features, and we found no public information on routing rules or automations, ticket search, or response-time reporting — so this is organised assignment work, not SLA-managed work. 4 5 1 4
The Integrator
Tickets carry assignment, priority, status, tags, notes and smart views, and the developer documentation exposes departments and custom fields on every ticket — this is a real ticketing engine, not a mailbox. But the captured ticketing pages describe prioritisation and assignment only, and I found no public information on SLA targets, queue-level policies, escalation, routing rules or search across tickets; the API even resets agent assignment when a ticket is marked solved. 4 5 1 6 4
The Skeptic
Tickets carry priority, status, tags, departments and per-agent assignment with real-time visibility of who has what open, and a documented ticket-data endpoint confirms the data model — but the captured ticketing page itself states no SLA or queue features, and I found no public information on SLA targets, routing rules, ticket search or response-time reporting. Macros appear once on the WhatsApp page; nothing documented reaches business-hours policies or escalation. 4 4 5 1 6
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 — No customer channel of its own; the product only works on tickets entered by hand or by another system.
3 — Email turned into tickets, with a web form or one further channel.
5 — Email, a web form or portal and live chat or a messenger landing as tickets in one inbox, with the customer's earlier conversations visible to the agent.
8 — The above plus telephony integration with call logging, at least one messenger (WhatsApp or similar) with its consent handling stated, social channels, and a customer portal where a requester can see their own tickets — all in one history.
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
WhatsApp, Messenger, Instagram, email and live chat land in one panel with the full conversation history, a returning WhatsApp customer is recognised by phone number, and part of a chat can be turned into a ticket. The gaps for a full omnichannel desk: we found no public information on telephony with call logging, a requester-facing portal, or how messenger consent is handled. 7 7 1 6
The Agent Advocate
Email forwarded from any provider, live chat, WhatsApp, Instagram and Messenger all land in one panel with the full history next to the conversation and returning customers recognised by phone number — that is the one screen I want. The ticketing page, though, places emails in a dedicated tab separate from chats, and we found no public information on telephony, a requester-facing portal, or messenger consent handling. Strong on chat and messengers, unproven beyond them. 4 7 7 1 6
The Data Protection Officer
WhatsApp, Messenger, Instagram, email and live chat all land as messages in one panel, forwarded email arrives as tickets beside the chats, the full conversation history sits next to each exchange, and WhatsApp visitors are recognised by phone number with their existing data shown. We found no public information on telephony with call logging, a customer portal where requesters see their own tickets, or messenger consent handling. 6 7 7 1 6 4
The Shop Operator
WhatsApp, Messenger, Instagram, email and live chat land in one panel with the full message history kept next to the chat, and WhatsApp arrivals are matched to the existing customer record — the WhatsApp-and-the-shop-in-one-queue test passes, with multiple agents on WhatsApp at once. One captured page shows emails in a dedicated tab separate from chats while another presents one inbox for both; we found no public information on telephony, a customer portal, or WhatsApp consent handling. 7 7 1 6 4
The Integrator
WhatsApp, Messenger, Instagram, email and live chat all land in one panel with the full conversation history kept next to the chat, and the product recognises returning WhatsApp customers and shows their existing data to the agent. I found no public information on telephony integration, a customer portal where a requester sees their own tickets, or messenger consent handling, so it is strong on messengers but short of the full multichannel picture. 7 7 1 6 4
The Skeptic
WhatsApp, Messenger, Instagram, email and live chat are all promised in one panel, forwarded email from any provider arrives as a ticket, and existing customers are recognised across channels with history visible — but the vendor's own ticketing page puts emails in a dedicated tab separate from chats, bridged by manually turning part of a chat into a ticket. I found no public information on telephony, a customer portal where requesters see their own tickets, or WhatsApp consent handling. 7 7 6 4 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 or self-service of any kind; the product is a ticket inbox only.
3 — A knowledge base or FAQ with articles, internal or public, that agents can link in replies.
5 — A searchable public help centre with categories and its own branding, draft and publish states, and agents able to insert or suggest an article in a reply.
8 — Article suggestions to the customer before they submit and to the agent while they answer, multilingual articles, review dates or versioning 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
Deflection here is the AI agent and bots answering shipping, order and returns questions, grounded in the customer's own website, help centre and store data — useful on a Monday queue, but not a curated knowledge base. We found no public information on a branded public help centre, article workflow, multilingual articles or deflection reporting. 7 1
The Agent Advocate
Deflection is documented, but it is a bot rather than a library: Lyro answers grounded in your website, help centre and product data, chatbots handle shipping and returns questions, and the vendor claims a 75% average resolution rate. We found no public information on a hosted help centre, article workflow, suggestions to agents, or reporting on which articles deflect. 7 1
The Data Protection Officer
Deflection is documented as chatbots and the Lyro agent answering common questions about shipping, orders and returns, grounded in the customer's own website and help-centre data with a claimed 75% resolution rate. We found no public information on an article library with draft and publish states, multilingual articles or deflection reporting inside the product. 7 1
The Shop Operator
Deflection is genuine but it runs through bots, not articles: chatbots answer shipping, orders and returns questions, Lyro resolves incoming emails grounded in the buyer's own help-centre and store data, and a 75% average resolution rate is claimed. We found no public information on a knowledge base, article workflow, or customer-facing help centre of the product's own, so I cannot credit article-based deflection. 7 1
The Integrator
Deflection happens through AI rather than a managed knowledge base: Lyro grounds its replies in the customer's own website, help centre and product data, and chatbots answer common shipping, order and returns questions. I found no public information on a hosted help centre with article workflow, review dates, multilingual articles or deflection reporting — self-service leans on content the buyer already has elsewhere. 7 1
The Skeptic
Lyro answers are grounded in the customer's website, help center and store data, and chatbots automatically handle shipping, orders and returns questions — that is deflection, of a kind, with a claimed 75% resolution rate. But I found no public information on a knowledge base with articles, draft and publish states, article suggestions to agents, or deflection reporting; the help center named in the pages is the AI's data source, not a documented authoring product. 1 7 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 under DSGVO, and what the vendor does with attachments — judged on what the product documents it executes.
0 — The vendor's own terms state that ticket content is used for purposes beyond providing the service, or that a data processing agreement is not offered.
3 — A privacy policy and a data processing agreement (DPA) offered, with agent roles that limit what an agent can do.
5 — A DPA published or signable online, agent roles and group- or queue-level visibility, and deletion of tickets or of a requester's data documented in the help centre.
8 — Automatic retention or deletion rules per queue or data category, attachment handling stated, an audit log of agent access or changes, documented support for access and erasure requests, and 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
The privacy policy names joint controllers, claims GDPR compliance alongside SOC 2 certification, documents account deletion with a six-month cap after unsubscribing, and answers subject requests free of charge. For a data-protection audit I would still be short: we found no public information on agent roles, retention rules per queue, redaction or an audit trail of agent access, and the terms reserve Tidio the right to enter the account for technical purposes without prior notice. 2 3 1
The Agent Advocate
The privacy policy is GDPR-framed with concrete retention rules, an in-app account-deletion feature, free subject-request handling and SOC 2 certification, and the terms incorporate a DPA by reference. We found no public information on agent roles, queue-level visibility, per-queue retention, redaction, or an audit log of agent access — and the terms reserve the vendor's right to access your account without prior notice. 2 3 1
The Data Protection Officer
Documented: a privacy policy with GDPR and California posture, a data processing agreement announced as incorporated by reference, SOC 2 certification, free-of-charge handling of data subject requests, and deletion of tickets and of the account with a six-month retention fallback. We found no public information on agent roles or queue-level visibility, redaction of ticket content or automatic retention rules; audit logs appear only as a homepage bullet, and the terms reserve the vendor's right to access the account for technical purposes without prior notice. 1 2 3 5 1
The Shop Operator
The paperwork is specific: GDPR processing as controller for the site, a DPA announced in the terms, retention defined (account data until deletion, a six-month fallback after unsubscribing), subject requests free by default, SOC 2 certification and Data Privacy Framework commitments. We found no public information on agent roles, per-ticket deletion or retention rules, attachment handling or redaction, and the terms reserve Tidio's right to access the account for technical purposes without prior notice. 2 3 1
The Integrator
There is a published privacy policy with GDPR and CCPA statements, SOC 2 certification and a trust centre, an offered data processing agreement, retention limits tied to account deletion, and subject requests handled free of charge — a credible baseline. I found no public information on agent roles or queue-level visibility, automatic retention per category, redaction or an agent-access audit log, and the terms reserve the vendor's right to access the account for technical purposes without prior notice. 2 3 1
The Skeptic
The privacy policy states GDPR processing with retention limits, free-of-charge subject requests, a 45-day complaint process and DPF enrolment, and SOC 2 certification with a trust centre are advertised; audit logs appear once as an AI guardrail claim. The terms reserve the vendor's right to access the customer account for technical purposes without prior notice, and I found no public information on agent roles, queue-level visibility, ticket-level deletion, attachment handling or redaction. 3 2 1 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 — A closed tool with no API and no integrations; context is copied in by hand.
3 — A handful of named integrations or a connector service such as Zapier, or an API with basic documentation.
5 — Named integrations for common CRM, shop or collaboration tools, a documented REST API, and webhooks or triggers that call other systems.
8 — An app marketplace with maintained bidirectional integrations, customer context from other systems shown inside the ticket, SSO and 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
Twenty integration categories with Salesforce, Zendesk and Shopify named, a documented ticket-data API with pagination and webhooks, and a Jira link that creates issues from chat and maps custom fields on the Plus and Premium plans. Order history and carts appear inside the conversation, which is the context my agents want, though we found no public information on single sign-on, SCIM provisioning or a developer sandbox. 5 8 9 1 8
The Agent Advocate
Salesforce, Zendesk and Shopify are named, Jira comes with issue creation, custom-field mapping and status tracking including its plan availability, and there is a documented ticket-data API with honest pagination guidance plus webhooks and a mobile SDK. We found no public information on SSO or SCIM provisioning, a sandbox, or maintained bidirectional marketplace apps — so it sits above connected, short of platform. 5 8 9 7
The Data Protection Officer
A documented developer API for ticket data with pagination and webhooks, an integration directory spanning CRM, ecommerce, analytics and more with Salesforce, Zendesk and Shopify named, a maintained Jira integration that creates issues from chats and maps custom fields, and order history and carts shown inside the conversation. We found no public information on single sign-on, user provisioning, a sandbox or published rate limits. 5 8 9 1 8
The Shop Operator
Salesforce, Zendesk and Shopify are named among eighteen integration categories, there is a documented ticket data API with webhooks, Jira issues can be raised from chats with status tracked back (on higher-priced plans), and the vendor builds custom API integrations. The part I care about is there — carts, order history and discounts handled inside the conversation — but we found no public information on SSO, SCIM provisioning, or a sandbox. 5 8 9 1
The Integrator
There is a genuine developer site with a documented ticket endpoint — keyset pagination, a 25-second statement timeout returning 408, webhooks — plus named Salesforce, Zendesk and Shopify integrations and a Jira integration with custom field mapping, status tracking and customer context passed into issues. But the 5 8 9 1 8
The Skeptic
Salesforce, Zendesk and Shopify are named alongside a plan-gated Jira integration that passes context and tracks status, carts and order history surface inside the conversation, and a genuinely documented ticket-data endpoint with webhooks, pagination and timeout behaviour exists. I found no public information on SSO, SCIM provisioning, documented rate limits or a sandbox, and the integrations page reads as a catalogue rather than a maintained marketplace. 5 8 9 8 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. Dimensions the evidence does not establish are unknown, not non-EU.
0 — Proven non-EU on every dimension the evidence covers: non-EU vendor and contracting entity and non-EU hosting, with no EU option stated.
3 — One European element proven — an EU hosting option, an EU contracting entity or EU representative, or a published DPA — with the rest of the chain unstated.
5 — EU hosting stated as standard or selectable and an EU contracting entity or EU representative, with a DPA offered; the subprocessor chain is unstated or partly non-EU.
8 — EU or DACH hosting with a named data-centre provider, EU contracting entity, subprocessor list published with locations, 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
Storage is stated as mainly within the EEA on servers there, Tidio Poland Sp. z o.o. sits as joint controller, and a data processing agreement is available. The chain is not European end to end: the contracting party is Tidio LLC of San Francisco under California law, the privacy policy acknowledges data may be transferred to and processed in the United States, and the subprocessor disclosure gives categories with a few named entities rather than a located list. 2 3
The Agent Advocate
Storage defaults to the EEA, Tidio Poland appears as joint controller, and a DPA is on offer — genuine European elements. But the contracting entity is a California LLC under California law, the policy concedes data may be transferred to and processed in the United States, and the published subprocessor information is categories including at least one US company. Half a chain, not a whole one. 2 3
The Data Protection Officer
Data is documented as mainly processed within the EEA with some transfer and processing in the United States, a Polish company acts as joint controller alongside the San Francisco contracting entity, and a data processing agreement is announced in the terms. The contracting party remains a California company under California law with Data Privacy Framework commitments, subprocessors appear as categories with a few named companies rather than a published list with locations, and the terms reserve the vendor's right to access the account without prior notice. 2 3
The Shop Operator
Two European elements are proven: data is mainly processed in the EEA and Tidio Poland in Szczecin is a joint controller, with a DPA announced in the terms. But the contracting entity is Tidio LLC in San Francisco under California law with Data Privacy Framework and FTC commitments that point to US handling of personal information, and subprocessors are given as categories rather than a published list with locations. 2 3
The Integrator
Processing is stated to be mainly within the EEA and Tidio Poland Sp. z o.o. appears as joint controller, which gives the ticket archive a partly European footing. The contracting entity in the terms is Tidio LLC of San Francisco under California law, the privacy policy says some data may be transferred to and processed in the United States under the Data Privacy Framework with FTC enforcement, and subprocessors appear only as categories, so the chain is neither named nor fully European. 2 3
The Skeptic
Processing is stated to happen mainly in the EEA, with servers located there, and Tidio Poland Sp. z o.o. is named as a joint controller — but the contracting entity is Tidio LLC of San Francisco under California law with San Francisco venue, US transfers are acknowledged under the Data Privacy Framework with FTC enforcement, and named subprocessors include Twitter Inc. Hosting options, certification and a transfer impact assessment are unknown from these pages. 3 2
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 public "from" price or one priced tier, per agent or flat.
5 — Per-agent prices public for the main tiers with the billing period stated and the main features per tier listed.
8 — Every tier and add-on priced publicly with per-agent maths, telephony or messenger costs and light-agent or contact limits given, 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
Five tiers carry public prices in US dollars — a free plan, Starter $29, Growth $59, Plus $300 and Enterprise $2999 — under "Paid plans from $29/mo", with the terms stating customers bear value-added tax. I still cannot produce an invoice from it: we found no public information on per-agent maths, add-on or channel costs, or a feature-by-tier breakdown, the captured pages give different plan names (the Jira page references Plus and Premium), and the terms permit automatic upgrades when usage exceeds the plan, with an opt-out. 2 1 4
The Agent Advocate
Five plans carry public prices — Free at $0, Starter at $29, Growth at $59, Plus at $300 and Enterprise at $2999, with "Paid plans from $29/mo" — and the terms state VAT treatment, automatic upgrades with an opt-out, and refund limits. An annual invoice still is not computable: we found no public information on per-agent maths, per-tier feature lists, or add-on and AI-usage costs, and integration availability simply "depends on your Tidio plan" — with the Jira page naming a Premium tier where the pricing page's list ends in Enterprise. 2 9 1 4
The Data Protection Officer
Public figures exist for all five tiers — Free at $0, Starter at $29, Growth at $59, Plus at $300 and Enterprise at $2,999 — with "Paid plans from $29/mo", a free plan forever, cancellation in two clicks and the terms putting VAT responsibility on the customer. We found no public information on per-agent maths, prices for the AI add-ons or usage-metered channel costs, so the real annual invoice for a given team cannot be computed from these pages alone. 2 9 1 4
The Shop Operator
All five plans carry public prices — Free, Starter $29, Growth $59, Plus $300 and Enterprise $2999, with "Paid plans from $29/mo" stated, a free tier with no credit card, cancellation in two clicks, and the terms putting VAT on the customer. But the real annual invoice is not computable from what I read: we found no public information on per-operator maths, add-on or AI usage pricing, or minimum terms. 2 1 4
The Integrator
Five tiers are priced publicly in US dollars — free, 29, 59, 300 and 2999 — with a monthly basis stated ( 2 9 1 4
The Skeptic
All five tiers carry public numbers — Free, Starter at $29/mo, Growth at $59, Plus at $300, Enterprise at $2,999 — and the terms state VAT is the customer's responsibility; but the add-on and usage prices behind the terms' automatic-upgrade clause are not public, no per-agent basis, light-agent limits or channel costs are given, and the captured pages give different tier names, with the Jira page naming a Premium plan the pricing list does not. 4 1 2 9
European sovereignty — proven facts
3 of 6 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 |
Incorporated in US
unverified
Why unverified?The pages also name Tidio Poland Sp. z o.o. (Szczecin) as a joint controller and "a company in the TIDIO capital group" without stating which entity is the group parent, though nothing marks Tidio LLC itself as a subsidiary. |
0/2 pts | 2 Report an error |
|---|---|---|---|
| Hosting location |
EU by default
unverified
Why unverified?Storage is only "mainly" in the EEA; some data may be transferred and processed in the United States. |
2/4 pts | 3 Report an error |
| Hosting options | Not determined | — | uncited Report an error |
| Open source | Not determined | — | uncited Report an error |
| Data processing agreement |
Published, self-serve
unverified
Why unverified?The Terms only announce that the DPA is incorporated by reference; the DPA text itself is not reproduced in this excerpt. |
1/1 pts | 2 Report an error |
| Transfer impact assessment | Not determined | — | uncited Report an error |
Questions about Tidio
Is Tidio European?
Not determined: the vendor’s pages as captured do not say where Tidio is based. Its vendor, Tidio, is incorporated in the United States, per the vendor’s page captured 16 Nov 2026.
Where does Tidio store data?
Tidio stores customer data in the EU by default, though not exclusively, per the vendor’s page captured 16 Nov 2026.
Does Tidio have a free plan?
Yes. Tidio has a free plan, per the vendor’s page captured 26 Oct 2026.
What are the best alternatives to Tidio?
As of 18 Nov 2026, the panel rates Zendesk (3.5/5), LiveAgent (3.5/5) and Intercom (3.5/5) highest among the other 35 Customer Service & Helpdesk products evaluated. Ratings that look equal are rounded to half stars; the order uses the unrounded rating, then the name. The highest-rated European alternative is Zammad (EU-Made, Germany). Ratings are the AI panel’s opinion, formed from public evidence: how scores are made. The full list, with European products first: Tidio alternatives.
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 — Data processing agreement. The Terms only announce that the DPA is incorporated by reference; the DPA text itself is not reproduced in this excerpt.
- Weak sourcing — Legal entity. The pages also name Tidio Poland Sp. z o.o. (Szczecin) as a joint controller and "a company in the TIDIO capital group" without stating which entity is the group parent, though nothing marks Tidio LLC itself as a subsidiary.
- Weak sourcing — Hosting location. Storage is only "mainly" in the EEA; some data may be transferred and processed in the United States.
- 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.
- 42 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
- 41 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
- 9 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
- 8 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
- 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 data 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 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
- The pricing here was last read more than 30 days ago. Vendors change prices without notice; the capture date is shown with every figure. 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 16 Nov 2026 +2 earlier captures: 26 Oct 2026, 22 Sep 2026 Details →
- 2 Terms of service — found from the homepage www.tidio.com Checked 16 Nov 2026 Details →
- 3 Privacy policy — found from the homepage www.tidio.com Checked 16 Nov 2026 Details →
- 4 Ticketing, queues & SLA — found from sitemap www.tidio.com Checked 16 Nov 2026 +1 earlier capture: 2 Nov 2026 Details →
- 5 Ticketing, queues & SLA — found from sitemap developers.tidio.com Checked 16 Nov 2026 Details →
- 6 Channels in one queue — found from sitemap www.tidio.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 7 Channels in one queue — found from sitemap www.tidio.com Checked 16 Nov 2026 +1 earlier capture: 1 Oct 2026 Details →
- 8 Integrations & API — found from sitemap www.tidio.com Checked 16 Nov 2026 +1 earlier capture: 26 Oct 2026 Details →
- 9 Integrations & API — found from sitemap www.tidio.com Checked 16 Nov 2026 Details →