REQUEST A DEMO

Tag: SLA

SLA Calculations using Dovetail Carrier

August 9, 2016 I was recently working on a project that wanted to track SLAs, but the specific SLA rules were more complex than could be handled just using business rules.  But, the logic would be pretty straightforward to enforce via code. So we came up with a solution that used a combination of business rules and a custom Dovetail Carrier extension.  In this post, I’ll walk through how we accomplished this. There’s a lot of information here, so grab a cup of coffee (or perhaps a glass of scotch), settle in, and lets get to it. Photo by @ederpozo   SLAs Over the past 20+ years of working in the Support/CRM space, I’ve worked with a number of organizations that want to enforce SLAs (service level agreements) in their Support app. Example SLAs All cases must be responded to within 2 business…

Replacing Disparate Field Service Software with Dovetail Mobile

Dovetail Mobile
July 5, 2016 Clarify SupportMany organizations who utilize Amdocs Clarify or Dovetail CRM also employ field based specialists to support everyone and everything from end customers, smaller satellite offices, clinics, retail store fronts, to various campuses or colleges associated with a larger, central university perhaps. They could be IT technicians, seasonal staff, lab support, just about any type of field deployed employee.When the deployment of field personnel reaches a point of needing to be managed on a sizeable scale, technology typically comes into play. There are more than a few providers offering this type of technology, but is the use of these specialty offerings simultaneously creating a rash of ROI killing effort on the backend? Is it tied directly into the CRM where you’re already managing cases and tracking work and workflow? If not, is this causing disparate cross-functional reporting and/or increasing reporting…

Case Aging, including “pauses”

October 7, 2011 Over the years of working with Clarify, I’ve seen a request come up a few times for calculating case aging, including “pauses”.   It’s easy to calculate a total case age. For open cases, it’s the difference between now and the time the case was opened. For closed cases, it’s the difference between case open time and case close time.   But what about the workflows where a case can be paused? For example, the customer may go on vacation, or any other myriad of reasons where we want to pause the clock on the case.   The common approach to this from an application standpoint is to have a new case Status value of Paused (or something similar), so that we simply change the status to Paused to pause the case, and then change it to something else to…

SLA Monitoring

August 31, 2007 One of the common tasks for a support/call center manager is making sure the team is living up to its service level agreements (SLAs). Pretty much every customer I've ever dealt with has different SLAs. As you can imagine, there's a zillion ways for companies to setup and track their SLAs.   Example SLAs:   All cases must be responded to within 2 business hours All Urgent priority cases must be responded to within 1 hour regardless of business hours All cases must be responded to within the phone response time as stated on the contract All cases must be closed within 5 days. All subcases of type "Hardware Upgrade" must have a technician onsite within 36 hours. All new cases for a Gold level customer must get a call back from a senior tech within 1 hour. An initial response…