{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":6295,"path":"customer-service-management/csm-playbook-complaint-overview.md","title":"Case Playbook for Complaints","bundle":null,"doc_type":null,"release":"australia","body":"\n# Case Playbook for Complaints\n\nUse the Case Playbook for Complaints to guide agents through the steps that are needed to resolve customer complaints.\n\nA complaint case captures the information about the customer, the product, and the details about the complaint. The complaint playbook provides the activities and tasks that agents can perform to research and resolve the complaint. Agents can also create and assign tasks as needed and use the playbook to communicate with the customer.\n\nThe Case Playbook for Complaints can be used with cases that are created using the complaint case type. This playbook is available for both CRM Workspace and CSM Agent Workspace. In the CSM Workspaces, the playbook appears in the **Playbook** tab on the case record.\n\n**Note:** If you have the admin role, you can configure a playbook to use the compact mode in CRM Workspace. Use the compact mode to move the playbook from a tab in the Workspace to a tab in the contextual side panel.\n\n## Case Playbook for Complaints application\n\nThe Case Playbook for Complaints 3.0 application \\(com.sn\\_csm\\_complaint\\_caseflow\\) is available from the ServiceNow® Store. For more information, see [Playbook plugins](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/customer-service-management/setting-up-csm-playbooks.md).\n\n## Case Playbook for Complaints PAD process definition\n\nThe Case Playbook for Complaints 3.0 includes a new Process Automation Designer \\(PAD\\) process definition called **complaint\\_playbook\\_v1**. This process definition contains the optimized stages and activities for the complaint playbook.\n\nThe process definitions are stored in the Process Definitions table \\(sys\\_pd\\_process\\_definition\\). To view a list of processes, do the following task:\n\n1.  In the application navigator, enter **sys\\_pd\\_process\\_definition.list** in the application navigator.\n2.  [Configure the list](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-user-interface/c_PersonalLists.md) to show the **Name** field.\n\nOnly one PAD process per playbook can be active at a time. .\n\n## Case Playbook for Complaints features\n\nThe Case Playbook for Complaints 3.0 includes the case features and enhancements that are listed in the following table.\n\n<table id=\"table_csx_knc_bqb\"><thead><tr><th>\n\nFeature\n\n</th><th>\n\nDescription\n\n</th></tr></thead><tbody><tr><td>\n\nCreate a complaint case using the Case Playbook for Complaints\n\n</td><td>\n\nFeature that opens the complaint playbook and initiates the first activity in the Intake stage, which is gathering complaint details. The agent can complete and save this activity to create the record.\n\n For more information, see [Create a record using a playbook](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/customer-service-management/csm-playbook-create-record.md).\n\n</td></tr><tr><td>\n\nFocused activity view\n\n</td><td>\n\nFeature that determines how the stages and activities appear in the playbook. [Select a playbook activity view](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/customer-service-management/playbook-select-activity-view.md)\n\n The Case Playbook for Complaints uses the Focused Activity View, which enables agents to see:\n\n-   The end-to-end life cycle of the complaint workflow in the playbook life-cycle panel.\n-   The current stage is expanded and the current activity is highlighted within the playbook life-cycle panel.\n-   The details of the current activity that is displayed in the playbook work area.\n\n</td></tr><tr><td>\n\nContextual side panel\n\n</td><td>\n\nFeature that displays the following information in the contextual side panel:\n\n-   Activity stream\n-   Ribbon information, such as the case overview, customer details, timeline, and SLAs\n-   Dynamic related records\n\n**Note:** The activity stream and ribbon information are available in CRM Workspace only.\n\n For more information about using the contextual side panel, see\n\n-   [Using activity stream in the contextual side panel](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/customer-service-management/csm-playbooks-using-activity-stream.md)\n-   [Viewing the ribbon information in the contextual side panel](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/customer-service-management/csm-playbooks-viewing-ribbon-info.md)\n-   [Viewing dynamic related records in the contextual side panel](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/customer-service-management/csm-playbooks-viewing-rel-records.md)\n\n</td></tr><tr><td>\n\nActivity visibility\n\n</td><td>\n\nFeature that uses the following settings to control activity visibility:\n\n-   Hide the activities in a stage that the logged-in user can't access.\n-   Hide the pending activities in a stage.\n\n For more information about configuring this feature, see [Configure playbook stage and activity visibility](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/customer-service-management/playbook-config-activity-visibility.md).\n\n</td></tr><tr><td>\n\nCompact mode\n\n</td><td>\n\nMode that moves the playbook from a tab in the Workspace to the contextual side panel. Agents can complete the playbook activities in the side panel while they’re viewing the other tabs in the record page. **Note:** This mode is available in CRM Workspace only.\n\n Users with the admin role can configure a playbook to use the compact mode in the playbook component configuration in UI Builder.\n\n</td></tr><tr><td>\n\nDynamic related records\n\n</td><td>\n\nFeature that displays the records in the contextual side panel. These records dynamically change based on the context of the current record or playbook activity.\n\n From the **Related Records** tab in the contextual side panel, agents can\n\n-   Filter the list of related records\n-   Open the list in a new tab\n-   Create records\n\n**Note:** The dynamic related records feature is available in CRM Workspace only.\n\n For more information, see [Viewing related records in the contextual side panel](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/customer-service-management/csm-playbooks-viewing-rel-records.md).\n\n</td></tr><tr><td>\n\nSLA widget\n\n</td><td>\n\nActivity cards in the playbook work area that can display an SLA widget. The widget appears on the activity card when the playbook activity has an SLA. This widget includes the activities in the following stages:\n\n-   Triage\n-   Research\n-   Respond\n\n The color of the widget indicates the time remaining for the SLA:\n\n-   Green: 0–50%\n-   Yellow: 50–75%\n-   Orange: 75–99%\n-   Red: 100% or breached\n\n</td></tr></tbody>\n</table>## Using the playbook stage and activity pickers to navigate stages and activities\n\nThe playbook stage picker enables agents to see the entire complaint workflow. Agents can navigate the playbook stages and activities by doing the following tasks:\n\n-   Expand and collapse stages to show or hide activities.\n-   Use the filter in the stage picker to filter activities by the assigned user or the activity state.\n-   Select an activity to display the details in the activity viewer.\n\n## Using the Playbook Actions menu\n\nThe Playbook Actions menu in the playbook header includes the actions that agents can perform at the playbook and activity levels. The agents can select the Playbook Actions icon \\(\\[Omitted image \"playbook-ellipses.png\"\\] Alt text: Playbook actions menu icon.\\) to access this menu.\n\nThe Playbook Actions menu includes the following playbook-level actions:\n\n-   **Expand All Stages**: Expands all the stages in the playbook.\n-   **Collapse All Stages**: Collapses all the stages in the playbook.\n-   **Request Info**: Displays a pop-up window that the agent can use to communicate with the customer and to request information about a case or case task. This action also saves the details to the case or case task activity stream. By using this action, the state of the case or case task changes to Awaiting Info and pauses the SLAs and any timers.\n-   **Info Received**: Returns the case or case task to the previous state and restarts the SLAs and any timers.\n\n**Note:** The **Request Info** and **Info Received** actions can also be configured to appear on case task activity cards.\n\nThe activity-level actions can vary depending on the type of activity and in which stage it appears. For example, actions are available to accept cases, create related cases, create case tasks, and propose solutions.\n\n## Complaint playbook stages and activities\n\nThe following table lists the Case Playbook for Complaints stages and activities that agents can use to resolve customer issues.\n\n<table id=\"table_nrj_z2s_llb\"><thead><tr><th>\n\nStage\n\n</th><th>\n\nActivity\n\n</th><th>\n\nActivity Details\n\n</th></tr></thead><tbody><tr><td>\n\n**Intake** Guides the agent to collect the information needed to create the complaint case.\n\n</td><td>\n\nGather complaint details\n\n</td><td>\n\nWhen an agent creates a complaint case, the workspace opens the Create New Complaint Case form, launches the complaint playbook, and uses the first activity to gather complaint details.\n\n The agent can enter the information about the customer, the service, the complaint, and the expected outcome for the case. As the agent enters the complaint details, additional fields appear on the activity card such as the **Category** and **Subcategory** fields.\n\n**Note:** For more information about the service, see [Service definitions](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/customer-service-management/csm-service-definitions.md).\n\n Agent actions:\n\n **Continue**: Creates the complaint case and adds the case number to the **Record** tab. It also marks the first activity as complete and moves to the second activity.\n\n</td></tr><tr><td>\n\n \n\n</td><td>\n\nAdd involved parties\n\n</td><td>\n\nActivity that the agent can use to add involved parties to the complaint case:\n\n1.  Select **Add new** to open the Create New Related Party form in a new tab.\n2.  In the **Type** field, select the related party with the correct entity type, such as a co-complainant who is a customer contact.\n3.  Select **User**.\n4.  Select **Save** to add the user to the Involved Parties list on the activity card.\n\n Agent actions:\n\n-   **Assign to me**: Available if the case isn’t yet assigned. Assigns the case to the logged-in user.\n-   **Add new**: Adds a user to the Involved Parties list \\(see the previous steps\\).\n\n</td></tr><tr><td>\n\n \n\n</td><td>\n\nVerify primary address\n\n</td><td>\n\nActivity that shows the fields from the Primary Correspondence Address form section on the **Details** tab. Agents can accept this address or select a different address. Agent actions:\n\n-   **Save**: Saves the updates to the Primary Correspondence Address fields.\n-   **Move to triage**: Completes the Intake stage, marks the activities in the stage as complete, and moves to the next stage in the complaint playbook.\n\n</td></tr><tr><td>\n\n \n\n</td><td>\n\nNotify customer\n\n</td><td>\n\nActivity that displays the details of the email that was automatically sent to the customer at the completion of the Intake stage.\n\n</td></tr><tr><td>\n\n**Triage** Enables the agent to do the initial troubleshooting on the case.\n\n</td><td>\n\nVerify complaint\n\n</td><td>\n\nCase task that agents can use to review any available related search results in the contextual side panel and add notes or attachments.\n\n Agent actions:\n\n-   **Request info**: Requests additional information from the customer. This action changes the state of the case task to Awaiting Info.\n-   **Post**: Posts the comment or the work note to the case task record activity stream.\n-   **Submit for review**: Marks the case task and the Triage stage as complete.\n\n</td></tr><tr><td>\n\n \n\n</td><td>\n\nNotify customer\n\n</td><td>\n\nActivity that displays the details of the email that was automatically sent to the customer at the completion of the Triage stage.\n\n</td></tr><tr><td>\n\n**Research** Uses the Research AI agent to help the agent research the case, and sends the case to different back-office teams for follow-up.\n\n</td><td>\n\nResearch AI agent\n\n</td><td>\n\nActivity that embeds the Complaint Case Research AI agent directly in the Research stage. Select **Start Now Assist** to invoke the agent and view its recommended troubleshooting steps and case tasks.\n\n Role required: sn\\_now\\_canvas\\_ai.interactive\\_view\\_user. Only the user who invokes the agent can interact with the activity and view its output.\n\n By default, this activity appears when the Complaint Case Research AI Agent trigger is inactive in the Accelerate Complaint Case Handling agentic workflow. You can edit the playbook if you don't want to include this activity.\n\n For more information, see [Use the Research AI agent activity](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/customer-service-management/now-assist-for-csm/acc-complaint-case-handling-research-activity.md).\n\n</td></tr><tr><td>\n\n \n\n</td><td>\n\nReview legal implications\n\n</td><td>\n\nCase task that agents can assign to a different user for legal review.\n\n To assign the task:\n\n1.  Select the View Task icon in the activity card. This action opens the case task in a new tab.\n2.  Select the user in the **Assigned to** field.\n3.  Add information to the other fields on the Case Task form as needed and select **Save**.\n\n Agent actions:\n\n-   **Request info**: Requests additional information from the customer. This action changes the state of the case task to Awaiting Info.\n-   **Post**: Posts the comment or the work note to the case task record activity stream.\n-   **Review complete**: Marks the case task as complete.\n\n</td></tr><tr><td>\n\n \n\n</td><td>\n\nProduct owner review for other similar issues\n\n</td><td>\n\nCase task that an agent can assign to a different user for a review of similar issues.\n\n To assign the task:\n\n1.  Select the View Task icon \\[Omitted image \"pop-out-icon.png\"\\] Alt text: View task. in the activity card to open the case task in a new tab.\n2.  Select the user in the **Assigned to** field.\n3.  Add information to the other fields on the Case Task form as needed and click **Save**.\n\n Agent actions:\n\n-   **Request info**: Requests additional information from the customer. This action changes the state of the case task to Awaiting Info.\n-   **Post**: Posts the comment or the work note to the case task record activity stream.\n-   **Review complete**: Marks the case task as complete.\n\n</td></tr><tr><td>\n\n \n\n</td><td>\n\nVerify check entitlement\n\n</td><td>\n\nCase task that an agent can assign to a different user for an entitlement review.\n\n To assign the task:\n\n1.  Select the View Task icon \\[Omitted image \"pop-out-icon.png\"\\] Alt text: View task. in the activity card to open the case task in a new tab.\n2.  Select the user in the **Assigned to** field.\n3.  Add information to the other fields on the Case Task form as needed and select **Save**.\n\n Agent actions:\n\n-   **Request info**: Requests additional information from the customer. This action changes the state of the case task to Awaiting Info.\n-   **Post**: Posts the comment or the work note to the case task record activity stream.\n-   **Review complete**: Marks the case task as complete.\n\n</td></tr><tr><td>\n\n \n\n</td><td>\n\nBilling review for any refunds\n\n</td><td>\n\nCase task that an agent can assign to a different user for a billing review.\n\n To assign the task:\n\n1.  Select the View Task icon \\[Omitted image \"pop-out-icon.png\"\\] Alt text: View task. in the activity card to open the case task in a new tab.\n2.  Select the user in the **Assigned to** field.\n3.  Add information to the other fields on the Case Task form as needed and select **Save**.\n\n Agent actions:\n\n-   **Request info**: Requests additional information from the customer. This action changes the state of the case task to Awaiting Info.\n-   **Post**: Posts the comment or the work note to the case task record activity stream.\n-   **Review complete**: Marks the case task and the Research stage as complete.\n\n</td></tr><tr><td>\n\n \n\n</td><td>\n\nNotify customer\n\n</td><td>\n\nActivity that displays the details of the email that was automatically sent to the customer at the completion of the Research stage.\n\n</td></tr><tr><td>\n\n**Respond** Guides the agent in drafting a response to the case.\n\n</td><td>\n\nCompose email\n\n</td><td>\n\nActivity that the agent can use to communicate with the customer. Agent actions:\n\n-   **Request info**: Requests additional information from the customer. This action changes the state of the case task to Awaiting Info.\n-   **Post**: Posts the comment or the work note to the case task record activity stream.\n-   **Review complete**: Marks the case task and the Respond stage as complete.\n\n</td></tr><tr><td>\n\n**Resolve** Manages the activities for case resolution.\n\n</td><td>\n\nPropose resolution\n\n</td><td>\n\nActivity that shows the fields from the Resolution Notes section on the Case form. An agent can add the resolution details and select **Propose solution**.If the customer rejects the solution, the agent can return to the Resolve stage and propose another solution.\n\n Agent actions:\n\n-   **Propose solution**: Proposes the solution to the customer and marks the Resolve stage as complete.\n-   **Change solution**: This action appears after the agent proposes a solution.\n\n</td></tr><tr><td>\n\n \n\n</td><td>\n\nNotify customer\n\n</td><td>\n\nActivity that displays the details of the email that was automatically sent to the customer at the completion of the Resolve stage.\n\n</td></tr><tr><td>\n\n**Close** Manages the activities for closing the case and sending a survey to the customer.\n\n</td><td>\n\nClose case\n\n</td><td>\n\nWhen the customer accepts the resolution, the Resolve stage completes and the Close stage is also marked as complete.\n\n</td></tr><tr><td>\n\n \n\n</td><td>\n\nNotify customer\n\n</td><td>\n\nActivity that displays the details of the email that was automatically sent to the customer at the completion of the Close stage.\n\n</td></tr></tbody>\n</table>## Process-based page variant for complaint case type\n\nThe Case Playbook for Complaints v5.0 application includes a process-based page variant that you can activate and use with the complaint case type in CRM Workspace. This page includes the following features:\n\n-   Horizontal stage picker in the record that provides an end-to-end view of the complaint process.\n-   Related list tabs that are displayed in the Dynamic Related Records component in the contextual side panel.\n-   Persistent account and contact information that is displayed in the panel.\n-   **Email** tab that is displayed in the **Activity Stream**.\n-   Email templates that are displayed in the contextual side panel.\n-   Customization of the start and end states of the approval flow as fields in the Approval request activity.\n\nAgents can create tasks as needed as well as view and update case details. For more information, see [Configure templates and pages](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/customer-service-management/csm-playbook-pages.md).\n\n"}}