Voice of Customer
helio / user-feedbackDrop raw Discord messages, an interview transcript, or a meeting link. It pulls each distinct issue, labels it P0 to P3, files the doc to Notion, and opens engineering tasks for the bugs.
Here's a batch of Discord feedback and an interview transcript. Pull out each distinct issue, label it P0 to P3, file the interview doc to Notion, and open engineering tasks for the bugs. Ask me what you need before you start.
Swap in your own channels and Notion repo. Paste chat, a transcript, or a meeting link — it reads all three the same way.
What is Voice of Customer?
A teammate that turns raw Discord messages, interview transcripts, and meeting recordings into prioritized, tracked items in Notion, with dev-scope bugs routed to engineering as tasks. It labels and files the signal; the call on what to actually build stays with you.
What it does
Any chatbot summarizes a feedback thread once. Helio runs it as a standing job — from your context, kept current, delivered to you.
| Owns the job, not just the summary | It prioritizes each item, files the interview doc, and opens the engineering task, then calls the batch done once every issue is tracked. |
| Runs again without starting over | The nightly scan of your docs repo runs the same vetted process on a trigger, not a fresh prompt each time. |
| Works from your context | It writes to your Notion, follows your P0–P3 labels and interview-doc structure, so new items match how your team already tracks feedback. |
| Keeps itself current | When your priorities or doc format change, it updates the workflow. You don't re-teach it what P0 means. |
| Lands where you work | The prioritized items and a digest arrive in your team channel and a DM. You don't open Helio to read them. |
Three things it gets right
One loop for every input
A Discord message, an interview transcript, and a meeting link all become the same tracked, prioritized item, so nothing gets a different pipeline.
Repeats collapse into signal
An issue raised in two interviews becomes a single item with the count attached, so the pain users actually feel ranks first.
Bugs become tasks
A dev-scope issue turns into an assigned engineering task before the thread closes, with the next action written out.
What Voice of Customer connects to.
Questions
- What formats can it process?
- Pasted chat messages, screenshots it OCRs, and meeting transcripts you link or paste from tools like Tencent Meeting or Feishu. It reads what you give it.
- How does it decide P0 vs P3?
- P0 blocks a core user flow, P1 is serious UX damage, P2 is a meaningful improvement, P3 is a nice-to-have. Override any label with a one-word reply.
- Does it create engineering tasks automatically?
- Yes. Any bug or dev-scope issue pulled from feedback, interviews, or meeting minutes becomes a Helio task assigned to the right teammate. Disable it per session.
- What runs on the nightly scan?
- Every night it scans your docs repo for that day's interview notes, extracts the product issues, writes them to Notion, and sends a digest.
- Does it listen to meeting recordings?
- Yes, if you connect a meeting source. It screens each recording for real product or engineering signal, skips the rest, and reports any it can't access. Summaries carry roles only, with no names or verbatim quotes.
Paste your next batch of feedback. See it structured in 2 minutes.
No setup. Paste chat messages, a Tencent Meeting transcript, or a Feishu link, and Scout extracts the issues, writes to Notion, and DMs you the digest.
Ask about this automation