Cancel-to-save: role and approval matrix
When a customer wants to cancel, the team needs to know at once who may offer what. Without that, one handler gives a free month and another gives nothing. This matrix sets out who prepares each step, who approves it, what proof is needed and what happens if approval is refused. The owner fills it in once, and the retention specialist, account owner and approver follow it.
When to use it
Use it when you set up your cancellation process, when a new person joins any of these roles, and whenever you launch or withdraw an offer. Use it also to settle disputes, for instance when a handler says they thought a discount was allowed.
The template
The first table covers the steps. The second names the people and sets the limits.
| Decision or step | Prepared by | Approved by | Required proof | If rejected |
|---|---|---|---|---|
| Record the request to cancel or pause | Retention specialist | Account owner | Cancellation request record | Request returned for the missing detail, customer told it is being handled |
| Record the reason given | Account owner | Approver | Customer statement | Reason re-confirmed with the customer by call or message |
| Make a save offer | Retention specialist | Approver | Approved offer, within the list and limit | No offer is made and the customer is told the standard options |
| Accept the customer's decision | Retention specialist | Account owner | Consent record | Decision stands. Nobody may override the customer |
| Record the outcome and any win-back | Account owner | Approver | Outcome record with the follow-up date | Outcome corrected before the case is closed |
| Role | Person | Stand-in | Limit of authority (₹ or period) | Cannot approve |
|---|---|---|---|---|
| Retention specialist | Offers only from the approved list | Any offer above the list | ||
| Account owner | Discounts up to a value you set per customer | Own handled cases | ||
| Approver | Offers above that value, up to a stated amount | Cases they handled themselves |
How to fill it
- Prepared by and Approved by: always two different people for the same step. In a small team, the owner is the approver.
- Required proof: name the record, not just "evidence".
- If rejected: say what the customer is told and by whom, so that rejection does not mean silence.
- Person and Stand-in: write real names. The stand-in must be someone able to say no as well as yes.
- Limit of authority: set limits in rupees or months of free service, for example up to ₹1,000 or one month. Choose limits that fit your margins.
- Cannot approve: list what each role may never sign for, so nobody approves their own case.
Refund approval, credit notes and rules on contacting customers can be fixed by law. Check the current rule on the official portal or with your CA before acting.
Example row
| Decision or step | Prepared by | Approved by | Required proof | If rejected |
|---|---|---|---|---|
| Make a save offer | Retention specialist: Kavita Shah | Approver: Rohit Mehta | One free month on the ₹2,300 plan, approved on 4 Nov | Kavita tells the customer the standard options; the case continues as a cancellation |
Stand-in note: while Rohit is travelling from 10 to 14 Nov, offers up to ₹2,300 are approved by the owner, Anita Rao.
Review and sign-off
- The owner signs the matrix and each named person initials the line that applies to them.
- Review it every quarter and whenever you launch an offer or change a person in these roles.
- Escalate to the owner when an offer is made above anyone's limit, when an approver is absent with no stand-in, or when someone is asked to approve a case they handled.
Keeping it up to date
- Date each version and keep earlier ones, so you can show who held authority when a past case was handled.
- Keep old versions for the period your CA or the law requires.
- Tell all affected staff in writing when the matrix changes and note the date they were told.