Table · reads plan

Pricing table

Tiers and prices.

Rows and columns, sortable and filterable.

Build an agent that makes this All modules

"Best for" does more work than any feature row. It answers the actual question.

PlanPriceIncludesBest for

Starter€01 agent, 200 messagesTrying it out

Pro€29/mo3 agents, custom domainA working business

Team€99/moUnlimited, shared accessMore than one person

BespokeTalk to usEverything, plus helpVolume or unusual needs

What it does

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

Plans sit side by side, because comparison is the only reason to render pricing as a table at all.

The best-for row does more work than any feature list: it answers which one is yours, which is the question people arrive with.

The agent quotes from these rows, so a price change on the page is a price change in the conversation.

A talk-to-us tier is a first-class option rather than a gap, so enterprise pricing needs no separate page.

How it works

1
Plans are listed side by side, because comparison is the only reason to render pricing as a table.
2
Best for is required, since it does more work than any feature row.
3
The agent quotes from these rows, so the page and the conversation cannot diverge.
4
A talk-to-us tier needs no separate page.

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
Planrequired	text	What the tier is called, in the words a customer would repeat back.
Pricerequired	text	What it costs, or Talk to us as a first-class option.
Includesrequired	text	What you get, phrased as capability rather than feature list.
Best forrequired	text	Who it suits. Required — it answers the question people actually arrive with.

What it does not do

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

No billing integration. This describes pricing; it does not charge.
No per-currency or per-region pricing.
No feature matrix with ticks — Includes is prose, deliberately.
Nothing tracks which plan enquiries actually convert.

Before it works

What you have to provide, if anything.

Write Best for before Includes. If you cannot say who a tier suits, the tier is wrong.
Pair with Services when the work is scoped rather than packaged.

In practice

A studio that had been quoting packages by email, differently each time.

“Three packages: essentials at 1,200, standard at 2,800, and bespoke on enquiry.”

What was said to the agent

What the agent built

A three-column table with what each includes and who it suits, and the agent briefed to quote from it.

What changed

The middle tier went from a third of enquiries to over half — because it was the one described as for a working business, not the one in the middle.

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.

FAQLive

Visitors ask the same handful of things — hours, delivery, pricing, whether you do X — and the answers should be identical on the page and in the chat.

Intake formLive

New enquiries need the same information every time and chasing it afterwards costs days.

Who uses this page

Venue manager

Answers availability and capacity questions instantly, and turns them into real bookings.

Boutique hotel or B&B

Answers guests before they book, and again once they have arrived.

Tutor or school

Answers parents’ questions and captures the level, subject and availability that matter.

Hairdresser or salon

Takes bookings while your hands are in someone’s hair.

Questions

What data does the Pricing table page use?

It reads plan records the agent has collected. Tiers and prices. 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.

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