Suite | Team, Growth, Professional, Enterprise, or Enterprise Plus |
Support with | Collaboration add-on |
Support with | Light agents add-on |
- Suite Growth plans include up to 50 light agents.
- Suite Professional plans include up to 100 light agents.
- Suite Enterprise plans include up to 1000 light agents.
- Suite Enterprise Plus plans include up to 5000 light agents.
Light agents have limited permissions but can stay informed about tickets and, when needed, provide subject matter expertise and advice by adding private comments to the ticket. Ticket comments by light agents are private, including the first comment of any tickets they create. However, when a light agent is the ticket requester, and they're not a member of the group or brand, their private comment will be converted to public.
To assign a light agent role, see Setting roles and access in Zendesk Admin Center.
This article contains the following sections:
Understanding what light agents can do
Light agents have the following access and permissions.
Area | Light agents can... | Light agents can't... |
---|---|---|
Tickets |
|
|
People |
|
|
Help center (not available in Team plans) |
|
|
Reports |
|
|
Views |
|
|
Business rules |
|
|
Channels |
|
|
Mail API |
|
|
Apps |
|
Configuring light agent ticket access and reporting permissions
After you understand when to use the light agent role and what they can do, you can configure some of the permissions. The method you use to configure permissions for light agents varies depending on whether you are on a Suite Growth, Professional, or Enterprise plan. You can configure options for ticket access for light agents, and, if you're on Suite Professional or above, you can additionally configure access to reports. The other light agent permissions shown in the table above can't be changed.
Configuring light agent permissions with Suite Growth and Professional
If you're using Suite Growth or Professional, you can configure light agent permissions for reports and ticket access.
To edit reporting and ticket permissions for light agents (Suite Growth or Professional)
- In Admin Center, click
Workspaces in the sidebar, then select Agent tools > Agent interface.
- Next to Light Agent access, select an option for What kind of tickets can
this agent access?:
- All within this agent's group(s) for light agents to access only tickets in their groups.
- Requested by end users in this agent's organization for light agents to access only tickets requested by end users in their organization. This also means the light agent won't be able to update organization fields for end users or lookup relationship fields that point to organizations.
- All for light agents to access all tickets.
- If you selected All within this agent's group(s) above, and you want light agents to still be able to assign tickets to any group when they're the requester, also select Agent can assign to any group.
- For What can this agent do with reports, set Insights reporting permissions to Can view only or Cannot view.
- When you are finished, click Save.
Configuring light agent permissions with Suite Enterprise
If you're using Suite Enterprise, you can only configure light agent permissions for ticket access.
To edit reporting and ticket permissions for light agents (Enterprise)
You can't clone or modify the light agent role, except for the two settings for tickets and reporting.
- In Admin Center, click
People in the sidebar, then select Team > Roles.
- Next to the Light agent role, click edit.
If you are using Explore, you can only change settings in the Tickets section.
- Under Tickets, select an option for What kind of tickets can this agent
access?:
- Requested by end users in their organizations for light agents to access only tickets requested by end users in their organization. This also means the light agent won't be able to update organization fields for end users or lookup relationship fields that point to organizations. Light agents with Suite Enterprise can't access queries or edit Explore reports, but you can share Explore dashboards with them in view only mode.
-
All within their groups for light agents to access only tickets in their
groups.
- Assign tickets to any group for light agents to be able to assign tickets to groups they don't belong to, including private groups.
-
Within their groups and all public groups
- Assign tickets to any group for light agents to be able to assign tickets to private groups they don't belong to.
- All for light agents to access all tickets.
- If you selected All within this agent's group(s) above, and you want light agents to still be able to assign tickets to any group when they're the requester, also select Agent can assign to any group.
- Click Save.
86 comments
Chris Todd
Can you explain more on what needs to be configured for Light Agents to see HC articles that are restricted to agents? In your table, it says “View areas of the Help Center knowledge base and community that are restricted to agents.”
I have to either make them a full Agent for Support or an Agent in Guide (not View). This opens up access rights that I rather not grant to everyone.
THX!
0
Shawna James
0
Adam Martin
It is kind of painful that light-agents cannot unfollow tickets b/c they do not have cc edit access. Can this be changed so they can at least remove themselves from that field?
2
Centro de Soporte Softland
desde el dia de ayer los agentes ligth no le salen las opcion de filtrar vistas
0
Tarandeep Gohlar
I don't understand why a light agent cannot submit a request on the knowledge base and cc in the customer.
While the request is submitted, the cc does not come into the ticket.
Annoying.
0
Raman Kalia
Why can't a clone of light agent be a light agent but a paid license. I have created a clone of light agent and allowed it to access tickets organization wide. But, the moment I map a user to this cloned role, it consumes a paid license. Ironically, as per Zendesk, a clone of Light Agent will not be considered same as the original. Second, it is not about the permission as one can change permission of the default role for organization access. A conundrum whether to call it silly or malicious on Zendesk's part.
0
Chad Susa (Gravity CX - Zendesk Partner)
Hi Gina
Our contact page (don't want to put up my email address in case of spam) is linked below. If you fill out that form I will get it and I will be in contact. We are based in Melbourne, Australia.
https://www.gravitycx.com.au/contact
Cheers
Chad
0
Gina
Hi Chad, definitely keen to have a chat. The biggest issue we face is the store not being able to see their solved ticket as the ticket reassigns to the Head Office Customer Service agent when they solve the ticket. If we could find a solution to that, it would be a huge win!
0
Chad Susa (Gravity CX - Zendesk Partner)
Hi Gina,
We are a Zendesk partner and we worked with a Zendesk customer (furniture retailer) to configure something similar.
Each store is a Light Agent and they create tickets for various support issues including requests on behalf of the store customers (end customers are requesters) as well as creating their own tickets for 'Store Support' (the stores are the requester).
They wanted the ability for the Stores (Light Agents) to access a view to be able to see ONLY their tickets they have created for end users, which were assigned as normal to the HQ customer service team, as well their own tickets where the store needed support from HQ.
They didn't want to use Organisations as mentioned above by Pedro (which is a great idea).
Our solution is a little in depth so it might be best to explain one-to-one with you.
Let me know if you interested.
The other thing that might work is using the 'Followed Tickets' view under the agent profile. When you say "All customer complaints are fielded by the CS Team at head office and where the complaint is store specific, the CS agent will triage it to the store." - how are they 'triaged' out to the stores? Do you add them as a follower to the ticket? If so, your stores can access the 'Followed tickets' view under their individual profile to see tickets they are followers on. (See below)
Cheers
Chad
0
Pedro Rodrigues
Hi Gina, if your light agents are allowed to access any tickets within their groups and any public groups, you should be able to set up a View for your Stores to see solved tickets, regardless of who solved them.
Exmaple. You can create a trigger that detects the Store's internal note (and group reassignment, if it happens during the same action/event), and add a tag ('stores_solved'). Then your View would be available to the Stores group, and have two conditions: status is greater than On-hold (or Pending if you're not using On-hold status), and tags contain stores_solved).
Additionally, if you need each store to see their own tickets exclusively - that is, store A shouldn't be able to see store B's tickets and vice versa - then I'd suggest taking a look at Organizations and consider modifying the light agent role to tickets "Requested by end users in their organisations" (if that doesn't affect any other teams with light agent roles and different workflows/tasks). This change would allow you to have a single "Stores" group but multiple Orgs (for example: "Stores Org • Store A", "Stores Org • Stores B". Because of the role's settings, the same Solved tickets view would show Store A different tickets than Store B.
These are just examples of how to address this issue based on my interpretation of the situation described.
Hope it helps!
0
Sign in to leave a comment.