Table · reads person
Userbase
End-users of the agent + captured data.
Rows and columns, sortable and filterable.
How it works
- 1
Every field becomes a column; you choose which to show.
- 2
Sorting and filtering happen on the data, not just the visible page.
- 3
Values stay editable in place where the field allows it.
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.
Questions
What data does the Userbase page use?
It reads person records the agent has collected. End-users of the agent + captured data. 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.
Confirm dietary needs
Send quote
Order langoustines
Deposit received
Site visit
Prospects / leads
Pipeline by stage.
Guests
Invitees with RSVP.
Seasonal tasting menu
Canapé selection
Service — per waiter
Glassware hire
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