The 9:01 Panic: Why Room Tickets Are Different

Monday, 09:01, at Stonebridge Insurance. The desk phone rings and Omar picks it up to a voice he recognises as Fiona, the chief executive's assistant, speaking quietly and fast. "The boardroom screen is dead. Margaret's got eleven people in there and four on the call and it just says NO SIGNAL. Can someone come now?" Omar has been on the desk for seven months and has been trained well. He opens a new ticket, and his mouth, running on its own, says "Can I take a few details first?" There is a pause on the line that he will remember for some time. "She's standing in front of it," Fiona says. "Please just come."

A room ticket is any request about a meeting room's screen, sound, camera, sharing or call. And it is the only kind of ticket most desks handle where the fault has a live audience. The person asking is not the person suffering. The people suffering are the eleven in the room, the four on the call, and the one at the front whose meeting has stopped. The fault itself is usually small. The cost of taking ten minutes over it is not. This article is part of our Meeting Room & AV Support series. The series covers the response standard, the triage card, standardising rooms, the check routine, hybrid meetings and measuring room tickets. This article is about the first of those: what a desk owes a room with a meeting in it. It covers how to deliver that without abandoning the queue.

It covers why a room ticket is different from the rest of the queue, then the ten-second budget and the person-minute arithmetic. Next comes the response standard, which is go first and log afterwards. We cover who goes and what they carry, then the first minute in the room. Next come the ticket written afterwards and what it must say, then the call that turns out not to be the room's fault. We cover what the standard costs and what it buys. We finish with a short war story and the room response standard to copy, in that order.

Why a Room Ticket Is Different

Every other ticket in the queue is waited for by one person who can usually do something else in the meantime. A locked account, a printer that will not print, a slow laptop: each is a problem for its owner and for nobody else. And the owner can send the e-mail from their phone or print from the other floor. A room fault stops a group. Eleven people have cleared an hour, four more have dialled in from somewhere, and the organiser has a plan that begins with a slide nobody can see. There is no doing something else. There is standing in front of a blue rectangle, and the rectangle is winning.

The second difference is that the audience is watching the desk work. A technician fixing a laptop at someone's desk is fixing a laptop. A technician walking into the boardroom at 09:04 is a performance, with a cast of fifteen and a critic at the front. Every minute of fiddling is being timed by people who did not ask to be there. The fault is forgotten by lunch if it took one minute. It becomes an anecdote if it took ten, and the anecdote has the desk's name in it, not the projector's.

The third difference is that the cost is out of all proportion to the fault. Nine room faults in ten are one of four things. There is an input on the wrong source, a cable not pushed home, or a mute light nobody saw. Or there is a laptop that needs to be told where to send its picture. None of these takes a technician more than a minute to fix. The same minute, taken ten minutes late, has already cost the organisation a room full of senior salaries and the organiser a good deal of composure. The desk's instinct, trained on the rest of the queue, is to treat a small fault as a small ticket. The room does not agree, and the room is right.

The Ten-Second Budget

A meeting will tolerate about ten seconds of the organiser pressing buttons before people start looking at their phones. It will tolerate about two minutes of waiting before it adapts without you. After two minutes the organiser is talking without slides, and the remote attendees have been told to hang on. Somebody has gone to look for a technician in person. That means the call to the desk was a formality and the real escalation is on foot. Whatever the desk does after that point is tidying up. The window in which the desk can save the meeting, rather than apologise for it, is the first two minutes. And most of that is walking.

The arithmetic that makes this plain is person-minutes, the number of people waiting multiplied by the minutes they wait. A single user waiting forty minutes for a printer fix is forty person-minutes. Fifteen people waiting four minutes for a room is sixty, and they are not any fifteen people. A boardroom at 09:01 holds the most expensive hour the organisation buys all week. The ordinary way of deciding urgency, by how many people are affected and how badly, is covered in Impact and Urgency in Practice. A room with a meeting in progress scores high on both axes by that method without any special pleading. The special pleading is only needed to explain why the desk did not move.

The budget also explains why a one-hour response target, perfectly reasonable for the rest of the queue, is meaningless for rooms. Service-level targets per priority on a business-hours schedule, the kind QuerySolv and most tools apply to tickets, are built for problems that wait. A room fault does not wait; it expires. By the time a one-hour target is breached the meeting has finished and the organiser has rebooked. The only thing the desk can still deliver is a resolution note on a ticket nobody needs. The room needs a different promise, measured in minutes, and it needs the promise kept by someone walking rather than by a clock.

Go First, Log Afterwards

