What it does · Concierge
A request that lands where somebody will see it.
A guest asking for towels through the television is only useful if that becomes a task in front of the person who fetches towels. Niteporter raises every request as a trace against the reservation in RMS, routed to the department that owns it — so it appears where your staff already work, not in a system nobody has open.
How it works
The menu is yours. Every item on it names a department, and that department is where the request arrives.
Because the trace is written against the reservation, it carries the room, the guest and the time with it. Nobody has to work out who asked. And because it lives in RMS rather than here, it is in the same list as every other job the department has, and it closes the same way.
A request the guest makes is confirmed on the screen with the time it went in. That is the difference between a feature people use and one they try once.
Asking how it went
The same interface can collect a rating at the end of a stay. It is a small thing that pays for itself the first time a guest tells the television something they would never have said at the desk.
Low scores go somewhere on purpose
You set the threshold and the department. A rating below it is routed as its own trace — to the duty manager, or whoever should hear about it while the guest is still in the building rather than a week later in a review.
Startup refuses a configuration where low ratings would reach nobody. A feedback form that quietly discards complaints is worse than not asking.
What you control
All of it, from the portal, without ringing us. Changes take effect on the next request — there is no restart and no deployment.
- The menu. What appears, what it is called, and in what order. A resort's list is not a city hotel's list.
- Where each item goes. Every entry names an RMS department, so towels go to housekeeping and a taxi goes to the desk. Startup refuses an item routed to a department that does not exist, and refuses a route for an item that is not on the menu.
- Faults, sent to maintenance. LG's interface has no maintenance category, so a broken kettle arrives looking like a request for towels. Give the fault its own menu item, point it at its own department, and it stops landing on the housekeeper.
- What a request costs, if anything. An item can be free or it can carry a charge, in which case it posts through the same sundry mapping as everything else you sell.
- Whether feedback is collected, at what threshold a rating counts as low, and who hears about it.
The fine print
- Niteporter routes requests; it does not manage them. Fulfilment stays in RMS, where your staff already are. Building a second task list nobody has open would help no one.
- A request is only as useful as the department behind it. If nobody works the trace queue at 3am, the television will still have raised it faithfully at 3am.
- Wake-up calls are raised as tasks in RMS, not fired by the broker. It does not ring telephones or override alarms.
- Requests carrying a charge follow the money rules: refused while RMS is unreachable rather than accepted and posted later.
Everything on this site is one price. A property's room band covers every interface — this one included — along with the portal, hosting, backups and updates. Nothing on this page is an extra. See the band for your rooms · running a group?
Want to see it against your own data?
The quickest way to judge any of this is against your RMS training database. It needs no production credentials, it cannot touch a live reservation, and it is the one mode that lets you watch a whole night happen before you commit to anything.