Table · reads person
Contacts
Everyone the agent knows.
Rows and columns, sortable and filterable.
What it does
Behaviours, not fields. Choosing between two modules is choosing between these.
Fills itself from conversation. There is no import step, and no moment where somebody has to sit down and enter a list.
A name mentioned once is held and not written. Twice, or once with contact details, makes it a person — the threshold that keeps the list from filling with noise.
Last seen is written on every exchange and is not editable, which is why it is the one field that stays true.
Later details fill empty fields on the existing person rather than creating a second one.
How it works
- 1
A name appears. The agent holds it without writing anything.
- 2
On a second appearance, or a first alongside contact details, it becomes a row.
- 3
Every later exchange updates Last seen. Nothing else is touched unless the fact changed.
- 4
Details arriving later — a phone number, a company — fill empty fields rather than creating a second person.
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 |
|---|---|---|
| Namerequired | text | A name used twice, or once alongside a way of reaching them.Once is a mention. Twice is a person. That threshold is what keeps the list from filling with noise. |
| Role | choiceClient · Supplier · Partner · Prospect · Colleague · Other | How they relate to the business, from context rather than a stated title. |
| Any address given in conversation. Validated for shape, never for delivery. | ||
| Last seen | date | Written on every exchange. Not stated by anyone, and not editable.The one field here nobody maintains, which is why it is the one that stays true. |
What it does not do
A module chosen for something it cannot do costs more than one that was never offered.
- Matching is on name text. "Camille Marchand" and "C. Marchand" are two people until someone merges them.
- No deduplication pass. The system never decides that two rows are one; that is a judgement with consequences.
- It holds personal data. Deletion is the owner’s obligation and the module does not track consent or lawful basis.
- One row per person, not per relationship. Somebody who is both a client and a supplier gets one Role.
Before it works
What you have to provide, if anything.
- Nothing. It is the default people module and fills itself.
- Add Companies first if customers are organisations, or three contacts at one client will look like three accounts.
In practice
A consultant who had client names in three places and none of them current.
“Camille from Maison Lauret emailed about the September work.”
What the agent built
Nothing, on the first mention. On the second, a contact with the name, the company and the email that had appeared in between.
What changed
After a month there were 41 contacts, all of them people actually spoken to. The old spreadsheet had 300, most of them from a conference in 2023.
Better with
These do a different job on the same data. An agent can have all of them.
You sell to organisations, several people at each, and the relationship belongs to the company not the person.
The agent bills clients or is billed by suppliers, and someone needs to see what is unpaid without opening the accounting tool.
Meetings produce commitments and those commitments currently evaporate between the room and the inbox.
Who uses this page
Private chef
Takes the brief — dates, guests, diets, budget — while you are still cooking.
Property manager
Takes tenant issues, sorts the urgent from the routine, and keeps every unit’s history.
Insurance broker
Collects what a quote actually needs, without a twenty-minute call.
Coach or therapist
Answers the questions people are nervous to ask, and books the first session.
Questions
What data does the Contacts page use?
It reads person records the agent has collected. Everyone the agent knows. 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
Userbase
End-users of the agent + captured data.
Proposal
Bureau Kessler
Negotiating
Café Bellevue
First contact
Hôtel Vasari
Prospects / leads
Pipeline by stage.
Guests
Invitees with RSVP.
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