The room response standard is one rule with three parts. When a room with a meeting in it calls, someone goes at once. The only questions asked on the phone are which room and what the screen shows. The ticket is written after the room is working. "Go" means a person is moving within a minute of the call. Not "a ticket is opened within a minute", not "the room is called back within a minute". Moving. The ticket, the diagnosis and the notes all happen, but they happen after the walk, because the walk is the diagnosis. Nobody has ever fixed a seated cable over the phone.

The two questions are the whole intake. Ask "Which room?" so the right person goes to the right door. Ask "what does the screen show?" because the answer sorts most faults before the technician has left the desk. NO SIGNAL is an input or a cable, and a black screen is power. A screen showing the previous meeting's slides is a laptop still connected somewhere. And "it says the room is not signed in" is the call, not the display. Anything beyond those two questions is a delay dressed as diligence. The organiser does not know the make of the panel and cannot tell you which input is selected. They are standing in front of fifteen people being asked to describe a cable. Ask the two questions, say "someone is on their way", and put the phone down.

The standard applies to any room with a meeting in it, not to any room with an executive in it. The boardroom at 09:01 and the small meeting room where three warehouse supervisors are trying to share a rota are the same call. Both have an audience, a plan and a budget of two minutes. Desks that reserve the fast walk for senior people have built a shadow service level without writing it down. That is the trap described in No Shadow SLA. It has an ugly side effect: the supervisors learn that the desk comes running for directors, and stop calling. The standard is about the room, not the rank. The chief executive gets the same walk as everyone, which happens to be the fastest walk the desk has.

Who Goes

The person who goes is the nearest competent person, not the most senior or the one who "does rooms". A desk that routes every room call to one specialist has given the specialist a reason never to be away from their chair. It has given every other technician a reason to say "that's not mine". The walk is a first-line job. Any technician who can find the input button, reseat a cable and tell a mute light from a power light can clear nine room calls in ten. And the tenth is the one they phone about from the room with the fault in front of them. Everyone on the desk learns the rooms. It is a smaller syllabus than it sounds.

On a desk of three or more, name a room cover for the busy hours. That person drops what they are doing for a room call between, say, half past eight and quarter past ten. They do the same again either side of lunch, when meetings start. The rest of the day the nearest person goes. The cover rotates weekly so nobody becomes the room person. And the rota is written where the whole desk can see it, because "I thought Priya had it" is how a 09:01 becomes a 09:09. A desk of two names the cover by the morning. A desk of one is the cover, and the question becomes what happens to the phone while they walk. A voicemail greeting answers that: "if you are calling about a meeting room, I am probably on my way to it".

Facilities can share the walk and often should. In many buildings the facilities team is closer to the rooms and already walking the floor. An agreement that either team goes to a room call while the desk still writes the ticket doubles the number of people who can answer in a minute. It needs one sentence in writing and one shared number to call. Facilities will reseat the cable. They will not notice that it is the fourth reseat in that room this month, because counting is the desk's half of the job.

What the Person Carries

The technician who goes carries a room bag, a small bag kept at the desk and never unpacked for anything else. A walk that ends with "I'll just go and get a cable" is two walks and the meeting has been counting both. The bag holds the things that fix the common faults without a second trip. It does not hold a toolkit, a spare display or ambitions; it holds what a one-minute fix needs. The list below is the one most desks settle on after a few months of forgetting one item at a time.

• One spare video cable of the type the rooms use, long enough to reach from the table to the display.
• The adapter set for laptops that lack that port, kept together on one ring.
• Fresh batteries for the remotes and the wireless microphones in every size the rooms use.
• A spare remote for the room system and a spare presentation clicker.
• A laptop known to work with every room, signed in and awake, as the fallback for a presenter whose own will not share.
• The printed triage card for the table, in case the room's copy has walked.
• Whiteboard markers that write, and a cloth.
• The desk's phone number and the room list with the panel type for each room, on one laminated sheet.

The known-good laptop earns its place more often than anything else in the bag. The presenter's own machine may refuse to share when the two-minute budget is nearly spent. In that case, the fastest fix is not to diagnose their laptop in front of the room. It is to put the file on the desk's laptop, connect it, and let the meeting start. The diagnosis moves to the corridor afterwards. The bag's contents are checked on the weekly walk described in The Room Check Routine. That is also where the batteries get replaced before they are needed rather than after. A bag that has been raided for a desk job and not restocked is a bag that fails at 09:04, which is the only time it is opened.

The First Minute in the Room

