Tidio for SaaS: Fit, Costs and Limits for Support Teams

Tidio fits a SaaS support team of up to 10 people that answers most questions in website or in-app chat and wants AI on its product docs without paying per seat. The price follows conversations, not people. Growth starts at $59 a month billed monthly, or $49.17 a month billed annually, for 250 billable conversations, with 10 seats included for the project.^[1] It stops fitting when you need the developer platform, departments or single sign-on. Webhooks, the OpenAPI and departments sit on Plus, which Tidio sells through sales from $300 a month plus monthly usage. SSO needs the top tier, Premium. Good for lean teams. Weak on enterprise controls.

Morning: chat inside the product, with users already identified

A SaaS support day starts in the app, not on the marketing site. Tidio's widget installs with one JavaScript line, and the widget SDK (tidioChatApi) works on every plan to open, hide and restyle the widget or track custom events. Secureframe, a US compliance platform, runs the widget behind its customer login for existing users only, Tidio's case study says.^[2] That split matters: support sees paying users while sales chat stays public. Tidio does not help implement the SDK, so budget some developer time.

Identification is the part to get right. Calling document.tidioIdentify with a distinct ID, email, name or phone merges conversations from the same user in the admin panel.^[3] The older setVisitorData call does not merge them, and its email gets replaced by the identify email after a refresh if the two differ. Account plan or workspace ID can travel as contact properties through setContactProperties, but each property must first be defined in Settings. Custom events sent with track become triggers in the Flows editor, so an in-app event can start a guided Flow. A native Mobile SDK exists only on Premium.

Lyro on your docs, and what it can actually do

Lyro answers only from the knowledge you give it: website URLs, manual Q&A, CSV and PDF files, public Zendesk Help Center articles and Tidio's own Help Center builder. A project takes up to 500 website URLs, more on Plus. Two traps hit documentation sites. Cloudflare firewalls can block scanning, and re-syncing a website source replaces its generated Q&A, so manual edits are lost. The Help Center builder publishes on tidio.help or your own domain, with articles in several languages, but it cannot import existing articles yet. You write from scratch.

Moving from Intercom? Its conversations and Help Center articles can be imported into Lyro with Tidio's help, but only with an active paid Lyro subscription. Lyro covers 48 languages, sees three hours of recent conversation history and, on email, answers only the first message of a new thread before a human takes over. Tidio's SaaS help-desk post says Lyro solves up to 75% of customer questions automatically; treat that as the vendor's figure, not a forecast. Copilot drafts agent replies from the same knowledge, needs Lyro enabled, and is listed on every plan.

Actions and Procedures for account questions

Actions let Lyro call your API, for example to look up an account or log a lead, with options to run in the background or ask the visitor to confirm first. Free, Starter and Growth get one Action without a paid Lyro quota and three with one; Plus gets up to 10. The Terms require all inputs at the start, return one deterministic outcome, and leave the results of any change with you. Procedures chain Actions, contact properties and ticket creation into multi-step workflows, five on Starter and Growth, for live conversations only. Tidio helps configure Actions and API calls only on Plus. Our Tidio AI playbook covers setup in depth.

Afternoon: tickets, SLA targets and the engineering handoff

Not every question closes in chat. Email, widget tickets and social conversations share one inbox, and SLA policies set internal first-reply and next-reply targets per ticket source, in calendar hours, invisible to customers. Ticket priority can follow the SLA policy. These are your targets, not a promise from Tidio, which publishes no uptime commitment. Growth adds what a busier queue needs: macros, permissions and custom roles, automatic assignment and per-agent advanced analytics. Automatic assignment covers live chat and social only. Emails stay unassigned.

The handoff to product work is where SaaS support differs from retail. Tidio's SaaS post describes a Jira integration that turns a chat into a Jira issue with the customer messages attached and shows the issue status inside Tidio. HubSpot syncs contacts and saves the transcript to the contact record, and Salesforce does the same. Zapier works one way, from Tidio to the other app, and only with data a Flow collected. Tidio's own post says it is not an ITIL service desk with asset management. Our integrations guide lists each connector with its plan.

