Overview
Coordinate systemic problems and explicit case resolution/reopen state with linked history and customer-safe updates.
Prerequisites
Permissions required
Steps (4)
-
1
Link shared operational problems where required
Relate affected cases to a problem or incident and maintain its scope, updates, internal work, and timeline.
Tips
Validation
Success criteria
-
2
Confirm case work and approvals
Review internal work, service-action results, approvals, SLA state, requester communication, and outstanding dependencies.
Tips
Validation
Success criteria
-
3
Record the resolution
Create the resolution record and move the case according to the configured lifecycle and customer communication policy.
Tips
Validation
Success criteria
-
4
Reopen the same case when service continues
Use the REOPENED lifecycle and reopen history so follow-up remains attached to the existing case.
Tips
Validation
Success criteria
About this guide
Agent Desk is a complete service-operations workspace for customer and internal support. Requests can enter from staff, customer portals, trusted applications, APIs, governed workspace calls, Bridge v2 connections, events, and configured inbound providers.
Agents work from permission-aware queues with skills, presence, capacity, assignment, priority, SLA, requester identity, live business context, customer conversation, internal notes, attachments, approvals, related work, source-authorized actions, and a complete case timeline.
Supervisors and operations teams manage queues, routing, service levels, problems and incidents, knowledge, quality, workforce, reports, integrations, automations, retention, audit, and enterprise identity from the same application. Connected systems integrate through capability-based provider contracts so each source application can remain authoritative for its own business data while Agent Desk owns service operations.