Nobody Is Angry About the Bug

My job title is Resolution Specialist. What that actually means is that I am the last stop.

If you call QuickBooks support, get an answer that does not work, call back two days later, and still do not have a fix, the next call routes to me. I am the single point of contact from there. I own it until it is genuinely done, even when the fix belongs to a team I do not sit on.

So I spend most of my week talking to people who are already past their limit. Here is what that has taught me.

Distressed is not the same as annoyed

People mix these up, and it leads to the wrong response.

Annoyed is “this is inconvenient.” Distressed is “I do not know what I am going to do.” Those need completely different things from you. Annoyed needs efficiency. Distressed needs to know that someone has a hand on the wheel.

The thing to remember is what sits behind the software. QuickBooks is not a hobby app. When it breaks in the wrong way, somebody cannot run payroll on Friday, or cannot send the invoice that covers their own rent. I spent almost three years in Data Services repairing corrupted company files, and that job rewired how I think about this. You are not restoring a database. You are restoring somebody’s ability to pay their people.

When you understand that, the tone on the other end of the phone stops being a personal attack and starts being information.

The damage is the retelling

Here is the part most support orgs underrate.

By the time someone reaches me, the original problem is usually not what is upsetting them. What is upsetting them is that they have explained it four times. Every handoff resets the story. Every new person asks them to start from the beginning, and every retelling is another reminder that nobody has actually taken it on.

That is where the trust goes. Not in the first failure. In the third explanation.

So the single highest value thing I do all day is boring: I read the whole case before I pick up the phone. Every note, every previous call, every failed attempt. Then I open with a short summary of what I already know and ask them to correct me if I have it wrong.

It costs me ten minutes. It changes the entire call. You can hear someone’s shoulders come down when they realize they do not have to start over.

What actually works

None of this is complicated. It is just uncomfortable enough that people skip it.

Say what you do not know. “I am not sure yet, and here is how I am going to find out” beats a confident guess every single time. A guess that turns out wrong costs you the rest of the relationship. People are far more patient with uncertainty than they are with being misled.

Own the parts that are not yours. Most of my cases need another team to move. That is my problem to solve, not the customer’s. Sending someone to go chase a different department is just a handoff wearing a nicer coat. I go get the answer and bring it back.

Give a real date. Not “soon.” Not “as quickly as possible.” A specific day, and one you can actually hit. If you have to pick between a date they will like and a date that is true, pick the true one. A second broken promise does more damage than the original issue ever did.

Call back when you said you would, even with nothing. This is the one people skip most, and it is the one that builds the most trust. A call that says “no news yet, still on it, I will check again Thursday” tells them they have not been dropped. Silence tells them they have.

Let them finish. When somebody is venting, the instinct is to jump in with the fix as soon as you spot it. Do not. They will not absorb a word of it until they believe you actually heard the problem. Thirty seconds of listening buys you a conversation that works.

Resolved is not a status field

The thing I care about most, and the thing I will keep pushing on, is what counts as finished.

A ticket marked resolved is not resolved. A fix that was deployed is not resolved. Resolved is when the customer does the thing they were trying to do in the first place and it works.

That means following up after the fix lands. Not to close the case, but to confirm. And if it turns out it did not work, going back to whoever owns it and pushing again. That last part is where most processes quietly fall apart, because it is the point where everyone’s dashboard already says success.

Why this is worth doing properly

It would be easy to frame all of this as being nice to people, and it is, but that undersells it.

These customers are the most expensive ones you have. They have already consumed several support interactions without getting anything for it. They are the most likely to leave, and they are absolutely the ones who tell other people about it. Every repeat call is money already spent on a problem that is still not fixed.

Handling them well is not a soft skill. It is the cheapest fix available for a cost you are already paying.

And there is a second thing, which I learned managing a support team before this. Watching what lands in the escalation queue tells you exactly where your product and your process are broken. Repeat callers are not a nuisance to be absorbed. They are the clearest feedback you will ever get, and it arrives for free.

The short version

Most of what makes a distressed customer distressed is not technical. It is the accumulated experience of not being taken seriously. You fix that with attention, honesty about what you do not know, and actually following through, which are not complicated things. They are just things that require somebody to decide the problem is theirs.

That is the whole job, really. Be the person who does not pass it along.