What a SaaS support team pays

The plan price buys human-answered conversations only. A conversation Lyro or Flows handles alone is not billable, but each runs its own meter. Lyro's 50 free conversations are one-time per project, and ongoing AI starts at $39 a month billed monthly, or $32.50 a month billed annually, for 50 Lyro conversations, counted per conversation joined, not per resolution. Flows reach 100 unique visitors a month free, then cost from $29 a month billed monthly, or $24.17 a month billed annually, for 2,000, and at the cap Flows stop for new visitors. Monthly self-serve packages on new projects move up a level at 95% of a quota unless you switch that off, and at 100% of the conversation quota agents cannot see new conversations until the monthly reset or an upgrade.

By our arithmetic, a team answering 250 conversations a month by hand with 100 Lyro conversations pays $59 plus $75, or $134 a month billed monthly; billed annually it comes to $1,340 a year, about $111.67 a month. At 1,000 human conversations plus 500 Lyro conversations the total is $529 a month billed monthly or $440.83 a month billed annually. In both cases the AI quota costs more than the plan. The Terms owe no refunds, and discretionary ones are capped at three months, so test on the 7-day trial before paying annually.

Seat pricing is where conversation pricing pays off. For three agents, Zendesk Suite Team at $69 per agent a month billed monthly comes to $207 a month, against $59 a month billed monthly for Tidio Growth 250. Zoho Desk Standard billed annually at $14 per agent a month totals $42 for three agents, the one plan in our comparison that costs less than Tidio Growth 250 at $49.17 a month billed annually. Secureframe chose Tidio because its pricing let the entire team use the platform, Tidio's case study says. Our Tidio alternatives guide covers the per-agent tools.

Where Tidio stops fitting a SaaS company

The 10-seat cap is the first wall. Free, Starter and Growth include 10 seats per project, and an eleventh person means Plus, sold through sales from $300 a month plus monthly usage. Plus is also where the developer platform lives: the full OpenAPI, signed webhooks, the Analytics API, departments, ticketing automations, the Slack integration and live-chat support from Tidio. A team that wants support events in its own warehouse or alerting stack needs Plus. Those are not small gates for an engineering-led company.

Identity and audit controls sit higher still. SAML single sign-on, set per project with an option to force it for the whole team, is Premium only, priced by quote. Tidio does not publish an audit log, SCIM user provisioning or IP restriction, items that security reviews at larger customers usually ask about. Tidio says it completed a SOC 2 Type II examination. Tidio says data is mainly processed in the EEA, but its privacy policy says it may be transferred to the United States. Tidio is not a HIPAA business associate. Health-data products should look elsewhere.

What Tidio's SaaS case studies report

Tidio's case study says Secureframe, with 200+ employees, reached a 59% Lyro resolution rate and a 79% answer rate, up from 2-3% with its previous chatbot, after basic onboarding of about two weeks with a dedicated customer success manager. Endeksa, a Turkish PropTech data platform, reports a 59% drop in waiting times, and a 138% rise in leads since subscribing to Plus, which it credits to pre-chat surveys, according to Tidio's case study. Neither figure is an independent measurement.

Integratec, a Mexican B2B SaaS company, reports about 25% more qualified leads from website chat, Tidio's case study says. Adjoe, a Hamburg adtech company handling 3,000 to 5,000 daily inquiries with a Flows decision tree, saw contacts created through the bot rise from 9,000 to 12,152 in one month and support email fall 80%, Tidio's case study says. Read the pattern, too. Endeksa and Integratec both mention Plus, and Secureframe had a dedicated manager, so these results describe sales-led setups more than self-serve Growth.

The bottom line

Tidio suits a SaaS support team of up to 10 people that lives in chat, keeps its docs current and wants Lyro to absorb repeat questions without seat pricing. Budget three meters (the plan, the Lyro quota and, if in-app events trigger Flows, the Flows quota), wire up visitor identification on day one, and use SLA policies to hold your own reply targets. Once you need webhooks, the OpenAPI, departments, SSO or more than 10 seats, the price moves to sales-led Plus or Premium, and the comparison with per-agent help desks starts over.