What VIP Support Is, and Is Not: Grace Without a Shadow SLA

Tuesday, 10:40, at Meridian Parts. Jonah is in his second week on a desk of four when the phone rings and it is Priti, assistant to Anders, the managing director. "Anders' laptop won't wake up and he has the bank in at eleven." Carla, who runs the desk, is already standing. "Go now. Take the loaner." Jonah takes the loaner and finds that the laptop is fine and the dock is not. He swaps the dock from the spares shelf and is back at his seat by 10:55 with the bank still twenty minutes away. He had left a ticket about a shared folder half-finished and a warehouse supervisor waiting for a call back. Nobody mentions either.

Afterwards he asks Carla the obvious question. "Do we do that for everyone?" She says no. "Who decided?" She thinks about it, and then says the sentence that this whole series exists to replace: "Nobody decided. It's just how it is." VIP support is the handling of a short, named list of people differently from everyone else, in stated ways, for stated reasons. The rules are written down where the whole desk can read them. Three words carry the definition: short, named, written. Remove any one and what is left is not VIP support but a habit. Habits on a help desk are enforced by anxiety and measured by nobody. This article is part of our VIP & Executive Support series. The series covers what the handling is and is not, keeping priority honest, and discretion around the executive's devices. It also covers board days, the executive assistant, and measuring the cost.

This article covers the honest reasons some people get different handling, then what VIP support is. Next comes what it is not, which is a shadow service level. We cover the list and who decides it, then what the desk says when asked why. Then come the differences made visible in a table, where it goes wrong, a short war story, and the VIP support charter to copy.

Why Some People Get Different Handling

Start with the uncomfortable part, because a desk that cannot say why it treats some people differently will either stop doing it or do it in secret. The second is worse. There are honest reasons, and they are about the organisation's hour, not the person's importance. The first is the cost of the person's hour to the business. When the managing director cannot sign, nothing that needs signing moves. When a sales director cannot present, a contract waits. When the finance director cannot reach the bank, a payment run slips. The hour has the same sixty minutes as anyone else's, but more of the organisation is waiting on it.

The second reason is the audience. An executive's technology fails in front of people: the board, the bank, a client, two hundred staff at an all-hands. The failure costs the hour of everyone in the room and a piece of the organisation's reputation besides. A laptop that will not wake at a desk is a ticket. The same laptop refusing to wake in front of the bank is a story the bank tells about the company for a year. Handling the second differently is not favouritism; it is arithmetic about how many people are watching.

The third reason is confidentiality. The people on the list carry the organisation's most sensitive information on their devices: the acquisition, the redundancy plan, the salary file, the dispute with the regulator. A technician on their laptop sees more than a technician on anyone else's. The handling has to account for that in who is sent and how they behave. The fourth reason is that these people, by and large, cannot wait in a queue because they are not at a desk to wait in one. They are in the car, the airport, the meeting. The ticket that would be a five-minute chat for an analyst is a lost afternoon for a person whose day is fifteen-minute slots. None of these reasons is "because they are senior". Seniority is a proxy for all four, and a loose one. The list should be built from the reasons, not the organisation chart.

What VIP Support Is: Grace and Discretion

VIP support is grace, which is a human answering quickly, and discretion, which is the technician seeing a great deal and saying nothing. That is nearly all of it. Grace in practice means that the first reply is from a person and arrives in minutes. There is a named technician the executive and their assistant know by name. The desk goes to the person rather than asking them to come to the desk or to sit through a remote session they do not have time for. A loaner is kept ready so the fix can be a swap. The work is done at a time the assistant chose rather than at a time the desk found convenient. The handling is faster at the front, where a human picks it up, and more careful in the middle, where the work is done. It is not faster at the back. The fix takes the time the fix takes.

Discretion in practice means the technician asks before opening anything, turns the screen where the executive can see it, searches rather than browses, and closes what they opened. They write a ticket note that records the fault and the fix and not one thing they saw on the way. Discretion is the subject of the third article in this series, Discretion and the Executive's Devices and Data. Here it is enough to say that it is half of what VIP support means and the half most desks forget to write down. Everybody remembers the speed. The discretion is assumed, which is another way of saying it is unstated, which is another way of saying it will be breached by someone who did not know.

