Product Support for Technology playbook stages and activities
Summarize
Summary of Product Support for Technology Playbook Stages and Activities
The Product Support for Technology playbook assists agents in efficiently researching and resolving technology cases. Upon creating a case, the system opens a service selector for agents to choose the relevant service, which launches the playbook outlining various stages and activities necessary for case resolution.
Show less
Key Features
Intake Stage
- Gather details: Agents collect account, contact, and product information.
- Describe the problem: Agents provide issue type, details, and can add users to a watch list.
- Identify impacted instances: Agents select instances impacted by the issue.
Triage Stage
- Review the problem: Agents review and update case information.
- Send initial response: Agents communicate with the customer, using templates if needed.
Troubleshoot Stage
- Diagnose: Agents utilize decision tables to modify conditions and run diagnostics.
- Test results: Agents review test outcomes and create repair tasks for failed tests.
- Update action plan: Agents document findings and next steps.
Resolve Stage
- Propose resolution: Agents provide root cause, resolution codes, and notes.
Close Stage
- Close case: Agents update issues with summaries and comments before officially closing the case.
Key Outcomes
By following the playbook, agents can streamline case management, ensuring thorough documentation and effective communication with customers. Each stage is designed to enable agents to efficiently gather information, analyze problems, propose solutions, and close cases effectively, leading to improved customer satisfaction and resolution times.
The Product Support for Technology playbook includes stages and activities that assist agents in researching and resolving technology cases.
When an agent creates a Product Support for Technology case, the system opens a service selector modal and displays the services defined for the Product Support for Technology type.
The agent selects a service and then selects Create to create a case. The system creates the case and launches the Product Support for Technology playbook. This playbook includes the stages and activities described in the following sections.
Intake stage
During the intake stage, an agent gathers information about the customer, the issue, and the impacted instances.
| Activity | Description |
|---|---|
| Gather details | The agent gathers information about the account and contact and the product and adds a short description. Select Continue to save the information and move to the next activity. |
| Describe the problem | The agent describes the issue type and the details and adds a case description and steps to reproduce. The agent can also add users to the watch list and add attachments. Select Continue to save the information and move to the next activity. |
| Identify impacted instances | The agent adds the impacted instances from a list of instances that belong to the account. Select Continue to save the information and move to the first activity in the Triage stage. |
Triage stage
During the triage stage, the agent reviews the case information, makes changes as needed, and sends an initial response to the customer.tech-product-case-resolve
| Activity | Description |
|---|---|
| Review the problem | The agent can review information about the customer issue, including the affected instances selected in the Intake stage and the sold product or product component. In addition to reviewing information, the agent can update the list of affected instances and the attachments. The following actions are available:
Once the case is assigned, the agent can select Continue to save the information and move to the next activity. |
| Send initial response | The agent can send a response to the customer by entering text in the Initial response field. If desired, the agent can use a template from the Response Templates tab in the contextual side
panel. The agent can also enter text in the Work notes field to capture internal information. After entering text in these fields, the agent can:
|
Troubleshoot stage
During the troubleshoot stage, the agent investigates the customer's issue and updates their findings in the action plan. The agent can leverage tools such as search or recommended actions as part of the investigation. If the agent
needs assistance, they can create case tasks or other types of records or initiate a Sidebar discussion.
| Activity | Description |
|---|---|
| Diagnose |
The decision table is provided with the Product Support for Technology application. You can modify the conditions that have been defined, and the results to suit your requirements. To enable the diagnostic activity in the troubleshoot stage, select the case category in the decision table as Issue, the diagnostic activity field is field is updated to True. The status can be changed to False by the agent. For more details on updating decision tables, see Decision Tables. The agent can view and do the following actions in these tabs:
|
| Update action plan | The agent investigates the issue and adds information to the following fields:
Selecting the Update and continue action:
|
| Related work |
The agent can see the action status of the case, if available, and can update the Needs attention field. The Related work activity includes a Recommended Actions card, Talk to an expert, that agents can use if they need assistance.
The Related work activity shows lists of related case records. The agent can expand these related record lists and view the record cards or create records.
The Related work activity includes Resolution Tasks, that agents can use If the test fails and manually create the resolution task to solve the issue. The agent can expand these Resolution Tasks lists and view the list of resolution tasks or create one. |
Resolve stage
In the Resolve stage, the agent proposes a solution to the customer.
| Activity | Description |
|---|---|
| Propose resolution |
The agent updates the following fields:
The agent can also enable the Add resolution notes to comments check box to add the resolution information to the case activity stream.
Note: If the Now Assist for Customer Service Management (CSM)
application is installed and the resolution notes generation skill has been configured, the Resolution notes field is automatically populated. For more information, see Using Now Assist for CSM to generate resolution notes for a case.
|
Close stage
- The customer accepts the proposed solution.
- The agent accepts the proposed solution on behalf of the customer.
- The agent closes the case.
- The system auto closes the case after it remains in the Solution Proposed state for a certain number of days.
In the Close stage, the agent updates the case with a summary of the issue and provides any additional comments or work notes.
The case record is read-only when the state is Closed.
| Activity | Description |
|---|---|
| Close case |
The agent updates the following fields:
After the case is closed, the agent can select Create Post Case Review to open a post case review record in a sub-tab. |
Save and Continue actions
When a stage is in progress, the Continue action saves the information in the stage and moves the agent to the next activity in the flow. This can be the next activity within a stage or the first activity in the next stage.
When a stage is complete, the Save action is also available. This action saves the information in the stage but does not move the agent to the next stage. The Save action enables agents to update information in completed stages.
Displaying Recommended Actions in playbook activities
Recommended actions can be configured to appear inside playbook activities. By default, the Talk to an expert recommendation appears in the conceptual side panel.
- Provides the recommendation for an agent to discuss a case issue with an expert. This recommendation.
- Includes the following actions:
- Start discussion: starts a Sidebar discussion.
- Dismiss: dismisses the recommendation card.
For more information, see Recommended Actions.