RSVP clarity changed the guest-list decision.
The host started with 139 invitation contacts. As responses developed, the dashboard made declined invitations and unresolved contacts visible in one place. By 24 September, the original list showed 37 declined contact records and 121 confirmed guests.
Using that clearer picture, the host added 30 previously left-over invitation contacts who had not been accommodated in the original list because of space constraints. The guest list moved from 139 to 169 contacts.
Count Me In didn't create more venue space. It gave the host better information about the space already available.
Declines became visible early enough for the host to reconsider invitations rather than discovering unused capacity only after the guest list was already closed.
The critical before-and-after moment
The two snapshots below were taken on 24 September. Accepted contacts and confirmed guests initially remained unchanged, while the contact list increased by exactly 30. That documents the host's decision to invite an additional list after RSVP clarity improved.
Final pre-event planning position
On 27 September, one day before the event, the dashboard recorded 109 accepted contacts representing 148 confirmed guests: 83 gents and 65 ladies. Another 44 contact records had declined. The remaining 16 contacts had not responded and, based on the host's planning decision, were considered not attending.
Important: 148 is the confirmed pre-event headcount, not a verified count of people who physically attended the event. The screenshots supplied do not establish actual on-site attendance.
The documented RSVP journey
| Snapshot | Contacts | Accepted | Declined | Pending | Confirmed guests |
|---|---|---|---|---|---|
| 16 Sep · Save the Date | 139 | 0 | 3 | 136 | Not established |
| 18 Sep · RSVP progress | 140 | 75 | 25 | 40 | 102 |
| 21 Sep · Growing clarity | 139 | 82 | 36 | 21 | 118 |
| 24 Sep · Before expansion | 139 | 84 | 37 | 18 | 121 |
| 24 Sep · After expansion | 169 | 84 | 37 | 48 | 121 |
| 26 Sep · Pre-reminder | 169 | 106 | 43 | 20 | 145 |
| 27 Sep · Final pre-event | 169 | 109 | 44 | 16 | 148 |
The contact list briefly changed to 140 on 18 September and returned to 139 by 21 September. The case study preserves each screenshot as recorded rather than normalising the figures.
What this implementation demonstrates
Earlier capacity decisions
Declines were visible from the Save-the-Date stage, giving the host information before the final headcount deadline.
Contacts are not headcount
109 accepted invitation records represented 148 confirmed guests — the operational number is the people attending, not only WhatsApp numbers responding.
Targeted follow-up
Pending contacts remained identifiable at each stage, so follow-up could focus on unresolved invitees rather than everyone.
Original dashboard evidence
The following anonymised screenshots document the progression. They are included as first-party implementation evidence rather than a customer quotation.
16 September — Save-the-Date
18 September — RSVP responses
21 September — Growing clarity
24 September — Before expansion
24 September — After expansion
26 September — Before final reminder
27 September — Final pre-event position
Don't just count invitations. Know who's coming — and who else you may be able to invite.
Count Me In brings responses, guest composition and pending follow-up into one view so hosts can make timely decisions using their own event data.
Editorial disclosure: This is a Count Me In first-party implementation case study based on anonymised dashboard screenshots and information supplied about the host's guest-list decision. It is not a direct customer quotation, independent review or verified on-site attendance report.