Notice what is on that list and what is not. A named technician, a visit, a loaner, a quiet note: these cost the desk a little time and nobody else anything. The handling is different; the rules are the same. The executive's ticket goes in the same queue as everyone's, gets a priority by the same method, and waits behind the same outage. It gets its identity checked before a reset by the same standard. If you run QuerySolv, the assistant's phone call and the warehouse's web form end up as the same kind of ticket in the same queue. Each has its full event history, which is the whole point: the handling differs and the record does not. In any tool, the test is that a stranger reading the queue could not tell the VIP's ticket from the others except by the marker on it.

What VIP Support Is Not: The Shadow Service Level

A service level is a written promise about how fast the desk responds and resolves, usually different for each priority. A shadow service level is the same kind of promise made to some people, never written down, enforced by habit, and measured by nobody. The plain version is explained in SLA in Plain Words; the shadow is the thing this series is named against. Carla's desk had one. Nobody had decided that the managing director's tickets were answered inside five minutes and worked before anything else. It had simply happened once, gone well, and become the standard by repetition. Jonah learned it in his second week without anyone teaching it, which is how you can tell it was a shadow and not a policy.

VIP support is not a jump to the front of every queue. The warehouse supervisor Jonah left waiting had a scanner down and a lorry at the door. A shift of twelve stood behind that ticket. A dock swap for one person, however senior, is a smaller thing by any honest measure of impact. The method for measuring it is in Impact Times Urgency in Practice. The executive's ticket gets a fast human reply, a named technician and a visit; it does not get to go ahead of the lorry. Keeping those two things apart is the subject of No Shadow SLA, the next article in this series. The charter below is where the desk commits to it.

VIP support is also not a secret, not a separate desk, and not a lower standard of security. Not a secret: the list and the handling are written where any technician and any department head can read them. That is because a rule nobody can see is a rule nobody can question, and a rule nobody can question grows. Not a separate desk: there is one queue, one tool, one set of reports, with the VIP tickets as a cut of the same data. That is how they get measured at all. Not a lower standard of security: the executive is the person an attacker most wants to be. So the identity check before a reset is the same check as for anyone, applied with more care rather than less. A desk that waives the check for the chief executive "because we know her voice" has built the one exception an attacker needs. (They do know her voice. They have listened to the investor call.)

The List, and Who Decides It

The list is short, named by role, owned by someone above the desk, and reviewed on a calendar. Short means a desk of four can know every name on it without looking. For most small and mid-sized organisations that is somewhere between three and eight people. A list approaching the size of the leadership team has stopped being a list and become a tier. Named by role means "the managing director, the finance director, the chief executive's assistant", not a set of names that survives the people leaving. The people change; the roles mostly do not.

Owned above the desk means that a named executive sponsor, usually the person the desk lead reports to or the chief operating officer, decides who is on it and signs the charter. The desk proposes, the sponsor decides, and the desk never adds a name on its own, however senior the person asking. This is the single most important rule in the article and the one most often skipped, because adding a name is easy and refusing to is awkward. The sponsor's job is to absorb the awkwardness. "I'd need to put that to Marta, who owns the list" is a sentence any technician can say to any director. It costs the technician nothing because the decision was never theirs.

Reviewed on a calendar means twice a year, or once if the organisation is stable. At that review, the sponsor and the desk lead read the list and the hours it cost and remove the names whose reasons have gone. Lists only ever grow between reviews. The head of marketing was added for the product launch and never removed. The former finance director's successor inherited the handling without the reasons. A regional manager was added "temporarily" during the merger. Each is reasonable on its own day, and the review is the only mechanism that ever takes a name off. Measuring the cost, so the review has a number to look at, is the last article in this series.

Then there is the honorary VIP: the person who is not on the list and expects the handling. Usually that is because they once got it, or because someone at their level has it, or because they are the sort of person who expects things. The answer is the same as for anyone off the list, delivered with the same courtesy as to anyone on it. They get the standard handling, well done, and the route to the sponsor if they think they should be on it. A desk that quietly extends the handling to anyone who sounds like they expect it has a list with no edges. A list with no edges is the shadow service level with a nicer name.

