Technology Product Support case type
Summarize
Summary of Technology Product Support case type
The Technology Product Support case type is designed for technology companies to manage and resolve issues related to digital products and services. It encompasses the necessary processes, data structures, roles, SLAs, notifications, and workflows to effectively support customers through case resolution. This case type is part of the Technology Product Support Case application (sntechproductsupport) and extends the standard Case table to address technology-specific requirements.
Show less
Key Features
- Tables and Data Model: Utilizes the Tech Product Support Case table, which extends the Case table, to store case data with technology support specifics.
- Roles: Includes specialized roles such as Customer, Partner, Agent, Developer, Major Case Manager, and Resource Manager, each providing tailored access and capabilities to facilitate issue resolution and collaboration.
- Case States and State Flows: Cases progress through defined states—Draft, New, Work in Progress, Awaiting Info, Solution Proposed, Closed, and Cancelled—with controlled transitions triggered by agent or customer actions to streamline case handling.
- List Views: Preconfigured list views are available for both CSM/FSM Configurable Workspace and Core UI, enabling agents to efficiently manage cases by state and assignment.
- Special Handling Notes: Important case-specific notes can be configured and surfaced to agents based on conditions such as account or product, ensuring critical information is highlighted.
- Service Definitions: Defines service categories like Question, Service Request, Something is Broken, and Performance Issue to help customers quickly identify and request appropriate support.
- Email and Provider Notifications: Automated email notifications keep both customers and internal users informed of case updates, while provider notifications alert agents to case assignments and status changes via the application interface.
- Service Level Agreements (SLAs): SLAs define response and resolution timeframes based on case priority (P2, P3, P4), including first response, ongoing response, and case resolution times, with pause and restart conditions aligned to case state.
- Record Producer for Case Creation: Enables customers with appropriate roles to create technology product support cases directly from the Customer Service Portal, with fields capturing key issue details such as issue type, product, business impact, and reproduction steps.
- Case Action Status and Field Indicators: Visual indicators and color-coded highlights in case lists help agents quickly identify cases needing attention, blocked cases, and priority levels, enhancing case management efficiency.
- Auto Close Resolved Cases: Cases in the Resolved state are automatically closed after a default period of 10 days without customer action, with prior notifications sent at 3, 5, and 8 days to remind customers.
Practical Use for ServiceNow Customers
By implementing the Technology Product Support case type, customers can establish a structured and efficient process for handling technical support cases related to digital products. The included roles and state flows facilitate precise case assignment and lifecycle management, ensuring timely communication and resolution aligned with defined SLAs. Automated notifications and field indicators keep all stakeholders informed and focused on cases requiring action. The built-in record producer streamlines case submission from the customer portal, capturing essential information to accelerate troubleshooting. Auto closure of resolved cases helps maintain case hygiene by ensuring stale cases are closed systematically.
What to Expect
- Improved visibility into technology product support cases through tailored views and visual indicators.
- Clear role-based access control supporting collaboration across customers, partners, agents, and developers.
- Robust SLA enforcement with pause and restart capabilities based on case interactions.
- Automated and configurable notifications to keep customers and agents informed throughout the case lifecycle.
- Streamlined case intake via the Customer Service Portal with detailed data capture for faster issue diagnosis.
- Automatic case closure to maintain an active and relevant case backlog, reducing manual overhead.
The Technology Product Support case type enables technology companies to provide support for digital products and services.
A case types represents the processes and the data that are needed to resolve a specific type of customer issue. The Technology Product Support case type includes the table, roles, SLAs, email notifications, and other items needed to resolve technology issues.
The Technology Product Support Case application (sn_tech_product_support) includes the Technology Product Support case type. To view a list of available case types, navigate to .
| Item | Description |
|---|---|
| Tables | The Technology Product Support Case application includes the Tech Product Support Case [sn_tech_product_support_case] table. This table extends the Case table and can be extended. For a detailed description of the Tech Product Support Case table, including field descriptions, see Tech Product Support Case table. |
| Roles | Roles control access to features and capabilities in the Technology Product Support Case application, menu, and modules. |
| Case states | Technology product support cases follow a specific life cycle and move through a series of states from creation to closure. |
| State flows | State flows are customized transitions from one state to another, such as when an agent moves a technology product support case from Work in Progress to Awaiting Info. |
| List views | The Technology Product Support Case application includes list views for CSM/FSM Configurable Workspace and for Core UI that appear in the application navigator. |
| Special handling notes | Special handling notes bring important information to an agent's attention. |
| Service definitions | Service definitions enable customers to quickly discover and request the services they need and agents to create cases of the right type to support those requests. |
| Email notifications and email templates | Email notifications are sent to the contact and, in some cases, to users on the case watch list for specific actions. The system uses email templates to create these notifications. |
| Provider notifications | Provider notifications for agents are sent following updates to technology product support cases. |
| Service level agreement (SLA) definitions | An SLA definition includes the timing, conditions, workflows, and other information required to create and progress task SLAs. |
| Record producer | A record producer is a specific type of catalog item that allows end users to create task-based records from a service catalog. The Technology Product Support Case application includes the following record producer: Create a Technology Product Case. |
| Case action status | The case action status feature enables agents to easily identify cases that need attention. |
| Field indicators and highlights | The Technology Product Support case type uses field indicators and field highlights to indicate information about cases. |
| Auto close cases | Cases in the Resolved state can be closed automatically if customers do not take any action. |
Roles
User roles available with the Technology Product Support Case application address the diverse skill sets needed to resolve complex technical issues. These roles enable users to research technical issues, collaborate with development teams, and implement advanced troubleshooting techniques.
| Role | Description | Contains roles |
|---|---|---|
| Customer [sn_tech_support.customer] |
Users with this role:
|
|
| Customer admin [sn_tech_support.customer_admin] |
Users with this role:
|
|
| Partner [sn_tech_support.partner] |
Users with this role:
|
|
| Partner admin [sn_tech_support.partner_admin] |
Users with this role:
|
|
| Agent [sn_tech_support.agent] |
An agent role for the Technology Product Support Case application. |
|
| Creator [sn_tech_support.creator] |
Users with this role can create technology product support cases. | |
| Developer [sn_tech_support.developer] |
A developer role for the Technology Product Support Case application. |
|
| Report viewer [sn_tech_support.report_viewer] |
Provides report viewer access to Technology Product Support cases. | |
| Viewer [sn_tech_support.viewer] |
Provides read-only access to technology product support cases. | |
| Writer [sn_tech_support.writer] |
Provides write access to technology product support cases. | sn_tech_support.viewer |
| Major case manager [sn_tech_support.major_case_manager] |
Users with the major case manager role can:
For more information, see Major issue management overview. |
|
| Resource manager [sn_tech_support.resource_manager] |
Users with this role can assign technology product support cases to agents. |
|
| Navigation menu [sn_tech_support.navigation_menu] |
Provides access to the Technology Product Support Cases menu and modules in the application navigator. |
Case states
| State | Description |
|---|---|
| Draft | A case that is being created but is not yet submitted. |
| New | A case moves from Draft to New when it is submitted or when the case intake is completed. |
| Work in Progress | An agent accepts an assigned case or selects the Assign to me action and sets the state to Work in Progress. If a customer rejects a proposed solution, the case returns to the Work in Progress state. |
| Awaiting Info | The agent requests additional information from the customer. |
| Solution Proposed | The agent proposes a solution to the customer. |
| Closed | The customer accepts the proposed solution or the agent selects the Close case action. The case can also be auto closed if there is no response from the customer within a specified about of time. The case record is read-only when the state is Closed. |
| Cancelled | A case that has been cancelled by a user. |
State flows
| From state | To state | Trigger |
|---|---|---|
| Draft | New | Agent actions:
|
| New | Work in Progress | Agent actions:
|
| New / Work in Progress | Awaiting Info | Selecting the Request Information action changes the state from New or Work in Progress to Awaiting Info. |
| Awaiting Info | Work in Progress | The agent selects Information Received or the customer updates the case comments. |
| Work in Progress | Solution Proposed | The agent selects Propose Solution. |
| Solution Proposed | Work in Progress | The agent or customer selects Reject solution. |
| Solution Proposed | Closed | The agent or customer selects Accept Solution or the case is auto closed. |
List views
| User interface | Description |
|---|---|
| CSM/FSM Configurable Workspace | Technology Product Support Cases
|
| Core UI | Technology Product Support Cases
|
Special handling notes
Special handling notes bring important information to an agent's attention. You can configure special handling notes to appear based on one or more conditions, such as a specific account, contact, or product.
- Account
- Contact
- Product
- Install Base
- Assigned to
Service definitions
- Question
- Service Request
- Something is Broken
- Performance Issue
For more information, see Service definitions and Service definition categories.
Email notifications and email templates
| Notification | Action | Email template |
|---|---|---|
| Tech Case opened for customer | An agent opens a case for a contact. The notification is sent to the contact and to users in the watch list. |
case.opened.for.customer |
| Tech Case commented for customer | An agent adds a customer-visible comment to a case. The notification is sent to the contact and to users in the watch list. |
case.commented.for.customer |
| Tech Case awaiting info for Customer | An agent requests more information for a case from the contact. The notification is sent to the contact and to users in the watch list. |
tech.case.awaiting.info |
| Tech Case closed for customer | An agent closes a case. The notification is sent to the contact and to users in the watch list. |
case.closed.for.customer |
| Tech Case cancelled for customer | An agent cancels a case. The notification is sent to the contact and to users in the watch list. |
tech.case.cancelled |
| Tech Case solution accepted for customer | An agent accepts a solution on behalf of the customer. The notification is sent to the contact. |
tech.case.solution.accepted.for.customer |
| Tech Case solution rejected for customer | An agent rejects a solution on behalf of the customer. The notification is sent to the contact. |
tech.case.solution.rejected.for.customer |
| Tech Case resolved for customer | An agent resolves a case for a customer. The notification is sent to the contact. |
case.resolved.for.customer |
| Tech Case resolved - customer_watchlist | An agent resolves a case for a customer. The notification is sent to the users in the watch list. |
case.resolved.for.customer.watchlist |
To access a list of email notifications, navigate to .
To access a list of email templates, navigate to .
Provider notifications
| Case update | Notification |
|---|---|
| A case is assigned to an agent | Tech Case assigned to notification |
| Case comments or work notes are updated | Tech Case comments/notes added |
| The proposed solution is accepted or rejected | Tech Case solution accepted/rejected |
| The case is cancelled | Tech Case cancelled notification |
SLA definitions
The Technology Product Support Case application includes the following SLA definitions.
| SLA type | Description |
|---|---|
| First Response Time - P2 (8 Hours) First Response Time - P3-P4 (2 Days) |
The first response time is the time between the customer submitting a case and receiving a response. The first response time is defined by case priority.
This SLA is fulfilled when the customer receives a response in one of the following ways:
For the playbook experience, this SLA is fulfilled when the initial response is posted in the activity stream. |
| Ongoing Response Time - P2 (8 Hours) Ongoing Response Time - P3-P4 (2 Days) |
The ongoing response time begins after the first response time SLA is fulfilled and continues until the agent sends the next update to the customer. The ongoing response time SLA is defined by case priority:
ThIs SLA is fulfilled when the agent updates the additional comments in the activity stream. Once completed, the ongoing response SLA is reset and the default ongoing response is applied again. This SLA is paused when the case is in the Awaiting Info state and is restarted when the customer responds to the request for information. This SLA is stopped when the agent proposes a solution for a case. If the customer rejects the solution and the case moves back to work in progress, a new ORT SLA instance is started. |
| Case Resolution - P2 (14 days) Case Resolution - P3-P4 (28 days) |
The resolution time is the maximum amount of time in which a customer can expect a solution to be provided. This is the time between the customer submitting a case and accepting a solution (or a case being automatically
closed). The case resolution SLA is defined by case priority:
This SLA is paused when the case is in the Awaiting Info state and is restarted when the customer responds to the request for information. This SLA is stopped when the agent proposes a solution for a case. If the customer rejects the solution and the case moves back to work in progress, this SLA resumes. |
Record producer
- sn_tech_support.customer
- sn_tech_support.customer_admin
- Select .
- Select the Support category.
- Select the Create a Technology Product Case catalog item.
- Fill in the fields on the record producer. For field definitions, see the Create a Technology Product Case record producer fields table below.
- Select Submit.
| Field | Description |
|---|---|
| Issue Type | Select the type of issue for the case:
|
| Account | Auto filled with the account of the logged-in user. |
| Contact | Auto filled with the name of the logged-in user. |
| Affected Instances | Add the affected instances to this list. |
| Sold Product | Select a product from the list of available products. This list includes the sold products for the logged-in user. |
| Product Component | Select a product component from the list of available product components. |
| Short Description | Provide a brief description of the issue. |
| Description of the issue | Provide a more detailed description of the issue. |
| Describe the Business Impact | Describe the impact that this issue is having on your business. |
| Steps to reproduce | Add the steps to reproduce the issue. |
| Contact Timezone | Displays the timezone of the user in the Contact field. |
| Add attachments | Add any attachments to the case. |
Case action status
- A blue indicator highlights cases that need attention, such as cases that have been updated by customers or internal users and are waiting for input or review.
- A red indicator highlights cases that are blocked, such as cases that have open related task records or are waiting for customer feedback.
- The Action status field is updated to Customer Responded.
- The Needs attention field is enabled.
- Case action status
- Case action status (CSM Configurable Workspace)
Field indicators and highlights
| Column | Description |
|---|---|
| Priority |
The Priority field uses the following colors to highlight the case priority:
|
| Action status |
The Action status field uses the following colors to highlight the following actions:
|
| State |
The State field uses the following colors to highlight the case state:
|
| Escalated cases and accounts |
Field indicators and field highlights appear on the Short description field for escalated cases and on the Name field for escalated accounts.
For more information, see Case and account escalation. |
Automatically close technology product support cases
A case can remain in the Resolved state for 10 days before it is automatically closed. System administrators can change this default value in the Auto Close Resolved Cases Flow Designer flow.
- First notification: sent after 3 days
- Second notification: sent after 5 days
- Third notification: sent after 8 days
For more information, see Automatically close customer service cases.