Skip to content

Feed · reads note

Feedback

Incoming comments.

What happened, newest first.

The last one is a wording problem on one page, findable only in someones own words.

Today

Mixed

Yesterday

Positive

9 Sep

Request

8 Sep

Confusion

What it does

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

What people said, in their words, which is what changes a mind in a meeting when a percentage does not.

Gathers from every channel into one stream, so comments stop vanishing into inboxes.

Sentiment is recorded but the sentence is kept, because the phrasing is the useful part.

How it works

  1. 1

    Comments arrive from every channel and land in one stream, newest first.

  2. 2

    The wording is kept verbatim, because the phrasing is what makes it usable in a decision.

  3. 3

    Sentiment is a tag rather than a number, since a five-point scale on four comments is false precision.

  4. 4

    Recurring themes surface by repetition rather than by classification.

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.

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
WhenrequireddateWhen it was said. Drives the ordering.
ChannelrequiredtextWhere it came from — chat, email, in person. Different channels attract different comments.
CommentrequiredlongtextThe words themselves, verbatim. Paraphrasing loses the useful part.
SentimentchoicePositive, Mixed, Request or Confusion. A tag, not a score.

What it does not do

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

  • No automatic theming or clustering. Reading them is the work.
  • No reply or resolution tracking — this records what was said, not what was done about it.
  • Sentiment is coarse on purpose, which means it cannot be trended.
  • Volume is self-selected, so it over-represents the very happy and the very annoyed.

Before it works

What you have to provide, if anything.

  • Nothing. It fills from conversations the agent is already having.
  • Pair with Surveys when you need a representative answer rather than a vivid one.

In practice

A business collecting comments in three inboxes and remembering none.

Somebody said they could not tell whether the subscription auto-renews.
What was said to the agent

What the agent built

A feedback entry with the channel, the wording and a sentiment tag.

What changed

It was a wording problem on one page, findable only in a customer own words. Two similar comments the same week made it the priority.

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.

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