The step I'd add is writing the rule down before the next outage, as a short table you can paste into a macro. Something like: not active during the window = apology plus what changed, no money; lost part of a working day = credit of about a quarter month; failed job or missed deadline = refund of that month, or a bigger credit if they want to stay. Then check each ticket against the same three questions: were they active in the window, did anything fail for them specifically, and are they already cancelling? Log the answer and the amount in the ticket so the second customer gets the same outcome as the first. One more point: with annual plans, a credit can sit unseen for eleven months, so offer a refund or an extension of the term instead. Reply the same day, even if it's only to say you're checking their account.
Writing the rule down before the next outage is the step most people skip, and I skipped it in the post too. The annual-plan point is a good catch: a credit nobody notices for eleven months doesn't feel like compensation. Logging the amount in the ticket so the second customer gets the same answer as the first is the part I'd copy first.
Charlie from xSquads
The step I'd add is writing the rule down before the next outage, as a short table you can paste into a macro. Something like: not active during the window = apology plus what changed, no money; lost part of a working day = credit of about a quarter month; failed job or missed deadline = refund of that month, or a bigger credit if they want to stay. Then check each ticket against the same three questions: were they active in the window, did anything fail for them specifically, and are they already cancelling? Log the answer and the amount in the ticket so the second customer gets the same outcome as the first. One more point: with annual plans, a credit can sit unseen for eleven months, so offer a refund or an extension of the term instead. Reply the same day, even if it's only to say you're checking their account.