Hybrid Meetings and the Remote Half Who Cannot Hear

Wednesday, 10:05, at Bluewater Bank. Imogen is at her kitchen table, two hours from the office, in the weekly lending team meeting. Eight colleagues are in the room; she and two others are on the call. She can see the room, from an angle that shows the top of the door and a strip of ceiling. She can hear a sound like people talking in the next flat. The screen the room is looking at is, on her call, a grey rectangle. She types "can't hear you, can't see the slides" into the chat. Nobody in the room is looking at the chat, because the room is looking at the slides, which are fine. At 10:20 she raises a ticket from her phone: "room audio and sharing bad for remote attendees, lending meeting, room 2". Callum on the desk reads it at 11:00, walks to room 2, and finds it empty, tidy, and working perfectly.

A hybrid meeting is one with some attendees in a room and some joining remotely. The remote half is the people on the call. Their entire experience of the meeting is manufactured by the room's camera, microphones and sharing. People in the room cannot perceive that experience from where they sit. That asymmetry is the whole subject. The room cannot see what the remote half sees. The remote half cannot easily interrupt to say so. The ticket, when it comes, arrives after the meeting, from the person who was not in the room, about a room that looks fine. This article is part of our Meeting Room & AV Support series. It is about the four ways the remote half loses, the room that was never built for them, and what the desk can suggest without running anyone's meeting.

It covers why the remote half gets the worst of it, then the remote attendee who cannot hear and the camera that shows the ceiling. Next come the shared screen that is not shared, the echo from two joins in one room, and the room not designed for hybrid. Then it covers the etiquette the desk can suggest, followed by the hybrid ticket and how to handle one. A short war story and the hybrid meeting guide to copy finish the article.

Why the Remote Half Gets the Worst of It

In an ordinary room fault the audience is in the room and the fault is on the wall, so everyone sees it at once and someone calls. In a hybrid fault the audience is split, and the half that suffers is the half that cannot be seen. The room hears itself fine, sees its own slides fine, and reads the remote half's silence as attention. The remote half hears a rumble, sees a ceiling, and reads its own experience as a problem with its connection, because that is what it usually is at home. So the remote half says nothing, or types into a chat window nobody in the room has open. The meeting ends. The room thinks it went well. The remote half has attended a different, worse meeting, and nobody will find out unless one of them writes it down.

This is why hybrid tickets are rare, late and vague, and why their rarity means nothing. A desk with few hybrid complaints may have good rooms or may have remote colleagues who have stopped expecting to hear. The second is more common, and it is found by asking. That is why the remote attendees' experience belongs on the list of things the desk measures about remote work in Supporting Remote Workers, rather than waiting for it to appear in the queue. The desk's job in a hybrid room is to be the remote half's eyes and ears before the meeting. That means using the test call described in The Room Check Routine, because during the meeting nobody in the room is going to be.

The other reason the remote half loses is that most rooms were built for people in them. Picture a long table with one microphone at the near end. Add a camera on a side wall, a display chosen for the people facing it and a speaker that fills the room. All sensible for a room full of people, all wrong for the three who are not. Equipment fixes some of this. Behaviour fixes more of it, which is why the last part of this article is a guide the desk can hand to organisers, and why that guide is advice rather than policy. The desk does not run meetings. It can say what makes them work.

The Remote Attendee Who Cannot Hear

"They can't hear us" has four usual causes. The first check is to find out which microphone the call is using, because it is very often not the room's. A laptop in the room that joined the call is using its own microphone, two metres from the nearest mouth and pointed at the keyboard. Meanwhile, the room's table microphone sits unused. The fix is to choose the room's microphone and speaker as the call's devices. Or better, join from the room system so that the question never arises. The second cause is the mute: the room's microphone has a mute button and a red light. The previous meeting left it on, and the room cannot tell because the room can hear itself. The third is distance: one microphone at the near end of a long table picks up the near end. The people at the far end are heard as a rumble. The fix is a second microphone in the large room profile. Until then, the chair asks far-end speakers to come closer or repeat. The fourth is the room's behaviour: people talk towards the display, away from the microphone, and the remote half hears the back of their heads.

