Activity Tracking / Interaction History / Prefill Fields
Eliminate double entry of data. Once a caller is identified, let 2Ring pre-create a new interaction history activity record, automatically prefill fields certain fields under a new ticket or prefill some fields for the agent to create a new contact/account in MS Dynamics 365.
Call Control in MS Dynamics 365
2Ring soft phone client provides agents with details about incoming call. Agents can review CallVariables, perform all call related actions right there on the MS Dynamics 365 screen, and even select their wrap-up code. Access to an external address-books with click2dial capabilities is a must for consults and transfers. On top of that, it is possible to also display a list of speed-dial buttons for frequently used transfers.
Click2Dial from MS Dynamics 365
Agents can click on a phone number in MS Dynamics 365 to dial it out or to edit the number before it gets dialed out. Automation options are available for outbound calls as well – for calls dialed out using an automated dialer (campaigns)*, and also for manual dials by agents. Placing an outbound call triggers a creation of an activity item on the contact. Outbound calls are usually tracked in MS Dynamics 365
* Dialer-invoked outbound calls are like inbound calls with the small difference that the customer’s identity is already known. This means that a single match is always expected, and the agents are usually not required to verify the caller
Customer Identity’s Transfer
If multiple agents take part in a call, the identity of the customer can be passed along the call to the other agent so that it is not necessary to identify the customer again.
Customer Lookup & Screen-Pop
2Ring can use any information provided by the caller (E.g. MemberID) or available about the call (e.g. ANI – caller’s phone number) to lookup matching accounts (contacts, or leads) and then let the agent decide what should happen next, or even automatically take the agent to the caller’s profile in MS Dynamics 365 and even pre-create a new interaction history activity record, prefill fields under a new case, a new opportunity, or prefill some fields for the agent to create a new contact in MS Dynamics 365.
Some remote systems can invoke workflow events directly from their own native screens. The workflow events are then handled by the workflow engine running in the Dialog Gadget. These are the most complex scenarios that can orchestrate and simplify work between multiple systems. To give you a sample scenario, an agent is working on an account in MS Dynamics 365. Clicking the ‘Request Consultation’ button in the MS Dynamics 365 application triggers an event handled in 2Ring Dialog Gadget. The workflow engine then creates a new Task in the MS Dynamics 365 application requesting a consultation for the customer.
Use Native Cisco Finesse Tools
Agents are still able to access any of the native gadgets in Cisco Finesse® – to have a full visibility for their personal interaction history, state history, and many other contact center metrics. Learn more about what Cisco Finesse can do for your agents and supervisors here.