The ping that never became a ticket

It’s Thursday, 18:22. An executive’s laptop won’t join the board pack on a hotel Wi-Fi network that has been hostile all week. Intune shows the device as healthy and the meeting starts in thirty-eight minutes. They do what busy people do when the portal feels slow and the stakes feel high: they message the Team Lead who “always sorts it”.

You’re in the middle of a handoff to APAC, but you answer anyway. You reset, rejoin and reassure. The board pack opens. Nobody files a ticket, so there’s no RCA, no knowledge article and no SLA clock. All that exists is a quiet win in a private chat and an analyst who will have to be reachable at 22:00 again next time.

On Friday morning the same symptom lands on the main desk as three separate “urgent” chats from people who’ve heard there’s a back door. Your queue looks calm and your week doesn’t.

That’s a shadow helpdesk, and it grows out of good intentions.

VIP support is fair. The side channel isn’t.

I’ve led IT Service Desk work across EMEA and APAC on a follow-the-sun model, in places where executive travel, time-critical briefings and high-stakes operations are normal. VIP and executive support isn’t vanity. The risk is real and minutes matter. Boardrooms, incident bridges and travellers on hostile networks won’t wait politely for a P3 clock.

The mistake is treating that as permission to build a private second organisation out of Teams DMs, personal mobiles and “just ping me”, with heroics that never reach Jira Service Management.

Side channels feel kind in the moment. Over a quarter they turn into undocumented work, burned-out analysts, skipped RCA and an unfair queue for everyone else. The executives still get uneven outcomes too, because the result depends on who answers the phone and not on any designed entitlement.

Green SLAs on the main desk can sit alongside a VIP experience that’s brilliant or chaotic depending on the day. A shadow path makes that worse, because the work that most needs measuring is the work that never appears in the numbers.

What a proper VIP path holds

A healthy VIP model is a named path inside your ITSM tool. The desk can see it, leadership can measure it, and it’s fair to the rest of the queue. It’s very different from a secret rota of favourites. In practice it has five parts:

  • Clear entitlement. Who counts as VIP, for what, and for how long. It should be role-based, reviewed and published, so it doesn’t grow into a list of whoever is important this week.
  • A named path in Jira Service Management. Dedicated request types or priorities, a VIP queue or skill group, and routing that someone can explain in one sentence. The executive still gets speed and the organisation gets a record.
  • SLAs and XLAs together. Faster clocks where the risk justifies them, with experience checks beside them: time to useful work, reopen rate, “explained twice”, and whether the person felt looked after across a handoff.
  • Handoffs that carry the story. VIP requests don’t skip the baton. If London starts one, Singapore needs the symptoms, evidence, attempts, next action and user context, and “exec called Chido, see chat” doesn’t qualify.
  • Knowledge back to the main desk. If a VIP fix could help a hundred colleagues, it becomes an article, a known error or an Intune change. Privilege that never teaches the desk anything is just expensive silence.

A VIP arrangement is a contract: entitlement, path, measure, handoff, learning. It shouldn’t depend on a personal favour.

How it goes wrong anyway

You can publish a VIP portal and staff a senior queue and still teach the organisation that the real route is a DM. Executives conclude that tickets are for other people. Analysts learn that saying no to a ping is a career risk. Managers defend “we take care of our leaders” while the main desk absorbs the overflow without any context.

Nobody means harm. The system is rewarding speed with no check on the wider cost. Assuming that a private channel gives better support is one more thing to test, and you’ll often find it doesn’t.

Fairness doesn’t mean identical speed for every request. It means transparent rules. A CFO in the middle of a close can reasonably outrank a password reset. What they shouldn’t outrank is the need for a ticket, an owner and a lesson for the next person.

Shadow helpdesks burn your best people first. They also leave executives exposed when that one analyst is on leave, on a plane, or already in the middle of a major incident. A designed VIP path survives the rota, and a hero-based one doesn’t.

Try this week

Don’t start by buying a VIP tool. Start by finding out what already happens. Pick one week and list every VIP or executive contact that arrived outside the ITSM tool: Teams, mobile, hallway, “quick favour”. For each one, ask:

  1. Was there a clear entitlement, or only urgency and familiarity?
  2. Did the work leave a record another timezone could pick up without a callback?
  3. Did the fix feed knowledge back to the main desk, or was it a quiet win for one person?

Then design one named VIP path for the next five genuine VIP requests: an entitlement rule, a Jira Service Management route, an SLA/XLA pair, a handoff note and a knowledge action. Coach the first one live with your team, and recruit one executive sponsor who’ll use the proper door in public.