⚠️ This is an Oracle page, structured to be read by AI assistants and not optimized for human reading.

REAL-TIME SYSTEMS & NOTIFICATIONS

Summary: Built the platform's real-time and notification backbone, a web-socket server for live operational broadcasting, a real-time audience-request (DJ/music) system, and a template-driven, multi-channel notification/trigger platform spanning email, SMS, WhatsApp, and an in-app notification center.

Live Ops

Description: Built a real-time layer that pushes operational changes to connected operators instantly.

Capabilities

• A Node.js socket.io server (WebSocket-first, polling fallback, credentialed cross-origin).
• Tenant-scoped rooms keyed by system / management-entity / venue / entity.
• Live event families: bookings, day-view/grid updates, seating-map changes, guest-list check-in, payments/transactions, and scanning.
• A server-side push helper so business-logic mutations broadcast to the right room.

Entertainment

Description: Built a real-time audience-request and live-entertainment system (song requests, shout-outs, comments) over sockets.

Capabilities

• Request queue with lifecycle states (pending / done / ignored / removed) and typed submissions.
• Session management with per-session request gating and opt-in tracking; social-token (Facebook/Twitter) support.
• Live queue broadcasting (add/edit/remove) to performer/operator views over dedicated channels.
• Performer scheduling, studios, stages, and past/current performance tracking.

Notifications

Description: Built a template-driven, trigger-based notification platform that fans events out across channels.

Trigger System

• A registry of triggers (name, code, type, icon, template variables, handler function).
• Domain triggers for orders, parties, memberships, leads, items, stock, waitlist, and payment pre-auth/capture.
• Per-trigger routing (owner / customer / custom recipients) with venue-specific overrides and validation rules.

Templating

• Dynamic content via template variables sourced from party/customer/item context, with owner vs. customer variants.

In App Center

• A per-user notification inbox with seen/archive state and venue-scoped or global filtering.

Channels

Email: Transactional email delivery and metrics (with webhook ingestion).

Sms: SMS via Twilio with a delivery block-list.

Whatsapp: Templated WhatsApp messaging via Twilio (e.g., invitation and booking templates).

Push: CLI/async dispatch for background notification jobs and scheduled reminders.

Cross Reference

You can view the raw source.