Skip to content
Install on Shopify
Apps & Tools

Tidio vs Arbyn: Conversation Caps vs Unlimited Shopify Support

Tidio vs Arbyn comes up constantly for one specific reason: a store hits Tidio's Lyro AI conversation limit, gets pushed toward an upgrade, and starts looking for what a Shopify su

Summarize with AI
Odera Joseph
Founder · July 18, 2026 · 7 min read
Tidio vs Arbyn: Conversation Caps vs Unlimited Shopify Support

Tidio vs Arbyn comes up constantly for one specific reason: a store hits Tidio's Lyro AI conversation limit, gets pushed toward an upgrade, and starts looking for what a Shopify support tool without a conversation ceiling actually looks like. The comparison is straightforward once the two billing structures are laid out side by side, since the products solve overlapping problems but charge for them in almost opposite ways. Anyone researching Tidio vs Arbyn specifically because of a surprise Lyro bill should start with the pricing structure below, since that's almost always where the actual difference lives.

We get asked to compare against Tidio a lot, and the honest version of that comparison isn't that Tidio is bad. It's that their pricing punishes exactly the outcome a store wants, which is more customers getting helped.

Odera Joseph Echendu, Founder, Arbyn

What Tidio Actually Charges, Precisely

Tidio's base Customer Service plan runs from a free tier up through paid tiers, with its Growth plan landing around 59 dollars a month. Lyro, Tidio's AI agent, is priced and metered entirely separately from that base plan, starting at 39 dollars a month for 50 AI conversations and scaling upward from there according to volume, per multiple 2026 pricing breakdowns including ones from Chatsy and Featurebase. A store on the 59-dollar Growth plan that also wants a meaningful volume of AI conversations, 500 a month for example, is realistically paying somewhere in the 150 to 250 dollar range once Lyro is added, before counting seats, Flows automation, or branding removal, each billed as additional line items on top.

Every new Tidio install gets 50 Lyro conversations included, but as a one-time lifetime allowance rather than a recurring monthly one. Once that runs out, Lyro stops responding until a paid quota is purchased, which is a meaningfully different mechanic from a monthly allowance that refreshes. The plan structure also includes a tier cliff worth knowing before budgeting a full year: Tidio's stack jumps from the 59-dollar Growth tier directly to a Plus tier starting at 749 dollars a month, a roughly 12 times increase with nothing in between, according to a 2026 pricing analysis from Chatarmin. A store that outgrows Growth's allotment isn't looking at a modest step up. It's looking at a cliff, and the only way to soften it is stacking a separately metered Lyro package on top of Growth and hoping the combined total lands below what Plus costs outright.

What Arbyn Charges, Precisely

Arbyn runs two plans, not a base-plan-plus-metered-AI-addon structure. Arbyn Starter is 0 dollars a month for 150 AI conversations per calendar month, full features, no gating, and no separate charge for the AI layer since there isn't a separate AI layer to charge for, the plan simply is the AI agent. Arbyn Agent is 99 dollars a month flat for unlimited conversations, with no per-conversation metering, no separate AI add-on fee, and no tier cliff between Starter and Agent, just the two plans. Billing starts immediately when a store owner selects Arbyn Agent, and there is no trial period on either plan. The first 50 lifetime conversations on any new install, either plan, are a calibration window where the agent learns the store's tone, catalog, and rules, and those 50 do not count against Starter's monthly cap, distinct from Tidio's lifetime-allowance model where the free conversations are the entire free tier rather than a separate calibration period sitting outside a larger monthly allowance.

The Structural Difference This Actually Creates

The practical gap between these two models shows up most clearly at the exact moment a store's AI usage is succeeding. Under Tidio's structure, a Lyro deployment that's working well, answering more conversations, engaging more shoppers, generates a bigger bill specifically because it's working, since the metered pricing charges per conversation handled. Under Arbyn's structure, a growing conversation count inside Starter's 150-a-month allotment costs nothing extra until the store actually needs to move to unlimited, and once on Agent, more usage costs the same flat 99 dollars whether it's 200 conversations or 5,000. The tool's incentive under each model is different by construction: one is paid more for volume, the other is not, which changes what each vendor is actually optimizing to deliver.

This incentive difference is worth stating plainly rather than treating as an abstract structural detail: a vendor billed per conversation has a direct financial interest in a store generating more billable conversations, which is not necessarily the same thing as a store's actual interest in resolving issues efficiently and moving on. A vendor billed flat has no such conflict, since the fee doesn't change either way, meaning the incentive gap between a per-conversation model and a flat one is not just a pricing curiosity but a genuine difference in what each business model rewards the vendor for optimizing.

The tier cliff comparison is worth stating plainly rather than softening. Tidio store owners who outgrow the Growth plan's Lyro allotment face a genuinely difficult choice: stack a separately metered add-on and watch the combined bill climb unpredictably, or absorb a roughly 12 times jump to the Plus tier. Arbyn has no equivalent cliff between its two plans; a store crossing from comfortably within Starter's 150 conversations to needing more moves to a single flat number, 99 dollars, regardless of how far past 150 the actual volume runs.

