Niteporter

In development

What we are building next.

Nothing on this page ships today. It is here because a roadmap you can check is worth more than a feature list you cannot. Each of these is on it for the same reason: most of the machinery it needs is already running in the product, so it is a piece of work rather than a wish.

If one of them is the thing that would decide it for you, say so. What gets built first is decided by which hotels are waiting on it.

On the list

Status words below mean what they say. "In build" is being written now; "design" means the shape is agreed and nothing has been written; "largely exists" means most of it is in the product and the missing part is the view you would actually use.

In build

Ordering by QR code, from the guest's own phone

A code on the desk in the room opens a menu on the guest's phone. They order, and it goes on the room bill like anything bought through the television — useful for the guest who would rather not drive a menu with a remote control, and for the food and beverage numbers of hotels that have tried it.

The menu is the concierge catalogue this product already serves to televisions. The charge is the existing posting path, with its sundry mapping and its reconcile-rather-than-retry behaviour. Even the code generation is already a dependency here — it is what draws the enrolment code when you set up two-factor sign-in on the portal.

Left to build: the page the guest sees, and how a code is bound to a room.

Modelled

A digital compendium

The folder in the drawer, on the screen: breakfast times, the wifi password, how the shower works, what is worth walking to. Edited in the portal by the hotel, so it is right, which is more than can be said for most printed ones.

Directory entries are already part of the concierge interface and already served to Pro:Centric. What exists is the data; what does not is anywhere pleasant to read it or write it.

Left to build: the browsing screen, and the editor behind it.

Design

Text messages to guests

"Your room is ready." "Your car is at the door." "Here is your invoice." Sent on the things the broker already knows have happened, in the hotel's own words, to guests who are not sitting in front of the television.

Messages to a room already work — the portal writes to one television or every occupied one, over the same durable outbox that carries check-in to Pro:Centric. Sending to a telephone instead is another reader of a stream that is already there, fed by events the broker already records.

Left to build: a gateway, your templates, and the consent rules that go with them.

Largely exists

One dashboard across a whole group

Occupancy, health and what happened overnight across every property at once, rather than one hotel at a time. For the person who owns eight hotels and wants to know before breakfast which one had a bad night.

A property already has its night on one page — arrivals, departures, what was charged from a television, what was asked for and never closed. Occupancy, event throughput and connection health are all reported per property, and the tenant boundary that decides who may see which hotel is enforced in the database. The numbers exist and are already scoped correctly.

Left to build: the same page, for a group, at once.

The illustrations on this page are drawings of an intention, not screenshots. Nothing above has been photographed because there is nothing yet to photograph.

What we decided against

Worth saying, because the absences are deliberate and you would otherwise have to ask.

  • Maintenance scheduling and lost property. RMS does both, and your staff are already in RMS. Building a second place to look would make the day worse, not better.
  • Energy reporting. The broker knows whether a switch was told to turn off. It does not know how much power anything drew, and a sustainability number that is really a guess is not one you should put in a report.
  • A voice concierge. Not because it could not be done, but because a microphone in a hotel room is a decision about your guests' privacy, and that conversation should start with you rather than with a release note.

Which of these would you use first?

What gets built next is decided by which hotels are waiting on it. If one of these is the thing that would make the difference, that is worth an email.

Tell us which one matters