The diagnostic the desk can do, from the room, in thirty seconds, is to ask the remote half a question with a name in it. "Imogen, can you hear Priya at the far end?" The answer sorts the four causes. If she can hear the near end and not the far, it is distance. If she cannot hear anyone, it is the mute or the device. If she can hear but the sound is thin and clattery, it is a laptop's microphone. The question is also the first line of the etiquette guide. It is the one the chair can ask at the start of every meeting without any technical knowledge at all. It catches the fault in the first minute rather than in a ticket at 10:20.

The reverse complaint, "we can't hear them", is the room's speaker. It is usually the call playing through a laptop's own speaker rather than the room's, or the room's volume at zero on the control nobody looked at. The first checks are the same as the audio column of The Room Triage Card: mute, volume, and where the sound is going. The remote attendee's own microphone and headset are the other half of this. They are a home-equipment question, covered in What the Desk Supports at Home; the room can only deliver what arrives.

The Camera That Shows the Ceiling

The camera that shows the ceiling, or the door, or the left-hand half of the table, is the fault the room will never report, because nobody in the room is looking at the room. Cameras drift when they are knocked by a cleaner, tilted by an organiser who wanted a closer shot of the whiteboard, or left on a preset from a meeting that used the room differently. A camera on a side wall was wrong from the day it was mounted, because it shows the remote half a row of ears. The remote half sees it every meeting. The room finds out at the quarterly review, if then.

The fixes are a mounting and a preset. The camera lives on or under the display, pointing down the table, which is the layout rule in Standardising Rooms to Cut Tickets. It has a default shot that shows the whole table, which the room system returns to when the meeting ends. Rooms whose cameras can be moved by remote get a label on the remote saying which button restores the default. The walk checks the shot every week by joining the test call from a phone and looking. A camera that follows the speaker is a pleasant thing to have and a thing the remote half can live without. A camera that shows the ceiling is a meeting the remote half has been removed from.

The Shared Screen That Is Not Shared

Sharing to the room and sharing into the call are two different acts, and the organiser who has done the first believes they have done both. A laptop plugged into the table cable sends its picture to the display on the wall, where the room sees it. The call sees nothing, or sees the camera's view of the wall, a grey rectangle, or the last thing that was shared. To reach the remote half the picture has to be shared inside the call, from the laptop's own sharing control or from the room system's. That is a second step with a second button. It is the single most common hybrid fault, and it is invisible from the room. The room is looking at the wall, where the slides are, and the slides are fine.

The fix is one line on the card and one line in the guide: "share into the call, not just to the room". Rooms with a room system usually have a way to share that does both at once, which is the reason to use it and the reason the profile says how. Rooms without one depend on the organiser sharing twice, and the chair's opening question for this fault is "Imogen, can you see the slides?", asked the moment they go up. Of all the hybrid faults this is the one the etiquette guide fixes most completely, because the equipment is fine and the missing step is a habit.

The Two Joins Problem: Echo

When two devices in one room are both in the call with their microphones live, each hears the other's speaker and sends it back. Everyone on the call hears themselves a half-second late, as if speaking in a tunnel. The cause is nearly always a laptop in the room that joined the call to see the chat, or to share. Or the organiser joined from their own machine out of habit and the room system joined from its calendar. So the room is in the call twice. The fix is one join per room: the room system joins. Laptops that must be in the call for sharing or chat join with microphone and speaker off. Nobody unmutes a laptop in a room with a live microphone. The guide says it in six words, "one join per room; mute the rest", and the card says it in the call column.

Echo is also the fault the room does notice, because the room hears it too, and it is the one hybrid complaint that arrives as a 09:01 call. The walk-in fix is to find the second device, usually a laptop with its lid open and its microphone live, and mute it. The lasting fix is the habit. The habit arrives when the room system is the only sensible way to join because it is in the calendar and starts the meeting at a touch. A room that is awkward to join from its own system is a room that will be joined from laptops, twice.

