What Is a Light Agent in Zendesk? Permissions, Seat Limits and Pricing (2026)

A Zendesk light agent is a limited internal role that can read tickets and add private comments but can't be assigned tickets or reply to customers, and it doesn't use a paid agent seat: Suite Growth includes up to 50 light agents, Suite Professional up to 100, Suite Enterprise up to 1,000 and Suite Enterprise Plus up to 5,000. It's the role for the engineer, finance lead or lawyer who needs to weigh in on a handful of tickets a month without costing you a full seat. The permissions below are checked against Zendesk's own documentation, updated September 2026.

What is a light agent in Zendesk?

A light agent is a restricted internal role in Zendesk built for collaboration, not for working a queue. Think of them as a subject-matter expert you can pull into a ticket: they can see the conversation and add internal notes that only your team can read, but they never reply to the customer and they never own the ticket.

The mental model that makes the rest of this click: a light agent is a read-and-advise role. They consume tickets and contribute behind the scenes. Everything they're allowed to do supports that, and everything they're blocked from doing is reserved for full agents who actually handle and resolve customer requests.

What can a light agent do?

Within the tickets they're allowed to see, a light agent can:

• View tickets, scoped by an admin setting in Admin Center (People > Team > Roles > Light agent): tickets requested by end users in their organization, tickets within their groups, or all tickets on non-Enterprise plans. Enterprise plans swap "all tickets" for finer options such as their groups plus all public groups, or everything within their brand membership.
• Add private (internal) comments. This is the core of the role. Light agents post internal notes that are visible to your team but never sent to the customer.
• Create tickets, including on behalf of existing end users. A light agent's first comment is private by default; the end user won't see the ticket until an agent adds a public comment.
• Be CC'd on a ticket or added as a follower so they get looped in and notified. End users can't see a light agent who's been CC'd, so adding one never exposes an internal name to the customer.
• Add and download attachments, so they can drop a screenshot, log file or spec onto a ticket.
• Take part in side conversations: create, reply to, close and reopen email-based side conversations, which is often the cleanest way to bring an expert into a single thread. (The exception: light agents can't create, send or be assigned side conversation child tickets.)
• Act as a designated approver in approval workflows, and apply existing macros (a macro that does something the role isn't allowed to do won't work).
• View user profiles and Help Center content, and add or edit knowledge base articles where agents have permission (see Guide management permissions). On Professional and Enterprise, an admin can let light agents view shared Explore dashboards or go further and manage reports and dashboards.

What can't a light agent do?

The restrictions are what keep the role cheap and safe:

• Can't be assigned tickets. A light agent can never be the ticket's owner or sit in the assignee field. Resolution stays with full agents.
• Can't reply publicly to customers. Every comment they make is internal. There's no path for a light agent to email the requester.
• Can't change the status or edit ticket properties (priority, type, group, custom fields) unless they are the requester of that ticket. They classify nothing on tickets they're merely advising on.
• Can't initiate @mentions. This one trips people up. Zendesk confirms "light agents and contributors can't use @mentions." The reverse is less of a hard wall than people assume: an @mention from a full agent adds the mentioned person as a CC or follower, and light agents can be CC'd, so a full agent can still loop a light agent in that way. The most reliable methods are to CC them directly or use a side conversation. Light agents also can't CC anyone other than themselves.
• Can't create or edit business rules (no creating macros, triggers or automations; on Enterprise they can't even view triggers and automations) and can't create new end users or edit user profiles.
• Can't serve chat or messaging conversations, answer calls, or respond to CSAT surveys, or otherwise act in a customer-facing capacity.

If you need someone to do those things, they need a full agent seat, not a light agent.

Why does the light agent role exist?

The light agent exists for one reason: cost. Full Zendesk agent seats are billed per agent, per month (Suite Team is $55 and Suite Professional $115 per agent a month on annual billing), and they're priced for people who live in the help desk all day. Most of the experts you want to consult (an engineer, an account manager, a finance lead) aren't doing support work. They just need to read a ticket occasionally and leave a note.

