The "Light Agent" Illusion: Why Cheap Seats Cost You Double
It sounds like a bargain: "Unlimited free collaborators." But when your engineering team can't see the ticket history, "free" becomes very expensive.
You are calculating your budget. You have 10 full-time support agents. You also have 20 engineers and product managers who occasionally need to chime in on tickets.
The vendor's pricing page says:
"Full Agent: $80/month"
"Light Agent: Free (or $0)"
Perfect! You budget for 10 seats ($800/month) and assume the 20 engineers will use the free Light Agent seats.
Three months after implementation, your budget explodes to $2,400/month. Why? Because you discovered that Light Agents are functionally useless for actual work.
The "Read-Only" Trap
Vendors define "Collaboration" very differently than you do. To you, collaboration means "helping solve the ticket." To them, it often means "leaving a private note and nothing else."
Here is what typically happens when an engineer tries to use a Light Agent account:
- They cannot change the ticket status. If they fix a bug, they can't mark the ticket as "Solved" or even "Pending." They have to ping a Full Agent to do it for them.
- They cannot see private notes. Often, Light Agents are restricted from seeing sensitive internal discussions, meaning they lack context.
- They cannot be assigned tickets. You can't "assign" a bug report to an engineer. It sits in a queue they can't own.
The result? Friction. Your Full Agents become secretaries for the Light Agents, constantly updating statuses and relaying messages.
Eventually, the engineering manager demands: "Just give me a real license so I can do my job." And just like that, you are paying $80/month for someone who logs in once a week.
The "Occasional Agent" Day Pass
Some vendors (like Freshdesk) offer a different solution: "Day Passes." You pay a small fee (e.g., $2-5) for every day a casual user logs in.
This sounds fair, but it introduces Administrative Overhead.
- Who approves the day passes?
- What happens when an engineer logs in just to check one status update? Did that cost $5?
- If they log in 10 times a month, you've paid $50—almost the cost of a full seat, with none of the benefits.
The "Jira Service Management" Exception
One notable exception is Jira Service Management (JSM). Because Atlassian wants to sell Jira Software licenses to your engineers, they allow Jira Software users to be "Collaborators" on JSM tickets for free, with decent permissions (commenting, viewing). This is a strategic loss leader to lock you into the Atlassian ecosystem. If you are already a Jira shop, this "Light Agent" model actually works. If you aren't, it's a trap to get you to buy Jira.
Strategic Recommendation
When evaluating pricing, ignore the "Light Agent" column entirely.
Assume that 20-30% of your "collaborators" will eventually need full licenses.
If your workflow requires engineers to act on tickets (change status, reassign, edit fields), budget them as Full Agents from day one. If they truly only need to leave a comment once a month, consider using an integration (like Slack or Jira) to let them comment without ever logging into the helpdesk.
For more on how to structure your team's licenses without going broke, see our guide on Helpdesk Software Selection.