Walk in quietly, go to the panel or the cable rather than to the presenter, and say one sentence to the room: "I've got it, carry on." The sentence does two jobs. It gives the organiser permission to keep talking, which half of them will. It tells the room that the person at the panel is not going to ask it questions. The technician's audience for the next minute is the equipment. The organiser's audience is the room. Keep the two separate and the meeting continues around the fix instead of stopping to watch it.

Check the common faults in a fixed order, the same order every time, so the hands do it while the head is still arriving. Is the display on? Is the input the one the cable goes to? Is the cable seated at both ends? Is the laptop awake and sending a picture? Is the mute light on? Is the volume on the room control, not the laptop, above zero? That order clears most rooms inside a minute. It is the same order the organiser could have followed from the card on the table, which is the subject of The Room Triage Card. The technician does it faster only because they have done it before and are not being watched by their own manager.

If two minutes pass with no fix, stop diagnosing and offer the fallback. That could be the known-good laptop with the presenter's file on it, or the room next door if it is free. Or it could be audio-only from the room phone while the picture is sorted. Say which one you are doing and do it. The meeting wants a working room more than it wants an explanation. The explanation can be given to the organiser in the corridor afterwards, in the three-sentence form described in The Three-Sentence Explanation. Never narrate the diagnosis to the room. "It might be the cable, or it could be the panel firmware, let me just try..." is a sentence fifteen people will quote later, and not fondly.

Leave when the meeting works, not when the diagnosis is complete. A technician who has got the picture up and then stays to work out why the input had changed is standing in a meeting. That is a different thing from supporting it. If the fix was a workaround, say so to the organiser on the way out, in one sentence, with a time: "That's working on the spare cable; I'll swap the room's cable at lunch."

The Ticket Written Afterwards

The ticket is written after the walk, with the real times. And it is written every time, including the thirty-second fixes, because the walk is only half the job. The other half is knowing that this was the fourth NO SIGNAL in that room this month. It means knowing that three of them were the input being changed by the previous meeting. And it means knowing that the fix is a label on the panel rather than a fifth walk. None of that is visible without the tickets. A desk that fixes rooms without logging them has the untracked walk-up problem in its purest form: busy, appreciated and unable to prove either. The ticket is the memory. The walk is the reflex.

Write six things. The room. The time the call came and the time the room was working, which together are the number the standard is measured on. What the screen showed when you arrived, in the organiser's words. What the fix was, in one line. Record what the cause was, which is often different from the fix. The fix was "selected the right input"; the cause was "the previous meeting's laptop was still connected to the other input". And whether anything is still owed: a cable to swap, a battery to replace, a part to order. If you run QuerySolv, the ticket's event history begins the moment you open it. So the time the call actually came goes in your first note by hand. The history records when you typed, not when you walked, and the standard is measured on the walk.

Mark the source so room calls can be counted on their own. A ticket type or a field that says "room" with the room's name beside it is enough. It is what makes everything in Measuring and Reducing Room Tickets possible later. Logging after the fact is honest when the ticket says so. "Room call at 09:01, attended 09:04, working 09:05, logged 09:20" is a record. The same ticket with an opening time of 09:20 and a resolution time of 09:21 is a desk that fixes rooms in a minute from its chair. That is a claim nobody will believe and nobody should.

When It Is Not the Room

About one call in three turns out not to be the room's fault at all. The presenter's laptop will not wake, or will not share, or shares the wrong screen. Or the file is on a drive that needs a sign-in the presenter has forgotten. Or the meeting was never added to the room's calendar so the room system has nothing to join. The organiser does not know which of these it is and should not have to; from the front of the room every fault looks like "the room is broken". The standard is the same. Go. The sort between room fault and presenter fault happens at the panel, in the first thirty seconds. The fallback laptop in the bag covers most of the presenter faults without diagnosing them in public.

What changes is the ticket and the follow-up. A presenter fault is logged against the person and their device, not against the room, so the room's count stays honest. It is followed up at the person's desk later, where the diagnosis can take as long as it needs. A room that collects a dozen "not the room" calls in a month is still telling you something, usually that the way to share is not labelled. That is a room fix even though the fault was never in the room. A hybrid call that nobody remote can hear is its own subject, in Hybrid Meetings and the Remote Half, and gets the same walk.

What the Standard Costs and What It Buys

Take a fictional desk to put numbers on it. Stonebridge Insurance has a desk of four and twenty-two rooms with a screen in them. In a typical month the desk takes somewhere between thirty and forty room calls. Under the go-first standard, a call costs a technician about six to eight minutes door to door, including the ticket written afterwards. That comes to three to five hours of desk time a month. Before the standard, the desk took details first and went when someone was free. The calls took about the same time to fix and a great deal longer to reach, and the difference was borne by the rooms. Stonebridge's rough count for the previous year was two or three meetings a month that gave up and rebooked. Each cost the organisation a dozen person-hours in a room and an hour of someone's time to re-arrange.

