In January 2026, a $145 charge appeared on my UPS account that was not mine. Nine months later, UPS closed the account for non-payment of that same invoice — the one they had already agreed I never owed.
Nobody at UPS decided to lose me. That is the problem, and it is the reason this story is worth your time.
I have shipped with UPS for decades. Not occasionally. Constantly. Books, workbooks, kits for keynotes, materials for clients on three continents. If loyalty were a frequent-flyer program, I would have been platinum for life.
What Actually Happened
January. A $145 charge appeared on my account. It was not shipped from my address. It was not shipped to any client I have ever had.
So I called. And called. Dozens of calls, and an amount of time on hold I could have used to write another book. Every person was polite. Every person was powerless.
August. The charge was finally removed. You’d think that was the end. It wasn’t.
Without telling me, UPS had been charging interest on the phantom invoice the entire time. More calls. The interest came off too.
September. UPS closed my account. Reason given: non-payment of the January invoice. The one they had already agreed was never mine.
I was routed to a department. Twenty minutes on hold. The person who finally answered was not in my region and had no access to my account. Transferred again. On hold again.
Nine months. One wrong charge. Zero people who could fix it.
This Is Not a UPS Story
I could tell you UPS is broken. That would be satisfying and useless. UPS has good people, a great logistics engine, and a billing system that cannot see the customer standing behind the invoice.
Here is what actually happened. Five separate systems each did exactly what they were built to do. Billing billed. Collections collected. Interest accrued. Account status flipped. Routing routed. Every one of them performed correctly.
That is THINKRUPTCY™: when the thinking behind the process went bankrupt years ago, and nobody noticed because the process kept running.
So here is the question I want you to sit with. What about your company? Which of your systems is, right now, doing exactly what it was told to do to a customer who has been with you for twenty years?
You won’t find out by asking your team. They’ll tell you everything is fine. They told UPS that too.
Five Steps So Your Customer Never Lives This Story
These are not about being nicer on the phone. They are about changing what the system is allowed to do without a human in the loop.
1. Make the systems talk before they act
The billing system removed my charge in August. The collections system never got the memo. The account-status system never got the memo. Three databases, three versions of the truth.
Ask one question in your next operations meeting: when a dispute is opened on an account, does every downstream system know within the hour? Not by email. Automatically.
AI Sauce: This is the lowest-hanging fruit in the building. A simple agent watches for a “dispute opened” event and freezes interest, collections, and account-status changes until the dispute closes.
2. Weight the customer, not the invoice
My account was closed over $145 while my lifetime spend with UPS would buy a very nice car. No one weighed those two numbers against each other because no one was asked to.
Set a rule: any adverse action on an account — interest, suspension, closure — above a certain customer-value threshold requires a human to approve it.
AI Sauce: Your CRM already knows tenure, spend, and dispute history. Have AI surface a one-paragraph brief before any adverse action: “This customer has been with us 40 years. Are you sure?”
3. Give the first human the power to end it
Every person I spoke to could sympathize. None could act. That is not a training problem. That is a permissions problem, and permissions are a leadership decision.
Pick a dollar figure. Give every frontline person the authority to resolve anything under it on the first call. No transfer, no ticket, no callback.
AI Sauce: Use AI to draft the resolution note and log the credit in real time while the agent is still on the phone, so “I’ll take care of it” means done, not submitted.
4. Kill the region wall
Twenty minutes on hold to reach someone who could not see my account because I was in the wrong region. The customer does not have a region. The customer has a problem.
If your routing sends a customer anywhere that can’t serve them, that’s not a queue, it’s a trap. Audit every transfer path.
AI Sauce: Before the call routes, AI reads the account, identifies the issue type, and sends the call to the one queue that can actually close it.
5. Tell the customer before the customer finds out
I found out about the interest by accident. I found out about the closure by trying to ship. Every surprise was UPS’s to prevent and mine to discover.
Any change to a customer’s account status, any new charge, any fee, gets communicated proactively, in plain language, with a name attached and a way to reply. Silence is not neutral. Silence is where loyalty goes to die.
AI Sauce: An agent drafts the notice the moment the status changes: “James, we’ve applied interest to a disputed charge. If you believe this is in error, reply here and we’ll pause it.” Human reviews, human sends. Ninety seconds. Nine months of my life saved.
The Takeaway
UPS did not lose me on any single call. They lost me in the space between systems that were never asked to think about the same customer at the same time.
Go find that space in your company. It’s there. It’s quiet. And right now, it’s doing exactly what it was told.
Shift Happens!® The only question is whether you see it coming.
James D. Feldman, CSP is a keynote speaker, business strategist, and AI implementation consultant. He doesn’t explain AI. He solves your problem with it. This account describes his own experience as a UPS customer.
Read the full THINKRUPTCY™ framework or start a conversation.
