glossary Recurring + delayed revenue Revenue OS - CRM, Lifecycle & Follow-Up

Cancellation Reason Code

A cancellation reason code is a mandatory field written when an account moves into a cancelled state. It converts a status change into a revenue event with a cause attached. Without one, the cancellation record holds a date, an acting user and possibly a free-text note, which means the business can count its losses but cannot group them, cannot bind a save offer to a specific cause, and cannot tell a price objection apart from a service failure or from a customer who simply moved away.

Definition

The code is one part of a three-part transition. A cancellation event should carry a cause value drawn from a closed list, an outcome for whatever alternative was offered, and a scheduled follow-up state. The list has to be short enough to be chosen accurately under conversational pressure and specific enough to separate causes that imply different responses. Where the field is optional it is populated inconsistently and cannot be trusted; where it is free text, classification becomes a manual reading exercise performed long after the conversation. Making it mandatory at the transition is a system design decision rather than a training one.

Why it matters

Retention work is unassignable without a cause dimension. A cancellation attributed to price implies a plan or offer change; one attributed to a missed delivery or visit implies a scheduling fix; one attributed to a move implies neither and arguably belongs in neither denominator. A single count blends all three and makes any programme built on it a guess. The code is also the join key for everything downstream - a win-back cadence, a save-offer comparison, or a read of how losses differ between routes, cohorts and service lines.

Explore related entities

[CLAIM BOUNDARY] A reason code records what was said at the moment of cancelling, which is not necessarily the underlying cause. Codes support grouping and routing; they do not establish why customers left, and no code distribution should be read as a measure of what was recoverable.