Page Comparison

sService Request

A Service Request It is a request ticket for service by a contact or system user raises (for a contact) to request a service from the business.

Service requests can be submitted by a A back-office user or Contact can submit Service Requests via self-service APIs (e.g. , CRM.COM app or portal).

A service request Service Request always belongs to a Queuequeue. A Queue queue is a CRM.COM user-defined grouping method that is used to group similar service requests (e.g.Service Requests, for example, reward or billing requests) .

Queue

Queues group and dictate the core SR behaviour, such as allowed Service Request behaviour using stages. Multiple stages can be defined under the In Progress state, and there is only one new New and one closed Closed state.

• New : - This is the first and the default status state upon SR Service Request creation.

• In Progress: - This is a transitional stage until an SR state until a Service Request is closed. Usually, this stage is divided into state consists of several stages (e.g. investigation, proposal, response, follow-up)

• Closed: - This is, by default, the final status state of every queue. Closed SRs are not visible in the Kanban view.

Once a Queue has been saved, three four additional options are available to the user:

• Edit Default Priority for Queue

  • Set the default priority for Service Requests created through the back-end for this queue. The user has the option to change it when creating the Service Request.

• Edit Alert Times for Queue:

  • These are notifications to users when a Service Request has not progressed from the New

  status

  • state yet. The alert times can vary depending on the priority of the Service Request.

• Edit Completion Times for Queue:

  • This setting indicates how long a Service Request should take to be completed (from creation) based on its priority.

• Configure Application Settings: In case contacts are allowed to

  • Set up this configure for those Service Request queues where Contacts can create Service Requests

  for a specific queue by using another platform

  • using customer-facing applications (e.g.

  ,

  • consumer app or portal)

  , then the Self-Service feature should be enabled

  • . Define the default settings such as the owner/team, priority, category, and tags that will be applied for such Service Requests. Ensure that the Service Request feature is also activated in the app/portal setings.

Stages

Stages are back-end, user-defined discrete process the steps in a queue. the queue that a Service Request progresses through one by one until it’s Closed. Each queue may have different stages based on the relevant process it supports (e.g., billing issues). The stages are completed and moving to the next as the service request progress until 'Closed'. Each stage in the queue represents the service request 'state'. 'New', 'In-Progress' and 'Closed' default queue stages are automatically mapped to the default SR states, respectivelyis mapped to one of the states (New, In Progress and Closed).

The default system states stages (New , and Closed) cannot be renamed or deleted as they are automatically assigned to each new queue upon creation.

User-specified stages are mapped to the 'In Progress' service request state; , these can be renamed or deleted as they are specified and created by a key user specifically for a type of queue.

Numbering Scheme

Select the numbering format for your Service Requests. Each new Service Request will be assigned a sequential number based on the given format.

Owner

The Owner of a service request A Service Request's owner is a CRM.COM back-end user or a team that is assigned to a service request Service Request ticket. The owner is responsible for progressing the ticket progress and ensures ensuring that this the ticket moves through the statuses stages in the respective queue until it is closed. The SR Service Request creator specifies the Owner and owner, who can be a system user or a team of users.

By defaultIf not specified, the Owner owner is the SR creator unless otherwise specified. The Owner Service Request creator by default. However, the owner can be changed to another user or team even after SR is executed on whilst the Service Request is progressing through the queue.

Priority Model

Priority models define the required effort for responding to and resolving a service request Service Request by the user. Priorities models can be arranged according to SR Service Request urgency and impact. The urgency and impact levels will be set upon Service Request creation (either by the user or assigned automatically through a workflow rule).

• Impact Levels represent levels represent how important the request is for the customercontact.   

• Urgency Levels relate levels relate to how quickly a resolution must be provided.  Priority Model - select  

Select a priority for each Impact-Urgency combination. If no combination is defined, then it is auto-populated by the system. 

The medium urgency and medium impact setting is the default priority when creating a new Service Request. 

Categories

Categories can be defined in a hierarchical - tree structure and are used to provide a business classification for the service request. Each Service Request Queue can have its own be assigned multiple applicable categoriesOnce categories are defined, each service request can belong to multiple categories .

When a Service Request is created, the user can assign one or more categories to it based on the queue it belongs to.Link to other

Related Service Requests

It's possible to link a Service Request to other Service Requests, if they are somehow related.

Related Address

Optionally specify an address related to the Service Request, if for example, if the Service Request has been raised for a technical issue requiring an on-site visit. The address can be one of the Contact’s addresses or any other address.