Channels and Feature Coverage, Beyond Just Pricing

Tidio's broader platform covers live chat widgets, email marketing automation, and a visual Flows builder for scripted automation sequences beyond AI-handled conversations, alongside integrations across a wide range of ecommerce and marketing tools built up over its years operating as a general-purpose customer engagement platform. This breadth is a genuine advantage for a store that wants one tool covering chat, email campaigns, and workflow automation together, rather than assembling those from separate vendors.

Arbyn's scope is narrower and more specifically Shopify-native by design: email and live chat conversations, both handled by the same agent that also does the AI work, with direct Shopify catalog and order data access built in rather than connected through a general-purpose integration layer. Arbyn does not currently offer the marketing-automation Flows builder or broader email campaign tooling Tidio provides, which matters for a store that specifically wants a single tool spanning both support and outbound marketing automation. For a store whose primary need is support and sales conversations handled well, rather than a full marketing automation suite, the narrower scope is not a missing feature so much as a different tool category, purpose-built for the support-and-sales job specifically rather than adapted to cover it as one module among several.

Neither Tidio nor Arbyn currently supports Instagram DM or Facebook Messenger as live, AI-handled channels at the time of this comparison, worth noting since both categories sometimes get marketed with broader channel claims than what's actually shipping. A store comparing either tool on channel breadth should verify directly, by messaging the channel in question as a real customer would, rather than assuming a feature list is current.

Setup and Time to Value

Tidio's setup, given its broader platform scope, typically involves more initial configuration across chat widget placement, Flows automation rules, and Lyro's knowledge base training, reflecting its position as a multi-purpose platform rather than a single-focus tool. Stores already using Tidio for live chat before adding Lyro report a smoother incremental rollout than a from-scratch setup, since the base chat infrastructure is already in place before AI gets layered on.

Arbyn's setup is narrower by design and correspondingly faster: connecting to a Shopify store's catalog and order data, running the 50-conversation calibration window to let the agent learn tone and common questions, then switching live. A store's actual time to value depends more on how quickly its own knowledge base and common-question documentation is in shape than on either platform's technical setup process specifically, a pattern that holds across most AI support tools regardless of vendor.

The Real Math at Different Volumes

Running specific volume figures through both pricing structures makes the comparison concrete rather than abstract. At 100 monthly AI conversations, a store on Tidio is likely still within or just past the free lifetime Lyro allowance, paying close to the 39-dollar entry tier on top of whatever base Customer Service plan tier that store needs, landing somewhere in the 60 to 100 dollar range all-in. The same store on Arbyn Starter pays nothing, since 100 conversations sits comfortably under the 150-conversation free monthly allotment.

At 300 monthly conversations, past Starter's cap, a store needs Arbyn Agent's flat 99 dollars. On Tidio, 300 Lyro conversations a month typically requires a mid-tier Lyro package running somewhere in the 100 to 150 dollar range, on top of the Growth plan's 59 dollars, landing the realistic Tidio total in the 160 to 210 dollar range, already above Arbyn Agent's flat rate at this volume.

At 750 monthly conversations, a volume that pushes many stores toward or past Tidio's Growth-to-Plus tier cliff depending on exact configuration, the gap widens further. A store forced into the 749-dollar Plus tier to accommodate that volume is paying roughly 7.5 times what Arbyn Agent costs for the same conversation count, or a store stacking a larger Lyro package onto Growth to avoid the Plus jump is still likely paying more than 200 dollars a month in combined base-plus-Lyro costs, well above Arbyn's flat 99.

None of these figures are official published rate cards from Tidio for every exact volume, since Lyro's tiered pricing beyond the entry level is not fully transparent on public pricing pages, which is itself worth noting as a comparison point: a store should request Tidio's exact Lyro pricing at its specific volume directly rather than estimate from published entry-tier numbers alone, since the tiers between 50 and the Plus-tier cliff are not uniformly documented in public materials.

Support and Sales in One Agent vs Two Separate Tools

A structural difference beyond pricing is worth naming directly: Tidio's Lyro is built primarily as a support and FAQ-handling AI agent, with sales-oriented features like proactive triggers and product recommendations available but positioned as a secondary capability layered onto a support-first tool. Arbyn is built from the ground up to handle both jobs inside the same conversation, with revenue attribution tracking which conversations produce sales by default rather than as an add-on reporting feature. For a store specifically interested in the support conversation also being a sales moment, not just a resolved ticket, this design difference matters more than either tool's raw pricing, since a support-first architecture with sales features bolted on behaves differently in practice than one built to treat every conversation as a potential sale from the start.

This is not a claim that Lyro cannot recommend products or that Tidio's broader platform lacks sales tooling entirely, since Tidio's Flows and broader marketing automation can support sales-oriented campaigns adjacent to the AI chat itself. It is a claim about what the AI agent specifically is optimized to do inside a single conversation, where Arbyn's narrower focus on the combined support-and-sales conversation is the core design premise rather than an added capability.

Where Tidio's Model Still Makes Sense