The Room Not Designed for Hybrid

Some rooms cannot hold a good hybrid meeting whatever the organiser does, and the honest thing the desk can say is so. Consider a long room with one microphone at one end, a display at the side, and a camera that sees half the table. Its speaker fills the room with the far end's voice while the far end hears a rumble. That is a room for people who are in it. The desk can patch it with a second microphone and a moved camera if the budget allows. If it does not, the desk can say which rooms are hybrid-capable and which are not, in the room standard and on the booking page. That way, an organiser with three remote attendees books a room that will hold them. "This room is for in-person meetings" on the door is not an admission of defeat. It is the difference between a known limit and a surprise.

A request to "make this room hybrid" is a change, not a ticket. It is answered the way any equipment request is. Give the profile it would need to join, the parts that would take, and the rooms already on the list to be done first by ticket count. Organisers who are told "that room is on the list for the medium profile next quarter; room 5 is hybrid-capable now and is free on Wednesdays" are organisers who have been given an answer. The ones who are told "we'll look into it" book the bad room again and the remote half hears the rumble again.

The Etiquette the Desk Can Suggest

The desk does not run meetings, and a desk that tries to tell chairs how to chair will be ignored, with reason. What it can do is publish a short guide for organisers that says what makes a hybrid meeting work for the people on the call. It takes the form of suggestions a chair can take or leave. Put it where organisers will see it: on the booking page, on the back of the card, and in a knowledge base article. The guide is short because a chair reads it once, and it is behavioural because most of what goes wrong for the remote half is not equipment. The complete version is the template at the end of this article; its substance is below.

Before the meeting: book a hybrid-capable room and add the room to the invitation so that the room system can join. If the meeting matters, ask the desk for a morning check. At the start: join once, from the room, and mute the laptops. Ask the remote half by name whether they can hear the far end of the table and see the shared screen. During: share into the call, not only to the room. Have one person in the room watch the chat. Have the chair repeat questions from the room before answering them, because the remote half heard the answer and not the question. Face the microphone, not the wall. At the end: leave the call from the room system so that the next meeting does not start inside this one.

The remote attendee's side of the guide is shorter and belongs to them. It calls for a headset rather than the laptop's speaker, camera on if the meeting is one where faces matter, and a connection that holds. That last one is a home-network question handled in The Home Network Variable rather than a room one. The desk can offer all of this as a page and none of it as a rule. The chairs who adopt it will have better meetings, their remote colleagues will say so, and the others will come round when they are the remote half for a week. The guide is published once and pointed at often. If you run QuerySolv, it is a knowledge base article visible to everyone. That way, the organiser in the corridor and the remote attendee at the kitchen table are reading the same page.

The Hybrid Ticket

The hybrid ticket arrives after the meeting, from the remote attendee, and describes a room the desk will find working. Treat it as a report from the only witness, not as a fault to reproduce by walking into an empty room. Ask three things: which room, which meeting and when, and what exactly they saw and heard, in their words. For example: "ceiling and the top of the door", "a rumble, I could hear Priya but not the far end", "a grey box where the slides should have been". Those three answers sort the fault into camera, microphone or sharing before anyone leaves the desk. They tell the desk whether it is the room, the room's behaviour, or the remote attendee's own connection, which is the branch handled by the remote-support articles rather than this one.

Then test from the far end. The technician joins the room's test call from the room and has a colleague, or their own phone in the corridor, join as the remote half. The technician looks at what the remote half sees. A camera that shows the ceiling is a preset; a thin, clattery sound is a laptop's microphone; a grey rectangle is a share that went to the wall only. Fix what is equipment, log what is behaviour, and reply to the remote attendee with what was found and what will change. The reply is the only evidence they will get that the room was looked at from their side. If you run QuerySolv, their answer of "still could not hear at today's meeting" to the resolved ticket reopens it. That is how the desk learns that a fix tested from inside the room did not reach the other half. In any tool, the way back must be open, because a hybrid fault fixed from the inside is not fixed until the outside says so.

