Setting up Guided mode


What's my plan?

All Suites
Enterprise or Enterprise Plus


Support
Enterprise


Verified AI summary ◀▼
Guided mode helps you manage ticket order by restricting agents to using the Play button to navigate through tickets. Agents can access views and work on tickets one at a time. Agents can skip tickets and provide reasons, which you can review.


Location: Admin Center > People > Team > Roles


Ensure tickets are addressed in the appropriate order with Guided mode, a custom role option that requires agents to work through tickets in a view using the Play button.

Tip: You can more effectively determine which tickets agents work on by using omnichannel routing to assign tickets directly to agents.


This article contains these sections:

Understanding the agent experience in Guided mode
Setting team member access to Guided mode
Viewing skipped tickets



About Guided mode

In Guided mode, agents can access views using the Play button. For more details, see Using Play mode. When agents click the Play button, the system automatically opens the first ticket in the view. After addressing the ticket, the agent submits the update and automatically moves to the next ticket.

In Guided mode, when an agent clicks the Views icon ( ) in the sidebar, they can do either of the following:

See and open all tickets assigned to them in the system Your assigned tickets view.
Click on any other view to open its available ticket and start Play mode. They won't be able to see a list of the tickets in the view.



When you set up Guided mode, keep in mind that:

Agents in Guided mode will still be able to view and open tickets they have access to from end-user or organization profiles and through search.
Tickets in Guided mode aren't automatically assigned to the agent who is working on them unless you use one of the routing and automation options to assign tickets.
Guided mode may show an agent another agent's assigned tickets. This can happen if the tickets meet all view conditions, agent permission settings, and are not being viewed by another agent.




Setting team member access to Guided mode

You'll need to create or edit a custom role and assign it to the team members who should have Guided mode access.

To assign Guided mode to a custom role


In Admin Center, click People in the sidebar, then select Team > Roles.

Next to the role you want to modify, click the options menu ( ), then select edit.
In the Agent workflow section, under View permissions, click Play views only.
Click Save.




Viewing skipped tickets

In Guided mode, team members can choose to skip a ticket. After they click Skip, a window appears prompting them to enter a reason.

Guided mode team members can still click Skip in the above window without entering a reason. If you're looking for specific information from team members when they skip tickets, you should communicate expectations on entering reasons and how you'll be using the responses.
Review skipped tickets and reasons in a Guided mode team member's user profile. Looking through skipped tickets can help you identify specific knowledge areas and processes that team members are struggling with.
Admins can view skipped tickets for any agent in Guided mode. Guided mode agents can view their own skipped tickets only.

To view a Guided mode team member's skipped tickets


In Admin Center, click People in the sidebar, then select Team > Team members.

Locate the agent you want to review.
Click the options menu ( ), then select Manage in Support to open the user's profile.

Click Play only.
A list of tickets the agent has skipped, along with each reason entered, appears.


Click a ticket to open it and view additional details.




//
const fast_path_style = document.createElement('style');
fast_path_style.innerHTML = `#article-body .fastpath{font-size:.9em;background-color:#f3f3f3;border:1px solid #d3d3d3;padding:10px 10px 8px;margin-bottom:16px}#article-body .fastpath::before{content:none!important}`;
document.head.appendChild(fast_path_style);
//

//
const ai_summary_style = document.createElement('style');
ai_summary_style.innerHTML = `#styled-article-body{padding:0 0 0}#article-body #docs-ai-summary{background-color:#f3f3f3;border:1px solid #d3d3d3;padding:10px 10px 6px;margin-bottom:16px}#article-body #docs-ai-summary #docs-ai-summary-toggle{font-size:.9em;font-weight:700;margin-bottom:4px;cursor:pointer;display:flex;justify-content:space-between;align-items:center}#article-body #docs-ai-summary #docs-ai-summary-toggle #up-triangle{margin-left:auto;padding-right:10px;display:none}#article-body #docs-ai-summary #docs-ai-summary-toggle #down-triangle{margin-left:auto;padding-right:10px}#article-body #docs-ai-summary #docs-ai-summary-content{font-size:.9em;padding-left:25px;padding-right:25px;margin-bottom:12px}`;
document.head.appendChild(ai_summary_style);

const toggleAISummary = () => {
const summary = document.getElementById("docs-ai-summary-content");
const upTriangle = document.getElementById("up-triangle");
const downTriangle = document.getElementById("down-triangle");
if (summary.style.display === "none") {
summary.style.display = "block";
upTriangle.style.display = "none";
downTriangle.style.display = "inline";
} else {
summary.style.display = "none";
upTriangle.style.display = "inline";
downTriangle.style.display = "none";
}
};

document.getElementById("docs-ai-summary-toggle").addEventListener("click", toggleAISummary);
//
