(blue star) CONTEXT / SCOPE

(blue star) IMPACTED TEAMS

(blue star) GLOSSARY

RESOURCES

(blue star) TABLE OF CONTENTS


The Escalation Process

Escalations can be worked on to achieve a potential save. We can consider an account to be escalated if one or more  of the following is true:

Churn Codes

To further understand the reasons behind escalations, please read below. This is accurate churn coding for escalation cases that allows us to interdict churn risk early, and understand where customers are having trouble.

Accurate churn coding within Salesforce cases is pivotal for our Customer Success team and all of MedTrainer. This detailed coding system enables us to promptly identify and address potential churn risks, enhancing our ability to mitigate them effectively. By categorizing churn reasons accurately, we can:

  1. Trigger Targeted Risk Mitigation Playbooks: Initiate specific, pre-defined playbooks that are tailored to address the identified risks, ensuring timely and effective interventions.

  2. Enhance Reporting and Forecasting: Provide precise and detailed churn reasons, facilitating more accurate churn reporting and forecasting, which supports strategic decision-making and resource allocation.

  3. Deliver Product Feedback: Collect actionable insights regarding product-related issues, enabling us to communicate specific feedback to our product teams and drive continuous improvement.

The comprehensive churn coding system covers various aspects including product-related gaps, service issues, pricing concerns, and customer-specific changes, ensuring a holistic understanding of customer challenges.

Escalation/Cancellation Reason

Churn Reason (Escalation/Cancellation Reason)

Description

Secondary Reason - multiselect list

Product-Related

Feature Gaps

Missing features that the customer requires.

  • Reporting

  • Integration

  • Customization

  • Course Content

  • Unmet Expectations (Miscommunication)

  • Unfulfilled Value

  • Poor User Experience

Service-Related

Support Issues

Problems with customer service or technical support.

  • Slow response

  • Unresolved issues

  • Lack of expertise

  • Bad Communication

  • Lack of training

  • Delayed OB/Implementation

Price-Related

Pricing Issues

Customer finds the pricing too high or not value for money.

  • Too expensive

  • Hidden fees/Unrecognized Charges

  • Price increase

  • Annual Increase

  • Past-Due

  • Terms and Conditions

Customer-Related

Company Changes

Organizational changes affecting the customer’s needs.

  • Bankruptcy

  • Acquisition

  • Going out of business/Retiring

  • Owner/Champion change

  • Low Usage

  • Ghosted

Competition-Related

Competitor Switching

Customer switches to a competitor’s product.


Escalation Conditions

To handle and ideally solve these kinds of escalations, please follow the steps below:

  1. If an account is past due, please follow this workflow, as stated in the https://medtrainer.atlassian.net/wiki/pages/resumedraft.action?draftId=4155047996&draftShareId=9965406d-e59c-4912-948c-b4a323803422 SOP.

note

Make sure to follow the usual escalation process: reaching out to the main point of contact daily. Establish communication with them, and take advantage of that conversation to mention the past due status (if applicable). Then, please refer them back to Jennifer Simon from the Billing Department (if applicable). 

Make sure to follow the usual escalation process: reaching out to the main point of contact daily. Establish communication with them, and take advantage of that conversation to mention the past due status (if applicable). Then, please refer them back to Jennifer Simon from the Billing Department (if applicable). 

  1. If the escalated account has the FMC service, request your respective TL to create an escalation slack channel, in order to keep the FMC team informed about the escalation details, even if they aren't related to the FMC product itself.

Creating an Escalation Case

There are two possible ways an admin can escalate. Regardless of which one, the receiving party must create a SF Escalation Case:

Please follow these steps to create the SF Case:

  1. Log into SF and go into the account in question.

  2. In the Cases section, click “New” and select “Escalations”:

20240717-2134-14.6324390.mp4
  1. Fill in the following fields:

20240717-2136-11.2780340.mp4

Make sure to always fill in the “Pending Cancellation Date” filed (which is the Contract Expiration/Renewal Date):

image-20240723-213349.png
note

Once you create the case, this is the case number you will need to have on hand:

image-20240717-213948.png

Once you create the case, this is the case number you will need to have on hand:

image-20240717-213948.png

Working the Case

Once the escalation case is created the CSM and TL must follow the process below:

  1. When reviewing or updating the case, make sure you are in the details tab of that case:

  1. Schedule a call between client and TL (CSM)

  1. Complete call with client and TL (TL)

note

If you scroll back to the top of the details section, you will notice the Escalation Status has updated. 

If you scroll back to the top of the details section, you will notice the Escalation Status has updated. 

  1. Resolution Approval (Accounting): The Accounting Department will be the one to deny or approve the resolution offer.

Special Mention: Explicit Escalation

When the customer escalates (i.e. they have explicitly complained), schedule a meeting with the Customer and TL within 24 hours. If the accounts are unresponsive, before deciding the resolution, we must try to contact them for at least 10 consecutive days in the following structure: 

note

Remember to use the (blue star) Outreach features so calls, emails, and meetings appear in the in SF (blue star) accounts.

Remember to use the (blue star) Outreach features so calls, emails, and meetings appear in the in SF (blue star) accounts.

image-20241011-193118.png

If the account is past due/delinquent, please refer back to the MT-CS-021: Delinquent Accounts: Payment Reminders and Collections SOP for the full process

note

Escalated accounts cases in Salesforce (blue star) need to be updated daily, filling in the “Escalation Notes” section, using the following structure: 

(blue star) If responded and needs finance approval:

Escalated accounts cases in Salesforce (blue star) need to be updated daily, filling in the “Escalation Notes” section, using the following structure: 

âť— If responded and needs finance approval:

Following Up

If the customer does not accept the resolution presented, the TL will renegotiate and review it again in the weekly finance meeting.