What the Desk Says When Asked Why

Three people will ask why, and each needs a sentence the technician can say without looking at their shoes. The first is the technician themselves, Jonah in his second week. The answer is the charter: here is the list, here are the reasons, here is what we do differently and what we do not, signed by Marta. A desk that can hand the new person a page has answered the question once and forever. A desk that answers "it's just how it is" has taught the new person that the rules are unwritten, which is a lesson they will apply to every other rule too.

The second is the department head who noticed. "Why did finance get a visit in fifteen minutes when my team waited two days for a printer?" The honest answer names the reasons, not the rank: "The finance director was presenting to the bank at eleven and the fix was a swap we could do in ten minutes. Your printer queue needed a part, and I'm sorry about the two days; that one is on us, not on the list." Then the list itself, because it is not a secret: "The list of people who get a named technician and a visit is five roles, Marta signs off on it, and I can send you the page." Most department heads, shown the page, agree with it. The ones who do not should talk to Marta, and the technician should say so cheerfully.

The third is the person on the list, asking for something the charter does not give. "Can you just push my ticket ahead of whatever that is?" The answer is a courteous description of what they are getting, which is a named person, now, working on it. It also includes a plain statement of what is in front of the ticket and why: "I'm on yours now; the scanner outage is being worked by Sam because a shift is stopped, and yours is next behind it." This is the three-sentence shape from Saying No Upward. The charter is what makes it sayable, because the technician is reading from a page the executive's own peer signed. Without the page, the sentence is a junior technician's opinion against a director's. With it, the sentence is the organisation's.

The Differences, Made Visible

The table below is the heart of the charter. It shows the moments at which VIP handling differs from ordinary handling, what each looks like, and the reason it is allowed. It is written to be read by a department head as much as by a technician. Every row has a reason; every row that cannot name one is a row the desk should delete. The rows that are missing are as important as the ones present. There is no row for priority, no row for the service-level clock, and no row for the identity check, because none of those changes.

Two rows deserve a word. The named technicians are two, not one, because one is a hero and a hero on leave is an outage, a failure described in The Seven Ways Support Quietly Fails. And the loaner is prepared, meaning signed in, patched, with the common applications on it and a dock and a charger beside it. That is because a loaner that needs an hour of setting up is a spare laptop, not a loaner. The list is short precisely so that the desk can afford to keep one ready.

Where It Goes Wrong

VIP support fails in three ways, and all three are slow. The first is the shadow service level. The handling is never written, the speed becomes the rule, and the queue for everyone else quietly reorders itself around the executive floor. The symptom is a technician leaving a shift-stopping outage to fix a dock, and nobody being able to say who told them to. The cure is the charter, with the "what does not change" section signed by the sponsor, and the next article in this series.

The second is the list that grows. Every department head who notices the handling asks for it. Every project adds a name. Every reorganisation inherits the previous list and adds its own. The desk cannot refuse, because nobody told it that it could. Within two years the list is the top three layers of the organisation and the handling is impossible to deliver to any of them. The symptom is a list nobody can recite from memory. The cure is the sponsor, the review, and the hours cost reported beside the list. That way, adding a name is visibly a decision to spend something.

The third is the executive technician: the one person on the desk who handles the list, knows the devices, and has the assistants' numbers. They are therefore never allowed to do anything else, take leave, or be promoted. The desk has created a hero with a smaller queue. The symptom is that the executive floor asks for the person by name and will not accept anyone else. The cure is two named technicians from the start, rotated, with the devices and the arrangements written down where the second one can read them. It is also kinder to the technician, who did not join a help desk to spend four years as one director's valet.

A Short War Story: The List of Forty at Larkspur Media

