---
sourceDocument: Zurich Proactive Service Experience Workflows
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/proactive-service-exp-workflows

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Proactive Service Experience Workflows

ft:clusterId :

    - psew

bundleId :

    - psew

workflow :

    - Customer and Industry


---

# Diagnose and resolve

# Diagnose and resolve a Product Support for Technology case {#ariaid-title1}

* Release version: Zurich
* 
* Updated July 31, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 4 minutes to read

As a customer service agent, review, diagnose, resolve, and close a case for the service-related issue experienced by the customer.

## Before you begin

Role required: sn_tech_support.agent

## About this task

The Product support for
technology case progresses through several stages from start to closure. It begins with a support agent reviewing and verifying the problem. Next is the diagnosis tab, where system-specified tests are
executed to identify the root cause. After the tests, the support agent moves to the repair stage, creating a task to fix the identified issue. The agent follows the instructions in the repair task to address the problem
areas. Once the repair is complete, the case is retested to confirm that the issue is resolved. Finally, the case is resolved and closed based on the customer's feedback on the provided solution.

## Procedure

1. Navigate to WorkspacesCSM/FSM Configurable Workspace.
2. Select the List icon.
3. Navigate to Product Support for TechnologyAssigned to me.
4. Open the Product support for technology case that is in the New or Open state.  
5. Review and verify the Product support for technology case.
   1. In the Intake tab, expand the Gather details, and then review and verify the general details for the Product support for technology case.
   2. Expand the Describe the problem and review the details of the Product support for technology case.
   3. Expand the Identify impacted instances and review the affected instances.
   4. Select Continue.  
      Note:  
      Before the state is moved to close, the fields in the Product support for technology case form can be edited from the case highlights card.

   {#diagnose-resolve-hitechcases__substeps_y2v_tr3_pbc}  
   The Product support for technology case moves to the Triage stage.
6. Review the case information.
   1. In the Triage tab, expand the Review the problem and review the details of the problem and affected instances.
   2. Expand the Send Initial Response and review the initial response.

   {#diagnose-resolve-hitechcases__substeps_b1g_254_sfc}  
   The Product support for technology case moves to the Troubleshoot stage.
7. Diagnose the Product support for technology case to identify the root-cause of the problem.
   1. To generate the test results, select Run diagnostics from the contextual panel.
   2. In the run diagnostics panel, select CI/Service from the drop-down list.
   3. Expand the cards in the Available Test Suite.  
      To set up test definitions, see [Setting up test definitions](https://www.servicenow.com/docs/qG~Eo25v0EPcHtW4orU5Dg "Define tests for a particular service type, product model, or inventory to troubleshoot the service-related problems.").

      To set up test group, see [Setting up a test group](https://www.servicenow.com/docs/v3cwba2T7~Buyi6EeZ0R1A "Define tests for a particular service type, product model, or inventory to troubleshoot the service-related problems.").
   4. In the manual test, select single/multiple tests.  
      In the automated test, selection of test isn't available.
   5. Select Configure.
   6. In the Configure tests dialog box, fill the test required characteristics form to activate the Run test button.
   7. **Optional:** In the test dialog box, select an option either to run the test now or to schedule it for later.
   8. Select Run test.
   9. In the diagnose tab, expand the Test results and review the results of the tests conducted in the previous step, checking whether each test is passed or failed.  
      The failed tests indicate that the issues causing the
      Product support for
      technology case to be identified and need repair.

      The maximum number of rows to the group is limited to 20 rows. To configure the maximum number of rows more than 20 rows to the group, see [Presentational List Usage](https://developer.servicenow.com/dev.do#!/reference/next-experience/yokohama/now-components/now-list/usage).
   10. **Optional:** Select the View Details icon for a specific test result to review its details.
   11. **Optional:** Select the Rerun test icon for a specific test result to run it again.
   12. Select Continue.
   13. **Optional:** In the Diagnostic tasks tab, select Create to create manually the diagnostic tasks.

   {#diagnose-resolve-hitechcases__substeps_fhq_1v4_sfc}  
   The case moves to the Repair stage.
8. Repair the case by creating a new or automated repair task.
   * Select Generate automated task to automatically create a repair task.
   * Select Create repair task to manually create a customize repair task.

   {#diagnose-resolve-hitechcases__choices_fzj_xcj_pbc}  
   A Repair task is created for all failed test cases related to the diagnosed cases.
   1. Select the repair task that you want to work on.
   2. In the Resolution task form, review the task details to identify the failed test and then work on those tests to fix the service problem.
   3. In the Select field, select an appropriate state from the list to update or close the repair task, such as Closed complete.
   4. Select Save and close the resolution task.
   5. Select Continue.

   {#diagnose-resolve-hitechcases__substeps_ocd_hn2_qbc}  
   The case moves to the Resolve stage.
9. In the Resolve stage, review the proposed resolution for the case.
10. Close the Product support for technology case.
    1. Go to the Close stage and fill in the fields.  
       {#diagnose-resolve-hitechcases__table_ny1_j2x_vfc__entry__2}

       | Field | Description |
       |-|-|
       | Issue summary | Summary of the issue. |
       | Resolution code | Code value that explains how the case is resolved. For example, Fixed by Support/Guidance provided. |
       | Resolution notes | Summarizes the resolution of technology product support case. |
       | Add resolution notes to comments | Option to make the resolution notes available to anyone who can view the case activity stream. |
       | Additional comments (Customer visible) | Comments related to the service problem case, if any. These comments are visible to your customer who can access this case. |
       | Work notes | Information about state transitions. |
       [Table 1. Close case form]

       {#diagnose-resolve-hitechcases__table_ny1_j2x_vfc}
    2. Select Accept Solution or Reject Solution based on the customer feedback.
    {#diagnose-resolve-hitechcases__substeps_inw_g2x_vfc}

## Result

The Product support for
technology case is resolved and closed successfully.

*[\>]: and then