What Is a Light Agent in Zendesk? (Permissions, Pricing & Use Cases)

That's the exact gap the Zendesk light agent fills. A light agent is an internal team member — usually from another department — who can read tickets and weigh in privately, without the cost or the customer-facing power of a full agent. This guide covers precisely what a light agent can and can't do, why the role exists, whether it's free, how it stacks up against full agents, contributors, and end users, and the mistakes teams make with it. Everything here is verified against Zendesk's own documentation.

What a light agent actually is

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 a light agent can do

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

• View tickets — scoped by an admin setting (see the pricing/availability section): only tickets in their groups, only tickets requested by end users in their organization, or all tickets.
• 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 as the requester. When a light agent opens a ticket themselves, their first comment is private by default.
• Be CC'd on a ticket so they get looped in and notified — and 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 one exception: light agents can't create, send, or be assigned side conversation child tickets.)
• Act as a designated approver in approval workflows.
• View user profiles and Help Center content, and — if an admin grants it — hold Guide management permissions to help write and review knowledge base articles, plus an Explore Viewer role to see shared dashboards (on Professional and above).

What a light agent can't 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: a light agent can't use the @mention feature from their own role to tag a colleague into a ticket — Zendesk confirms "light agents and contributors can't use the @mentions feature." The reverse is less of a hard wall than people assume: because an @mention from a full agent simply adds the mentioned person as a CC, and light agents can be CC'd, a full agent can still loop a light agent in that way. The cleanest, most reliable methods are to CC them directly or use a side conversation.
• Can't create or manage business rules — no macros, triggers, or automations — and can't create new end users.
• Can't respond to CSAT surveys or otherwise act in a customer-facing capacity.

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

Why the light agent role exists

The light agent exists for one reason: cost. Full Zendesk agent seats are billed per agent, per month, 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 — so the answer is attached to the ticket forever, 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 each plan comes 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 (and contributors) don't consume a paid agent seat. That's the whole point.
• If you exceed the included allotment, you can purchase additional light agents beyond the limit.
• Watch the edge cases. Zendesk even 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. Pricing and limits change, so confirm against your own account and Zendesk's pricing page before you plan around exact numbers.

Light agent vs. full agent vs. contributor vs. 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 broad, configurable read access. A contributor is an even more limited advisor — same private-comment idea, but locked to tickets in their own groups, with no option to see tickets outside them. An end user is the customer: they can only see and comment on their own requests. For the full picture of every role and what each can touch, see our guide to Zendesk roles and permissions.

How light agents relate to CCs, followers, and side conversations

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. Add the light agent as a CC 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, side-channel 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 part of the light agent's permitted scope (their group, their org, 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 and directing them to the right thread.

Common use cases

• 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 — finance, legal, 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.
• Knowledge contributors. With Guide management permissions, an SME (light agent) helps draft and review help center articles between tickets.

Common mistakes

• Expecting a light agent to @mention a teammate. They can't — the @mention feature is off-limits to the light-agent role, so an SME can't tag a full agent back into the thread that way. They'll need to use a CC or reply in a side conversation instead. (To pull a light agent in, a full agent can CC them or @mention them — which works by CC'ing 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. Leaving an expert too narrow means they 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 can start billing you for a seat you didn't intend.

Where AI fits — fewer experts in the loop

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 directly, draft it for the handling agent, or resolve routine cases outright — so a real SME only gets looped in for the genuinely novel ones.

The honest framing: it's another tool to set up, and it's only as good as the knowledge you connect. And the way it's priced matches what it actually does — Macha bills per AI action (any automated step: summarize, look up an answer, draft, route, or resolve — 0.5–9 credits depending on the model you choose), not per resolved ticket, because surfacing an expert's answer is automation, not necessarily a "resolution." If escalations to other departments are clogging your queue, that's exactly the gap it fills. You can try it free — 7-day free trial, 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 who 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 require the Collaboration add-on, 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 — they can't tag a colleague into a ticket that way. Pulling one in is different: because an @mention from a full agent just adds the person as a CC, and light agents can be CC'd, a full agent can loop a light agent in. The most reliable methods, though, 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. The difference is scope: a contributor can only see tickets in their own groups, while a light agent's access can be configured to their groups, their organization's tickets, 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.

The bottom line

A Zendesk light agent is the answer to 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 — all for free on most Suite plans, up to a generous cap. Just 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 instead), and no editing tickets they don't own. Get the scope right and the light agent is one of the most cost-effective collaboration tools in Zendesk. 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 verified against Zendesk's official documentation, June 2026. Zendesk updates its product and pricing periodically — confirm specifics in your own account before relying on them.