Invitations and email campaigns
Track event invitations, review exactly how invitation emails will be sent, and inspect each delivered message.
Overview
Invitations connect guests to the events they can RSVP for. The email workspace also lets you prepare and send personalized Save the Date and Wedding Invitation campaigns.
Key concepts
Each guest can be invited or not invited to each RSVP-enabled event. Cordially keeps those states separate from RSVP responses and email-delivery status.
This means "not invited", "pending", "attending", and "declined" are distinct states.
An email delivery contact is also different from an invited party member. One person's address may receive a message that names everyone in the household.
How it works
Use the Guests table to mark which events apply to each guest. Public RSVP only allows a guest to answer for invited events.
In the invitation email workspace, choose Save the Date or Wedding Invitation, edit the template and Reply-To addresses, then review the campaign before sending.
By default, Cordially prepares a separate email for every included regular guest with a valid email address. Host-created named +1s do not receive a separate copy unless you enable that option or include one explicitly. RSVP-created occupants of open +1 slots are never direct recipients.
When Send one email per household is enabled, Cordially sends one message to the selected main contact instead. Other household members remain in the invitation greeting but do not receive separate copies.
When One shared email to everyone in the group is enabled, Cordially sends
one message for the group and places every selected contact address in the
visible To list. This cannot be combined with one-email-per-household mode.
Addresses are normalized within each party. If multiple selected contacts in one household share an address, Cordially sends one email representing them. If the same address appears in different households, it receives a separate household-specific message for each and the review shows a warning.
Addressing and open +1s
Generated addressing uses a natural list of every visible named party member.
It also includes Guest or Guests when open +1 slots remain unfilled, such as
Alex and Guest. You can instead use the internal household name, save an
edited household name, enter a campaign-only label, or write custom addressing.
Preview and delivery history
Campaign review shows each planned destination, direct contact, represented party member, greeting, and non-blocking anomaly. A blocking problem excludes only the affected party; warnings do not prevent valid parties from being sent.
Every planned delivery has an exact email preview with From, Reply-To, To, Subject, and the rendered message body. After sending, Delivery history keeps the immutable headers, invited-person snapshot, HTML, plain text, and campaign image for each delivery. Historical previews use what was actually submitted at send time, not the current template.
Failed deliveries can be retried from their saved campaign state. Cordially does not automatically retry an ambiguous provider attempt, because the provider may have accepted the message even if it did not return a definitive delivery id.
Notes and limitations
Templates can be saved before publication, but a test or campaign send requires the selected public invitation surface to be published.
Invitation emails use the same published destination for everyone in that invitation type. Cordially does not create recipient-specific or tokenized RSVP links; guests continue to find their party by name when they enter RSVP.