The questions teams ask before bringing VIVI into the operation.
Concise answers about fit, channels, approved knowledge, integrations, rollout, customer data, and the role of hospitality teams.
What hospitality work can VIVI support?
VIVI supports guest-facing and employee-facing conversations such as reservations, property questions, service requests, concierge tasks, in-room dining, golf concierge, vacation-home support, and employee knowledge lookup. The right starting point depends on the requests your team receives and the approved information behind them.
How is VIVI different from a generic chatbot or IVR?
VIVI is designed around hospitality operations. Its agents use the property content, SOPs, availability, and business rules you approve; work across guest and employee use cases; and can connect with selected hospitality systems.
Which conversation channels can VIVI use?
VIVI can support voice, messaging, web chat, and Microsoft Teams experiences. Channel availability and configuration depend on the use case and deployment.
How does VIVI know what to say?
A VIVI agent is configured around approved sources such as property content, policies, SOPs, availability, and business rules. During rollout, teams define the knowledge and instructions that should guide each conversation.
What systems can VIVI work with?
VIVI can connect with selected property-management, point-of-sale, CRM, ticketing, HR, restaurant, spa, housekeeping, and enterprise service systems. Integration fit should be confirmed for the systems and operating process at your property.
What does a VIVI rollout look like?
The advisory process moves through four stages: assess the work and success measures, build around approved knowledge and rules, deploy a targeted use case, and measure answer quality and usage before expanding.
What happens when a request still needs a person?
VIVI is intended to support hospitality teams, not diminish the human service experience. Deployment planning defines what the agent should answer, what can connect to an existing system or process, and which requests should remain with staff.
How does VIVI protect customer conversational data?
Customer conversational data remains customer-owned. VIVI does not sell it or use it for marketing, encrypts it in transit and at rest, and limits internal access through controlled processes.
Can VIVI support multilingual conversations?
VIVI supports multilingual guest and employee conversations across its available channels. Confirm the language and channel coverage required for your deployment with a VIVI advisor.
How can I evaluate VIVI for my operation?
Start with a live hospitality demo, ask the contextual VIVI chat about your use case, or meet with an advisor. Bring the recurring questions, approved knowledge sources, channels, and systems you want to evaluate.