হোটেল হোক বা হোমস্টে — অতিথিবাণী, প্রতিটি অতিথির কণ্ঠস্বর।
Checkout ke 12 ghante ke andar AtithiVani har guest ko call karta hai — unki apni bhasha mein, aapki property ki taraf se. Jo baat woh review mein kabhi nahi likhte, woh aap seedha sun lete hain.
AI ke saath, baniye future-ready business
Figures describe the product as specified. The pilot has no audited results yet.
The post-stay call
A form gets answered by the guests who were already happy. A call gets answered by everyone, including the one whose heater failed — and it asks the follow-up question a form cannot.
Illustrative conversation. Guest names and rooms are invented.
From sentence to decision
Three agents, one loop. Nothing waits for an owner to read a dashboard.
Calls within twelve hours of checkout, in the language the guest booked in. It asks follow-ups — it is not a script read aloud.
Six dimensions come off the recording automatically: room, heating, food, access, staff, cleanliness. Sentiment lands beside them.
A detractor routes to the owner before a public review exists. A promoter gets a review link while the trek is still fresh.
The guest journey
AtithiVani is not a feedback tool bolted on at the end. It is present from before the guest leaves home.
যাত্রার আগে
Permit rules, the NH10 status and what to pack for Lava — sent before they leave home.
পৌঁছানো
A QR at check-in opens the assistant. Registration happens here, not at checkout.
থাকাকালীন
Treks, food, jeeps, emergency numbers — offline, in the guest’s own language.
ফেরার পর
The voice call, within twelve hours. The truth they would never type.
What it actually does
AtithiVani is not one clever prompt with a phone number attached. It is an orchestrator over nine sub-agents, with the rails, the regional data and the vendor network this belt actually needs.
The same agent, the same memory and the same three languages — whether the guest types on the web, talks into their browser, or picks up the phone twelve hours after checkout. One name, one voice.
আপনার থাকা কেমন হল?How was your stay?Twilio Media Streams, with barge-in
The ILP rules for Tsomgo, Nathu La and North Sikkim are a tool call, not a paragraph in a brochure — checked against the guest’s actual dates and nationality.
Road status, forecasts, elevation and air quality come from live signals, so a warning reaches the guest before the jeep does.
Four guardrail plugins run on every single turn — observability, grounding, consent and redaction. If a price, a grade or a permit rule is not in tool data, the agent says it will confirm rather than guessing. That is enforced offline in CI, not by a hopeful line in a prompt.
A fourteen-section manager dashboard: every live guest request, a service-recovery inbox that waits for a human, NPS and problem boards built from the post-checkout calls, and the day’s roads, weather and permits on the same screen.
Comps, refunds and vendor payments are recommended and never executed. The manager approves, every time.
PII lives in Firestore in asia-south1 behind deny-all rules, with a recording notice, instant opt-out and a full audit log.
The Gangtok dispatch desk AtithiVani negotiates with is a separate business on its own line — it never imports a byte of AtithiVani. Cab availability and operator-filed fares arrive over MCP; the booking itself is an A2A conversation with a signed agent card. That is what makes the network real rather than a demo.
A happy guest and an unhappy one get the same invitation. Recovery is a separate path, not a filter on who gets asked.
No bundler, no framework, self-hosted Indic fonts and a network-first service worker — because above Lava the network is the constraint.
Every capability above is built in the AtithiVani codebase today. Pieces that are specified but not yet wired in are deliberately left off this page.
The A2A moat
The defensible part is not the call. It is that AtithiVani's agent talks to the jeep operator's agent, the guide's agent and the permit desk — and re-plans a guest's day before the guest has finished breakfast.
Case · 14 August, NH10
What a closure on NH10 costs a belt of homestays, and what happens when the re-planning is not a human's morning.
NH10 is the only road for most of this belt. A closure does not produce a notification — it produces eleven separate phone calls an owner has to make while running breakfast service. AtithiVani makes them, in parallel, as agent-to-agent calls that do not need anyone to pick up.
One message, in the language they have been using, with the new plan and nothing else. Not six notifications, not a status page, not an apology for a delay that has already been solved.
Questions
The ten questions a homestay owner, a hotel manager or a district officer puts to us before anything else.
AtithiVani is a voice-first guest-experience platform for hotels and homestays in the Himalayan belt — Darjeeling, Sikkim, Kalimpong and the Dooars. It accompanies a guest from pre-arrival to post-stay, and within twelve hours of checkout it calls them in their own language, on the property’s behalf. It is a product of SARGVISION Intelligence Pvt. Ltd.
A form is answered by the guests who were already happy. A call is answered by everyone — including the guest whose heater failed — and it asks the follow-up question a form cannot. What comes back is the sentence a guest would never have typed.
Bengali, Hindi and English, spoken naturally rather than read from a script. The same agent, with the same memory, carries all three across web chat, browser voice and the phone call.
Every call is placed and conducted by an AI agent — no human dials. A human is required wherever money moves: comps, refunds and vendor payments are recommended by the system and approved by the manager, never executed automatically.
It is free to every homestay and hotel through December — calls, the guest assistant, WhatsApp summaries and registration, all of it, for the whole pilot. No card and no contract. We are not setting a price until the pilot shows what an owner actually wants to pay for.
Guest personal data lives in Firestore in Google Cloud’s asia-south1 region, inside India, behind deny-all security rules. Every call carries a recording notice, opt-out is immediate, and a full audit log is kept.
No. Guests scan a QR at check-in, and AtithiVani places the calls as a neutral third party — so a property cannot pick which guests are surveyed. Review invitations are never gated either: a happy guest and an unhappy one get the same invitation, and service recovery runs as a separate path rather than as a filter on who gets asked.
Yes. The ILP rules for Tsomgo, Nathu La and North Sikkim are checked as a tool call against the guest’s actual travel dates and nationality — not quoted from a brochure paragraph.
Road status, weather, elevation and air quality are live inputs. When a closure lands, the guest agent identifies every guest affected, renegotiates the jeep with the operator’s own agent, shifts the guide window, re-times any Sikkim permit that would have expired on the delay — and then tells each guest once, in their own language, with the new plan.
Four guardrail plugins run on every single turn — observability, grounding, consent and redaction. If a price, a grade or a permit rule is not in tool data, the agent says it will confirm rather than guessing. That is enforced offline in CI across twelve eval dimensions, ten of which are hard gates, so a regression fails the build rather than reaching a guest.
The pilot
Calls, the guest assistant, WhatsApp summaries and registration — all of it, at no cost, for the whole pilot. We are not setting a price until the pilot shows what an owner actually wants to pay for.
AtithiVani places calls on behalf of properties as a neutral third party. Guests scan at check-in, so a property cannot choose which guests are surveyed.