Helpdesk at $50-$150 per agent
Tickets, queues, SLAs, escalation. The center of the support stack.
Stack pattern
If your support team is paying per agent for ticketing, per agent for chat, per agent for the knowledge base, and per agent for the AI macros on top of all of it, you're paying for four separately-billed seats per actual person. This is the consolidation pattern.
What this stack usually looks like
Like the per-seat CRM stack, this one accretes purchase by purchase. Each new tool was justified at the time. The aggregate is the cost most operators don't see until they audit it.
Tickets, queues, SLAs, escalation. The center of the support stack.
Live chat, async messaging, customer-facing routing. Often a separate product with its own integration to ticketing.
Public docs, internal macros, AI-generated articles. Frequently a third tool that the helpdesk reads from but doesn't own.
Automated reply drafting, classification, sentiment scoring. The newest line item, often the most expensive per agent.
What consolidation changes
Consolidating support is not just per-agent math. It changes the experience customers receive because the agent has the full context of the relationship in one surface, not pieced together across four.
All four read and write to the same customer record. Agents stop tab-switching across four tools to answer one question.
Helpdesk shares the same identity, audit, and event layer as CRM, ERP, and drive. A ticket can reference an account, an invoice, or a permissioned file without integration plumbing.
Drafting, classification, knowledge surfacing are part of the helpdesk. No per-agent AI surcharge layered on top.
Get a compatibility check
A free written assessment of what would replace what, what migration looks like, and what the math actually changes. Two business days for the response.