Definition
Helpdesk pricing models directly affect MSP profitability. Per-ticket pricing punishes the very efficiency MSPs are paid to deliver — every additional ticket the technician closes is more cost without more revenue, eroding margin. Per-endpoint pricing scales with fleet size whether or not those endpoints generate tickets, similarly disconnecting cost from value delivered. Both models squeeze MSP margins as the business grows, and both pressure technicians to under-log work to keep ticket counts down — destroying the audit trail that protects the MSP and its clients when a breach does occur.
Per-named-agent unlimited-ticket pricing aligns the helpdesk economic model with how MSPs typically charge their clients. A fixed monthly fee per technician seat lets the MSP be efficient, take on additional clients without per-ticket cost increase, and predict helpdesk costs accurately.
Lavawall® prices its smart helpdesk at US$59 per named agent per month with unlimited tickets. The agent seat is named (assigned to a specific person, not floated) so the security and audit posture is clear; the unlimited-tickets model removes the friction that per-ticket pricing introduces.
Core components
- Named-agent licensing. Each helpdesk seat is assigned to a specific person rather than floated. Important for audit, accountability, and security.
- Unlimited tickets per agent. No per-ticket fee, no quota, no surcharge for ticket volume.
- Fixed monthly per-agent fee. Predictable cost that scales with technician headcount, not workload.
- Multi-tenant scope. MSP per-named-agent licensing typically allows the agent to handle tickets across all the MSP's client tenants from a single seat.
Why it matters
For MSPs, the per-named-agent model is the procurement standard because it matches how MSPs sell. An MSP that charges its client a fixed monthly fee for unlimited support tickets cannot economically pay its helpdesk vendor per ticket — every additional ticket is pure cost without revenue.
Per-ticket pricing also distorts technician behaviour: technicians become reluctant to log small interactions to keep ticket counts down, which destroys the audit trail and compliance evidence the MSP relies on.
Per-named-agent pricing isn't universal yet. Zendesk, Freshdesk, ServiceNow, and many enterprise ticketing tools price per agent but with tier-based feature gates that effectively penalise scale. MSP-tuned helpdesks (Lavawall®, HaloPSA, ConnectWise Manage) increasingly price more cleanly per named agent with unlimited tickets at the agent's normal feature tier.
How Lavawall® helps with Per-named-agent helpdesk pricing
Lavawall® prices its smart helpdesk at US$59 per named agent per month with unlimited tickets across all the MSP's client tenants. No per-ticket fee, no per-endpoint surcharge, no tier-based feature gating that punishes scale.
Each named agent has full access to AI knowledge-base suggestions, KB-gap detection, AI task breakdown, tabbed multi-ticket workflow, kanban / list views, device-GUID-linked tickets, and the rest of the smart helpdesk feature set at the named-agent price.
Because the helpdesk is bundled with the rest of Lavawall®, the agent has full RMM, GRC, breach-detection, application-control, and remote-support context one click away from any ticket without separate console swivel.
Frequently asked
- What if my technicians share a seat?
- Lavawall® helpdesk seats are named — assigned to a specific person. Sharing a named seat is a security and audit problem; the per-named-agent model deliberately discourages it.
- Are there feature tiers that gate at higher prices?
- Lavawall® helpdesk pricing is flat per named agent. The full feature set (AI KB, task breakdown, tabbed workflow, device context) is available at the named-agent price.
- What about my existing Zendesk or HubSpot tickets and KB?
- Lavawall® has both Zendesk and HubSpot importers that bring tickets, macros, and KB articles into the new helpdesk so the migration doesn't lose history.