Plan every event
in plain English.

Generic chatbots don’t have access to your live RSVPify data. You can describe your event to them, but they can’t tell you who actually RSVPd, which guests have dietary restrictions, or what your Q3 attendance trends look like, and they certainly can’t draft a website or send an email blast inside RSVPify. RSVPify Cue is built into the platform and reads your real workspace data, with the same permissions and audit controls you already use.

Most event-AI today falls into two buckets. Attendee-side chatbots live in the event mobile app and answer questions like “where’s the keynote.” Writing assistants on enterprise platforms draft content for emails, websites, and landing pages. Cue is built for the planner, the person doing the work, with persistent workspace memory across events, conversational queries over live data, and admin-level data controls. It doesn’t sit behind a premium tier or enterprise-only contract.

A workspace admin enables Cue for the workspace, accepts the Cue AI Terms of Use, and decides whether to allow guest-data (PII) access. Both settings can be changed any time. Non-admin users can request access, but only an admin can enable or disable.

No. We have a contractual no-training clause with our model providers. Workspace data, including PII, conversation content, and uploaded files, is processed for the duration of the request only. It is not retained for training, and cached results are wiped on schedule. Full details are in our Data Processing Addendum.

By design, disabling Cue or turning off PII access permanently deletes all Cue conversation history for the workspace, including chats started by other users. We do this to avoid orphaned records containing data the workspace has now told us it doesn’t want processed. The action requires a typed “I understand” confirmation from the admin.

Yes, just ask Cue. “SMS me when a VIP checks in” gets you a scoped event agent. “Ping #revenue when any workspace event sells over $10k in tickets” gets you a system-level one. There’s no separate agent-builder UI to learn; Cue interprets the request, wires up the trigger, and lists the new agent in your Agents panel with an enable/disable toggle. Every action an agent takes is recorded in the audit log just like a human user’s actions, so admins always know who did what.

Cue can prepare drafts, emails, websites, landing pages, forms, seating charts, automations, but nothing publishes, sends, or goes live until a human approves. The few exceptions (e.g. saving to workspace context when you say “remember…”) are clearly toasted and reversible from the audit log.

Yes. Cue uses RSVPify’s existing integrations. If your workspace has Salesforce connected, Cue can read and write to it through that connection, within the permissions your admin has scoped. Same for Slack notifications, Gmail drafts, Notion docs, and Calendly slots.

RSVPify Cue ships with RSVPify for Enterprise. It’s bundled into the Enterprise plan at no separate add-on cost, there’s no premium tier sitting on top of it. If you’re on a different plan and want Cue, talk to our Enterprise team about upgrading.

Cue is currently in early access on RSVPify for Enterprise. Capabilities, availability, usage limits, and pricing may change before general availability. We’re rolling out to Enterprise workspaces in waves, if you’d like priority access for your team, book a demo and we’ll get you in.