Excerpt | ||
---|---|---|
| ||
Find out how to create a new Service Requests |
What does this section cover?
Table of Contents | ||
---|---|---|
|
Navigating to Service Requests
Info |
---|
CRM Application > Service Requests > Manage Service Requests |
Explaining Service Requests Fields
Name | Description | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Accounts Receivable* |
Only existing accounts receivable can be used. Terminated accounts cannot be selected for new Service Requests.
Starting from CRM.COM R9 and forward the name of the account will be displayed instead of the number | ||||||||||||
Accounts Receivable Owner | The accounts receivable owner contact or company name | ||||||||||||
Caller Contact | The caller / customer who initiated the service request is selected from a list of the related contacts. The account owner is the first and default option on the list and the rest related contacts displaying the Relation in the form of Relation - Contact Name. | ||||||||||||
Caller Email | The Email of the caller that all communications will be sent. This field is mandatory if the active Service Request definition specifies so in the communication settings | ||||||||||||
Number | An auto-generated number that uniquely identifies each service request | ||||||||||||
Type* | The type of the service request | ||||||||||||
Status* | The status of the service request | ||||||||||||
Life Cycle State | The life cycle state of the service request which is automatically assigned based on the status selected:
| ||||||||||||
Category | The category of the service request. It defaults to the type's default category | ||||||||||||
Classification | The classification of the service request which are predefined in the system, not configurable and they cannot be overwritten. This information is calculated dynamically based on the selected category. The supported values are the following:
| ||||||||||||
Urgency Level | The urgency level of the service request. It defaults to the type's default urgency level | ||||||||||||
Impact Level | The impact level of the service request. It defaults to the type's default impact level | ||||||||||||
Priority Level | The priority level of the service request which is automatically calculated based on the impact and urgency level following the configuration described in relevant process | ||||||||||||
Key Dates* | The key dates of the service request which include the following:
| ||||||||||||
Description | A description of the service request | ||||||||||||
Assigned to* | The assignment information for the service request, since it is an Assignable Entity. | ||||||||||||
Job | The job that the service request relates to | ||||||||||||
Subscription | The subscription that the service request relates to | ||||||||||||
Related Service Requests | A list with the service requests that this request relates to, along with a description of the relation The related service request section includes the following sub sections:
| ||||||||||||
Affected Physical Goods | A list of the physical goods that the service request is about and can be traceable or non-traceable. | ||||||||||||
Affected Services | A list of services that the service request is about | ||||||||||||
Activities | A set of activities which are planned for the specific service request, sorted by their life cycle state. New activities can be planned for each service request. The activity types which are allowed to be used are controlled by the related service request type | ||||||||||||
Communications | A list with all the communications exchanged between the customer and the service provider regarding this service request record | ||||||||||||
Response | A section that indicates that the service request record was acknowledged. As soon as a response is added to the service request, which is based on the related service request life cycle state, all response fields are mandatory to be completed but they can also automatically be completed based on the service request's type settings:
| ||||||||||||
Temporary Resolution | A section that indicates that the service request record has been temporarily resolved. As soon as a resolution is added to the service request, which is based on the related service request life cycle state, all relevant resolution fields are mandatory to be completed. Some of the fields can also automatically be completed based on the service request's type settings:
| ||||||||||||
Final Resolution | A section that indicates that the service request record has been finally resolved. As soon as a resolution is added to the service request, which is based on the related service request life cycle state, all relevant resolution fields are mandatory to be completed. Some of the fields can also automatically be completed based on the service request's type settings:
| ||||||||||||
Owned By Group | The group owing the service request since Service Request is an entity with Explicit Viewing Access. If nothing is specified then the Group of the logged in user will be used. | ||||||||||||
Privacy Level | The Service Request's privacy level since Service Request is an entity with Explicit Viewing Access | ||||||||||||
Log Information | Includes the standard log information plus shared notes | ||||||||||||
Attachments | The attachments related to the specific service request |
Creating and Saving, Validations and Restrictions
Action | Validations | Restrictions |
---|---|---|
Create |
|
|
Save | Mandatory Fields:
|
|
Creating a Service Request
- Search using Search using the criteria available in the summary page
- From the top menu click on "NEW" to open the Service Requests data entry page
Customer Information
Fill out the mandatory information- Accounts Receivable: Provide the account that the service request is related with. The Accounts Receivable can be different from the caller's account receivable, in cases that the service is related to a Company. Only existing accounts receivable can be used. Terminated accounts cannot be selected for new Service Requests.
- Caller Email: If communication settings have been enabled at the active Service Request definition, then you must specify an email. Search for the caller's available email or specify a new email address.
- Service Request Terms
- Type: Select the type of the activity
- Status: Select the status of the activity
Life cycle state of the activity is set automatically based on the activity status selected - Related Entities
- Using the Search boxes search and add the entity that the Service Request is related to.
- The selection can be between
- Subscription
- Job
Affected Products
Add Physical Goods or Services that the Service Request is about.
Info title Affected Products Tip Products to be added should belong to the allowed products of the service request type and are filtered based on the the related Job's provided products or related Subscription's products.
- Related Service Requests
- Outward Relations: Add the Service Requests that this request is related with
- Outward Relations: Add the Service Requests that this request is related with
Key Dates & Assignments
Key Date
Dates and times can be selected using the calendar icon- Start Date: The date is set to the current date but can be manually updated
- Estimated Completion Time: Update if required. (Will automatically update Expected Completion Date)
Expected Completion Date: Update if required
Assignments
Select the Unit and/or User that the Job will be assigned to
The User may be left empty and then users in the Unit defined will be able to accept the Job. View /wiki/spaces/V4Manual/pages/9830639 for more information on accepting a Job that has been assigned on the Unit
Attachments
Include Page Attachments - Global Attachments - Global
Log Information
The following information is automatically set by the system on saving the Service Requests
Include Page Log Information - Global Log Information - Global
- From the Action Menu click on "SAVE"
System Processing
- The Service Request will be saved and a unique number will be assigned
- Relation will be created between the Service Request and the referred entity if one was defined
- A Communication will be created based on the active Service Request communication settings and the information will appear under Communications
Include Page Viewing Communications related to a record - Global Viewing Communications related to a record - Global
Note |
---|
Visit /wiki/spaces/WIP/pages/10010220 Understanding Service Requests for business examples related to Creating Service Requests |
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
Related Areas
|
Panel | ||||||
---|---|---|---|---|---|---|
| ||||||
Popular Labels
|