Tidio support budgeting: conversations, AI usage and actual coverage

Support volume has several meanings. A visitor may send many messages in one case; a simple product question may end quickly; an uncertain order issue may require several people. A Tidio budget needs the platform’s billing definitions and the team’s own useful-outcome definition without treating those units as interchangeable.

This fictional ecommerce team is deciding how much human support, Flows usage and Lyro assistance it needs. It wants to compare the complete cost of normal questions and exceptional work. It also needs an honest coverage plan for busy periods, when conversation volume and the proportion of difficult cases may change independently.

The pricing presentation reviewed for the main Tidio guide distinguished billable customer conversations, Lyro AI conversations and Flows usage. Confirm the current reset periods, included allowances, users and features for the selected configuration. Hypothetical amounts in the worked financial model are internal examples, not a Tidio price quotation.

Design the work around the actual completion event

1. Reconcile the billing unit with the case record

Write the current provider definition beside the internal support-case reference. Keep multiple messages, a reopened question and a separate new issue distinguishable in the operating report.

A dashboard count can look inconsistent with staffing because the platform and the team are counting different things.

2. Separate automation routes in the forecast

Estimate where human support, a predefined flow and AI assistance are actually proposed. Preserve overlap and handoff work when more than one route participates in a case.

Adding separate allowance figures can overstate useful capacity and omit the effort needed when automation escalates.

3. Model the difficult case mix

Create separate time assumptions for routine product questions and account-specific or uncertain issues. Investigate the reason behind a rising exception share rather than attributing every increase to growth.

An average conversation time can conceal a few issues that consume most available support coverage.

4. Include knowledge maintenance and review

Budget the time to approve answers, correct obsolete material and inspect selected outcomes. Treat an important policy change as an operating event with an owner.

An AI allowance can appear inexpensive when answer review and source maintenance are performed as invisible extra work.

5. Use an outcome measure that includes useful escalation

Define a resolved general question and an appropriate handoff separately. A correct escalation can be valuable even when it does not count as an automated resolution.

Optimizing one automation percentage can encourage an answer when the safer business action is to involve a person.

6. Compare eligible packages against the full routine

Check users, required functions and allowance boundaries in the actual quote. Compare quiet, expected and peak periods using the same quality standard and coverage plan.

A low starting amount can purchase a different support arrangement from the one the team actually needs.

Build a complete cost model with a consistent unit

The following comparison is a fictional purchasing exercise for an ecommerce support team planning human, automated-flow and AI-assisted conversation coverage. Arrangement A and arrangement B are hypothetical configurations, not named Tidio plans or current vendor prices. Their purpose is to expose a fixed-cost versus workload tradeoff. Replace every amount with the provider quote and the team’s observed work before making a purchasing decision.

Assume 400 attempted completed useful support outcomes in one review period. Arrangement A has $160 of allocated fixed cost and $1.20 of variable cost per attempt. Arrangement B has $340 of fixed cost and $0.60 per attempt. Both also require an assumed 8 hours of operating work at $45 per hour. That shared labor amount is $360. Keeping it visible prevents a subscription comparison from being mistaken for the complete cost of running the process.

Cost component	Arrangement A	Arrangement B
Allocated fixed amount	$160	$340
Attempted workload	400	400
Variable amount per attempt	$1.20	$0.60
Variable subtotal	$480.00	$240.00
Assumed operating labor	$360	$360
Scoped total	$1000.00	$940.00

Under these inputs, the lower scoped total is B. The arithmetic does not establish functional equivalence. If one arrangement cannot produce an accepted completed useful support outcome, its lower price does not purchase the same outcome. First establish that the relevant permissions, product functions and receiving workflow satisfy the requirement. Then compare the cost of the arrangements that remain eligible.

Calculate the crossover instead of choosing from one sample month

Ignoring the shared labor that is identical in this example, set the two totals equal: 160 + 1.20 × volume = 340 + 0.60 × volume. The difference in fixed amounts is $180; the variable difference is $0.60 per attempt. The crossover is therefore 300 attempts. Below that level A has the lower modeled platform allocation; above it B does, assuming the same definitions and the same quality of output.

For Tidio, inspect the selected customer-conversation, Lyro and Flows definitions. Several messages may belong to one support problem, and one problem can use automation followed by a person. Keep the purchased units distinct from the store’s resolved-or-escalated case measure. The 400 attempted completed useful support outcomes in this example are an internal operating measure. Translate them into the confirmed purchased units before replacing the hypothetical costs. A minimum commitment, annual term or tier boundary may require a different model; retain the current quote with its actual scope.

Divide by accepted output as well as attempted work

Suppose 320 of the 400 attempts meet the agreed completion criteria. This invented usable-output share is 80%; it is not a Tidio success rate. Arrangement A would cost $3.12 per approved completed useful support outcome, while B would cost $2.94. Dividing by all attempts instead would give $2.50 and $2.35. Both calculations are arithmetically valid, but only the first answers the question about accepted operating output.

