# RSVPs and approvals

> Confirm or approve guests, handle plus-ones, set a guest's answer for a session, approve session requests, and manage waitlists.

- Do first: [Find the event and the people in it](https://www.attend.vip/help/agents/find-your-event.md)
- Attend MCP tools: `guest_admin_edge__eventGuestConfirm`, `guest_admin_edge__eventBatchConfirm`, `guest_admin_edge__eventGuestApprove`, `guest_admin_edge__eventBatchApprove`, `guests__guestsGrantPlusOnes`, `guests__guestsGrantPlusOnesBulk`, `guest_admin_edge__eventGuestApprovePlusOne`, `guest_admin_edge__eventBatchApprovePlusOne`, `agenda_items__adminSetRsvp`, `agenda_items__adminDeclineGroup`, `agenda_items__adminDeclineActivity`, `agenda_items__agendaItemsApprove`, `agenda_items__agendaItemsApproveBulk`, `agenda_items__agendaWaitlistPromote`, `agenda_items__agendaWaitlistReorder`, `agenda_items__agendaWaitlistRemove`, `agenda_items__listAttendeeAgenda`
- Updated: 2026-11-02

There are two levels of RSVP:

- **Event RSVP**: is the guest coming on the trip at all? This is the guest's `status`.
- **Session RSVP**: is the guest going to a particular session? Its status is `confirmed`, `declined`, `cancelled`, `waitlisted` or `pending` (waiting for approval). Attendee apps never say yes, no or maybe.

## Event RSVPs

- **Confirm on a guest's behalf**, for example when they replied by email: `guest_admin_edge__eventGuestConfirm`. For many guests, use `guest_admin_edge__eventBatchConfirm`, up to 100 ids, with `input: {sendInvite, dryRun}`. `sendInvite: true` also emails their invite.
- **Approve** a pending or waitlisted guest: `guest_admin_edge__eventGuestApprove`, or `guest_admin_edge__eventBatchApprove`. On a published event the guest gets the approval email, so dry-run first and say so.
- **Plus-ones.**
  - `guests__guestsGrantPlusOnes` sets how many a guest may bring (`maxGuests`; `notify` alerts them). The bulk version is `guests__guestsGrantPlusOnesBulk`.
  - A plus-one a guest asked for is approved with `guest_admin_edge__eventGuestApprovePlusOne`, or `guest_admin_edge__eventBatchApprovePlusOne`. This sends the plus-one's invite.

The batch tools aren't all-or-nothing. They return a result per guest: report the failures by name and don't retry the whole batch.

## Session RSVPs

1. **See one guest's schedule** with `agenda_items__listAttendeeAgenda`: every session, group and activity, with that guest's status.
2. **Set a guest's answer** with `agenda_items__adminSetRsvp` (`guestId`, `agendaItemId`, `response: "confirmed" | "declined"`, an optional `note`). The same rules apply as when the guest does it:
   - in a pick-one group, confirming one option releases the others;
   - a full session with a waitlist puts them on the waitlist;
   - a `display` session refuses.
3. **Decline a whole group or activity** for a guest: `agenda_items__adminDeclineGroup` / `agenda_items__adminDeclineActivity`.
4. **Approve session requests** on sessions with `preApproved: false`: `agenda_items__agendaItemsApprove` (one RSVP id) or `agenda_items__agendaItemsApproveBulk`. These need organization staff; event crew can't approve.
5. **Waitlists.**
   - `agenda_items__agendaWaitlistPromote` confirms the next `count` guests.
   - `agenda_items__agendaWaitlistReorder` moves one guest to a position.
   - `agenda_items__agendaWaitlistRemove` takes guests off the waitlist.
   - All three take `dryRun`.

## Check the dry-run for

- How many guests change, and whether any email goes out.
- Seats freed or taken, and the waitlist positions afterwards.
