AT&T Logic Asset
A sanitized workflow map showing how I handled a high-friction cancellation call caused by a billing error. This is the logic behind retention work: stabilize emotion, verify facts, protect trust, and choose the right save path without creating more risk.
Start Node
Incoming state: elevated emotion, low trust, strong intent to cancel. Objective: lower escalation temperature fast enough to gather facts, then move into a fact-based retention decision.
Method
Decision Flow
Acknowledge the billing pain, empathize with the disruption, and reassure the customer that the issue will be reviewed before any irreversible decision is made.
Check service status, plan history, prior adjustments, recent changes, and whether the charge came from provisioning error, usage misunderstanding, or previous save offer overlap.
If the billing error is valid
Confirm the mistake, set expectations, apply or request the proper credit path, restate the corrected monthly impact, and ask for permission to continue service after the fix.
If the charge is valid but trust is weak
Reframe around fit: review usage, pain points, and service mismatch, then offer a more suitable plan, service adjustment, or retention package instead of a blanket credit.
Ask whether the concern is now resolved enough to remain on the account. If not, identify the remaining blocker and repeat the logic only once with sharper focus.
Document what triggered the cancellation, what was verified, which save path was used, and what next-contact agent should watch for if the account calls again.
Credit vs Upgrade Logic
Why This Works