AI Voice Agent for Hotel Operations
Building production-grade AI systems that handle the messy realities of real-world deployment — not just polished demos.
- Overview
- The Problem
- Product Thesis
- How It Works
- System Architecture
- Key Product Decisions
- Deployment & Impact
- Demo
- Learnings & What's Next
- About
Sakhi is an AI-powered voice agent designed to handle high-volume guest interactions in hotel operations — spanning support, reservations, and front office services.
The core insight: Most AI hotel assistants are chatbots. Sakhi is an operational workflow layer that integrates with existing hotel systems to complete tasks, not just answer questions.
Unlike proof-of-concept demos, Sakhi is built for production environments with:
- Noisy, real-world inputs (diverse accents, background noise)
- Real-time operational constraints
- Critical system integrations (PMS, ticketing systems)
- Human expectations for reliability and accuracy
Hotels face a crushing burden of repetitive, high-frequency guest calls:
"Can I get extra towels?"
"What's the WiFi password?"
"Is early check-in available?"
"I need a wake-up call at 6 AM."
| Pain Point | Consequence |
|---|---|
| Staff overload during peak hours | Guest service quality degrades |
| Slow response times | Guest satisfaction drops |
| Low-value repetitive tasks | Staff can't focus on high-touch experiences |
| Manual ticketing overhead | Increased operational costs |
The Real Issue: Not intelligence — it's workflow efficiency.
AI in hospitality should not replace humans.
Instead, it should:
- Handle repetitive workflows → Free up staff capacity
- Augment efficiency → Enable staff to focus on high-value tasks
- Preserve human touch → Escalate complex interactions seamlessly
Sakhi is not a chatbot.
Sakhi is an AI operations layer for hotel workflows.
Guest Call → Speech Recognition → Intent Detection → Decision Engine → Action Layer → Response → Confirmation → (Escalate if needed)
- FAQs: WiFi passwords, amenity locations, operating hours
- Ticketing: Automated creation for housekeeping and maintenance requests
- Status Updates: Real-time tracking and notifications
- Availability Checks: Real-time integration with PMS systems (AxisRooms, Oracle)
- Booking Processing: New reservations and modifications
- Confirmation Handling: Automated confirmation and follow-ups
- Check-in/Checkout: Late checkout requests, early check-in availability
- Guest Services: Wake-up calls, room service requests
- Special Requests: Custom guest needs and preferences
graph LR
A[User Call] --> B[Speech-to-Text]
B --> C[Intent Detection<br/>LLM Layer]
C --> D[Decision Engine]
D --> E[Action Layer]
E --> F1[PMS Integration]
E --> F2[Ticketing System]
E --> F3[Knowledge Base]
F1 --> G[Response Generation]
F2 --> G
F3 --> G
G --> H[Text-to-Speech]
H --> I[Response to User]
D --> J[Fallback: Human Agent<br/>with Full Context]
- Speech Processing: Real-time STT/TTS optimized for Indian accents
- NLU Engine: Custom LLM layer for intent classification
- Integration Layer: RESTful APIs for PMS and operational systems
- Fallback System: Seamless human escalation with conversation context transfer
The Problem: Full automation fails spectacularly in edge cases.
Our Approach:
- Built seamless escalation with full context transfer
- Zero information loss during handoff
- Guests never repeat themselves
Why It Works: Trust is built through reliability, not perfection.
The Problem: AI without actionability creates friction.
Our Approach:
- Deep PMS integration (AxisRooms, Oracle)
- Operational system connectivity (ticketing, notifications)
- Focus on task completion, not just conversation
Why It Works: Users care about outcomes, not clever responses.
The Problem: Highly variable outputs destroy user trust.
Our Approach:
- Structured flows with guardrails
- Predictable behavior over impressive but inconsistent responses
- Constrained decision trees for common paths
Why It Works: In operations, predictability > intelligence.
The Reality:
- Diverse accents (Hindi, Tamil, Telugu, Bengali)
- High background noise in hotel environments
- Operational variability across properties
Our Approach:
- Accent-robust speech models
- Noise-filtering pipeline
- Configurable per-property workflows
Why It Works: AI that works in labs ≠ AI that works in hotels.
Properties:
- Bloom Hotels (Bangalore)
- Ginger Hotels (Bangalore)
- Lemon Tree Hotels (Bangalore)
Duration: 6-month pilot program
| Challenge | Impact | Solution |
|---|---|---|
| Staff adoption resistance | Low initial usage | Champion network + peer-led training |
| System reliability expectations | Zero tolerance for failures | Graceful degradation + fast escalation |
| Integration dependencies | Third-party API reliability | Retry logic + fallback paths |
| Diverse use cases | Edge cases we didn't anticipate | Iterative workflow refinement |
The Insight: AI adoption is a behavior problem, not a technology problem.
Our Approach:
- Champion Network: Identified early adopters in each property
- Peer-Led Onboarding: Staff training by staff, not vendors
- Real-Time Feedback Loops: Weekly iteration cycles with teams
Results:
- 3x faster adoption than top-down training
- Higher trust in the system
- Organic feature requests from staff
- 40% reduction in repetitive call volume
- 2.5 minutes average time saved per interaction
- 60%+ automation rate for support queries
- < 5 seconds average response time
- 85% resolution without human escalation
- 4.2/5 guest satisfaction score for AI interactions
- 15+ hours/week freed up per property
- Focus shift to high-value guest interactions
- Reduced burnout from repetitive tasks
Guest: "Hi, I need to checkout late tomorrow. My flight is at 8 PM."
Sakhi: "I'd be happy to help with a late checkout. Let me check availability."
[Checks PMS system]
"Good news — late checkout until 3 PM is available at no charge.
Would you like me to confirm that for you?"
Guest: "Yes, please."
Sakhi: "Perfect. I've updated your reservation for late checkout at 3 PM
tomorrow. You'll receive a confirmation text shortly. Is there
anything else I can help with?"
Key Behaviors:
- Real-time PMS integration
- Natural conversation flow
- Proactive confirmation
- Task completion focus
The Gap: We built monitoring reactively after deployment issues.
Better Approach:
- Pre-deployment evaluation framework
- Synthetic test cases for edge scenarios
- Automated regression testing
The Gap: Initially underestimated accent diversity impact.
Better Approach:
- Larger accent-specific training datasets
- Regional model fine-tuning
- Active learning from production failures
The Gap: Escalation logic was too conservative initially.
Better Approach:
- Data-driven confidence thresholds
- User-configurable risk tolerance
- A/B testing escalation strategies
The Gap: Weekly iteration cycles were still too slow.
Better Approach:
- Real-time feedback collection
- Automated anomaly detection
- Daily micro-iterations on high-impact issues
- Natural Interface: Aligns with existing guest behavior
- Low Friction: No app downloads or account creation
- Ideal for Repetitive Tasks: High-volume, low-complexity interactions
- Clear Workflow Structure: Repetitive, rule-based tasks
- Measurable ROI: Time savings directly translate to cost savings
- Existing System Integration: PMS APIs enable actionability
Sakhi is not a chatbot — it's an AI workflow engine for hospitality operations.
-
AI Reliability ≠ Model Accuracy
System design matters more than model sophistication. -
Context Transfer is Critical
Seamless human escalation requires full conversation state. -
Real-World Data > Synthetic Data
Production edge cases are impossible to anticipate in labs.
-
Adoption Requires Champions
Top-down mandates fail; peer-led adoption succeeds. -
Actionability > Intelligence
Users value task completion over impressive conversations. -
Graceful Degradation > Perfect Automation
Systems that fail predictably beat systems that fail mysteriously.
-
Change Management ≠ Training
Behavior change requires ongoing support, not one-time sessions. -
Integration Reliability is a Dependency Risk
Third-party APIs become single points of failure. -
Edge Cases Emerge in Production
No amount of pre-deployment testing catches everything.
Speech Processing
├── STT: Custom-trained models for Indian accents
└── TTS: Neural TTS with prosody modeling
NLU & Decision Layer
├── LLM: GPT-4 for intent classification
├── Decision Engine: Rule-based + ML hybrid
└── Context Management: Redis for session state
Integration Layer
├── PMS: AxisRooms, Oracle Hospitality APIs
├── Ticketing: Custom REST APIs
└── Notifications: SMS (Twilio), Email (SendGrid)
Infrastructure
├── Backend: Python (FastAPI)
├── Database: PostgreSQL (transactional), Redis (session)
├── Deployment: Docker, Kubernetes
└── Monitoring: Prometheus, Grafana, Custom logging
sakhi/
├── speech/ # STT/TTS processing
│ ├── stt_engine.py
│ └── tts_engine.py
├── nlu/ # Intent classification
│ ├── intent_detector.py
│ └── context_manager.py
├── decision/ # Decision engine
│ ├── workflow_engine.py
│ └── escalation_logic.py
├── integrations/ # External system connectors
│ ├── pms/
│ └── ticketing/
├── api/ # API layer
│ └── main.py
├── tests/
│ ├── unit/
│ └── integration/
└── docs/
├── architecture.md
├── deployment.md
└── api_reference.md
- Python 3.9+
- Redis
- PostgreSQL
- Docker (optional)
# Clone repository
git clone https://github.com/prernaaagarwal/Sakhi.git
cd Sakhi
# Install dependencies
pip install -r requirements.txt
# Configure environment
cp .env.example .env
# Edit .env with your API keys and configuration
# Run database migrations
alembic upgrade head
# Start the service
python api/main.py# Build image
docker build -t sakhi:latest .
# Run container
docker run -p 8000:8000 \
--env-file .env \
sakhi:latest# Speech Services
STT_API_KEY=your_stt_key
TTS_API_KEY=your_tts_key
# LLM Configuration
OPENAI_API_KEY=your_openai_key
LLM_MODEL=gpt-4
# PMS Integration
PMS_PROVIDER=axisrooms # or oracle
PMS_API_URL=https://api.axisrooms.com
PMS_API_KEY=your_pms_key
# Database
DATABASE_URL=postgresql://user:pass@localhost/sakhi
REDIS_URL=redis://localhost:6379
# Monitoring
SENTRY_DSN=your_sentry_dsn
LOG_LEVEL=INFOStart a new voice interaction
Request:
{
"phone_number": "+919876543210",
"property_id": "bloom-bangalore-01"
}Response:
{
"call_id": "call_abc123",
"status": "initiated",
"timestamp": "2026-04-14T10:30:00Z"
}Process speech input during a call
Request:
{
"call_id": "call_abc123",
"audio_data": "base64_encoded_audio",
"context": {}
}Response:
{
"intent": "late_checkout_request",
"response_text": "I'd be happy to help with a late checkout...",
"action_taken": "pms_query_initiated",
"escalate": false
}Full API documentation: API Reference
# Unit tests
pytest tests/unit/
# Integration tests
pytest tests/integration/
# Full test suite with coverage
pytest --cov=sakhi tests/Current coverage: 85%+
Focus areas:
- Speech processing pipeline
- Intent classification
- Decision engine logic
- PMS integration error handling
We welcome contributions! Please see CONTRIBUTING.md for guidelines.
- Fork the repository
- Create a feature branch (
git checkout -b feature/amazing-feature) - Commit your changes (
git commit -m 'Add amazing feature') - Push to the branch (
git push origin feature/amazing-feature) - Open a Pull Request
- Python: PEP 8 with Black formatting
- Documentation: Google-style docstrings
- Commits: Conventional Commits specification
- Multi-language support (Hindi, Tamil, Telugu)
- WhatsApp integration
- Advanced analytics dashboard
- Proactive guest engagement (pre-arrival, post-checkout)
- Integration with additional PMS providers
- Mobile app for staff monitoring
- AI-powered upselling capabilities
- Sentiment analysis and escalation triggers
- Multi-property deployment automation
This project is licensed under the MIT License - see the LICENSE file for details.
- Bloom Hotels — Early feedback and workflow insights
- Ginger Hotels — Multi-property deployment learnings
- Lemon Tree Hotels — Staff training and adoption strategies
- AxisRooms — PMS integration support
- OpenAI — LLM infrastructure
Prerna Agarwal
Product Manager | AI Systems
📧 prerna@example.com
🔗 LinkedIn
🌐 Portfolio
Most AI voice agents are built as demos that work in controlled environments.
Sakhi is different:
- Built for production constraints
- Designed for real-world variability
- Focused on operational reliability
- Proven through pilot deployment
This is what AI product development looks like when you're solving real problems for real users in real environments.
Building AI systems that work beyond prototypes
Product Strategy × AI Capability × Operational Execution
Made with 🧠 and ❤️ by Prerna Agarwal