Light agents let you involve as much of the company as you want in support without buying everyone a full seat. The payoff is real: experts answer in the system, with full context, instead of in a Slack thread that vanishes. The answer is attached to the ticket for good, the handling agent stays in control, and nothing leaks to the customer by accident.

Are Zendesk light agents free? Pricing and availability

Mostly, yes, within limits. On the Zendesk Suite, the light agent role is included, and most plans come with a free allotment of light agent seats. On Support-only plans, you need the Collaboration add-on to get them.

Here's the current allotment of included (free) light agents by Suite plan, verified against Zendesk's seat documentation:

A few things worth knowing:

• The role is genuinely free up to the plan's limit: light agents don't consume a paid agent seat. That's the whole point.
• If you exceed the included allotment, you can buy additional light agents, from the subscription page on self-service accounts or through your account rep on managed accounts. Zendesk's documentation doesn't publish a price.
• Some add-on roles do use a seat. On Growth and Professional, making a light agent a Knowledge admin uses a seat.
• Watch the edge cases. Zendesk provides a report to find light agents that are quietly taking up paid seats, for example if someone was upgraded to a full role and nobody noticed.

So the honest answer to "are light agents free?" is: free up to a generous cap on most Suite plans, a paid add-on on Suite Team and Support-only plans, and purchasable beyond the cap. Suite Growth no longer appears on Zendesk's public pricing page, though existing Growth accounts keep their 50. Confirm against your own account before you plan around exact numbers.

How is a light agent different from a full agent, contributor or end user?

Zendesk has several roles that look similar from a distance. Here's how the four most-confused ones differ:

The quick read: a full agent does the customer-facing work and owns tickets. A light agent is an internal advisor with configurable read access. A contributor is a narrower advisor that Zendesk now lists as a "Chat Phase 4 only" role: it can view and privately comment on tickets in its own groups, and mostly appears when a Chat-only account adds Support. An end user is the customer: they can only see and comment on their own requests. For the full picture of every role, see our guide to Zendesk roles and permissions.

How do you loop a light agent into a ticket?

Because a light agent can't initiate an @mention from their own role, knowing how to bring one in matters. There are two clean mechanisms:

• CCs and followers. Add the light agent as a CC or follower on the ticket and they're notified and looped into the thread, invisibly to the customer. CCs and followers are their own topic with real gotchas; we untangle the whole model in requesters, CCs, and followers explained.
• Side conversations. When you want a focused discussion with an expert rather than cluttering the main ticket thread, start a side conversation and bring the light agent in there. They can fully participate in email side conversations: create, reply, and close or reopen them (they just can't create or be assigned side conversation child tickets).

If a ticket is inside the light agent's permitted scope (their org, their groups, or all tickets, per the admin setting), they may already be able to find and read it without being added at all. The CC or side conversation is about notifying them and directing them to the right thread.

When should you use a light agent?

• Tier-2 / engineering escalation. Support flags a bug; an engineer (light agent) reads the ticket and posts the root cause as an internal note, without ever touching the customer reply.
• Specialist input from finance, legal or security. A billing dispute or a security questionnaire needs a precise answer from the team that owns it. The expert advises privately; the agent relays it in their own words.
• Account managers and CSMs watching key accounts. A CSM is CC'd on their accounts' tickets so they always know what's happening, but the support agent stays the single customer-facing voice.
• Managers and QA reviewing without working the queue. Leaders read tickets and leave coaching notes without consuming a full seat, and on Professional or Enterprise can be given access to reports.
• Knowledge contributors. An SME with light agent access helps draft and review help center articles between tickets.

What mistakes do teams make with light agents?

• Expecting a light agent to @mention a teammate. They can't. The @mention feature is off-limits to the role, so an SME can't tag a full agent back into the thread that way; they'll need to reply in a side conversation or leave an internal note on a ticket the agent follows. (To pull a light agent in, a full agent can CC them or @mention them, but the light agent can't return the favor.)
• Buying a full seat for an advisor. If someone only reads tickets and leaves internal notes, a full agent seat is wasted money. A light agent does that job for free.
• Expecting a light agent to "just reply." They can't send a public reply, full stop. If a role genuinely needs to respond to customers, that's a full agent.
• Forgetting to set the access scope. "All tickets" vs. "their groups" vs. "their org" is an admin choice. Too narrow and an expert can't see the ticket you need them on; too broad may over-expose data.
• Letting light agents quietly become paid seats. Audit roles periodically. An accidental upgrade, or a Knowledge admin role on Growth or Professional, can start billing you for a seat you didn't intend.

