Two groups at one door
At ten o'clock a member arrives with a client for a pitch, having booked the eight-person room through the member app last week. Inside, an external hirer is setting up, having booked the same room through the website's hire page. The community manager at the front desk has a third booking for the same room written on the reception calendar from a phone call.
Across the corridor, the large boardroom has been booked all day by a member who has not turned up, and three people have asked for it.
Why bookings collide
A coworking operator often sells the same rooms in several ways: included credits for members, paid hourly hire for members over their allowance, day hire to the public, and listings on external marketplaces. Each channel has its own calendar.
| Booking channel | Where it is recorded |
|---|---|
| Member app or portal | Your membership platform |
| Website hire page | A separate booking plugin |
| External marketplaces | The marketplace's own calendar |
| Phone and walk-in | Reception calendar or memory |
| Internal events | The community team's shared calendar |
Two-way syncs between these break quietly, often when a booking is edited or cancelled rather than created. Nobody notices until two groups meet at the door.
What collisions and empty rooms cost
A member embarrassed in front of a client is a member reconsidering their membership. External hirers who arrive to a double booking leave a review. Rooms booked and not used could have been sold or given to members who needed them. The community team spends its mornings reshuffling bookings and apologising, and nobody trusts the room screens.
There is a revenue side too. Meeting rooms are often one of the few places a coworking operator can earn beyond the membership fee. If the calendar cannot be trusted, the team stops selling rooms to outside hirers on busy days, just to be safe, and that income never appears.
The booking layer we build
- One booking record per room slot, held in your membership platform if it can take the role, such as Nexudus or OfficeRnD, or in a small booking service we build next to it.
- Every channel writes to that record through its API: the member app, the website, marketplaces that support integration, and a simple reception screen for phone bookings.
- Edits and cancellations propagate the same way as new bookings, and any failed sync is flagged to the community team straight away.
- Screens outside each room show the live schedule and let people check in. If nobody checks in within the time you set, the room is released and shown as free.
- Members see real availability, including rooms released by no-shows, in the app.
- Each booking carries its billing basis, such as credits, paid hire or internal, so invoicing is correct.
If a marketplace does not offer an integration, we show its bookings on the reception screen and block the slot as soon as the confirmation email arrives, with a person checking anything unusual.
What a morning at the front desk looks like
One schedule that everyone trusts. Double bookings become rare exceptions caught before anyone arrives, rather than scenes at the door. Rooms nobody turned up for are released to people who need them. And the community manager's morning starts with members, not calendars.
The booking data also shows how rooms are really used. Which rooms are always full, which sit empty on Fridays, which are booked and abandoned. That is useful when deciding whether to convert a room or change its price.
Is this happening in your space?
- Members and hirers have arrived to find a room already occupied.
- Rooms are booked through several channels with separate calendars.
- Rooms sit empty after no-shows while others wait.
- The community team reshuffles bookings every morning.
- Room screens are not trusted.