Guide
How a software company handles cancellation requests
A cancellation request is the last conversation a customer offers you. Asked well, “why are you leaving?” saves some customers and tells you what to fix for the rest.
Most save desks fail by guessing: a discount offered to a customer who left because the product lacked a feature. Record the reason first, then choose the offer.
Step 1: hear the cancellation where it happens
Send your app’s cancellations to ContactRoll from Settings › Connect your app. With the template’s flow switched on, each one gives the owner a task within four hours.
Step 2: ask why, and record it
Open a request on the Save desk with the customer’s reason, from a fixed list, so the reasons can be counted.
Step 3: offer what fits the reason
A customer leaving on price may take a smaller plan; one leaving for a season may take a pause. Record what you offered and whether they stayed.
Step 4: read the reasons every month
The Save desk counts requests by reason and by offer for 90 days: which reasons come up most, and which offers keep customers.
Step 5: catch trials before they go quiet
In Settings › Trial playbook, switch on the rules for a trial that has gone quiet or not reached first value. Each gives the person’s owner a task, once a trial.
What ContactRoll keeps out of it
The save desk records the conversation and changes nothing in your billing: a discount or pause is made in your own billing system.
The software as a service template sets up the record types, pipeline and flows this guide uses in one step: see what it adds.
Questions
Does the playbook predict who will churn?
No. Its rules are counts of what your app sent, such as days since the last activity, each with the number you chose.
Can I see seats used against seats paid?
Yes. Choose the company field that holds the seats paid for, and the owner gets a task once a month when the people active in the last 30 days reach the share you set.