Integration · Feedback in

Catch the hallway conversation before it’s lost.

The customer email someone forwarded you, the thing a teammate mentioned, the line from the demo. A form, one submit, one feedback row attributed to the customer.

A form, for the feedback that doesn’t arrive through any other channel.

— How it connects —

From a passing comment to a tracked signal.

Three steps, the same pipeline as every other source.

01
Open Add Feedback.

From any surface — priorities, customer detail, the inbox.

Add feedback
Prioritiessurface
Customer detailsurface
Inboxsurface
02
Paste the text, attach the customer.

Optional customer name or email. Default source is manual.

Default source = manual
Feedback textpaste
maya@spacetour.aioptional
03
Submit.

One feedback row, attributed to the customer, into the same pipeline as everything else.

1 row · source='manual'
Attributed to customer
Into the pipeline
— What you get —

Nothing slips between the channels.

Nothing falls through the cracks.

The thing a colleague mentioned at lunch becomes a tracked signal, not a forgotten note.

Customer-attributed from the form.

Optional name or email; Circuit’s 4-tier identity resolver does the rest.

Same pipeline as every source.

Clustered, deduped, ranked alongside Slack, transcripts, CSV imports and the rest.

— The proof —

Manual feedback hits the same /feedback endpoint as the widget. One submit, one row tagged source='manual'.

— Questions —

Asked and answered.

Why have a manual option?

Because customer voice doesn’t always arrive through a channel. Sometimes it’s a forwarded email or a hallway comment — and it’s the most important kind.

Does manual feedback rank the same way?

Yes. Same intent classification, same clustering, same customer attribution. The source tag records where it came from.

Every signal counts. Capture them all.

Related

Part of Circuit’s autonomous product intelligence stack — see the full picture.