Userbase

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.

Who uses this page

SaaS support team

Answers from your real documentation, and escalates the rest with context attached.

Customer success team

Catches the questions that become churn, and tells you which accounts are quietly stuck.

Subscription box or DTC brand

Handles skips, swaps and “where is it” — the three messages that fill your inbox.

Utility or telecom provider

Takes meter readings and fault reports at the hour people actually notice them.

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.