Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Without an active call,  the user can search a customer profile in the Contacts List based on one of his phone number, First name or Last name to view or update the customer profile.

...


Image Added



Info
titleNote:
  • For now, the search can be done based on the five phone numbers (phone 1-5) and the customer’s first name, last name only. Search based on any other Customer field is NOT available

  • When the user types in some characters in the search bar, the search results show all customer records which contain that string in the name (either in the start, middle or at the end of the name)

  • The user will have to press ‘Enter’ after typing in the search string

  • The application always shows the first name and the phone 01 of the customer in the suggested answers regardless of which name (first or last name) and/or phone the search string contains

  • This means that if the customer is matched with the search string (the phone number exists in the customer profile in any of the five phones or the name matches to either first or last name of the customer), the customer record will be popped up in the results

  • To search a customer profile based on the phone number, type the full number or partial number and press the “Enter” key

  • It takes about 5 seconds to search a customer profile in a DB of 15 lac customers

...

The following details of a customer interaction are available:


Image RemovedImage Added



Field

Description

ANI

This shows the customer’s phone number from which the call was received

Calling Date and Call Duration

This shows the total call duration and the on which the call was received.

Call Wrap up

This is the Finesse Wrap-up provided by the agent/s who handled the call.

Agent ID

The shows the ID of the agent who handled the call.

Call Type

This shows the type of the call. It can assume the following values:

  • INBOUND: Simple inbound call.

  • OUTBOUND: The manual outbound made by the agent or supervisor to the customer

  • Transfer: This the call leg which got transferred to another agent or supervisor

  • Conference: This shows that the call was converted to a Conference call with multiple agents

Team

This shows the name of the team the agent belongs to

Start Time

This shows the time when the call was landed on the Finesse desktop

Recording player integration

This is shown when EF Voice Recording Solution is also purchased. In that case, each call that is stored in CIM as a customer interaction will also display the call recording along with the interaction record.

Note that this is available only for CCE customers at the moment.

...

  • Request Title: This contains the title of the request and is a mandatory field

  • Description: This is an optional field, containing a brief description of the request

  • Request Type: Administrators can define their own request types. Based on a request type, users can then also define other custom attributes particular to a specific request type. While opening a new type of request, the appropriate request fields are shown based on the selected request type.

  • Status: A request can have only two status values:

    • Active: Representing that the request is opened. New interactions can be linked with an existing, active request.

    • Closed: Users of CIM can later also choose to close a request. Any new interaction cannot be linked to a closed request.


Image RemovedImage Added

Create a New Request

...

A list of all five phone numbers will appear (if exist) as shown in the screenshot below. Select the desired number from the list and make sure that the agent is in the “Not ready” state to initiate the call.

...

Image Added

Once a call is received and connected, it will be recorded in CIM as an OUTBOUND customer interaction as shown in the screenshot below.

...


Image Added


Note

This feature is NOT available for administrators, that is, administrators cannot make an outbound call to the customer from the admin application. Instead, they have to have a supervisor or an agent credentials and log on to the Finesse gadget to make a call to the customer.

...

When a call is transferred from one agent to another agent, two call legs are formed, one for each individual agent. For instance, the screenshot below shows that the first call leg having the type “INBOUND” was first landed to the agent “shabber” and was later transferred to another agent “hassan1” having the call type as “TRANSFER”.

...

Image Added

It should also be noted that each leg will have its own wrap-up applied by the agent who handled the call leg. However, if the second agent doesn't apply any wrap-up to the second call leg, the same wrap-up applied by the first agent (to the first call leg) will also be stored for the second call leg.

...

Similar to Call Transfer, multiple call legs are formed in case of a Conference call since there could be two or more agents involved in the same call. For instance, the screenshot below shows that the first call leg having the type “INBOUND” was first landed to the agent “shabber” and was later transferred to another agent “hassan1” having the call type as “CONFERENCE”.

...


Image Added


In this case, again, the call will have two wrap-ups, each applied by the individual agent for each individual call leg. The principle of application of wrap-ups and the association of the interaction with a request is the same as it is for the Transferred call.

...

This allows business administrators to add custom attributes to store any business-specific information for their customers. These additional user-defined fields are available to agents/supervisors while creating new customer profiles.

Image RemovedImage Added

To start adding the new fields in the “Customer” object, click on the “ADD FIELD” button. While defining new fields, the user will need to select the following:

...

The “Request Schema” defines the type of information that should be stored while opening customer requests. Agents and supervisors will be able to see the type and the number of request fields in the CIM Finesse gadget based on the fields admins define under the “Request Schema” from the CIM Configurations.


Image RemovedImage Added


The user first needs to define the customized request types for the field “Type”. These request types are then used to group further sub-fields based on each individual request type. For instance, for a request type “complaint”, the business may require to take "device" or "model number" against which to open the complaint. Similarly, for a different type of request such as “Sales”, the business may need to define the desired service or package that the customer would like to subscribe to.

...