Room Booking App: What Belongs on a Phone and What Belongs on the Wall
A room booking app is a third place to look, competing with the calendar your people already have open all day. Some jobs really do belong on a phone: finding a room while walking, releasing one you no longer need, checking in. Most do not. Here is how to split the work across phone, wall, calendar and chat.
A room booking app is a third place to look. Your people already have a calendar open all day. If you bought panels, there is a screen by the door. The app is a third surface, and it is the only one of the three that has to be installed, logged into, and remembered at the exact moment somebody is standing in a corridor with a laptop under one arm.
That is not an argument against apps in general. It is an argument about which jobs earn a place on a phone. A few genuinely do. Finding a free room right now while you are already walking. Booking it on the way. Releasing one you no longer need from the back of a taxi. Checking in so the system knows the meeting is real. Those are phone jobs, and they work badly everywhere else.
Everything else belongs somewhere that is not a phone. This post splits room booking across four surfaces (the phone, the wall, the calendar, and the chat tool), says what each is genuinely good at, and is honest about the case where a dedicated app wins outright: a campus where the hard question is not whether a room is free but where the room is.
The thing that quietly kills these rollouts is installs
Room booking apps rarely fail because the software is bad. They fail because a chunk of the company never installs them, and the chunk that does forgets the app exists until somebody mentions it at a Monday all-hands.
The failure mode looks like success for about six weeks. Launch week, the office team installs it, books a few rooms, and the usage chart goes up. Then new starters arrive without the onboarding email. The mobile device management push covers company laptops but not personal phones. By month four the same eleven power users are carrying the whole number and everybody else quietly went back to Outlook. Nothing broke. The line just went flat, and a flat line is the easiest chart in the world to stop opening.
Two things make this worse than it sounds. Partial adoption is worse than none: if half the company books in the app and half books in the calendar, neither view is complete, unless the app writes to the same room resources the calendar uses. And if it does write to those resources, you should ask what the app is adding that the calendar is not already doing.
The second problem is selection. The people least likely to install a room booking app are exactly the people who cause the most room conflicts: contractors, visitors, the account managers who are in the office twice a month, and anybody who refuses to put a work app on a personal phone. Those are not edge cases. That is the tail that produces most of your double bookings.
The honest test: before you sign anything, ask what fraction of headcount you can realistically get installed within 90 days, and whether you can push the app to personal devices at all. If you cannot push it, you are running a voluntary rollout, and voluntary rollouts do not reach everybody. Design for the people who will never install it, because they exist.
What genuinely belongs on a phone
Finding a room right now, while walking
This is the strongest case for mobile and it is not close. Somebody needs a room in the next two minutes. They are already moving, they do not have a laptop open, and the calendar's room picker is built for a different task: scheduling a future meeting with invitees, not answering "what is free on this floor, right now, for 25 minutes, that seats four".
The right interaction is a filtered list and nothing more. This building, this floor, free now, minimum capacity. Three taps to a result. Anything more elaborate makes it slower than walking down the corridor and looking through the glass.
Which is the counterargument, and it is a good one. In a 30 person office with four rooms on one floor, walking past the doors is faster than any app will ever be. Mobile room finding starts to earn its keep when the number of candidate rooms is larger than the number a person can check on foot in under a minute.
Booking on the way to the room
Adjacent job, different moment. Having found a room, you want to hold it before you arrive, so that somebody with a laptop open two floors up does not take it while you are in the lift. This wants one button and a duration, with a sensible default of 30 minutes. It does not want a subject line, an attendee picker, or a required meeting description.
Releasing a room you no longer need
This is the highest value phone action in the whole category and the one most products treat as an afterthought. Meetings get cancelled while people are in transit, in an airport, or in the meeting that overran and caused the cancellation. If releasing the room means opening a laptop, the room stays blocked, and a blocked room that nobody uses is the most expensive thing in the building for that hour. We have written about what a ghost meeting actually costs if you want the arithmetic.
Argue against the app here, though, because you should. This job is already solved in the calendar app on the same phone. Deleting the event releases the room, provided the room mailbox or resource calendar is configured to auto-accept and to process cancellations. If your rooms are set up correctly, Outlook mobile and the Google Calendar app already do this. If they are not, an app will not save you, because the room will stay busy in the calendar that everybody else is looking at.
Checking in
Check-in exists for one reason: so that a room nobody claimed can be handed back automatically. Phone check-in is a reasonable way to do it and it is the only way to do it if you have no hardware. It is also the weakest of the four phone jobs, because when a panel exists, pressing a physical button on the wall as you walk in is faster than unlocking a phone, finding an app, and finding the booking.
Whichever route you take, the release rules matter more than the interface. Fifteen minutes for a 30 minute booking, ten for a shorter one, and a clear notice period, is a starting point. The mechanics are covered in our guide to releasing meeting rooms automatically.
What does not belong on a phone
Scheduling a real meeting. Six attendees, a recurring series, a Teams or Meet link, an agenda, a room that needs to suit the number of people who accept. Every one of those is faster on a keyboard, in the tool where the invite already lives, and none of them get better on a 6 inch screen. If a vendor demos "book a recurring weekly leadership meeting from your phone", they are demonstrating that the demo was built to look comprehensive rather than to be used.
What belongs on the wall
Status at the point of confusion, requiring zero interaction. Two people are standing outside a closed door disagreeing about whether they are allowed in. That is a wall problem, and the fix is a screen that answers it from about five metres away without anybody touching, unlocking or opening anything.
The wall's job should stay small: room name, free or busy, what is next, and how long until that changes. Add the organiser only if your privacy position allows it, and note that showing meeting subjects on a corridor screen is a decision with data protection consequences, not just an aesthetic one.
Panels can also take a booking, and the good ones reduce it to a single press for the next free slot. That is genuinely useful and it is the one interactive feature on a panel that gets used. The moment a panel grows a keyboard for meeting subjects and an attendee search, you have built a slow tablet at head height in a corridor, and nobody types on it twice.
The failure mode to plan for: a panel that has lost its calendar connection usually keeps showing the last data it received. On e-ink it is worse, because the image survives a flat battery, so a dead device looks exactly like a working display showing a room as free. Whatever you buy, insist on two things. The screen itself should show a last-updated time or an explicit offline state, and the back end should alert you when a device stops checking in.
What belongs in the calendar
Everything else, because that is where the meeting actually lives. Both major platforms already have room resources, and most offices are running them half configured.
On Microsoft 365, rooms are room mailboxes. They can auto-accept with Set-CalendarProcessing -AutomateProcessing AutoAccept, they can be grouped into room lists so that Room Finder can show them, they carry capacity and equipment attributes, and they can enforce a booking window with BookingWindowInDays and a maximum duration with MaximumDurationInMinutes. If your rooms do not appear in Room Finder at all, the usual cause is a missing room list rather than a missing product, which we cover in Outlook Room Finder not showing rooms.
On Google Workspace, rooms are calendar resources with buildings, floors, capacity and features, and they auto-accept by default. Room suggestions in Calendar use the building and floor of the organiser's assigned working location, which is why rooms sometimes seem to be missing for one person and present for another.
The reason this matters to an app decision is simple. A very large share of "we need a room booking app" conversations turn out to be "our rooms are badly configured in the calendar we already pay for". Fix the resources first. Then look at what is left over, because that residue is your actual requirement. The two IT checklists worth working through are the Microsoft 365 room mailbox checklist and the Google Workspace room resources checklist.
Slack and Teams: the fourth surface, and the underrated one
The reason a chat command beats an app is not features. It is that the install step happens once, by one admin, for everybody. Nobody has to be persuaded to put anything on a personal phone. The tool is already on every laptop and, for most companies, already on most phones, with notifications already enabled.
A slash command like /book covers most of what people actually want from mobile: find something free now, hold it, release it. It runs in the place people already are, which is the entire point. Our post on booking meeting rooms from Slack goes through the interaction in detail.
The honest limits: chat is text, so there is no floor plan and no visual wayfinding. Discoverability depends on somebody remembering the command exists, which means you will be pinning a message in a channel and repeating yourself. And if your organisation restricts app installation in Slack or Teams, the admin step is not as trivial as it sounds. It is still the lowest friction route for most offices under a couple of hundred people.
When a dedicated app genuinely wins
There is a real case, and pretending otherwise would be dishonest.
- Large campuses and multiple buildings. When "is it free" is easy but "where is it and how do I get there" is hard, a phone with a floor plan and a route is the only tool that answers the actual question. A list of room names does not help a visitor in a building they have never entered.
- Floor plans and neighbourhood seating. If people pick a room based on where it sits relative to their team, you need a map, and a map wants a screen you hold.
- Mixed estate. Once you are booking desks and rooms and registering visitors, one app that does all three beats three tools. That is a genuinely different product category from room display software, and we set out the boundary in desk booking versus room booking.
- Buildings where the phone is already the badge. If people unlock doors and lifts with a phone app, adding room booking to it costs nothing in adoption, because the app is already installed and already opened daily.
A rough dividing line: if a new starter can learn the room layout in one day, you do not need a floor plan, and without a floor plan the app is mostly a slower calendar. Somewhere above a few hundred desks, or more than about three floors, or two buildings, that stops being true. It varies with building shape and signage quality, so treat it as a prompt to check rather than a rule.
How to decide in an afternoon
- Write down the five moments that actually hurt in your office. Be specific: "two people arrive at the same room at 10:00 on Tuesdays", not "room booking is painful".
- Sort each moment by surface. Confusion at a door is a wall problem. Scheduling is a calendar problem. Finding and releasing on the move is a phone or chat problem.
- Fix the calendar configuration first, because it is free and it removes a surprising share of the list. Auto-accept, room lists, capacity, equipment, booking windows, working hours.
- Cover the wall next if door confusion survived step three. A screen with no interaction solves it and needs no adoption from anybody.
- Cover mobile with chat before considering an app, because chat has no install step.
- Only then ask whether the remaining problems need a map. If they do, buy the app. If they do not, you would be buying an icon.
Where Lobby fits
Lobby does not have a mobile app, and that is a deliberate position rather than a roadmap gap. Lobby reads your Google Workspace or Microsoft 365 room resources, read-only, and never writes to the calendar. It puts status on three surfaces: a 7.5 inch e-ink panel by the door, readable from about five metres; a virtual display, which is the same view as a URL you can open on any tablet, TV or monitor you already own; and a room overview board that shows every room on one screen. On Pro Unlimited there is a Slack /book command, which is our answer to the mobile question: the surface people already have, with no install step per person.
Pricing is free forever up to three active displays with no credit card, then USD 30 per month billed yearly for unlimited displays, or USD 60 per month billed yearly for Pro Unlimited. Never per room, never per user. The hardware is bought direct from the manufacturer and owned outright at USD 69 per unit, dropping to USD 62.99 at 10 or more, with no markup from us. Setup takes under ten minutes and there is no sales call.
What it does not do: no mobile app, no floor plans, no wayfinding, no desk booking or visitor management in the rooms product, no room automation or AV control, no occupancy sensors, no enterprise SSO or SCIM at scale, no MDM on the e-ink hardware, and no on-premises Exchange without a hybrid setup. If your problem is a 40,000 square metre campus where people cannot find the room, Lobby is the wrong tool and one of the floor plan products is the right one.
TL;DR
- A room booking app is a third surface competing with a calendar people already have open all day, and the install step is where these rollouts quietly die.
- Partial adoption is worse than none, because two incomplete views of room availability produce more conflicts than one complete one.
- Four jobs genuinely belong on a phone: finding a free room while walking, holding it on the way, releasing one you no longer need, and checking in when there is no panel.
- Scheduling a real meeting does not belong on a phone. Attendees, recurrence, agendas and conferencing links are all faster in the calendar.
- The wall's job is status at the point of confusion with zero interaction: name, free or busy, what is next, when it changes. Nothing else.
- A panel that has lost its connection keeps showing old data, and on e-ink a flat battery leaves the last image on screen, which looks exactly like a working display. Insist on a last-updated indicator and offline alerting.
- Slack or Teams beats an app for mobile because one admin installs it once for everybody. Its limits are real: text only, no map, and discoverability depends on people remembering the command.
- Configure the calendar before buying anything. Auto-accept, room lists, capacity and equipment attributes, booking windows and working hours remove a large share of the complaints for free.
- An app genuinely wins on multi-building campuses, where floor plans and wayfinding matter, or where desks, rooms and visitors are all in one product. If a new starter learns your layout in a day, you are buying an icon.
Related reading
- Meeting room display vs room booking software, which splits the screen from the system behind it.
- Meeting room booking system: what you need, what you already have, and what you are being sold.
- How to reduce meeting room no-shows, including check-in and auto-release rules that people tolerate.
- QR code meeting room booking, the mobile route with no app at all.
- Using the Seeed reTerminal E1001 as a meeting room display.
- Best meeting room booking software in 2026, if you have decided you do need a platform.
Sources
- Microsoft Learn: Room mailboxes in Exchange Online, for how rooms are represented and grouped into room lists.
- Microsoft Learn: Set-CalendarProcessing, for
AutomateProcessing,BookingWindowInDaysandMaximumDurationInMinutes. - Google Workspace Admin Help: manage calendar resources, for buildings, floors, capacity and features. Admin console layouts change, so check the current page rather than a screenshot.
- Lobby hardware, for the hardware prices quoted above, which are the manufacturer's own list prices and not ours.