Convergence Round up – Leo and Age of Customer Care

At convergence there were many announcements around the CRM road-map and upcoming Leo release. In this post I will summarise in a little more detail some of the great enhancements being made to Customer Care in the Q2 release. Note that the Q2 release will be available to Online and On Premise customers.

First of all lets share the Convergence slide on the Leo release:

Leo Release

Leo Release

So as you can see from just this slide we are not talking of a small enhancement to Customer Care, but a major release of functionality that finally brings customer care functionality up to the standard that we expect. So lets now dive deeper into the new functionality:

  1. Mobile – Android will be supported with a similar look and feel app as Windows and iPad. In addition the ability to reconfigure the org that it is working with will be provided. In addition the customer care entities will be supported across all platforms on the mobile app i.e. the case entity. This will enable mobilising the service desk.
  2. Unified Service Desk – This is a great new add and is similar to the Customer Care Framework. It provides a client side application that can be configured using standard records in CRM to connect to other systems in your ecosystem to provide a framework to enable pass through of context to other apps. In addition the ability to provide context sensitive call scripts will be provided natively and the ability to hook in a number of telephony provider add ons will be possible. This simple to use configure and deploy framework will make Enterprise contact centres a reality for Dynamics CRM.
  3. Unified Service Desk

    Unified Service Desk

  4. Case Hierarchies – Enables cases  to be related to a root cause case with dependencies defined across them.
  5. SLA – SLAs will be configurable based on CRM data, i.e. can provide a different SLA for a Premium contract customer vs a Bronze, or based on severity of the case. SLAs will control first response by and case resolved by timers. Workflow activities around escalation can be built into the SLA configuration to create tasks or emails etc, see below for an example where a task is created as part of the SLA failure state.
  6. SLA
  7. Entitlements – ability to manage what products a customer is entitled to service on.
  8. entitlements
  9. Timers – Based on the Customer SLA, timers will countdown the resolution time and change colour when getting close to resolution time. These timers will be standard functionality and be tightly tied to the SLA module. Within the Unified Service Desk they can be exposed out on the KPI control.
  10. timers
  11. Life-cycle State Model, you will be able to define the status transition life-cycle without code i.e if the case status in waiting for customer you can not move it to Resolved unless first moved in back to in progress.
  12. Queues and Routing – ability to define memberships around queues, and define routing rules around channel management i.e. if an email comes in auto create case or route to a specific queue. These can be manually or automatically triggered.
  13. Social Care – the Dynamics Team will provide an example listening app that can be utilised to convert posts from twitter into Cases in CRM.
  14. Socialinteraction
  15. Parature – future releases will see integration around web portals and knowledge base, likely Q4 release time-frame.

 

I hope you liked the summary of new functionality coming in the Q2 Leo release.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s