Service Recovery Alerts
Service Recovery alerts are generated automatically in response to a customer giving an overall satisfaction score below the Service Recovery Threshold configured in your Preferences (see here to learn more).
The purpose of the alert is to prompt the Support Lead (and Also Alerts) to contact the customer in order to acknowledge their concern, understand what happened and, if possible, make things right.
When this is done well, a complaint can be turned into a compliment and the customer converted from a Detractor into a Promoter. This practice is known as Service Recovery.
Contacting unhappy customers is a Net Promoter best practice. Every Apple retail store in the world does it. You can read an article here on why you should contact unhappy customers and how to have that conversation.
An alert consist of two things - an SMS message and a corresponding Service Recovery Report, emailed as a PDF attachment.
If there is at least one customer who has indicated they are unhappy on any given day, the relevant Support Lead(s) (and any Also Alerts) will receive a single text message the next day informing her of the number of unhappy customers there were.
At the same time, a corresponding Service Recovery Report will be emailed to the Support Lead(s) (and any 'Also Alerts') which provides the survey feedback given by the customer(s).
The Service Recovery Report includes a hyperlink for each survey response for entering Service Recovery Notes - a record of any conversation had with a customer as a result of service recovery.
Alerts are generated based on unhappy customer responses received in the 24 hours prior to your Alert Time. For example, if an unhappy customer completes a survey at 8am on Monday, and your alerts are scheduled for 9am, you will get alerted about that feedback at 9am on Monday.
In your Preferences in the Portal you can set 'Weekend Alerts' to 'No'. In this case, any SMS alerts that would normally be sent on Saturday or Sunday will be deferred for delivery on Monday. This setting only affects the timing of the SMS. Service Recovery reports will still be emailed on the Saturday or Sunday.
Surveys that have been submitted with invalid data (e.g. with an unknown or missing Support Group Code or Segment Code) will not generate an alert unless they are fixed before the alert time on the next day (regardless of your 'Weekend Alerts' setting).
The Service Recovery Report
When a Support Lead is notified via text message that there was at least one unhappy customer the previous day, a Service Recovery Report is emailed to them which provides more information on the feedback that was received.
The Service Recovery Report includes service recovery opportunities for all the Support Groups that a Contact is associated with, either as a Support Lead or Also Alert.
The Service Recovery Report provides:
- The date the feedback was received.
- The customer who provided the feedback and the Customer Segment they belong to (if provided).
- The agent who resolved the ticket (if provided) and the Support Group the ticket was assigned to.
- The ticket number that the feedback is concerning. This will be a hyperlink to the ticket in your Customer Support Software if a URL prefix has been setup in the Portal.
- The experience factors chosen by the customer in response to Q2 of the survey and their overall rating.
- Any verbatim feedback shared by the customer in response to Q3 of the survey.
- Clicking on the pencil icon against the survey displays the Service Recovery Notes dialog box for this survey response.
- Clicking on the pencil icon in the report title displays the Service Recovery Notes dialog box for all the survey responses in the report.
- The name of the report recipient and the 24 hour period covered by the report.
If you click on a hyperlink in the Service Recovery Report to access the Service Recovery Notes dialog box, but see an error message - "Your URL is formed correctly but we couldn't find any surveys that matched the criteria in your URL" - there are two possible reasons:
- After the report was produced, the customer has submitted another survey for the same ticket number. The more recent survey submission will have replaced the original submission.
- After the report was produced, the CIOPulse admin has used the Reassign Transactional Surveys function to assign the feedback to another Support Group.
Service Recovery Notes
Service Recovery is the practice of 'making things right' after a customer has had an unsatisfactory experience.
CIOPulse can be used to record notes on the service recovery actions taken by your Support Leads in response to feedback from an unhappy customer.
The dialog box for recording Service Recovery Notes for a survey response looks like this:
- Survey response details, including the overall score and feedback from the customer.
- The 'Ticket' label will be underlined and hyperlinked to the ticket record in your customer support system (if you have set this hyperlinking up).
- The name of the person entering the notes. This defaults to the first of these that apply: The name of the person who is logged on; or, the name of the person the Service Recovery Report was sent to (only when the dialog box is accessed via the pencil icon next to the report title); or, the Support Lead of the Support Group. But the name can be edited to any name. This field is not validated (apart from being mandatory).
- If you speak to the customer, tick the 'Spoke to customer?' checkbox. If you attempted to speak to the customer but were unable to (left a voicemail), leave this box blank.
- Enter your notes here.
- All three buttons save the notes entered in the Your Notes field. Only the highlighted button(s) can be clicked. The buttons that are highlighted will depend on how you accessed the Service Recovery Notes dialog box (see below).
- A log of any previously entered notes. Previous notes cannot be edited. Notes will say "(Spoke? Yes)" or "(Spoke? No)" depending on the 'Spoke to customer?' checkbox
All three buttons save the notes that have been entered. If you do not wish the notes to be saved, either delete all the notes in the Your Notes field or close the tab in your browser.
Once saved, notes cannot be edited.
How to access the Service Recovery Notes dialog box
There are four ways to access the Service Recovery Notes dialog box for a survey response.
- From the daily Service Recovery Report. Click on the pencil icon hyperlink at the report level or for an individual survey.
- From the Survey Responses Report. When the report is accessed with the
srnparameter in the URL, with a value of anything exceptsrn=n. Click on the pencil icon hyperlink for any individual survey. - From the Survey Responses interactive dashboard (
&dashid=SRES), there is a hyperlinked column named "SR" that takes you to the Service Recovery Notes dialog box. - Via bookmark or URL:
https://app.cio-pulse.com/service-recovery-notes?cpc={your Client Portal Code}
You must use any two of these three parameters, prefixing each parameter name with a &:
-
rgidThe Support Group Code of the Team or Department for whom feedback has been received. -
dateThe date feedback was received,yyyy-mm-dd. The date must be in the time zone set in your instance preferences. -
tidThe ticket ID of the ticket that feedback was received for.
When tid is specified (together with either rgid or date), the Service Recovery Notes dialog box will be displayed for this one survey response. The Previous and Next buttons will be inactive.
When rgid and date are specified together, the Service Recovery Notes dialog box will display the first survey response received on that day that requires service recovery. If there is more than response that requires recovery for that day, the Next and Previous buttons can be used to move through that feedback.
Viewing Service Recovery Notes
There are three ways to view the Service Recovery Notes for tickets:
1. By accessing the Service Recovery Notes dialog box as described above. Any notes that have already been entered for a survey will be shown at the bottom of the Service Recovery dialog box.
2. On the Survey Responses Report by using the srn parameter when requesting the report. Notes will be displayed when the srn parameter value is anything except n (srn=n tells CIOPulse not to show Service Recovery Notes on the report)
3. On the dashid=SRES interactive dashboard, there is a hyperlinked column named "SR" that takes you to the Service Recovery Notes dialog box. The latest Service Recovery Notes are also appended to the customer's feedback shown in the "Comments" column.
On both the Survey Responses Report and the interactive dashboard, surveys can be filtered according to their Service Recovery information. For the Survey Responses Report this is done using the srn parameter in the URL. For the SRES interactive dashboard, this is done by using the ServiceRecoveryNotes filter.
The table below describes the effect of these filters:
| Filter effect |
Survey Responses Report srn= parameter value |
SRES Interactive DashboardServiceRecoveryNotes filter setting |
|---|---|---|
| Display all surveys, showing any Service Recovery notes | y | (no filter set) |
| Display all surveys with a rating <= your Service Recovery Threshold | r | All needing recovery |
| Display all surveys with a rating <= your Service Recovery Threshold and that don't have any Service Recovery (SR) notes | x | No SR notes |
| Display all surveys that have Service Recovery (SR) notes |
w | With SR notes |
| Display all surveys that have Service Recovery (SR) notes, and where none of the notes for the survey have the 'Spoken to customer?' checkbox ticked |
v | SR notes - Never spoken |
| Display all surveys that have Service Recovery (SR) notes, and where at least one of the notes for the survey have the 'Spoken to customer?' checkbox ticked |
s | SR notes - Has spoken |
Data on the SRES dashboard is cached and updated every 15 minutes. If you add Service Recovery Notes to a survey response, it may take up to 15 minutes for the date in the 'SR' column to be updated on the SRES dashboard.
There is an interactive dashboard for viewing Service Recovery performance by Support Group, e.g. to see which Support Groups are performing service recovery and how quickly. This can be accessed using dashid=SRP
When a duplicate survey is received (a survey is completed again for a ticket), any Service Recovery Notes that were entered against the first survey response is automatically moved to the new survey response.
