Team / members

What it does

Behaviours, not fields. Choosing between two modules is choosing between these.

The same records the agent reads when a visitor asks who would handle their job, so the about page and the answer agree.

Focus rather than job title, because a visitor is choosing on what somebody does.

Renders as a public team page or an internal directory from one set of rows.

A part-time or weekend availability note is a field rather than a footnote nobody reads.

How it works

1
Team members are added as they join, usually in one sentence each.
2
The same rows serve a public team page and the agent answer to who would handle this.
3
Focus rather than title, because that is what somebody choosing is comparing.
4
Availability notes stop the agent offering a weekday slot with somebody who works Saturdays.

Best for

Things chosen by eye — products, venues, people.

Not the right choice for

Long lists someone needs to scan quickly.

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	How they are introduced.
Rolerequired	text	Their position, as a customer would understand it.
Focusrequired	text	What they actually do. A visitor is choosing on this, not on the title.

What it does not do

A module chosen for something it cannot do costs more than one that was never offered.

Public if the site is. Anything you would not print belongs elsewhere.
No permissions or accounts — this is a description of people, not a user list.
One row per person, so somebody with two roles gets one focus line.
Photographs are optional and the page reads noticeably worse without them.

Before it works

What you have to provide, if anything.

Nothing.
Pair with Bookings if the availability note should actually constrain what can be booked.

In practice

A four-person studio whose about page had been out of date for a year.

“Aïcha does identity and print. Jonas is weekends only.”

What was said to the agent

What the agent built

Two team cards with focus and availability, live on the site immediately.

What changed

Enquiries started arriving addressed to the right person. The agent stopped offering weekday appointments with someone who only works Saturdays.

Better with

These do a different job on the same data. An agent can have all of them.

ServicesLive

You sell time and expertise rather than objects, and people need to know the shape of an engagement.

BookingsLive

Customers reserve time, capacity is finite, and double-booking would be a real problem.

Org chartPartial

The team is large enough that reporting lines are not obvious, or a client organisation needs mapping before you sell into it.

Who uses this page

Conference organiser

Handles attendee questions at scale and keeps the programme, speakers and venue straight.

Gym or studio

Answers timetable, level and membership questions, and signs people up.

HR team

Answers the policy questions that fill your inbox, without anyone having to ask a person.

Cleaning company

Quotes from size and frequency, and fills the schedule without a phone call.

Questions

What data does the Team / members page use?

It reads person records the agent has collected. People in a group with roles. 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 cards the wrong choice?

Long lists someone needs to scan quickly. It is best for: things chosen by eye — products, venues, people.

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.