NewLate checkout approvals now in the front-desk console
Innstant gives every hotel guest a personal concierge on their own phone. They order dinner, ask for towels, reach the desk and extend their stay in a few taps. Your kitchen, housekeeping and reception see it the moment it happens.
What it is
Dinner with modifiers, extra towels, an iron, someone from the desk, a later checkout, where to eat nearby. Every request confirms instantly and shows its live state.
No app, no login, no waiting on hold
One order lands as a ticket, a pickup, a delivery and a folio line, each on the screen of the person who needs it. Nothing is relayed by radio or sticky note.
Kitchen display, staff phones, desk console
Service charge, delivery fee, late checkout tiers and taxes are configured once and applied every time. Promise times are measured. The event log settles arguments.
Revenue you were leaving in the room
How it works
One order, four screens, no phone calls. Every step writes to the folio and to an audit log, so nothing is lost between a guest, a runner and the front desk.
Walk through the productThe link already knows room 214, Anjali, and that she checks out Thursday. No login screen, no verification until the first charge.
Modifiers, quantity, a note for the runner. The cart pill morphs as items land. Sent to room 214, charged to the folio.
It pulses until someone acknowledges it. Accept starts the prep timer; reject sends the reason straight back to the guest.
He sees the note: no bell after 10, please knock. Picked up, delivered, done. The guest watched every state on her phone.
Devika sees the line, the timestamps and who delivered it. At checkout it settles with everything else, one receipt.
Revenue
Hotels leave money in the room because ordering is a phone call, late checkout is a shrug and the spa is a leaflet. Innstant turns each of those into a tap the guest takes on their own — priced, timed and charged to the room.
+38%
in-room dining orders
Guests order more when they can browse a menu with pictures and prices at their own pace, at 11pm, without speaking to anyone.
₹2,500
average late checkout fee
Tiered fees the guest requests themselves. The desk approves in one click when the room is free. It used to be a shrug.
6×
more amenity requests logged
Laundry, airport cars, a bottle of wine. In one list next to free towels, each with a promise time.
10%
service charge, applied every time
Service charge, delivery fees and taxes are configured once. Every order carries them. Every one reconciles.
“Our night kitchen used to take orders on a landline with the fryer running. Now the ticket is on the screen before the guest has put the phone down.”
“Late checkout was a favour we did for free, because arguing about ₹2,000 at the desk felt cheap. Now guests ask in the app and pay without a conversation.”
“I chose it because the guest app looked like our hotel and not like a food-delivery clone. Our guests notice that kind of thing. So do I.”
Themes
Colour, type, shape and motion are one layer of custom properties. A second property is a palette, not a fork of the layout — which is why these six are a week of work each rather than a rebuild.
Don’t see yours? We build a theme from your brand guide in about a week, and you can preview it before signing anything.
Security & multi-tenancy
Innstant runs many hotels on one platform. The isolation between them is enforced where a bug in a screen cannot bypass it: in the database.
The application connects as a role that owns no tables and cannot bypass RLS. Every query runs inside a tenant context. A cross-tenant read returns nothing, and a test in our suite tries every session.
A QR scan issues a request-tier session tied to the room and the active stay. The first charge escalates it with one verification prompt. Tokens are hashed at rest and revoked at checkout.
Every staff action is authorised against a resource and an action, not a page. Roles are seeded per property; a kitchen login cannot see folios, a runner cannot edit menus.
Every request body, every environment variable and every webhook is validated with a schema before a line of business logic runs.
Settlement runs through Razorpay. We store a reference and an amount. Orders are idempotent, so a retried request cannot charge twice.
Every status change writes a row in the same transaction that made it, to a table with UPDATE and DELETE revoked. It is the SLA record and the dispute record at once.
What we don’t do
Every demo property is seeded from a fixture and reset on demand. Sales, support and engineering never touch a live guest record to show you something.
Hosting
Application and database run in Singapore for latency to Indian properties. Payments go through Razorpay; card data never touches our servers. Media is stored in object storage with signed URLs.
Book a demo
Tell us the property and we set up a demo instance with your name, rooms and outlets before the call. You scan, you order, your team watches it land.
Or don’t wait for us — the demo property is open right now, with a kitchen, a runner and a front desk behind it that all actually work.