Count hybrid tickets as room tickets with a flag, by room. A room that produces three "could not hear" reports in a quarter is telling the desk something about its microphones or its layout. The weekly walk, done from inside the room, cannot tell it that. The counting is in Measuring and Reducing Room Tickets; the point here is that the remote half's report is the only measurement of the remote half's meeting the desk will ever get. It is worth a reply that says so.

A Short War Story: The Client Review at Larkspur Architects

Larkspur Architects ran a design review for a hospital extension from their large meeting room. Hugo, the partner, and the client's project director were in the room, and the client's four engineers joined from their own offices. The engineers saw a strip of ceiling and the top of a door for ninety minutes. They heard Hugo clearly and the project director as a rumble, and never saw the revised drawings. Hugo had plugged those into the table cable and shown them on the wall to the two people who did not need to see them. One engineer raised a ticket with Larkspur's desk afterwards, through the client's contact. The desk's technician walked into the empty room and found the display, the cable and the room system working. The technician closed the ticket as "room tested, no fault found". The review was repeated a week later with the engineers on site, which cost the project a week at a stage where a week mattered. It cost Hugo a morning explaining to the client why their engineers had attended a different meeting from his. The desk's review found that the room had never once been tested from the far end. The lesson written into the walk the following week was that a hybrid room is tested from the remote half's seat or it is not tested at all.

The Hybrid Meeting Guide

The guide below is for organisers and chairs, written as suggestions. It is one side of a page so that it can go on the back of the room card and on the booking page as well as in the knowledge base. Section A is before the meeting, B the first minute, C during, D the end, and E the remote attendee's own short list. Put your hybrid-capable rooms' names in the first blank and the desk's number in the last, and leave the rest as it stands.

HYBRID MEETINGS — A SHORT GUIDE FOR ORGANISERS AND CHAIRS
Hybrid-capable rooms: ______________________________   Desk: ______________

A. BEFORE THE MEETING
   [ ] Book a hybrid-capable room (above). Other rooms are for in-person meetings.
   [ ] Add the room itself to the invitation, so the room system can join from its calendar.
   [ ] If the meeting matters, ask the desk for a morning check of the room on the day.
   [ ] Send any slides or documents to remote attendees beforehand as a fallback.

B. THE FIRST MINUTE
   [ ] Join once, from the room system. Laptops in the room stay out of the call, or join muted.
   [ ] Ask the remote attendees BY NAME: "Can you hear the far end of the table? Can you see the screen?"
   [ ] If not, use the card on the table (audio and call columns) or call the desk. Do not continue without them.

C. DURING THE MEETING
   [ ] Share INTO THE CALL, not only to the room's display. Check the remote half can see it.
   [ ] One person in the room watches the chat and speaks for it.
   [ ] The chair repeats any question from the room before it is answered.
   [ ] Speak towards the microphone, not the wall. Far end of the table: lean in or repeat.
   [ ] Never unmute a laptop in a room that has a live microphone.

D. THE END
   [ ] Leave the call from the room system, so the next meeting does not start inside yours.
   [ ] Return the camera to its default shot if it was moved. Leave the remote in its holder.
   [ ] If anything did not work for the remote half, tell the desk: room, meeting, what they saw and heard.

E. FOR REMOTE ATTENDEES
   [ ] Use a headset, not the laptop's speaker and microphone.
   [ ] Say early, by name, if you cannot hear or see; the room cannot tell.
   [ ] Report anything that did not work after the meeting, with the room name and the time.

Callum replied to Imogen that afternoon with three questions and got "ceiling, rumble from the far end, grey box". He joined the room's test call with his phone in the corridor the next morning. He saw the ceiling. The camera had been tilted up at a whiteboard by a meeting a fortnight before and never put back. The microphone was the near-end one in a room that needed two. The lending team's chair had never heard of sharing into the call. One preset, one microphone from the spares shelf and one copy of the guide later, the next week's meeting began with "Imogen, can you hear Priya?" The answer, for the first time, was yes.

Frequently Asked Questions