Light agent seats: which help desk actions trigger a full license

Reading and noting rarely need a paid seat; answering the customer usually does.

Replying to a customer is the action that puts an occasional helper on a paid seat. Reading tickets does not. Neither does leaving an internal note. A light agent is the reduced role built around that line: an internal collaborator who can view tickets and comment privately but cannot answer the customer. Zoho Desk's plan comparison, as summarized in a 2026 pricing guide, names supervisors, engineers and stakeholders as the typical users, and it leaves the role off the Free plan entirely.

Zendesk bills full seats at $55 per agent a month on Suite Team and $115 on Suite Professional, on annual billing. That rate is built for people who work the queue all day, not for an engineer who weighs in on a handful of tickets.

Ticket status is softer than the role descriptions suggest. One organization's internal Zendesk training let light agents solve, pend or hold tickets through admin-built macros, while public comments, chats and calls stayed off limits. Before approving a seat request, ask your admin which status macros already exist, since one well-built macro can keep a helper below the paid wall.

The permission matrix that follows is compiled from published vendor documentation and guides, not from an in-house test across help desks, and it starts on the free side of that wall.

What can an occasional helper do without a paid help desk seat?

Reading tickets, being copied on them and adding private internal notes cost nothing in Zendesk, as long as the helper is set up as a light agent within the plan cap.

Before anyone asks for a seat, check three things in order:

1. Does the person only need to read tickets and comment privately?
2. Can their ticket access be limited to their organization, group or brand?
3. Is the account still under its plan's light agent cap?

Zendesk Suite Enterprise includes up to 1,000 light agents and Enterprise Plus up to 5,000, according to a getmacha.com guide whose permissions were checked against Zendesk's own documentation in September 2026. The same guide puts Suite Growth at up to 50 and Suite Professional at up to 100, while Suite Team gets light agents only as an add-on and Support-only plans need the Collaboration add-on. The allowance does not grow with the number of full seats you buy.

A light agent is a staff role that can see and discuss tickets internally but cannot work them for the customer. In practice, that covers most of what an engineer, finance lead or lawyer does on a ticket. Three yeses on the checks above put the helper in this role.

The common assumption is that a light agent is a read-only login. The documented role is wider than that, and approval rights sit on the free side:

Visibility is the second lever. A November 2025 video guide to the role explains that light agents can be copied on tickets and usually see only tickets within their groups, with broader access depending on how the plan is configured. In Admin Center, non-Enterprise plans let an admin choose the helper's organization, their groups or all tickets, while Enterprise replaces the all-tickets option with choices such as their groups plus all public groups, or everything within their brand membership.

One quirk deserves a warning. When a light agent is the requester on a ticket outside their group or brand, their private comment is converted to public. A note meant for colleagues can then reach the customer.

Across 4 published descriptions of the role, the core never changes: read access and private comments stay off the paid seat count. The paid line sits further out than many admins assume.

I would add one honest caveat about the word free. Every light agent is still an account someone must add, scope and remove as roles change, so the cost moves from the invoice to the admin's calendar. For teams with many occasional helpers, that trade still favors the light role.

Reviews at Zazachat are written and edited by our editorial team, led by Daniel Calloway, and the standards behind that work are published in our editorial and disclosure policy. The table above is compiled from cited role documentation rather than from a Zazachat test set. If you are still shortlisting platforms, our rankings of help desk software with live chat cover the wider buying decision. When nobody can say which row of that table a helper needs, I would start them as a light agent and change the role only when a real ticket calls for a paid action.

Which single action turns an occasional helper into a billed seat?

In Zendesk, two actions always cost a full seat: replying publicly to a customer and being assigned a ticket. Editing ticket fields, serving chats or calls, and admin roles follow.

A September 2026 affiliate pricing video says Gorgias charges by ticket volume rather than per agent, so not every vendor bills those actions by the seat. Zendesk's documented role rules, as checked in September 2026, reserve the following actions for a full agent, and none of them is available to a light agent at any plan level:

Read the first two rows as the real price tag. A helper who must answer the customer or own the ticket is doing support work, and the vendor bills support work by the seat. Most other rows are variations on those two: chats, calls and survey replies are customer conversations in another channel, while status and field edits are what an owner does. The remainder are admin powers no occasional helper needs.

Consultants who configure the role warn that the published light agent limits do not apply to legacy plans or add-ons, so older accounts should confirm their own allowance. They add a sharper upgrade signal. A light agent who keeps drafting replies for colleagues to paste is already doing paid work through a proxy, and the cleaner fix is a seat.

