Page Comparison

Service Request

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

A back-office user or

Contact can submit Service Requests via self-service APIs (e.g.

CRM.COM app or portal).

A

Service Request is always associated with a contact and a queue. A queue is a user-defined grouping method

used to group similar

Service Requests, for example, reward or billing requests

.

Queue

Queues group and dictate the core

Service Request behaviour using stages. Multiple stages can be defined under the In Progress state, and there is only one

New and one

Closed state.

• New

• - This is the first and the default

• state upon

• Service Request creation.

• In Progress

• - This is a transitional

• state until a Service Request is closed. Usually

• , this state consists of several stages (e.g. investigation, proposal, response, follow-up)

• Closed

• - This is, by default, the final

• state of every queue

• .

Once a Queue has been saved,

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

• • 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

• App Settings

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

• • using customer-facing applications (e.g., contact mobile app or

• • web portal). 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 App settings.

Stages

Stages are

the steps in

the queue that a Service Request progresses through one by one until it’s Closed. Each queue may have different

stages

and each stage in the queue

is mapped to one of the states (New, In Progress and Closed).

The default system

stages (New

and Closed) cannot be

deleted as they are automatically assigned to each new queue upon creation.

User-specified stages are mapped to the

In Progress

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

A Service Request's owner is a CRM.COM back-end

user

responsible

for progressing the Service Request and ensuring that it progresses through the stages in the respective queue until it is closed.

The Service Request creator specifies the owner, who can be a system user and/or a team of users

, or Automations can be utilised in order to automatically assign a Service Request to a user and/or a team.

If not specified, the owner is the

Service Request creator by default. Only the Service Request’s owner or any user with the Owner user role can edit it. When a Service Request is also assigned to a Team, then team members have viewing access to the Service Request and they can only add notes or re-assign the Service Request to them.

Priority Model

Priority models

define the required effort for responding to and resolving a

Service Request by the user. Priorities models can be arranged according to

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 how important the request is for the

• contact.   

• Urgency

• levels relate to how quickly a resolution must be provided.

Select a priority for each Impact-Urgency combination. If no combination is defined

, the system auto-

populates it. 

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

provide a business classification

for the service request.

Each Service Request Queue can

be assigned multiple applicable categories

.

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

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, 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. Notes can be added by the owner and team member (if the Service Request is also assigned to a team). However, only the latest Note can be deleted and only by the user who added it.

Attachments

Upload attachments related to the Service Request for easy referencing.

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

The back-end user can log charges related to the Service Request, including fees for one-time services required to resolve the Service Request and products (both traceable and non-traceable physical goods). These charges can be edited from the moment 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 provided. If the Service Request is cancelled or left unresolved, the invoice will not be issued.

Service Request Operations

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

All 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

• • stage in the queue

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

• Regressing a Service Request

• • To regress a

• • service request,

• • select the previous

• • stage in the queue. The user

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

• • beside the progress bar.

• Closing a Service Request

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

• • 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 Service Request charges

• • . If not resolved

• • , no charges will apply. In both cases

• • , the Service Request will be closed.

Automations

Automations 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

Approval of Service Request Progression

It’s possible to block a Service Request from progressing unless one or more users or the contact have 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. Approval Requests are configured using Automations.

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 - View a list of your Contacts with summarised financial information

    • Service Requests Analysis - A detailed analysis of logged Service Requests, grouped by queue, with the final outcome and charges information

• Insights

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

    • Service Request Created

    • Service Request Closed