Story

Ten Minutes Before the Executive Call

By Felix Maru · November 4, 2026 · 7 min read

The message came in at 2:47 on a Tuesday afternoon. My account manager: "Can you join a call in ten minutes? One of our clients escalated a ticket to their CEO. My manager is already pulling it up. I need you on."

No context. Just a client name and a ten-minute window.

What I found when I pulled the ticket

I opened the account and searched for open issues. There were three, but only one stood out. It had been open for sixteen days. The description was dry, the kind of language that makes a problem sound smaller than it is: "CRM sync discrepancy affecting support inbox contact records."

I read the history. The issue was real. Their CRM and helpdesk were not syncing contacts correctly. Any contact created in the CRM in the previous quarter was not appearing in the support inbox. When a customer wrote in, the support rep would open their ticket, find no contact record attached, and manually open the CRM in a second browser tab to look up the customer's history. It was a workaround. It worked. But it added friction to every single interaction, and it had been doing so for sixteen days without anyone from our side escalating it internally or committing to a fix timeline.

That was the problem, and I had eight minutes left.

What those eight minutes are actually for

There is a temptation, when you are short on time before a difficult call, to try to solve the problem. I have done it. You read the ticket, start tracing the technical root cause, open a couple of configuration screens, and then you are on the call with half an answer, a head full of half-formed hypotheses, and no prepared framing for the conversation you are actually about to have.

What matters in those eight minutes is not the fix. It is the structure. I opened a notes doc and wrote four things down:

What is broken. The CRM-to-helpdesk contact sync. Any contact created after a specific date is not appearing in the inbox. The team has been using a manual workaround for sixteen days.

When it started. From the ticket, I had a rough date. I could say "sometime in mid-October" without guessing.

Why it has been open this long. I did not know the technical reason yet. But I knew the operational reason: the ticket was categorized as medium priority and had not been escalated internally. Nobody had flagged it as affecting daily operations. That was a gap in how we were triaging issues.

What I own. This is the most important part of the prep. Sixteen days on something affecting every support interaction is too long. That is not a technical failure. That is a prioritization and response failure. I was going to say that plainly, before anything else.

The call started at 3:01.

The call

The CEO was not shouting. He was precise, which somehow made it feel more serious. He said the team had been dealing with this for over two weeks. His reps were doing double lookups on every ticket. He had heard about it three days ago and given us two more days to respond. We had not.

I did not start with the technical explanation. I started with the acknowledgment.

"Before I walk through what's happening technically, I want to say directly: sixteen days on something that's affecting your team's daily workflow is not acceptable. This should have been escalated and resolved much faster. That's on us."

There was a pause. Then he said: "Thank you for saying that."

That pause was the whole call shifting. He was not looking for a fight anymore. He was listening.

I explained the root cause in plain language. The integration between the two platforms used a field called contact_created_date as one of its sync conditions. At some point in October, a platform update on the CRM side had changed how that field was formatted in the API response. The helpdesk integration was still looking for the old format, finding nothing that matched, and skipping those records silently. No error. No alert. Just absence.

He asked two questions. First: why had there been no alert when it started failing? A fair question. The honest answer was that we did not have a monitor on sync volume between those two systems. We had a monitor on whether the sync was running, but not on whether it was creating records at the expected rate. Those are different things. I told him that.

Second: how long would the fix take? I told him I expected to have it resolved by end of business that day, or first thing tomorrow morning at the latest. I had already identified the field format mismatch. The fix itself was a configuration change, not a rebuild.

The call was eleven minutes total.

After the call

The fix took roughly forty-five minutes once I had the right integration config open. I updated the field format mapping in the helpdesk's sync settings, ran a test pull on a small batch of recent contacts to verify they were now resolving correctly, then did a full backfill to bring in everything that had been missed. By 5:20 pm, every contact from the previous quarter was in the inbox. I ran a spot check with the account manager.

Then I sent the CEO a direct email. Not through the account manager. Not through the ticket. Directly to him, since he had been on the call. The email was four sentences: the fix is live, here is what we changed, here is what we are putting in place to prevent recurrence, and I am available if anything does not look right.

He replied in about twenty minutes: "Confirmed, everything is working. Thank you."

Two months later, that client renewed.

What changed afterward

Three things, all from the same root cause.

The first was a sync volume monitor. Any integration between two core business systems now has a monitor on record creation rate, not just on whether the sync job is running. If the rate drops below a certain threshold relative to the previous period, it fires an alert. A silent failure now has a voice.

The second was a triage rule. Any ticket that involves a core workflow integration, something that affects how agents operate on every ticket, gets a 72-hour escalation trigger. If it is not resolved or on a clear fix path within 72 hours, it automatically surfaces to whoever owns the account. No more aging quietly in a medium-priority queue.

The third was a practice I now carry everywhere: when a ticket escalates to an executive, I follow up directly with that person once the fix is live. Not just the account manager. Not just the ticket. The person who had to make the call gets the confirmation in their inbox. It takes two minutes and it closes the loop in a way that account chain follow-ups rarely do.

The thing the ten minutes taught me

When a ticket ages, the problem stops being technical and becomes relational. The CEO was not angry about the sync error. He was angry that his team had been working around a broken tool for over two weeks and nobody on our side had treated it as urgent. The sync error was the cause. The sixteen days was the injury.

Acknowledge before you explain. If you skip straight to the technical root cause, you are defending before you have earned the right to. The acknowledgment is not weakness. It is the door that lets the technical explanation land as useful rather than as an excuse.

The other thing: prep time in a crisis is not for solving. It is for knowing what you own. If I had spent those eight minutes trying to fix the sync error, I would have walked into that call disoriented and defensive. Because I spent them writing down what I was going to say plainly, I walked in ready.

You will not always have the technical answer before the call starts. You will always be able to decide in advance what you are going to own. Those are different preparations, and the second one matters more.

If you have ever found yourself in a similar situation and want to compare notes on how you handled it, reach out. Happy to talk through it.

Share 𝕏 in ✉

Comments