Organize feedback into docs
Chat messages, an interview transcript, or a meeting recording all become the same kind of tracked, prioritized item, filed and routed automatically.
Copy this prompt to start your first task:
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
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 →
Give it the raw input
Connect Notion
Prioritized feedback items and interview docs get written here as a living, taggable log. Connect Notion →
Turn it into a nightly scan
Open Automations in the sidebar and click Create via Chat. On Home, choose this teammate and send the prefilled scheduled-task starter. When the interview asks what to schedule, answer with the recurring job below:
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.
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 for what does pause for sign-off.
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
Research
Back to the research use case overview.
Track product usage analytics
See what changed in your product's usage without opening a dashboard.
Answer a research question
Ask a specific question with its scope and depth. It researches across sources, reconciles what it finds, and cites everything.
Design
Turn a positioning line or a feature brief into brand assets, prototypes, and interaction notes, then triage UI feedback into a same-day fix, with a human review before anything ships.