Guest hospitality
Stop or resume guest emails
Product documentation · Reviewed
Stop or resume your household’s guest emails
Use Stop guest emails at the bottom of an invitation, RSVP reminder or announcement you received. The private page identifies the wedding and household email address. This preference covers operational messages for that household; it does not enroll you in marketing or authorize text messages.
Stop future emails
Choose Stop guest emails. Your invitation link and saved RSVPs remain available. Previously accepted messages may still arrive because stopping cannot retract an email already accepted by the provider.
The saved choice stops earlier queued messages and prevents retries of uncertain attempts. A provider receipt can still resolve an earlier attempt; that receipt does not restart the queue. Reload the page if someone else changed the preference while you were viewing it.
Review a decision to resume
A recipient opt-out can be restored using the current preference link from an email already attempted by the service. Choose Review resuming guest emails. Check the wedding, exact email address, scope of consent and the stated limitations. Tick the confirmation checkbox, then choose Confirm and resume guest emails.
The review lasts at most 15 minutes and can be used once. If your address, invitation access, current stop or the notice changes, review again. A lost response can be retried with the original request without recording a second restoration. If another stop was recorded afterward, an old retry reports the current stopped state rather than restoring consent again.
For example, Tess stops emails after receiving a welcome note. An arrival announcement was already queued for tomorrow. Tess later reviews and confirms a decision to resume. That arrival announcement stays stopped. The host must review a new message using the current household details before another email can be queued.
Complaints and delivery failures
A provider complaint remains stopped and cannot be cleared with this recipient confirmation or by editing the address. A delivery failure has a separate host recovery process: the owning administrator must save a different address verified directly with the household and review corrected contact recovery. That process cannot clear an opt-out or complaint. See guest message delivery and recovery.
Late feedback about an older consent generation is retained with its original delivery. It does not undo a more recent explicit restoration. A complaint associated with the current consent choice can still stop delivery; a complaint may also strengthen an already-stopped contact. Provider delivery acceptance and complaints remain separately recorded.
Link access and history
This is a private, possession-based preference link. Anyone who has it can make this choice for the household. The application does not claim to verify the person’s identity or ownership of the mailbox. Keep the link within your household.
The link stops working when its own expiry or the household invitation expiry is reached, when the invitation is revoked or replaced, or when the household contact changes. New preference links expire after at most one year and never outlast the associated invitation. Older links use the same bounded fallback. Ask your host for help when a link is unavailable; the host cannot use contact editing to clear your opt-out.
The preference page keeps a paginated history of recorded stops, confirmations and delivery-related changes. Earlier legacy stops may appear in the current state without a corresponding history entry; the application does not invent past consent evidence.
Provider activation
The preference workflow and delivery safeguards are tested using a disposable PostgreSQL database and deterministic email transports. Live sending, receiving, complaint callbacks, sender/reply domains and email-provider policy review remain part of coordinated activation. This page sends no verification email and performs no provider call. It does not resume SMS or a mailing-list subscription.