Can AI answer the questions you'd send to a light agent?

Light agents are how Zendesk lets you cheaply pull a human expert into a ticket. But the most expensive part of that pattern isn't the seat. It's the expert's time. Every escalation interrupts an engineer or a finance lead to re-answer something the company already knows.

This is where an AI agent layer changes the math. Macha sits on top of your existing Zendesk (it's not a help desk and not a Zendesk replacement) and connects to your knowledge: past tickets, internal docs, the help center and other systems. When a ticket comes in that would normally need a light agent, Macha can surface the expert's likely answer, draft it for the handling agent, or resolve routine cases outright, so a real SME only gets looped in for the genuinely new ones.

The honest framing: it's another tool to set up, and it's only as good as the knowledge you connect. The pricing matches what it does. Macha bills per ticket (one conversation, charged once, whether the agent summarizes, looks up an answer, drafts, routes or resolves), on one plan that starts at $299 a month for up to 750 tickets, never per resolution, because surfacing an expert's answer is useful work even when it isn't a "resolution." If escalations to other departments are clogging your queue, that's the gap it fills. You can try it with $50 of free usage, no credit card required.

Frequently asked questions

What is a light agent in Zendesk? A light agent is a restricted internal role for team members, often from other departments like engineering, finance or legal, who need to read tickets and add private internal comments but don't handle customers directly. They can view tickets (within a scope an admin sets) and advise behind the scenes, but they can't be assigned tickets, reply publicly, or edit ticket properties.

Are Zendesk light agents free? On the Zendesk Suite, yes, up to a per-plan limit. Suite Growth includes up to 50, Professional up to 100, Enterprise up to 1,000, and Enterprise Plus up to 5,000, and light agents don't consume a paid agent seat. Suite Team and Support-only plans need an add-on (the Collaboration add-on on Support), and you can buy more light agents beyond the included cap. Confirm current limits in your account.

Can a light agent reply to customers? No. Every comment a light agent makes is an internal note. They can't send public replies, and end users never see them on a ticket, even when they're CC'd. Customer-facing replies require a full agent seat.

Can you @mention a light agent? Light agents can't use the @mentions feature themselves. Pulling one in is different: an @mention from a full agent adds the person as a CC or follower, and light agents can be CC'd, so a full agent can loop a light agent in. The most reliable methods are to add them as a CC directly or include them in a side conversation.

What's the difference between a light agent and a contributor? Both are unpaid internal roles that can view tickets and add private comments. A contributor can only see tickets in its own groups and is now documented by Zendesk as a Chat Phase 4 role, while a light agent's access can be set to their organization's tickets, their groups, or all tickets.

What's the difference between a light agent and a full agent? A full agent is a customer-facing role that owns and resolves tickets, replies publicly, edits ticket fields and consumes a paid seat. A light agent is a read-and-advise role that adds internal notes only, can't be assigned tickets, and is free up to plan limits.

Can a light agent build Explore reports? Yes, if an admin allows it. On Professional and Enterprise plans the light agent role's Analytics setting can be "View dashboards" or "Manage reports and dashboards", which lets them create, edit and delete reports.

Is a light agent the right role for your expert?

A Zendesk light agent answers a specific, common problem: you need an expert's input on a ticket, but that expert doesn't do support and shouldn't cost you a full seat. Light agents read tickets, advise privately and stay invisible to customers, for free on most Suite plans up to a generous cap. Remember the role's hard edges: no public replies, no ticket assignment, no initiating @mentions (to loop one in, CC them or use a side conversation), and no editing tickets they don't own. From here, go deeper on roles and permissions, CCs and followers, and how the ticketing system fits together.

Light agent capabilities, availability and seat limits re-checked against Zendesk's documentation on 24 September 2026. Zendesk updates its product and pricing periodically, so confirm specifics in your own account before relying on them.