Skip to content

List · reads faq

FAQ

Question/answer pairs.

One row per item, the plainest possible view.

Change an answer here and the agent starts giving the new one.
  • Do you deliver outside Paris?Yes — anywhere in France, 2–4 working days.
  • Can I change an order after paying?Until it ships. Message the agent and it will handle it.
  • Do you do wholesale?From 12 units. Ask for the trade price list.

What it does

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

A public page and a source at once, so the page and the conversation can never drift apart.

Editing an answer changes what the agent says on the next message.

Built from the questions actually asked rather than the ones somebody imagined.

How it works

  1. 1

    Questions accumulate from what the agent is actually asked rather than from what somebody imagined.

  2. 2

    An answer written here is the same string the agent uses, so the page and the conversation cannot drift.

  3. 3

    Editing an answer takes effect on the next message. There is no publish step.

  4. 4

    A question asked repeatedly and not present is surfaced as a candidate.

Best for

Reading and scanning. It is the right default more often than it looks.

Not the right choice for

Comparing many fields at once — use a table.

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.

FieldTypeFilled from
QuestionrequiredtextA question visitors actually ask, in roughly the words they use.
AnswerrequiredlongtextThe answer the agent should give. Editing this changes what it says.

What it does not do

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

  • One answer per question. Anything needing conditions belongs in the knowledge base.
  • No versioning, so a change loses what was there before.
  • No per-audience answers — trade and retail cannot be told different things here.
  • Long answers work but read badly; past a paragraph it is an article.

Before it works

What you have to provide, if anything.

  • Nothing. Three questions is a useful FAQ.
  • Let it grow from real questions rather than writing twenty up front, which mostly produces the wrong twenty.

In practice

A shop answering the same five questions every day.

People keep asking whether we do wholesale. From twelve units, trade price list.
What was said to the agent

What the agent built

An FAQ entry live on the site, and the same answer available to the agent.

What changed

The wholesale question stopped reaching a person. Three trade accounts opened in the following month from visitors who had self-served the answer.

Questions

What data does the FAQ page use?

It reads faq records the agent has collected. Question/answer pairs. 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 list the wrong choice?

Comparing many fields at once — use a table. It is best for: reading and scanning. It is the right default more often than it looks.

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

Agents

More

👤
Profile
FAQ