Scoping sample, November 2025: a proposal, not a delivered case
AI guest-service automation on WhatsApp
Prepared for Sataya Resort
A standalone, multilingual guest-service system proposed for a resort that routed every guest request through reception by phone.
The problem and the proposal
Guest requests came in by in-room phone and were routed by hand through reception: delays, miscommunication between departments, missed requests, inconsistent service and no tracking or accountability.
Proposed: one WhatsApp number for every guest request, reached by QR codes around the resort; an AI intent engine that detects the request and routes it to the right department; a digital ticket for every request; bilingual Arabic and English staff dashboards; management KPIs; and a standalone cloud deployment that needs no property-system integration.
Eight components
- WhatsApp interface: a single number for all guest requests, via QR codes
- AI intent engine: detects and routes each request
- Department agents: housekeeping, maintenance, food and beverage, guest services, spa and activities, each trained on its own requests
- Digital ticketing: open, in progress, resolved or escalated, with room verification, priority, SLA timers, overdue reminders, staff notes, attachments and audit logs
- Staff dashboard: department queues with an Arabic and English toggle, on mobile, tablet and desktop
- Management dashboard: response and resolution times, volume trends, department and staff performance, exports
- QR access points throughout the resort
- Cloud deployment, independent of existing systems
Timeline: a 14-week plan
| Weeks | Phase | What happens |
|---|---|---|
| 1 to 2 | Discovery | Requirements, workflow mapping and architecture with every department |
| 3 to 4 | Design | UI mockups, data models and the multilingual workflow |
| 5 to 7 | AI development | The intent engine, the department agents and the translation layer |
| 8 to 10 | Backend | Ticketing, the SLA engine, APIs and notifications |
| 10 to 11 | Dashboards | Staff and management interfaces on the backend |
| 11 to 12 | Cloud API integration, QR codes and end-to-end testing | |
| 12 to 13 | Testing | QA, acceptance testing with staff, load testing and refinements |
| 13 to 14 | Launch | Staff training, a pilot and the resort-wide rollout |