Explain what happened to the remaining 80 cases. Some may be inappropriate inputs; others may need a correction or an unavailable decision. Do not describe them all as software failures. Equally, do not erase their inspection cost from the comparison. A useful review separates input quality, the configuration’s behavior and the receiving team’s ability to continue the work. Each requires a different response.

Include switching effort and the cost of carrying an exception

A new arrangement may require preparation, record cleanup, template work or training. If a controlled estimate adds twelve hours at the same $45 rate, that is $540 of transition labor. State whether it is a one-time investment and over what period you intend to recover it. Do not treat it as a monthly fee indefinitely or disappear it from the decision merely because an existing employee performs the work.

Now vary the exception burden. Adding four hours of review increases either arrangement by $180. That can be more consequential than a small difference in the quoted fee. The practical question is which input or handoff creates those hours and whether the proposed configuration removes them. A larger allowance that leaves the repair process untouched may increase throughput without making the work more economical.

For an ecommerce support team planning human, automated-flow and AI-assisted conversation coverage, compare quiet, expected and spike periods using the same completed useful support outcome definition. The modeled 400 attempts are only one workload. A changed package boundary or approval burden can alter the comparison, so retain a range where the work is uncertain. Link the commitment to the actual requirement and review point rather than treating the spreadsheet’s decimal places as evidence that future demand is known.

Test the six assumptions that could change this budget

The following exercises connect the financial model to the actual Tidio workflow. Keep input definitions, the selected configuration and the person responsible for each decision beside the observed result. A provider demonstration can establish an available route; it does not replace the team’s own acceptance of the business meaning or the ongoing work required to maintain it.

Exercise 1: Reconcile the billing unit with the case record

Trace a short question, a multi-message case and a returning visitor through the proposed measurement.

The team can explain the relationship without forcing all activity into one misleading total. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 2: Separate automation routes in the forecast

Use a controlled case that begins with automated help and requires a person to approve the final decision.

Both the purchased usage and the human continuation appear in the estimate. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 3: Model the difficult case mix

Hold the visitor count constant and increase the proportion of cases needing a supervisor.

The staffing and source-improvement decisions respond to the changed work rather than just the total count. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 4: Include knowledge maintenance and review

Estimate the effort for a normal publishing month and for a month with a material product-policy update.

The cost model includes the work required to keep the support information reliable. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 5: Use an outcome measure that includes useful escalation

Classify a correct answer, an uncertain answer and an account-specific request using the agreed criteria.

The report recognizes correct support behavior rather than rewarding completion language alone. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Exercise 6: Compare eligible packages against the full routine

Price the same controlled case mix under the eligible configurations and include extra human work.

The selected arrangement explains its capacity, its limitations and the complete scoped cost. Record the input reference, the observed result and the responsible next operator. If the result depends on a manual convention, retain that convention with this exercise so the next person can repeat it.

Keep an operating record someone else can continue

For an ecommerce support team planning human, automated-flow and AI-assisted conversation coverage, keep one reference for each completed useful support outcome. Use that reference across the input, the accepted result and any exception record. It allows a reviewer to follow the work without relying on a customer’s name, a screenshot title or the memory of the person who first handled it. Where the destination system assigns its own identifier, retain both references and explain the relationship.

Record field	What to put in it	Why it belongs in this workflow
Input reference	The original request, item or approved brief	Connects the result to the actual starting point
Configuration version	The relevant rule, template or account arrangement	Makes an observed result reproducible
Completion evidence	What establishes an accepted completed useful support outcome	Keeps the outcome definition stable
Exception reason	The missing fact, conflict or failed requirement	Directs repair toward the cause
Current owner	The person or queue that accepted the next action	Makes continuation visible
Review point	When the case or configuration needs another decision	Prevents unfinished work from disappearing

For one completed useful support outcome, write what the evidence establishes before proposing an explanation. In an ecommerce support team planning human, automated-flow and AI-assisted conversation coverage, the note needs the starting reference and the accepted next responsibility as well as a visible result. Keep the supporting source small enough to inspect. A large screenshot collection should not replace an explicit decision about this particular outcome.

Before increasing the workload for an ecommerce support team planning human, automated-flow and AI-assisted conversation coverage, review the held completed useful support outcomes by their actual cause. Use the six exercises to locate an input, configuration or responsibility gap, then repeat the affected route after its repair. The first ordinary completed useful support outcome does not establish that a different unresolved case has become acceptable.

Make the next decision from the evidence

Keep a small set of support cases with the financial model. They define what the team is trying to purchase and prevent a renewal discussion from becoming a comparison of incompatible allowance totals. Revisit the source material and escalation route when the difficult-case share changes.

Choose additional capacity when the appropriate support work justifies it. Choose better knowledge, clearer product information or more reliable coverage when those are the constraints. Tidio’s pricing units are inputs to that decision; they do not replace a business definition of useful support.

Keep a short decision note for this specific Tidio use case: the work approved, the conditions still outstanding, the owner of each outstanding decision and the next review date. A conditional approval is useful when its boundaries are visible. It becomes misleading when an unresolved requirement is presented as an observed capability.