The RSVP
That Stopped VIP Chasing

The RSVP
That Stopped VIP Chasing

Designing clarity at the moment guest action triggers operations.

Designing clarity at the moment guest action triggers operations.

Summary

INVITI’s VIP RSVP form was causing delayed responses and manual follow-ups across event teams.


I redesigned the confirmation flow to make VIP responses immediate and reliable, stabilizing the event workflow.

Product Type:

B2B2C · VIP RSVP Interaction

Role:

Product Designer

Scope:

UX · Interaction · Visual System

Stabilizing the RSVP Trigger

VIPs stopped ghosting.

Teams stopped chasing.


+58% RSVP completion
–50% time to submit
–30% manual follow-ups
100% show-level customization


The RSVP trigger stabilized and the workflow stopped leaking.

Decision 01

Making Confirmation Immediately Clear

VIPs couldn’t quickly understand the invitation or required action when opening the RSVP.


Workflow effect
Delayed responses → manual chasing.


Design decision
Event identity, timing, and confirmation action were made immediately visible at entry.


Decision 02

Making RSVP Progress Visible

Guests couldn’t judge how long the RSVP would take or what remained after starting.


Workflow effect
Incomplete RSVPs → operational uncertainty.


Design decision
Steps, progress, and completion scope were made continuously visible throughout the RSVP.

RSVP steps and completion scope are visible from entry.

RSVP steps and completion scope are visible from entry.

Designing RSVP as a Workflow Trigger

In INVITI, guest confirmation activates the event workflow.


When RSVP is delayed, planning stalls and teams chase responses manually.


The RSVP therefore acts as the workflow trigger and must remain clear and reliable for the system to advance.

Preventing RSVP Drift

Before, RSVP hesitation shifted work downstream into manual chasing.


With clear confirmation and visible progress, responses now occur at the trigger point, allowing the workflow to advance without compensation.