Affected Services

If the Contact associated with the Service Request is a subscription service member, and the Service Request is being raised for a particular subscription service, then select the subscription service related to the issue.

Notes

Add internal notes related to the Service Request. Important notes can be pinned to appear at the top of the list of notes.

Attachments

Upload attachments related to the Service Request for easy referencing. Tags

Assign tags associated with the Service Request. Tags can be used as a filtering option on summary screens and reports.

Custom Fields

If you require additional information not supported by CRM.COM, you can create custom fields of various formats to meet your specific needs.

Activities

If additional tasks need to be scheduled as part of the Service Request, create an activity and assign it to another user or team to complete.

Charges

On a service request, the The back-end user will be able to charge can log charges related to the Service Request, including fees for one-time services (activities) that are required to resolve the service request Service Request and for products (both traceable and non-traceable / untraceable physical goods). Upon completion, this will generate an invoice, and if the SR has been resolved(closed), the Contact will be invoiced for These charges can be edited from the time the Service Request is created until it is Closed.

Once the Service Request is completed and marked as resolved (when Closed), an invoice will be generated for the Contact, covering the associated services and products supplied. These charges are editable from the moment of creation of the service requests until the SR is resolved and closed. If the service request is cancelledprovided. If the Service Request is cancelled or left unresolved, the invoice will not be postedissued.

SR Operations

Service Request Operations

The owner selects a Service Request from the Summary summary screen and to edit it.

All values of a service request Service Request details are editable except the Contact and the Queue associated with a Service Request.

• Progressing a Service Request:

  • To progress a Service Request, select the next

  status

  • stage in the queue

  . A Service Request can only be progressed to the next status, following the current status or

  • or if it’s the last stage it can be closed.

• Regressing a Service Request:

  • Select the previous

  status

  • stage in the queue to regress a Service Request. The user

  has to

  • must provide a reason for regressing. The history of regression is displayed

  below

  • beside the progress bar.

• Close Closing a Service Request :

  • By selecting the Close button from either the summary screen or the

  service request

  • Service Request screen, the user will be prompted to specify whether the request has been resolved. If resolved, the Contact will be billed for all the items listed in the charges

  on

  • of the

  service request

  • Service Request. If not resolved, then no charges will apply. In both cases, the

  SR ends up as

  • Service Request will be closed.

Automations

Stage change Approvals

Configure Automations to manage the progression of the SR through the queue by requesting approval from one or more system users or the contact themselves (who can approve it through a communication sent to them).

System users can see approvals pending on them and accept/reject each oneAutomations for Service Requests can be created based on the following trigger events:

• Events

  • New Service Request

  • Update Service Request

  • Update Service Request Stage

  • Regress Service Request

  • Close Service Request

  • New Service Request Note

  • Update Service Request Note

  • Approval on Service Request Queue Stage Change

  • Service Request Owner Changed

Available actions depending on the selected event:

• Actions

  • CRM.COM Communications

  • CRM.COM Service Request Provisioning

  • CRM.COM Activity Scheduling

  • CRM.COM Webhooks

  • CRM.COM Approvals

Approving the progression of a Service Request

It’s possible to block a Service Request from progresing unless one or more users or the contact has given their approval. The users can see their pending approvals from the back-end system and the contact can give their approval by clicking on a link sent in a communication.

Print the Service Request

Print the Service Request using a configurable template to determine the layout.

Email the Service Request

Email the Service Request to the contact’s email address using a configurable template to determine the layout.

Events History

View the actions taken for the Service Request and the user who performed them.

Tags

Assign tags associated with the Service Request. Tags can be used as a filtering option on summary screens and reports.

Custom Fields

If you require additional information not supported by CRM.COM, you can create custom fields of various formats to meet your specific needs.

Custom Forms

Configure your own custom data screen for Service Requests.

This is an external implementation designed using CRM.COM’s Back-Office APIs and hosted outside of CRM.COM, which can be loaded and used via the back-end system.

Analytics

• Dashboards

  • View summarised Service Request numbers from the following dashboards:

    • Home

    • CRM Overview

• Reports

  • Generate or schedule Service Request reports to run regularly according to selected criteria.

    • Service Requests Summary

    • Service Requests Analysis

• Insights

  • Set up insights for Service Requests using customisable criteria and filtering options using events:

    • Service Request Created

    • Service Request Closed