Hybrid work was supposed to combine the best of both. In practice it often combines the worst: the people in the office cannot see the people at home, the people at home cannot tell whether the office is busy or empty, and everyone spends the first minutes of every interaction working out where the other person is.
That friction has a name in most hybrid teams, even if nobody says it out loud: the "are you in?" tax. This guide is about removing it with a shared presence layer that works the same whether someone is at a desk or a kitchen table.
The hybrid visibility gap
A fully remote team has one mode. A fully in-office team has one mode. A hybrid team has at least four on any given day: in the office and free, in the office and busy, at home and free, at home and busy. And the signals for each come from different systems that do not talk to each other.
The office signals are physical: you can see someone at their desk, see their headphones, see the meeting room is occupied. The remote signals are digital: a chat status, a calendar block, a camera that is on or off. Nobody has both sets at once. The person at home cannot see that the office is empty because it is a Friday; the person in the office cannot see that their remote colleague has been in a focus block for two hours.
So people ask. "Are you in today?" "Is anyone around?" "Free for a quick one?" Each question is small. Multiply it across a team and a week and it becomes a real cost, not just in minutes but in the questions that never get asked because the asking felt like too much.
The fix is a single presence layer that both halves of the team maintain, and it has to be one that mostly maintains itself.
The six presence states explained
A good presence system has more than online and offline and fewer than a dozen states. Six covers what a team needs to know.
| State | Meaning on a hybrid team | Set by |
|---|---|---|
| Available | Working and can be approached, wherever you physically are | Default when the office is open |
| Focus | Working, please do not interrupt unless urgent | You, when you start a block |
| In a meeting | Currently in a meeting room or on a call | Automatically, when you enter a meeting |
| Do not disturb | Hard no; treat as unavailable | You, rarely |
| Away | Stepped out; back soon | You, or automatically after inactivity |
| Offline | Not working | Automatically when the tab closes or the heartbeat expires |
Two details make this work for hybrid teams. First, the states describe availability, not location. An engineer at a desk in the office and one at home are both simply available, which is the question people actually want answered. Location can go in a status message ("in the office today") if it matters. Second, the transitions that people forget, in a meeting and offline, happen automatically. Presence that expires when someone closes the tab is the difference between a board that people trust and one they double-check with a message.
KioskMate implements exactly these six states, with an optional status message and the room you are in, and expires presence on a heartbeat. The features page has the details.
Rooms as location
States tell you whether someone can be approached. Rooms tell you where they are and, often, what they are doing, without a word being typed.
In a persistent virtual office everyone is in a room. If the design lead is in the open floor, she is available for ordinary contact. If she is in a focus room, the room itself says do not knock. If she is in the client suite, she is with a customer. If she is in the break room, she would probably like company. The office layout becomes a shared map that both the in-office and remote halves of the team read the same way.
This is the part hybrid teams underestimate. The office building already gives in-person staff a map; the point of a virtual office is to give the whole team the same one, so that the person at home sees the design lead in the client suite exactly as the person two desks away would. In-office staff keep the office open in a tab just like remote staff do, and for about a week that feels redundant. Then someone in the office needs a remote colleague, looks at the board instead of sending a message, and it stops feeling redundant.
Norms for hybrid teams
Tooling supplies the signals; norms make people trust them. Three are enough.
Let the heartbeat do the work. Do not ask people to set themselves away or offline. Ask them to keep the office open while they work and let presence expire naturally when they stop. Manually maintained status is wrong within an hour; automatically expiring status is wrong for at most a few minutes.
Use status messages for location and context, not for availability. "In the office, desk 14" or "working from the Lisbon apartment this week" is useful. "Busy" is not, because the state already says that. A status message is where hybrid teams put the information that a fully remote team would not need.
Meeting rooms are the meeting. When a hybrid meeting happens, everyone joins the virtual meeting room, including the people sitting together in the physical one. It feels odd for a day. It removes the split between the people in the room and the people on the screen, because there is no longer a room and a screen, just a room. It also means the meeting shows up on the board as in a meeting for everyone involved.
Choosing a tool: calendar, chat or a persistent office
Hybrid teams typically try three approaches in order.
Calendar status. Blocking "office day" or "WFH" in the shared calendar tells people where you plan to be. It says nothing about whether you are free now, it is set once and never updated, and it lives in a tool people open to book time, not to check availability. Useful for planning, useless for presence.
Chat status. The green dot is the most common answer and the least trusted. It is green during meetings, grey when someone is working with the app closed, and the custom status text is whatever someone typed three days ago. Chat is excellent at asynchronous communication; presence is a synchronous problem, and the tool was not built for it. Our piece on virtual office vs Slack goes deeper on where each belongs.
A persistent office. States that expire, rooms that mean something, and a board both halves of the team read. It is the only one of the three that answers the actual question, who is around and can I approach them, without anyone asking it. The trade-off is that it is one more tab to keep open, and the norms above have to be written down.
For most hybrid teams under about a hundred people the third option is the right one, and it is cheap to find out: the Free plan on KioskMate gives a team of up to 8 an office with 7 rooms. Set it up on a Monday, ask both the office and remote halves to keep it open for a week, and count how many times anyone asks "are you in?" by Friday. You can open the office here.