Tree · reads person
Org chart
Reporting / membership hierarchy.
Nesting, shown as nesting.
- Confirm dietary requirementsDue tomorrow
- Send quote to MarchandDue Friday
- Order langoustinesIn progress
- Book second serverNot started
How it works
- 1
Parent links in the data become indentation.
- 2
Branches collapse so a deep structure stays readable.
- 3
Depth is visible without counting.
Best for
Categories, org charts, anything with real hierarchy.
Not the right choice for
Flat data given artificial parents.
Questions
What data does the Org chart page use?
It reads person records the agent has collected. Reporting / membership hierarchy. 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 tree the wrong choice?
Flat data given artificial parents. It is best for: categories, org charts, anything with real hierarchy.
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.
Confirm dietary needs
Send quote
Order langoustines
Deposit received
Site visit
Prospects / leads
Pipeline by stage.
Guests
Invitees with RSVP.
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