Feedback

How it works

1
Every change worth recording becomes an entry.
2
Entries are grouped by day and by actor.
3
Older history loads as you reach it.

Best for

Activity, audit trails, "what changed since I last looked".

Not the right choice for

The current state of anything — a feed is history.

Who uses this page

Restaurant

Answers the menu, the allergens and the opening hours — in every language your guests speak.

Online shop

Answers sizing, stock and shipping — the three questions that lose a sale.

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.

Questions

What data does the Feedback page use?

It reads note records the agent has collected. Incoming comments. 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 feed the wrong choice?

The current state of anything — a feed is history. It is best for: activity, audit trails, "what changed since I last looked".

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.