Checking your access…
Set their username, optional phone number, password, and starting role.
Controls what visitors land on. "Coming soon" shows index.html; "Live" shows the full production site and books via room pages.
Search by username or phone, or filter by role.
| Username | Phone | Role | Change role | Permissions | Edit | Delete |
|---|
The big heading visitors see first on the production website.
Shown to guests in the booking window when they request a room.
Paste any Google Maps link — a normal share link, directions link, or the proper "Embed a map" link all work now. Leave blank to auto-generate one from the address instead.
Choose a gallery category, then pick one or more photos/videos — visitors browse these as clickable tiles on the production site. You can give each file its own caption below before uploading.
Photos for a room are uploaded separately below, once the room is created.
Drag a photo to reorder. The first photo is used as the room's cover photo everywhere on the site.
A guest asked to cancel one of their current/upcoming bookings from "My bookings" and gave a reason. Approve marks the booking Cancelled; Decline leaves it as it was.
Guests submit these from a room's "Book now" button. Confirm availability and rates by phone, then mark as Confirmed or Declined here.
Each visiting IP address is counted once, site-wide, plus a separate unique-view count and a booking count per room category.
Every booking request and its current status, most recent first.
Recent page visits (most recent 300), including who was logged in at the time.
Sent automatically the moment a guest taps "Talk to an agent".
The menu of common issues & queries guests see in "Need Help?" — no login needed to browse these.
Opened whenever a guest taps "Talk to an agent". Closing a ticket ends the guest's access to it.
Loading stats…
Handoffs, senior-manager escalations, completed enquiries, and anything the AI couldn't handle. A WhatsApp ping also goes to the right staff number the moment this happens — this list is the record of it.
Loading alerts…
Loading conversations…
Edit the welcome message and the menu options guests see when they message the hotel on WhatsApp. Changes take effect within ~30 seconds — no code deploy needed.
WhatsApp numbers the AI notifies. Changes take effect within ~30 seconds — no code deploy needed. Every number below (reception + senior manager) also gets a daily "please reply to reset the timer" ping at 12:00 noon, so WhatsApp doesn't close the 24-hour messaging window with an inactive staff member.
Every number here gets notified for bookings, banquet/service enquiries, media, and general handoff requests. One per line (or comma-separated). Country code, no + or spaces (e.g. 919719162432).
Gets notified instead for complaints, upset guests, refund requests, or a guest asking for "the manager". Leave blank to use the reception number for these too.
Controls what Gemini knows about the property and how much conversation history it sees before replying to a guest on WhatsApp. Changes take effect within ~30 seconds — no code deploy needed.
Address, rooms, amenities, policies, pricing notes — anything the AI should treat as fact when answering guests. It will not invent details beyond this.
How many previous messages of a chat the AI sees for context before replying. Higher gives better continuity but costs more per reply.
Any additional tone or behavior notes for the AI, e.g. "always mention we're closed for Diwali on Nov 12."
Control the cases where the bot should stay quiet instead of auto-replying. Changes take effect within ~30 seconds — no code deploy needed.
Off by default. Staff are always alerted about the file either way — this only controls the automated reply back to the guest.
Comma-separated. If a guest's entire message is one of these (and there's no form/booking in progress, and it's not their very first message), the bot won't reply — this stops the "ok" / "sure" / "Ji" tail end of a conversation from triggering another bot message.
Note: a staff/reception number replying to the daily "reset the timer" ping never gets a bot reply, an alert, or a ticket — that's built in and not affected by these settings.
Pick exactly what each role can do. These are the defaults every user in that role gets, unless they have a personal override (set from the Users tab).
To give one specific user a custom permission set instead of their role's defaults, open the "Permissions" button next to their name in the Users tab.
Using role default. Check "Custom override" to set a personal permission list for this user.
Changing the username or phone updates how this person logs in — they'll need to use the new value next time.
This permanently deletes their account — login, profile, and role. This can't be undone.
Tell us why — this goes in the log, and can optionally be emailed to the guest.