Step By Step
New Case Creation | |
|---|---|
•When creating a new Customer Request the user needs to choose between the different types of Cases that exist. •Let’s follow David, working as a Customer Service Representative while he creates a new Customer Request. •Under the Case tab, David clicks on New to create a new Customer Request. |  |
There is another way the customer request can be created from Lightening by flowing the steps given as below.
A new button has been created on Lightening for Gmail and It allows the user to create a new customer. |
|
•David now needs to select the Record Type for the Case. •He has the choice between Complaint, Sample Request and Customer Request.
•David selects Customer Request and clicks on Continue. This will open the Customer Request edit page. |  |
Case Information | |
|---|---|
 Basic information needs to be populated in the Case Information section. This section contains the following fields:-Account Name: Main Account (can be Ship-to, Sold-to or Corporate Group) -Subject: Subject of the Request -GBU: GBU concerned by the Customer Request (automatically selected bases on the User GBU) => New Winter 17' Release -BU: Business Unit of the GBU -Product Family: Product (level 3) -Type: What the Customer Request is about – GBU specific (Mandatory) -Sub-type: More granuar level of Type -Originator: User who logged the Customer Request - | |
Case Owner: User |
or Group of Users that are responsible to act on the Customer Request |
on each phase
|
| ||
-Status: Open – Pending Approval – Approved – Resolved – Closed – Rejected -Final Communication Sent: Checkbox that flags if Customer Communication has been sent. -Received Date: Date that Solvay received the Customer Request (Mandatory). -Estimated Resolution Date: Estimated date when the Customer Request will be resolved (Mandatory for some GBUs). -Requested Resolution Date: Requested date when the Customer Request should be resolved (Mandatory). - |
Priority: Low – Medium – High / By default on “Medium”. => Severity has now been renamed to Priority -Case Origin: Inbound email – Inbound call – Face to Face – Website -Confidential: Restrict visibility of the Customer Request. |
|
| |
 Each Customer Request can be linked to assignees. The different assignees are the persons in charge of one or more steps of the Customer Request process.•David can Assign |
2 different people to the Customer Request: -Originator: The person logging the Customer Request – in our case David |
-Approver: The person responsible of approving the Customer Request– in our case John.
-Processor: The person responsible of processing the Customer Request – in our case Laurie. -Notified: The person that needs to be notified of the Customer Request |
The Approver and the Processor will be automatically assigned by the System based on each GBU rule
|
|
Severity | |
|---|---|
| During the Customer Request Registration step, David needs to fill-in the Severity of the Customer Request. There are 3 types of Severity: -High -Medium -Low •The Severity is by default on the value Medium. |  |
 The definition of these severity values is the following: |  |
Status
Status Automatic Update
•A process flow on top of the screen shows the progress status of the Customer Request.
•The Status order is as follows:
-Open: As soon as the Customer Request is created.
-Pending Approval: When the Customer Request is submitted for approval.Customer Request |
|---|
-Resolved: Once the Customer Request has been processed.
-Closed: When the Customer Request is closed.
-Rejected: When the Approver has rejected the Customer Request.
•Changing the Status of the Customer Request is an automated process for the following Statuses:
• Nevertheless, for the other Statuses, the values are automatically updated:
-Open: Default status after creation of a Customer Request.
-Pending Approval: Automatically updated when the Customer Request is submitted for approval.
-Approved: Automatically updated when the Approver approves the Customer Request OR when the user creating the Customer Request has a Salesrep profile.
-Rejected: Automatically updated when the Approver rejects the Customer Request.
-Resolved: Automatically updated when the fields Resolution Date and Resolution are populated.
-Closed: Automatically updated when the Customer Request is closed.
Visibility | |
|---|---|
Customer Requests have 2 visibility options to manage confidential cases •Visible: the Customer Request is visible by everyone (by default) •Confidential: By ticking the box “Confidential”, user make the Customer Request accessible only to the | |
Owner (User or Queue), the Approver and the Case Team. |
|
Customer Contact Information | |
|---|---|
Multiple contacts can be maintained on the Customer Request. David can maintain a main Contact and has the possibility to add Additional Contacts in the related list once the Customer Request is saved. Example •When choosing a Contact, David can search for any Contact but the Contacts related to the Account Name will be the ones displayed by default. To show the Contacts not related to the Account Name, David needs to click on “Show all results”.  | Hovering the cursor of the mouse on the main Contact reveals additional information on this Contact such as Name, Account Name, Phone, Email and Language. |
Request Description | ||
|---|---|---|
•More detailed information on the Customer Request are populated in the Description Section. This section contains the following fields: -End Customer: Final Customer (Ship-to). -Internal Description: Detailed description of the Customer Request -Opportunity: Opportunity related to the Customer Request.
•Once David has populated all the relevant fields for his Customer Request, he can save it by clicking on the Save button. |
|
Adding Products | |
|---|---|
| Now that the Customer Request is saved, David can add Products using the Products related list. |  |
| In order to add a Product, David goes on the Customer Request Products related list, clicks on the “New Customer Request Product” button, selects a Product from the lookup field. David can also select an Application or End Use and a Manufacturing Plant for this Product information purpose and clicks on Save. | |
 | |
| The Product is added to the Customer Request Product related list. |  |
For Fibras & Coatis : The, add a validation rule on the case team for Fibras & Coatis to make the Customer Request MUST have at least one account manager and one CSR in the case team. |
|
Adding Additional Accounts | |
|---|---|
•Additionally, David can add Additional Accounts using the Account related list. |  |
•In order to add an Additional Account, David goes on the Case Account Associations related list, clicks on the “New Case Account Association” button, selects an Account from the lookup field and clicks on Save. |  |
| •The Account is added to the Case Account Association related list. |  |
•Furthermore, David can add Additional Contacts using the Contacts related list. |  |
| In order to add an Additional Contact, David goes on the Contact related list, clicks on the “New Contact” button, selects a Contact from the lookup field and clicks on Save |  |
| The Contact is added to the Contact related list. |  |
Need help?
| Include Page | ||||
|---|---|---|---|---|
|