<aside> <img src="notion://custom_emoji/e12b42ac-4e54-476f-a4f5-7d6bdb1e61e2/29cefdee-ad05-808c-9f11-007a1d9fbfb2" alt="notion://custom_emoji/e12b42ac-4e54-476f-a4f5-7d6bdb1e61e2/29cefdee-ad05-808c-9f11-007a1d9fbfb2" width="40px" />

Route every product bug and request to the right owner the moment it comes in

This agent removes triage limbo by turning raw feedback into an owned, logged, and shared work item.

At Notion, this agent routes 200+ feedback items per week, saving 15+ hours of manual triage and ensuring every bug and request reaches the right owner immediately.

</aside>

How it works

• Routes incoming bugs, feature requests, and questions from #all-product-feedback-chatter to the right owning team.
• Creates the ticket automatically with issue details, classification, and routing context — no manual data entry.
• Notifies the owning team and original reporter in the right channels so nothing sits unacknowledged.
• Flags ambiguous ownership for human review instead of routing to the wrong team.
• Improves routing over time by learning from corrections and proposing updates to the routing rules.

Build your own

1. What to have ready before you start

• Your workflow: The sequence of steps the agent runs, from trigger to final output. Know this before you build.

  For this agent:

  1. New feedback is posted in #all-product-feedback-chatter.
  2. Agent checks routing rules and determines the likely owning team.
  3. Agent creates the right task or bug record in Notion.
  4. Agent replies in-thread with the routing decision and next step, and notifies the owning team.

• Context it needs: The information the agent draws on to do its job: docs, directories, and databases it reads to route and log work. You'll swap these into the starter prompt in step 2.

  For this agent:

  • [ ] Routing rules page → [ROUTING RULES PAGE]
  • [ ] Relevant bug or task databases → [BUG OR TASK DATABASES]
  • [ ] Team ownership map → [TEAM OWNERSHIP MAP]
  • [ ] Team Slack channels or notification destinations → [TEAM CHANNELS]

• Tools to connect: The apps the agent needs access to for reading, messaging, and taking action.

  For this agent:

  • [ ] :slack-logo-transparent: Slack (to monitor the intake channel, reply in-thread, and notify owning teams)
  • [ ] :notion: Notion (to read routing rules and create tickets)

2. Copy and paste this starter prompt

<aside> <img src="/icons/info-alternate_gray.svg" alt="/icons/info-alternate_gray.svg" width="40px" />

In your left-hand sidebar, go to the Agents section and click the + button.

</aside>

You are a product feedback routing agent for the [TEAM NAME] team. Monitor [SLACK CHANNEL OR INTAKE CHANNEL] and use [ROUTING RULES PAGE], [BUG OR TASK DATABASE], [TEAM OWNERSHIP MAP], and [TEAM CHANNELS] to route incoming product feedback to the right owner. Determine whether each message is a bug, feature request, or question; extract the core issue, environment, urgency signals, and relevant links or screenshots; then use the routing rules as the source of truth to identify the owning team. If ownership is ambiguous, do not guess—flag the feedback for human review. When ownership is clear, create the appropriate ticket in [TICKETING SYSTEM OR DATABASE], reply in-thread with the routing decision and next step, and notify the owning team in the relevant channel. If a human corrects the owner, capture that feedback and propose an update to [ROUTING RULES OR KNOWLEDGE BASE] so routing improves over time.