CordiallyDocs
Platform OverviewWebsite EditorTips & TricksChangelog
DocsWebsite EditorGuests & RSVP

Households

Use households to organize guests who should RSVP together or be managed as a group.

Overview

Households group guests who belong together.

Key concepts

A household can represent a family, couple, or invited party. Guests can also exist without a household.

Households make RSVP easier because members of the same party can be found and reviewed together.

A household can also have a main contact for one-email-per-household invitation campaigns. The first regular guest added to a new household becomes its initial main contact, and you can choose a different eligible contact during campaign review. Member order controls how the party appears in guest management and generated invitation addressing.

How it works

When adding or editing a guest, choose no household, an existing household, or create a new household. The Guests table can show household grouping and lets you rename groups, reorder members, move complete linked parties, or delete groups when needed.

Host-created named +1s are fixed members of their primary guest's party. They must share the same household, and moving either linked party member moves the primary guest and companions together. RSVP-created names entered for open +1 slots remain transferable occupants rather than fixed named invitations.

The internal household name can be used for invitation addressing. Campaign review also lets you edit and save that name or use a campaign-only label without changing the household record.

Common workflow

  1. Add the first guest in a party.
  2. Create a household name.
  3. Add other guests to the same household.
  4. Review the party together in RSVP and guest management.

Notes and limitations

Deleting or changing household organization can affect how RSVP parties are grouped and addressed. Cordially reviews broad moves and locks the current membership during reorder, but you should still check the resulting party before sending invitations.

A primary guest with fixed named +1s cannot be deleted until those links are resolved. Existing inconsistent legacy relationships are shown as campaign review issues and are not silently reorganized.

Related docs