# Cam-Events AI — Pilot Product Overview **Version:** 2.0 · September 2026 **Status:** Pilot-ready scope; advanced capabilities remain planned **Positioning:** AI-powered event operations and guest hospitality platform --- ## 1. Purpose Cam-Events AI gives event agencies, planners, hotels, transport teams, and field staff one operating record for guest hospitality. It replaces fragmented spreadsheets and chat-based updates across RSVP, accommodation, transport, check-in, luggage, VIP handling, and event-day exceptions. The initial market focus is Indian weddings, destination events, corporate gatherings, and other high-touch programmes. --- ## 2. Available in the pilot | Area | Available capability | |---|---| | **Guest operations** | Guest and family records, imports, RSVP status, travel details, consent and communication preferences | | **Event programme** | Multi-function schedules, venues, public RSVP pages, and function-level guest participation | | **AI voice / IVR RSVP** | Outbound calls, keypad or configured conversational flows, callback handling, outcome sync, exception queues, and manual override | | **Hotel operations** | Room blocks, room assignments, occupancy details, room status, special requests, and hotel-team access | | **Transport operations** | Vehicles, drivers, pickup and drop assignments, trip states, active location sharing, and replacement requests | | **QR check-in** | Guest lookup, QR scanning, access records, walk-in handling, and event-day audit history | | **Field operations** | Native role-aware mobile app for check-in, drivers, hotels, porters, VIP shadows, and managers | | **Hospitality services** | Porter and luggage custody workflows, issue evidence, VIP shadow checkpoints and handovers, helpdesk incidents, shifts, and tasks | | **Operational controls** | Role-based access, outreach safeguards, activity records, and configurable event settings | Some integrations require customer-specific provider configuration before they can be activated. --- ## 3. AI voice and IVR flow 1. An organizer selects eligible guests and reviews the campaign. 2. The system checks consent, suppression status, event calling rules, and campaign safeguards. 3. The configured provider places the call. 4. The guest responds through keypad or the approved conversational flow. 5. Webhooks link the outcome to the exact guest call record. 6. RSVP, callback, no-answer, transcript, and error states appear in the workspace. 7. The operations team handles exceptions or applies a manual override. Calling windows are configurable. Supported languages, scripts, provider numbers, retention, allowances, and compliance responsibilities are confirmed during onboarding; they are not assumed from the website. --- ## 4. Role-aware mobile operations Cam-Events AI uses one mobile app with a role-aware experience rather than separate applications for every field team. | Role | Focused workflow | |---|---| | **Organizer / manager** | Event status, assignments, exceptions, approvals, and escalations | | **Check-in staff** | QR scan, guest lookup, arrival and access status | | **Driver** | Assigned trips, guest contact, navigation, trip status, and approved location sharing | | **Hotel team** | Assigned rooming, arrivals, room readiness, and guest requests | | **Porter** | Assigned luggage jobs, custody scans, counts, status, incidents, and damage evidence | | **VIP shadow** | Assigned guest schedule, checkpoints, handovers, notes, SOS, and active assignment tracking | Offline-supported operations queue changes when connectivity is poor and synchronize them when a connection returns. Device capabilities such as background location require user permission and an active assignment. --- ## 5. Pilot onboarding flow 1. Cam-Events AI approves and provisions the agency workspace. 2. The agency owner accepts the pilot scope and data-processing responsibilities. 3. Named users are invited and assigned roles. 4. Event functions, venues, communication rules, and provider settings are configured. 5. Guest data is imported and reviewed for invalid records, duplicates, consent, and suppression. 6. The team tests a small outreach batch before a larger campaign. 7. Hotel, transport, check-in, porter, and VIP-shadow assignments are prepared. 8. Field users test their role on physical devices. 9. The event runs with exception monitoring and supervisor escalation. 10. Reports are exported and retention or deletion actions are completed after the event. --- ## 6. Indicative pilot packages The website shows three indicative monthly package levels: | Package | Indicative price | Proposed guest limit | Proposed voice allowance | |---|---:|---:|---| | **Starter** | ₹4,999/month | Up to 500 | 300 IVR + 100 AI voice minutes | | **Pro** | ₹9,999/month | Up to 2,000 | 700 IVR + 250 AI voice minutes | | **Premium** | ₹14,999/month | Up to 5,000 | 1,500 IVR + 600 AI voice minutes | These are planning figures, not an online purchase offer. Final limits, taxes, billing cycle, supported modules, provider costs, support, refund terms, and additional usage rates are stated in the signed order form or pilot agreement. --- ## 7. Planned, not part of the current promise - Predictive no-show and operational risk models - Automated smart hotel, seating, and route allocation - General guest-service chatbot - Vendor marketplace - Full customer-controlled white-label platform - Any certification, recovery objective, or service-level commitment not agreed in writing --- ## 8. Customer responsibilities The agency or organizer remains responsible for: - Lawful collection and use of guest data - Guest notice, consent, opt-out, and applicable DND or telecom obligations - Accuracy of imported information and field assignments - Approval of voice, email, and WhatsApp content before sending - Safe event-day decisions and appropriate supervision of staff - Obtaining location, media, and evidence permissions where required Cam-Events AI assists coordination; it does not replace professional, legal, safety, hospitality, or on-ground judgment. --- ## 9. Success measures for the pilot - RSVP completion and exception-resolution rate - Time required to reconcile guest, rooming, and transport changes - Check-in throughput and unresolved access exceptions - On-time pickup, room readiness, luggage handover, and VIP checkpoint completion - Field synchronization success under weak connectivity - Operator feedback and issues found during real events --- ## 10. Next commercial step Request a guided walkthrough and workflow-fit assessment. The final pilot proposal should name the customer, events, user roles, guest volume, activated communication providers, usage allowances, onboarding work, support hours, data-retention policy, pricing, taxes, and responsibilities. *This overview describes the September 2026 pilot scope. The signed agreement controls if it differs from website or proposal copy.*