Calculate the total cost of a help desk

The advertised monthly price is not the cost of running a help desk. A business pays for the plan that contains its actual workflow, the people who need access, the conversations it handles and the work required to make the system dependable. A cheaper entry plan may become the dearer choice when a required report, SLA or integration forces an upgrade.

This guide is a calculation method. The pricing overview explains current plan shapes; the provider's quote and terms decide the final number. Do not present a single projected amount as certain when future volume, exchange rates or staffing can change.

The formulas behind the result

Monthly base = max(replying users, minimum billed seats) × selected seat price + platform fee. Add monthly integrations and both usage charges. Each usage charge is ceil(max(0, monthly usage − monthly allowance) ÷ block size) × block price. “Ceil” means round up to the next whole purchased block. Annual software cost is the sum of the twelve separately calculated months, not the annual average usage put through one monthly allowance.

Year-one vendor cash before tax = annual software + one-off vendor fees. Tax cash uses the rate you enter on those vendor amounts. Internal effort value = (setup + training + migration + exit provision hours) × internal hourly value. Economic cost adds that effort value and any tax you choose to treat as unrecoverable. This is a comparison convention, not accounting or tax advice. An exit provision is a planning allowance: remove it from year-one hours if it belongs in a later budget.

Monthly line items are rounded to two decimals in the input currency before summing. Converted results multiply by your explicitly entered exchange rate and are displayed to two decimals; small displayed-line rounding differences can occur. Bank fees, different exchange rates on different invoices and price changes are not inferred. Keep a native-currency copy of each candidate before comparing converted totals.

Worked example: two users and one busy month

Entirely illustrative; these are not any product's prices or results. Two users cost £20 each monthly equivalent on an annual base term; integrations cost £10 monthly. The fictional allowance is 300 tickets monthly with £0.40 per additional ticket, plus 100 AI sessions with £0.50 per additional session. Eleven months contain 200 tickets and 150 AI sessions; month eleven contains 800 tickets and 350 sessions. One-off fees are £150 and four internal tasks each take ten hours at £25 per hour.

The recurring software monthly equivalent is £100, but that does not mean every invoice is £100. The peak is five times a normal software month. Year two repeats £1,200 software and £240 assumed tax cash, with no one-off fees and no annual internal hours entered: £1,440 cash. If you add ongoing administration, a renewal rise or another hire, replace the inputs; this is not a prediction of the provider's renewal bill.

Save the assumptions before choosing

Download the printable cost worksheet. It records the plan, source, billing term, monthly units and what remains unknown. A blank or unpriced quote-only component is not zero: mark the comparison incomplete until it can be priced. Record mandatory add-ons separately, and do not use this tool to smooth annual AI pools or automatically changing ticket tiers into monthly allowances.

A useful conclusion from this example is conditional: a seasonal usage plan needs peak cash headroom even when the annual total looks affordable. The charging-model comparison isolates that boundary, while the AI budget ledger explains why paid AI units and accepted customer outcomes are different denominators.

Use one twelve-month equation

Year-one total = subscription + seat charges + volume/AI overages + necessary add-ons + implementation and training + integration costs + tax + expected support or migration costs. Separate cash paid to the vendor from internal staff time. The latter may not appear on an invoice, but it still affects whether a small team can make the change successfully.

For each candidate, list the lowest plan that meets every must-have, not the cheapest plan on the pricing page. Count all paid agents and supervisors who need to reply, not just the people currently on shift. Ask how occasional collaborators are licensed. If billing is in dollars, retain the provider's currency and add a stated exchange-rate assumption; do not quietly convert a displayed dollar price into pounds.

Model three operating cases

Use your own ticket-volume forecast for the busy case. A ticket-volume plan may look economical in a quiet month but change quickly during a launch. A per-agent plan may have a stable bill through a surge yet rise at the next hiring point. Neither model is inherently cheaper; their risk drivers differ.

Find the hidden triggers

Read the feature grid line by line. Does the required knowledge base, audit log, custom report, social channel or role restriction need a higher tier? Does a connector charge separately per account or transaction? Is AI sold per agent, session, credit or successful resolution? What happens when an allowance is exceeded? A support team can accidentally compare a complete plan from one vendor with an incomplete entry plan from another.

Check invoicing, VAT, annual payment, renewal notice, minimum seats, contract term and price-change language. Record what happens if you reduce users mid-term. Ask whether historic data export, API access and cancellation assistance are included; a difficult exit is a real cost even if you never intend to leave.

Price the implementation honestly

Allow time to clean and import active cases, connect the support address, set ownership and permissions, write macros, test customer replies and train the team. The implementation checklist identifies the tasks. A fast launch that misroutes messages can cost more in recovery and customer trust than a careful pilot.

Run a trial with the exact use cases you will purchase. If a provider says a capability is available, note the plan, any add-on and the evidence you saw. For example, compare HelpDesk's focused subscription, Freshdesk's agent-based tiers, Zendesk's ticketing versus Suite paths and Gorgias's billable-ticket rules using the same team and workload assumptions.

Make the comparison usable

Put each candidate in one sheet with the same assumptions, then show year-one cash, year-one internal effort and the plausible year-two run rate. Keep uncertain inputs as ranges. A decision maker should be able to change agent count, ticket volume or AI adoption and see which vendor's bill moves. That is more honest than a ranking based on a headline monthly figure.

Sources

• Gorgias: billable events and billing
• Freshdesk pricing
• Zendesk UK pricing
• HelpDesk pricing

Cost scenarios and product-fit guidance are Support Sorted's editorial judgement. Prices and plan terms should be reconfirmed with the provider before purchase.