Escalation and Kudos Process
Article ID: 1048
You may receive an interaction from a patient who requests to speak with a Supervisor or Team Lead. Keep the following in mind when handling these interactions:
For Escalations
-
If the patient is escalating for an issue that our department is unable to resolve, advise the caller you will escalate the matter to their HME. Remember, supervisors and team leads have access to the same level of information as a Client Services Representative. See Contact Solutions Operation Specialists (SOS Team) (ID: 3604) for information regarding this process.
-
Ensure you have taken all possible steps to assist the patient without getting a supervisor's involvement. This includes reaching out to the HME via phone for RRS calls unless otherwise stated in Salesforce.
For Escalations and Kudos
-
You MUST keep your Salesforce case open and provide the Case Number to the person taking the escalation. Do NOT close your case, as notes are required to be added after the leadership team has spoken with the patient.
-
When you connect with a supervisor or team lead in the Teams Chat, explain the situation and what steps you have taken (if any) to resolve the patient's concern, the patient details, the Salesforce case number, and warm transfer the patient as described in Transfer Calls in RingCentral (ID: 6018) and RingCentral Call Transfer Cheat Sheet (ID: 4816).
NOTE: If you are not able to connect with a Supervisor or Team Lead within 2 minutes of placing the patient on hold, explain to the patient that no supervisor is available at the moment. However, a supervisor will review the issue, and contact the patient back. Confirm the best number for your supervisor or team lead to call the patient back. Email the case number to ResupplyPatientCareLeadership@ResMed.com. If a patient asks when to expect a callback, advise they will be contacted before the end of the next business day.
Escalations
Escalate a patient interaction as follows depending on whether you have a Patient Care or Resmed ReSupply interaction.
Patient Care Escalation
-
Use the Teams chat to request assistance from a Supervisor or Team Lead
-
Create a Salesforce case with the following field settings:
See Create a Salesforce Case (ID: 784) for details on creating cases.-
Case Owner: Leave this in your name.
This allows you to track and ensure the case is completed and gives you credit for the call in your case-to-call ratio. -
Status: In Progress
This allows you to track and ensure the case is completed. Do NOT close your case. -
Support Category: Escalation
-
Saved Reason: N/A
-
Subject: Escalation Call Back Request
This allows for your case to be easily located by the agent following up. -
Description: Use the following Escalation Callback
-
Patient is requesting a supervisor callback for (enter reason)
-
Alternate Contact Number:
-
Best date and time for callback:
-
-
Resmed ReSupply Escalation
-
Use the Teams chat to request assistance from a Supervisor or Team Lead
-
Create a Salesforce case with the following field settings:
See Create a Salesforce Case (ID: 784) for details on creating cases.-
Case Owner: Leave this in your name.
This allows you to track and ensure the case is completed and gives you credit for the call in your case-to-call ratio. -
Status: In Progress
This allows you to track and ensure the case is completed. Do NOT close your case. -
Support Category: Escalation
-
Subject: Use the appropriate option for the call
-
Description: Include the following information
-
The patient is requesting a supervisor callback for (enter reason)
-
Alternate Contact Number:
-
Best date and time for callback:
-
-
CSR Kudos
If the patient has an email on file, they will receive a CSAT Survey via email after every call and email. They can fill this out with feedback about you or the program itself.
All surveys come into Leadership for review and WOW Factor submission.
Escalate all CAT 1 Patient Care Calls
All CAT 1 calls to Patient Care must be escalated. See CAT 1 Escalation Process (ID: 3417) for details on how to escalate CAT 1 calls.
- Article Metadata
- The following table provides management and control details about the current published version of this article.
Prepared By
Ryan King, Hannah Vincent
Reviewed By
Ryan King Process Owner
Diane Clarke
Subject Matter Expert
Nader Omar
Visibility
Internal - ACE
Revision Workflow
Standard
Archive Date
DAC
DAC1
- Revision History
- The following table summarizes changes for each published version of this article.
Date
Changes
10 April 2025
Removed SubCategory from ReSupply section. (K01793)
25 March 2025
Minor edits for clarity to escalation process. Updated Kudos section to reflect current process. Updated title. (K01699)
12 March 2024
Add tags: escalation, kudos. Update format to the current standard. Incorporate outstanding draft revisions. Revise CSR Kudos section to remove CSAT option. Rework content to instructional steps and remove redundancies and internal cross-references. Fix broken links; replace ININ and Salesforce call transfer links with RingCentral links. Change Article Type from Topic to How-to. Add Summary. Minor revisions for clarity.
13 November 2018
Initial publication. All new content.