At Larkspur Media, a publisher with about three hundred staff, the desk lead, Eoin, inherited a VIP list of four names and no page explaining it. Over three years the list reached forty. That was because each new editor-in-chief, each commercial director and each head of a launched title asked for the handling. Nobody on the desk had the standing to say no. The desk of five was by then spending, by Eoin's later count, around eleven hours a week on visits and named-technician handling for the forty. The ordinary queue's first response had slipped from under an hour to most of a day, which the forty did not notice and the other two hundred and sixty did. The failure that finally surfaced it was a newsroom-wide login outage on a press day that waited forty minutes behind two editors' laptop swaps. That was because the technicians had learned that editors came first and nobody had ever written down that outages came before editors. The chief operating officer asked Eoin for the list, read it, and asked who had approved it. Nobody had, which was the answer to every question she asked that afternoon. She cut it to six roles, signed a page, and the eleven hours became three. A list nobody owns is owned by whoever asks last.

The VIP Support Charter

The charter is one page, signed by the sponsor, posted where every technician and every department head can read it, and re-signed at every review. The sections follow the article: the list by role with its reason, the handling that differs, the handling that does not, the sentences the desk says when asked, and the review. Fill in the roles rather than the names. The names go on a separate line that changes more often. Keep the "does not change" section exactly as long as the "does change" section, because the first one is the one the sponsor is really signing. Where the desk has a knowledge base article visible to everyone, as in QuerySolv and most tools, that is the natural place to post it. That way, the department head who asks why can be sent a link rather than an explanation.

VIP SUPPORT CHARTER — ONE PAGE
Organisation: ______________________   Sponsor (name, role): ______________________
Desk lead: ______________________      In force from: ____________   Review due: ____________

1. THE LIST (by role; names kept on a separate line that changes more often)
   Role                           Reason (hour cost / audience / confidentiality / mobility)
   ____________________________   ____________________________________________
   ____________________________   ____________________________________________
   ____________________________   ____________________________________________
   ____________________________   ____________________________________________
   ____________________________   ____________________________________________
   Assistants to the roles above are included for tickets raised on their behalf.
   Nobody is added to this list except by the sponsor, in writing, with a reason.

2. WHAT IS DIFFERENT FOR PEOPLE ON THE LIST
   [ ] First reply from a person, by phone or in person, within ____ minutes in business hours
   [ ] Worked by one of two named technicians: ______________ and ______________
   [ ] A visit at a time the assistant picks; remote sessions only with consent, narrated
   [ ] A prepared loaner offered first when the fix will take longer than ____ minutes
   [ ] Ticket notes record the fault and the fix only; nothing seen on the device or in the mailbox
   [ ] Board days and large events prepared in advance under the event checklist

3. WHAT IS NOT DIFFERENT
   [ ] The ticket goes in the same queue as every other ticket
   [ ] Priority is set by impact and urgency, by the desk, by the same method as for anyone
   [ ] A higher-priority ticket for anyone else is worked first
   [ ] Service-level targets and clocks are the same for every priority, whoever raised it
   [ ] Identity is verified before any reset or access change, by the desk's standard, every time
   [ ] Exceptions to any policy go to the policy's owner, never granted by the technician

4. WHAT THE DESK SAYS
   To a new technician:   "Here is the charter; the list is in section 1 and the reasons beside it."
   To a department head:  "The list is ____ roles, owned by ______________; here is the page."
   To a person on the list asking to go first: "I am on yours now; ______ is ahead of it because
                                                 ______________; yours is next."
   To anyone asking to be added: "That is ______________'s decision; I will pass it on today."

5. THE REVIEW (every ____ months)
   Hours spent on list handling last period: ______   Tickets: ______   Names added: ______
   Names removed: ______   Reasons re-confirmed for every role: [ ]   Re-signed by sponsor: [ ]

Signed (sponsor): ______________________   Date: ____________

Carla wrote the page the week after Jonah asked and took it to Marta, the operations director. She had it signed with five roles on it, two fewer than the desk had been quietly serving. Jonah was named as the second technician, which he took as a compliment and Carla meant as insurance. The next time Priti called, the managing director's ticket was answered by a person inside three minutes. It was worked second, behind a payroll export that had stopped for the whole finance team. When Anders asked why, Jonah had a page to read from. It was, he said afterwards, the easiest hard conversation he had ever had.

Frequently Asked Questions