Helpdesk Seat Price
The published subscription charge for one paid support-user seat, before usage, add-ons, implementation, integration, and internal administration costs.
Base annual seat cost = paid seats × monthly list price × 12; evaluated cost = base seats + required add-ons + usage + implementation + internal operating costHelpdesk seat price is the cleanest number on a pricing page and the easiest one to misuse. It usually means one named or concurrent user for one month at a specific plan tier and billing term. Plans with the same per-seat shape can include radically different channels, routing, analytics, knowledge, security, AI, and usage allowances, so the number is only a list-price reference — not a value comparison.
Normalize every quote to the same currency, billing term, seat definition, minimum commitment, and required feature set. Then add the charges that do not scale by seat: message or ticket overages, telephony, storage, sandboxes, premium support, AI outcomes, implementation, integrations, and the internal administrator time needed to keep the system useful. Read the resulting number alongside total cost of ownership.
What it hides: vendors can move formerly standard capabilities into higher tiers or add-ons without changing the entry price. Promotional discounts, annual prepayment, enterprise negotiation, and free collaborator seats also make public figures diverge from real invoices. Treat any published comparison as a dated snapshot, retain the plan URL and capture date, and rebuild the model before a renewal decision.