Solve it once
A customer we'd refunded and shown the door tried to sneak back in months later under a new email. It should have cost forty-five minutes. Our systems made it four.
Here’s what actually happened.
Last winter a customer blew up on us and demanded a refund when their subscription renewed. They had been notified ahead of time. After renewal, they asked for continued access for free.
We granted the refund, and closed the account. Months later they came back asking to be let back in. We held the line, still closed.
Then this week they turned up again, trying to sign up under two different emails to get around the account we’d shut.
So a thorny one comes in. And we need to triage.
Who is this?
What’s our history?
Did we already make a call here? What was it?
What do we say, what do we leave out?
Where does it get logged so no one’s blindsided next time?
A year ago that would have taken 45 minutes. Not productive.
Today, it took four minutes.
The Company brain had the whole history in one place: the blowup, the refund, the standing call we’d already made on this exact person, written down where anyone would look. Nothing to reconstruct.
The Customer ops engine had the rest: the house voice, and the way a closed account trying to walk back in gets handled. What to say, and how, was settled long before they messaged.
The judgment call wasn’t judgment anymore. Invoke the system. Confirm the standing position still holds. Log the new attempt. Tell the team in one line. Done.
And it wasn’t a one-off. Anything that repeats runs this way now: solved once, written down, close to free every time after. The cost doesn’t recur. It compounds the other way.
A business that remembers itself, so three people put out the work of twenty. Nothing costs full price twice.