Guest requests

Guest request management software for hotels, with QR codes and SLAs

The part Nivasik began as: every request from a room, the desk or WhatsApp becomes a ticket with one owner and a clock.

Free for 45 days · no card · we do the setup

Nivasik turns every guest request into a ticket with one owner and a clock. The guest scans the QR sticker in the room with the phone’s camera — no app, no login — and the request reaches the right person’s phone with acknowledge and resolve targets running, escalating up the chain if a target is missed.

It is in every plan, from ₹2,999 per property a month for up to 40 rooms or beds, and free for 45 days.

From scan to resolved

Seven steps, and the guest does only the first two.

  1. Scan. The guest points the camera at the sticker and the page opens already knowing the room — no app, no login, no room number to type.
  2. Ask. They tap a category — plumbing, AC and electrical, housekeeping, repair, security, front desk, amenities — then what they need, with an optional note.
  3. Route. An assignment rule sends it to whoever handles that category, and their phone rings; on the Android app, a critical request is a full-screen alert.
  4. Promise. The guest sees a reference number and the time the team has committed to.
  5. Clock. The acknowledge and resolve targets for that category run on the ticket, with every timestamp recorded.
  6. Escalate. A missed target re-assigns the ticket up the chain and notifies the next person.
  7. Resolve. The resolution is stamped, and it counts in each person’s response and resolution times.

What was measured at the pilot

The one figure Nivasik publishes, with the part that did not count left in.

32min

At the pilot — one small property, 12–30 May 2026 — 45 guest requests were raised in nineteen days and 29 were resolved, with a median of 32 minutes from request to resolved. The other 16 were never marked resolved and are not counted. 28 were logged by staff, 14 came from a room's QR code, 2 by voice and 1 on WhatsApp.

This is the only measured statistic Nivasik publishes. There are no customer counts, ratings or review scores to cite.

Not only from the QR

At the desk

Walk-ins and phone calls are logged at reception as the same kind of ticket, so the desk is not a second, invisible queue.

From WhatsApp

A request that arrives on WhatsApp is logged too, and from then on it has an owner and a clock like any other.

From housekeeping

A fault found while cleaning is raised from the room’s tile on the housekeeping board, with the room taken off sale if needed.

From the calendar

Preventive maintenance schedules raise their own tickets on the day they fall due.

From any building

Offices and shops use the same queue with their own categories — washroom hygiene, pantry supplies, a fridge that stopped cooling.

Into a daily digest

On Pro, an AI daily digest and anomaly flags are computed from your own tickets — nothing to set up.

Why a clock changes behaviour

A request posted in a staff WhatsApp group belongs to fourteen people, which means it belongs to nobody. The same request as a ticket has one name on it and a target next to that name, and the target is visible to the person, to the manager and — as a promised time — to the guest.

Nothing here does the work for anyone. What changes is that an ignored request stops being invisible: it breaches, it escalates, and it shows up in that person’s numbers at the end of the week. That visibility is the whole mechanism.

What it does not do

What the request queue leaves to people.

Not included, said plainly

  • The full-screen alert that rings through a silent phone is on the Android app only (downloaded from nivasik.com; it is not on Google Play yet).
  • A guest needs a phone camera and mobile data or Wi-Fi to scan; a guest without either still asks at the desk, and the desk logs it.
  • Targets and escalation make a delay visible and move it up the chain; they do not fix the tap.

What it costs

The request queue — QR portal, tickets, reception intake, targets per category, escalation, staff and permissions, reports and the Android alert app — is Core at ₹2,999 per property a month for up to 40 units, or part of Pro at ₹4,999 for up to 80. It is the part of Nivasik that has already run at a real property.

Core ₹2,999 per property / monthPro ₹4,999 per property / monthGroup ₹2,499 per property / monthPOS ₹1,499 per outlet / month45 days free, no card

Questions people ask

Do guests need to download an app?

No. They scan the QR sticker with the phone’s normal camera, tap a category and send — no app, no login and no phone number required.

How do QR codes for hotel rooms work?

Each room, dorm bed or space gets its own code, printed from Nivasik, so the request arrives already knowing where it came from. Editing a room never changes its code, so the sticker on the door keeps working.

What is an SLA for hotel requests?

A service-level target: how fast a request must be acknowledged and resolved. Nivasik keeps one pair of targets per category and runs the clock on every ticket.

What happens when a request is ignored?

When a target is missed, the ticket escalates up the chain and the next person is notified. The breach also shows in the reports, per person and per category.

Can I use this without the PMS?

Yes. Core is the request queue on its own — rooms and QR codes, staff, targets and reports — and a hotel can keep an existing PMS alongside it.

Does it work for offices and shops?

Yes. The words and categories change with the building: washrooms, pantries and meeting rooms in an office; equipment, billing and cold storage in a shop.

Try it on your own place, free for 45 days.

We set it up for you — your rooms, menu or stock list, your staff and your prices — and walk it end to end on your phone. No card, and we invoice only if you stay.