Some triggers hide in other products. A 2022 breakdown of Zendesk roles listed Explore admin and editor, Talk agent and team lead, and Chat agent roles as counting against Support seats, while Explore and Guide viewers did not. It also warned that a light agent granted Explore admin permission needed a Support seat.

Voice shows how far documentation and selling can drift apart. In a January 2024 r/Zendesk thread, an admin implementing Zendesk Professional reported that the documentation said light agents could not use Zendesk Talk, while their account manager said yes. All 5 commenters either said light agents could not use Talk natively or recommended a two-system setup instead. One wrote, "I'd go with the documentation which has a firm 'no'." Another explained that Talk access needed a different Support role.

My advice from that exchange is blunt. Treat a verbal yes on seat entitlements as a no until it appears in the order form.

Live chat follows the same logic. A helper who serves chat conversations is a full agent, so the per-seat prices in our live chat software rankings apply to every person who answers a website visitor. For a phone-heavy team, the seat count is set by who answers calls, not by who works tickets.

How do you keep occasional helpers off paid seats without breaking the rules?

Audit by activity, not logins: move anyone who only writes internal notes to a light role, and rotate full seats for helpers who reply occasionally.

Run the review in this order:

1. Export the team member list and sort it by last login, flagging anyone idle for weeks or months.
2. For active users, check what they post. Anyone who writes only internal comments is a downgrade candidate.
3. Reassign their open tickets, then change the role to light agent.
4. Give a helper who must reply a full seat for that task, then unassign it when the task ends.
5. Repeat the review every quarter rather than the month before renewal.

Step two is where most audits stall. Last login is easy to read in the admin panel, but admins who have tried this point out that it is far harder to see who posts only internal comments. They argue that tickets touched and Help Center edits say more about real activity than logins do. A login-only review misses the person who visits daily and never replies.

Step four is the compliant answer to a tempting shortcut. In a September 2026 r/Zendesk thread on managing seats, a startup admin described swapping occasional helpers between light agent and agent or admin seats as "fairly chaotic" and asked about a shared login instead. A commenter replied, "Sharing of licences is against the terms of service but you can assign and unassign licences at will." Seat pressure is not only a startup problem, either: another commenter said their telecom employer's about 130 seats were "always on the verge of having none free."

Rotation is clumsy. It is also allowed.

The leak is large enough to justify the effort. One license management vendor says its data shows 45% of Zendesk licenses go unused, and it warns that cutting seats at renewal can cost negotiated discounts. That argues for reclaiming seats mid-contract, while nothing is being negotiated.

Buyers often ask about a day pass for the helper who replies twice a month. None of the vendor documentation cited here describes one. Temporary assignment of a full seat is the closest legitimate equivalent.

Pricing structure changes the math as well. A July 2026 Zoho Desk pricing breakdown put light agents at a $6 per agent a month add-on on Standard and Professional, against full seats of $14 and $23 on annual billing, while Enterprise at $40 includes 50 free light agent licenses. Its worked example found that a 10-agent team with 5 light agents pays about $3,120 a year on Professional, against $4,800 a year on Enterprise. At the other extreme, one flat-priced help desk described in 2022 offered no reduced-cost seat at all, so every person on the account paid for the full feature set.

For a handful of helpers, the add-on beats the tier upgrade. A flat model charges full price for exactly the people this article is about. I would price both paths before assuming a bigger plan's allowance is a saving, and small teams weighing those trade-offs can compare options in our live chat picks for small businesses.

A third model is arriving on top of both. Zendesk's outcome-based pricing was described at an August 2026 industry panel as paying for resolutions rather than seats, so the question of who may press reply is starting to share the invoice with how many tickets actually close.

Will the reply rule still decide your help desk bill next year?

Yes for seats, less so for the total. Public replies and ticket ownership will keep defining paid seats, while AI agent meters claim a growing share of the invoice.

A May 2026 analysis of SaaS renewals on Nate's Substack found that ServiceNow, Workday, Zendesk, HubSpot and Atlassian had each added an agent meter under their own name. Microsoft went further, stacking a separate $15-per-user agent governance license on top of its $30 Copilot seat. "The seat is not dead. It is being wrapped in a meter for delegated work," the author concluded.

I expect the reply line to matter more as those meters arrive. Not less. Seats will price who is allowed to talk to customers, and meters will price the work that never needed a person. A helper who reads, notes and approves belongs on neither line. Before the next renewal, list everyone who actually replied to a customer during the term, buy full seats for that list alone, and ask the vendor in writing what each automated resolution will cost on top.