None of this makes Tidio the wrong choice in every case. A store running genuinely low AI conversation volume, comfortably under 50 a month, might never need to pay for Lyro at all beyond the one-time lifetime allowance, making Tidio's base Customer Service plan, without Lyro, a reasonable low-cost option for a store whose support volume hasn't reached the point where AI automation pays for itself. Tidio's broader platform, including live chat widgets, email marketing tools, and automation flows beyond just AI conversation handling, also has genuine feature depth that a store evaluating tools purely on AI conversation pricing might undervalue if AI handling isn't the only capability being compared.

The comparison sharpens specifically once a store's AI conversation volume grows past the free lifetime allowance and starts generating a real, recurring Lyro bill on top of the base plan. That is the point where the metered-add-on-plus-tier-cliff structure starts working against a growing store in a way a flat-rate model does not, and it's the volume range, roughly 150 to 5,000 monthly conversations, where most of the comparison above actually applies in practice.

What to Actually Check Before Switching Either Direction

A store currently on Tidio considering a switch, in either direction, should run its own numbers rather than accept either vendor's framing at face value. Pull the last 90 days of actual Lyro conversation volume and the corresponding Lyro line-item cost from the Tidio invoice, not just the base plan charge. Compare that real number against Arbyn Agent's flat 99 dollars, or against staying on Arbyn Starter if the volume comfortably sits under 150 a month. A store whose real Lyro bill already exceeds 99 dollars a month has a straightforward financial case for the flat-rate alternative. A store whose Lyro usage sits well under that, still within the free lifetime allowance or a modest paid tier, may not have an urgent reason to switch on cost grounds alone, even though the structural incentive difference described above still exists in the background regardless of current bill size.

Beyond the cost comparison, a store should also factor in migration effort honestly rather than assuming a switch is frictionless in either direction. Existing chat history, customer tags, and any Flows automation built inside Tidio do not transfer automatically to a different platform, which means a switch has a real setup cost even when the ongoing pricing case is clear. For a store deeply invested in Tidio's broader marketing automation tooling beyond just Lyro, that migration cost may reasonably offset some of the pricing advantage a flat-rate alternative offers, at least in the near term, which is worth weighing honestly rather than dismissing in favor of the pricing math alone.

The seasonal case is worth checking specifically too, since it's where the two models diverge most sharply. A store's November and December conversation volume typically runs several times higher than a normal month, driven by order status questions, gift-timing questions, and holiday return policy questions arriving all at once. On Tidio's metered Lyro structure, that spike bills at whatever the applicable per-conversation or tier rate is for that volume, potentially forcing an unplanned tier upgrade during the exact weeks a store has the least bandwidth to deal with a billing surprise. On Arbyn Agent's flat structure, the same volume spike costs the same 99 dollars it costs in a slow month, which removes the seasonal pricing risk from the planning equation entirely rather than requiring a separate calculation for peak season specifically. Any store running this Tidio vs Arbyn comparison seriously should model both a typical month and a peak month, not just current volume, before deciding.

Arbyn is built specifically for the store that has already run this comparison and found its own Lyro bill, or its own anticipated bill as conversation volume grows, exceeding what a flat 99 dollars would cost for the same, or more, volume. That crossover point arrives earlier than most stores expect once Lyro's per-conversation metering is actually totaled against a real month of usage rather than glanced at as a low-looking entry price.

What Neither Vendor Advertises Clearly

Both companies' public pricing pages undersell how much the comparison actually depends on a store's own volume pattern rather than a single headline number. Tidio's marketing understandably leads with the 39-dollar Lyro entry price, not the realistic 150-to-250-dollar all-in cost at a genuinely useful conversation volume. Arbyn's flat rate is simpler to state honestly precisely because there's no tiered structure to selectively quote from, which is itself a difference worth noting: a pricing page that can state its full cost structure in one sentence is disclosing something a metered, multi-tier structure cannot as easily do without a longer explanation or a sales conversation to get a real number. A store comparing Tidio vs Arbyn on pricing transparency alone, not just final cost, should notice which vendor's full pricing fits in a single sentence and which requires piecing together a base plan, an add-on tier, and a possible cliff before arriving at a real monthly number.

The Tidio vs Arbyn comparison, stripped down to its actual structural difference rather than either vendor's marketing framing, comes down to a single question worth asking directly: does this store want a bill that grows every time the AI succeeds at handling more conversations, or a bill that stays the same regardless. Tidio's Lyro answers that question one way, tied to conversation volume through its metered add-on structure. Arbyn answers it the other way, with two flat plans and a cap that simply moves a store from one to the other rather than metering every conversation in between. Neither answer is wrong in the abstract. The right one depends entirely on which side of that growing bill a specific store wants to be on as its own support and sales volume increases.

Summarize with AI

Written by

Odera Joseph
Founder

For seven years I have led customer success and technical support inside high-growth SaaS and e-commerce companies. Customer Support Lead at DripShop.live, a live-commerce SaaS. Technical Support Specialist at Replo (Y...

View full profile

One good post at a time. No fluff.