23:47 · Room 304 is typing
Korimaa answers questions, takes requests, arranges services, recommends what's worth doing — and knows when your team should step in. All inside the app your guest already has open.
You are the guest. The Marigold House is an illustrative 22-room property — try anything a real guest would ask.
15 minutes · nothing for your guest to install · works alongside the PMS you run
What a quiet front desk actually costs Every message that waits until morning is a guest quietly deciding that next time, they'll book the place that answered.
How it works
This is the whole product. Everything below it is detail.
Korimaa answers instantly, from your hotel's own information — not from the internet's idea of your hotel.
The request is taken, confirmed, and dropped into the right team's queue — already sorted, without anyone relaying it.
Anything urgent, unhappy, or outside what it's been trained on goes loudly to a human — with the whole conversation attached.
It is your hotel's own WhatsApp number. Nothing to install, nothing to explain at check-in, nothing to abandon on day three. The thread stays in their chat list next to their family — which is exactly why they use it.
The whole stay
The same conversation follows the guest through the stay, so nobody has to start again — and neither does your desk.
Landing at 9:40 tomorrow — can someone pick us up?
Car booked for 9:40, driver's name sent the night before. Concierge desk notified.
We're early. Any chance of getting in before two?
Flagged for the desk; the guest is messaged the moment the room is turned around. Front desk notified.
Send dinner up to the room — the dal and rice.
Order placed, 25 minutes, on the folio. Kitchen notified.
The AC isn't cooling.
Apology, one question to tell maintenance what to bring, and someone on the way. Maintenance notified.
Somewhere nice for dinner tonight?
Two places your own staff would send family to — and a table held, if they want one. Your recommendations, not a search engine's.
Can we check out at 2 instead?
Answered against your actual policy, noted on the room, and a taxi offered for the airport. Front desk notified.
Behind the conversation
A guest sees one warm reply. Your house sees a request that has already been graded, routed and put in front of the right team. That grading is the actual product.
Questions answered. Wi-Fi, breakfast, timings, policies, directions. Logged for the morning digest. Nobody's phone makes a sound.
Requests routed. Towels to housekeeping, food to the kitchen, the AC to maintenance, a taxi to the concierge desk. If a team doesn't acknowledge it in time, it escalates on its own.
Humans interrupted. A complaint, a safety issue, an explicit "get me a person", or Korimaa failing twice in a row. The duty manager is alerted with the full thread.
Korimaa can only do the things it has been given the ability to do. When a guest asks for something outside that, it says so and passes the conversation on — rather than inventing an answer your front desk then has to apologise for.
Try it in the demo above: ask it something no hotel could answer.
For hotels
No dashboards to learn, no new screen for your team to watch. The work simply arrives already sorted.
Be skeptical
So here are the four objections that actually come up, answered without the marketing.
Your AI will say something wrong to my guest, and I'll wear it.
It can only do what it has been given the ability to do: answer from your information, take a request, take an enquiry, start a check-in, or fetch a human. There is no free-roaming answer machine behind it. Test that in the demo above — ask it something it cannot know.
Somebody will pay through a chatbot and it'll be my problem.
No payment is possible in the chat, because no payment capability exists in it. Charges go to the folio; settlement stays at your desk, by card, UPI or cash, exactly as it does now.
This will take months and drag my PMS into it.
Korimaa runs alongside the PMS you already have. Direct integration exists for IDS Next and Opera; if you run something else, ask on the call and you'll get a straight yes, no, or roadmap. The concierge itself goes live in days.
Where does my guests' data actually go?
Conversations run over WhatsApp's own infrastructure. ID documents, signatures and payment never touch the AI at all. Under India's DPDP Act the hotel is the controller and Korimaa the processor, so a data-processing agreement is part of onboarding. Korimaa holds no SOC 2 or ISO certification, and won't claim one.
Getting started
Rooms, menus, timings, policies, and the local recommendations your desk gives out twenty times a week. Usually one call and a folder.
You throw your guests' real questions at it until the answers sound like your hotel rather than a template. Your teams and their queues get set up in the same pass.
Your existing WhatsApp Business number, or a new one we set up. Guests message it the way they message anyone. Nothing changes for your team except the volume at the desk.
Questions hoteliers ask
No. Guests use ordinary WhatsApp on their own phone. There is no app, no QR code to explain at the desk and no login.
It doesn't guess. Korimaa can only do the things it has been given the ability to do — answer from your hotel's own information, take a request, start a check-in, take an enquiry, or hand over to a human. Anything outside that goes to your team instead of becoming an invented answer.
Korimaa runs alongside your existing PMS — you don't change systems to use it. Direct integration exists for IDS Next and Opera. For any other PMS, ask on the demo call and you'll be told honestly whether it is connected today or on the roadmap.
No, and deliberately. There is no payment capability inside the chat at all, so there is no payment surface to attack there. Charges go to the guest's folio and are settled at your desk exactly as they are now.
It replies in the language the guest writes in. The demo on this page shows English, Hindi and Hinglish; which languages your property needs is a configuration question, not a rebuild.
Days rather than months for the concierge itself. The part that takes real time is gathering your menus, policies and the answers your desk already gives, and that is done with you on a call.
No. The design principle is the opposite: take the repetitive load off the desk so your people are free for the guests standing in front of them. The human desk is always the fallback.
Pricing depends on the property's size and what you switch on, and it is given on the call rather than published here. There are no long lock-ins.
See what it would look like if they got an answer. Fifteen minutes, most of it you testing it against your own guests' questions.
15 minutes · no lock-ins · you can leave the call at any point
Or write to [email protected].