Those are a fictional desk's figures, stated as ranges, and your own will differ by building and by how many rooms you have. The shape will not. The walk costs a few hours a month of first-line time and interrupts the queue thirty times. In exchange, it removes the one kind of ticket whose failure is reported to the chief executive in person. A room cover rota keeps the interruptions to one person at a time. And the rest of this series is about making the calls fewer. Report the standard on two numbers each month: the calls and the share that met the promise. Leave the deeper counting to the last article in the series. The standard is the promise. The other five articles are how the promise gets cheaper to keep.

A Short War Story: The Ticket-First Desk at Redbrook Engineering

Redbrook Engineering's desk lead, Dev, had spent a year getting walk-ups to raise tickets and was proud of it. So when a sales director called at 10:02 about a client presentation room showing NO SIGNAL, the technician who answered followed the desk's own process. The technician asked for a ticket through the portal first, so that it would be "in the queue properly". The director raised the ticket from her phone, standing beside a client's procurement team. The technician picked it up fourteen minutes later when the triage pass came round. The technician walked to the room and selected the correct input in about ten seconds. The client's team had by then agreed to "pick this up next week", which turned into a month. The sales director's account of the morning reached the managing director before the technician reached the desk. Dev kept the ticket rule for everything except rooms and wrote the go-first standard on a card above the phone that afternoon. Dev spent a quarter rebuilding the sales team's willingness to call the desk at all. The cost was one delayed contract and a desk whose good year was remembered for its worst fourteen minutes. The lesson Dev wrote at the top of the card was that the ticket is the record of the walk, not the permission for it.

The Room Response Standard

The standard below is one page, kept beside the desk phone and in the knowledge base. And it is written so that a technician in their first week can follow it without asking. Fill in the hours, the rota and the numbers once; the rest is fixed. Section A is the promise, B is the intake, and C is who goes. Section D is the walk, E is the ticket written afterwards, and F is the two numbers reported each month. It is the only template in this series that is about the desk's behaviour rather than the room's, which is why it comes first.

ROOM RESPONSE STANDARD — ONE PAGE
Desk: ______________________   In force from: ____________   Reviewed: ____________

A. THE PROMISE
   A room with a meeting in it gets a person moving within one minute of the call.
   The room is working, or on a fallback, within five minutes of the call.
   This applies to every room and every meeting, whoever is in it.

B. THE INTAKE (the whole phone call)
   Ask:  Which room? ______________   What does the screen show? ______________
   Say:  "Someone is on their way."   Then end the call. No further questions.
   Do not open the ticket before moving. Do not diagnose over the phone.

C. WHO GOES
   Busy hours: ______ to ______ and ______ to ______   Room cover this week: ______________
   Outside busy hours: the nearest technician. Facilities may also go: yes / no   Shared number: ________
   Solo desk: voicemail greeting says you are on your way to a room.

D. THE WALK
   Take the room bag. Walk in; go to the panel, not the presenter; say "I've got it, carry on."
   Check in order: display on / input / cable seated / laptop awake / mute light / room volume.
   At two minutes with no fix, offer the fallback:  spare laptop / next room / audio from the room phone.
   Never narrate the diagnosis to the room. Leave when the meeting works.
   Tell the organiser in one sentence what was done and when you will return, if anything is owed.

E. THE TICKET (written after, every time, real times)
   Room: ______________   Called: ______   Attended: ______   Working: ______   Logged: ______
   Screen showed (organiser's words): ______________________________
   Fix (one line): ______________________________
   Cause (if different from the fix): ______________________________
   Still owed:  [ ] cable  [ ] battery  [ ] part  [ ] label  [ ] card  [ ] follow-up with presenter
   Fault was:   [ ] the room   [ ] the presenter's device   [ ] the booking   [ ] the call

F. REPORTED MONTHLY
   Room calls: ______   Met the promise (moving in 1 min, working in 5): ______
   Rooms with three or more calls this month: ______________________________

Omar got the standard on a card above his phone the following week. The next time Fiona called he said "which room and what's on the screen", heard "boardroom, NO SIGNAL", and said "on my way". He was at the panel inside two minutes. The input had been left on the wrong source by the eight o'clock meeting, as it had been three times that month. He fixed it in ten seconds and wrote the ticket at 09:11 with the real times in it. The fourth ticket was the one that got the input labelled. The first three had been walks without a record, and a walk without a record is a favour, not a service.

Frequently Asked Questions