The invitee confirmed. The event is on their calendar with their agreement.
RSVP tracking
See what happened after Send.
Six states per invitation, and the failures are shown at the same size as the successes. An invite that bounced is more useful to know about than one that landed.
Quarterly customer webinar
Closed · 30 July 2026
All six lifecycle stages complete, ending at attended.
100,482
Invite audience
98,710
Delivered
42,508
Accepted
31,204
Attended
Breakdown
Every response, and every non-response.
Each state is labelled and counted rather than encoded by colour alone, so the breakdown reads the same for colour-blind viewers, in print, and in forced-colours mode.
View as table
| State | Count | Share |
|---|---|---|
| Accepted | 42,508 | 43.1% |
| No response | 41,877 | 42.4% |
| Tentative | 8,421 | 8.5% |
| Declined | 5,904 | 6.0% |
States
What each state means.
Marked maybe. The time is held but not committed.
Explicitly refused. Useful signal — treat it as one.
The address rejected delivery.
Delivery could not be completed after retries.
Blocked by the suppression list before sending.
Consent withdrawn. Excluded from all future campaigns.
RSVP tracking depends on the recipient's calendar client and provider settings. Some clients report state partially or not at all, so “no response” is not proof that an invite was ignored. Delivery does not guarantee inbox placement or calendar acceptance. All figures on this page are illustrative.
Per customer
Aggregate is not enough.
Campaign totals tell you how the send went. The customer record tells you who to follow up with, and the two are the same system.
Event attendeesInvitees / Not accepted
Follow-up list| Customer | State | Delivered | Last invite |
|---|---|---|---|
| North Loop | Tentative | Yes | 3d ago |
| Event Arc | Declined | Yes | 3d ago |
| Harbour Legal | No response | Yes | 3d ago |
| Verde Books | Bounced | No | 3d ago |