Table · reads person
Guests
Invitees with RSVP.
Rows and columns, sortable and filterable.
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
The columns are the logistics ones. A guest list that does not answer dietary and seating is a list of names.
Counts confirmed heads rather than invitations, which is the number the caterer needs.
Chases the unanswered without being asked, because RSVPs do not arrive on their own.
Dietary notes stay attached to the person, so the requirement travels to the table plan.
How it works
- 1
A guest list is entered or built up as invitations go out.
- 2
Replies update the RSVP and the head count, which is the number the caterer needs.
- 3
Dietary notes stay attached to the person so the requirement reaches the table plan.
- 4
The agent chases the unanswered, because RSVPs do not arrive on their own.
Best for
Comparing many records across many fields.
Not the right choice for
A phone. A table is the first thing that stops working narrow.
What a row holds
Every field, and what the agent listens for to fill it — which is the difference between a page you type into and one that fills itself.
| Field | Type | Filled from |
|---|---|---|
| Guestrequired | text | Who is invited, including party names like the whole family. |
| RSVPrequired | text | Their reply and the head count. No reply is a real value and the important one. |
| Dietary | text | Requirements as stated, kept in their words rather than categorised. |
| Table | text | Seating, once it exists. Unassigned until it does. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- Head counts are per row, so a party of four is one row and four heads — easy to miscount if entered carelessly.
- No seating logic. Table is a label, and nothing checks capacity or who should not sit together.
- Dietary text is unstructured, so it cannot be filtered reliably the way a menu allergen can.
- No invitation sending; this records replies rather than soliciting them.
Before it works
What you have to provide, if anything.
- Nothing.
- Pair with Events when the same list needs a public date, and with Attendees when who turned up matters.
In practice
A wedding with 80 invited and a caterer needing numbers by Friday.
“The Marchands are coming, two of them, one vegetarian. Table three.”
What the agent built
A guest row with the count, the dietary note and the table, all from one sentence.
What changed
The Friday number was a filter rather than an evening of phone calls. Four unanswered invitations were chased on the Wednesday because they were the only rows left.
Better with
These do a different job on the same data. An agent can have all of them.
The business puts on things people attend and needs the next few dates visible on the site without editing a page each time.
Attendance is recorded per session and no-shows matter for planning, billing or certification.
A single day has many dependent parts and the order matters more than the date — a shoot, an install, a wedding, a service window.
Who uses this page
Caterer
Quotes the obvious, captures dietary requirements, and never loses a headcount.
Boutique hotel or B&B
Answers guests before they book, and again once they have arrived.
Wedding planner
Qualifies couples on date, budget and guest count before you give up a Saturday.
Holiday rental host
Answers guests before, during and after the stay — in their language, at their hour.
Questions
What data does the Guests page use?
It reads person records the agent has collected. Invitees with RSVP. Nothing has to be imported first — the page appears once there is something to show.
Do I have to build or configure it?
No. You describe what you need in a sentence and the agent chooses the view and fills it. Custom pages exist for the cases no built-in view covers, and those are reviewed before they go live.
When is a table the wrong choice?
A phone. A table is the first thing that stops working narrow. It is best for: comparing many records across many fields.
Does it stay up to date?
Yes. The page is a view over the data rather than a copy of it, so anything the agent learns afterwards shows up without a rebuild or a re-import.
More in People & CRM
Contacts
Everyone the agent knows.
Userbase
End-users of the agent + captured data.
Proposal
Bureau Kessler
Negotiating
Café Bellevue
First contact
Hôtel Vasari
Prospects / leads
Pipeline by stage.
Camille Marchand
Founder
Client work, pricing
Tomas Réal
Production
Install and logistics
Aïcha Benali
Design
Identity, print
Jonas Weiss
Part-time
Weekends and events
Team / members
People in a group with roles.
Ask for it in a sentence
You do not configure this page. You tell your agent what you need and it builds it from what it has already collected.
Build your agent free