# Organize feedback into docs (/use-cases/research/user-feedback)



Copy this prompt to start your first task:

<Prompt>
  Set up a daily user-feedback triage for me. Feed it [feedback, screenshots, a spreadsheet, or a channel link], have it cluster by theme, flag severity and frequency, and turn the top issues into prioritized tasks in Helio.
</Prompt>

<LivePreview component="NewThread" scenario="{ draft: &#x22;Set up a daily user-feedback triage for me. Feed it [feedback, screenshots, a spreadsheet, or a channel link], have it cluster by theme, flag severity and frequency, and turn the top issues into prioritized tasks in Helio.&#x22; }" />

## What is this workflow? [#what-is-this-workflow]

Organizing feedback into docs means turning a chat thread, an interview transcript, or a meeting recording into the same kind of tracked, prioritized item instead of something read once and left in a pile. A teammate extracts the distinct points, labels each one P0–P3 by how much it matters, and structures interview content into background, scenario, aha moment, and pain rather than leaving it as a raw transcript. Anything bug- or dev-scoped becomes a tracked engineering task before the thread even closes.

## How to use this workflow [#how-to-use-this-workflow]

<Steps>
  <Step>
    ### Hire a customer reply and triage teammate [#hire-a-customer-reply-and-triage-teammate]

    Open **AI Teammates** in the sidebar, click **Hire AI Teammate**, and pick the **Customer Reply & Triage Expert** template. Confirm the name and click **Create teammate**. They land in their own channel, which is where you'll send everything below. [More on hiring →](/ai-teammates/hire-an-ai-teammate)

    <LivePreview component="CreateAssistantPage" />
  </Step>

  <Step>
    ### Give it the raw input [#give-it-the-raw-input]

    <Prompt>
      Here's [a pasted chat thread / an interview transcript / a meeting recording link]. Extract the distinct points, label feedback P0–P3 by severity, and structure interview content into background, scenario, aha moment, and pain.
    </Prompt>

    <LivePreview
      component="AssistantChat"
      scenario="{ assistantName: &#x22;Customer Reply & Triage Expert&#x22;, messages: [
    { author: &#x22;user&#x22;, text: &#x22;Here's [a pasted chat thread / an interview transcript / a meeting recording link]. Extract the distinct points, label feedback P0–P3 by severity, and structure interview content into background, scenario, aha moment, and pain.&#x22; },
    { author: &#x22;assistant&#x22;, text: &#x22;Pulling out the distinct points now and labeling each P0 to P3 by severity. For the interview content I'll structure it into background, scenario, aha moment, and pain instead of leaving it as a raw transcript.&#x22; },
  ] }"
    />
  </Step>

  <Step>
    ### Connect Notion [#connect-notion]

    Prioritized feedback items and interview docs get written here as a living, taggable log. [Connect Notion →](/connect/connect-tools-to-ai-teammates)

    <LivePreview component="AssistantIntegrations" />
  </Step>

  <Step>
    ### Turn it into a nightly scan [#turn-it-into-a-nightly-scan]

    Open **Automations** in the sidebar, click **Create via Chat**, and pick this teammate in the New Thread composer that opens:

    <Prompt>
      Every night, scan our Notion workspace for interview notes added that day, extract product issues, write them to Notion, and send me a digest. File anything bug- or dev-scoped as a tracked task automatically.
    </Prompt>

    <LivePreview component="NewThread" scenario="{ populated: false }" />
  </Step>
</Steps>

<Callout type="info">
  If summaries should be anonymized (roles only, no names or verbatim quotes), say so in the teammate's instructions, and give the result a quick check before sharing it. An inaccessible recording gets reported as inaccessible, not silently skipped or guessed at.
</Callout>

**Nothing here needs your approval:** writing prioritized feedback and interview docs to Notion, filing a task, and sending you a nightly digest all stay inside your workspace — none of it is irreversible or sent externally. See [Control](/ai-teammates/control) for what does pause for sign-off.

## Tips for Better Results [#tips-for-better-results]

| Tip                                              | Description                                                                                                                                               |
| ------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Say up front if summaries need anonymizing       | Roles-only summaries (no names or verbatim quotes) don't happen by default — put it in the teammate's instructions, then check the result before sharing. |
| Hand over the raw input as-is                    | Paste the chat thread, transcript, or recording link directly. The teammate extracts and structures it, you don't need to pre-summarize.                  |
| Let bug-scoped feedback become a task on its own | Anything bug- or dev-scoped gets filed as a tracked task before the thread even closes, no separate step needed.                                          |
| Automate the scan once the pattern is clear      | A nightly Notion scan catches new interview notes and triages them without you re-running the same request.                                               |

## Common Questions [#common-questions]

<Accordions type="single">
  <Accordion title="How is feedback prioritized?">
    Each item gets labeled P0–P3 by how much it matters, so it's tracked and ranked rather than just logged in a pile.
  </Accordion>

  <Accordion title="What happens to interview transcripts?">
    They get structured into background, scenario, aha moment, and pain — not left as a raw transcript.
  </Accordion>

  <Accordion title="Does bug-related feedback automatically become a task?">
    Yes. Anything bug- or dev-scoped is filed as a tracked engineering task before the thread even closes.
  </Accordion>

  <Accordion title="Can summaries be anonymized?">
    Yes, if you say so in the teammate's instructions — roles only, no names or verbatim quotes. Give the result a quick check before sharing it either way.
  </Accordion>

  <Accordion title="What happens if a recording can't be accessed?">
    It gets reported as inaccessible, not silently skipped or guessed at.
  </Accordion>
</Accordions>

<Cards>
  <Card title="Research" href="/use-cases/research" description="Back to the research use case overview." />

  <Card title="Track product usage analytics" href="/use-cases/research/user-insights" description="See what changed in your product's usage without opening a dashboard." />
</Cards>