Using Information Request Playbook
Summarize
Summary of Using Information Request Playbook
The Information Request Playbook for Public Sector Digital Services assists case agents and managers in efficiently managing information requests and public records. It provides a step-by-step guide through the entire information request case life cycle, automatically appearing in the Playbook tab when a case is created in the CSM Configurable Workspace. The playbook breaks workflows into stages, each containing specific activities and the option for automated tasks, such as sending emails upon completion of activities.
Show less
Key Features
- Stages and Activities: The playbook includes stages such as Intake, Review, Process, and Decision, guiding users through the necessary steps to resolve cases.
- Visual Workflow: Users can visualize the whole workflow, tracking progress through a horizontal stage picker and accessing relevant record information and related records via a contextual side panel.
- Activity Management: Users can select activities, mark them as complete, and proceed through stages to resolve requests, enhancing efficiency and organization.
Key Outcomes
By utilizing the Information Request Playbook, ServiceNow customers can streamline their case management processes, ensure thorough reviews of requests, and enhance communication with constituents. This structured approach leads to improved resolution times and a better overall experience for both agents and requestors.
If you're an information request case agent or manager, you can use the Information Request Playbook for Public Sector Digital Services to manage and resolve requests for information and public records.
Overview
A playbook provides you with step-by-step guidance through the life cycle of an information request case.
- View the playbook stages and activities.
- Select an activity and perform the work to complete that activity.
- Mark an activity as complete and move to the next activity or stage.
- Complete the stages and activities to resolve the case.
The workflows for a type of case and the activities that you need to resolve these cases are in the playbook. By using a playbook, you can visualize the entire life cycle of the information request workflow.
Playbook stages
| Task | Description |
|---|---|
| Intake | Guides you through the record creation process by capturing the details of the information request and assigning it to the right agent. |
| Review | Acts as a checkpoint for duplicate cases and provides you with an opportunity to review the case details to verify that the issue is valid and needs to be resolved. |
| Process | Guides you through the activities for the information request fulfillment. |
| Decision | Captures and communicates the documents and information to the constituent and any other agents or involved parties. |
Playbook layout
A playbook is made up of several areas, including the playbook life cycle, the playbook work area, and the contextual side panel. The activity view determines how the stages and activities appear in the playbook.
The default activity view for the Information Request Playbook is the Process-based experience view. This view, which is shown in the following example, shows constituent or business information and case task information at the forefront of the playbook work area as you work on it.
- A horizontal stage picker that gives the agent a complete view of the entire process and where they currently are in that process. Agents can use the stage picker to track their overall progress as they work on cases.
Record information on the left side of the page, such as the contact information that is always available.
- Related records in the contextual side panel supported by the dynamic related records component.
| Playbook area | Description |
|---|---|
| Playbook header |
|
| Playbook Lifecycle |
|
| Playbook work area |
|
| Contextual side panel |
|
| Constituent or Business Card |
|
For more information on process-based layouts and process-based variants in the CSM Configurable Workspace, see Process page variants.