Feedback to roadmap
By Toolspoke
Reads a week of product feedback from Gmail and Slack, groups what repeats, and drafts prioritised tickets in Notion for review.
Needs a Toolspoke account. You choose which project it installs into.
- Slack + Gmail + Notion
- Required integrations
- Runs on a schedule
- Mondays at 9am by default
- Post one summary
- What its last step does
- Some actions can delete
- 2 of 38 actions in its tools
On this page
The short version
- What it is
- A ready-made Toolspoke agent that turns a week of product feedback into draft tickets with the evidence behind each.
- What it reads
- Feedback email found by a Gmail label or search, and the Slack channels you choose.
- What it finds
- Complaints and feature requests that two or more people raised, counted by person, not by message.
- What you get
- Draft pages in your Notion database, comments on tickets that already exist, and one Slack summary.
- How often
- Every Monday once you switch it on.
- What it never does
- Reply to a customer, change a ticket's status or priority, or take anything out of Draft.
- What you need
- A Toolspoke account, a Google account for Gmail, a Slack workspace and a Notion database.
What Feedback to roadmap does
Feedback to roadmap is an AI agent that reads a week of product feedback from email and Slack, groups what keeps coming up, and drafts a ticket for each group in Notion. You decide what goes on the roadmap.
Feedback arrives everywhere. A customer emails the feedback address, a support colleague pastes a complaint into Slack, an account manager mentions a request in a thread. Each one is read once and then lost, and the roadmap gets decided by whoever remembers the loudest.
Tagging every message by hand would fix it, but nobody keeps it up. A feedback tool would fix it too, if everyone moved their feedback into it.
Feedback to roadmap reads the places feedback already lands. It counts people rather than messages, so one customer writing three times is one voice, and it only drafts a ticket when two or more people raised the same thing. Every ticket links back to what they said.
In practice, every Monday you have:
- Draft tickets for recurring complaints and requests, each with a count of people
- Two or three short quotes per ticket, each linked to the email or Slack message
- A comment on any ticket that already exists, rather than a duplicate
- One Slack summary with the top five and the one-off mentions
How it works
Feedback to roadmap works in four steps each week: it reads the feedback, groups what repeats, checks your database and drafts the tickets. All of it comes from the agent's written instructions, which you can read and edit after you install it.
Step 1: Read the email
It reads the week's threads from your feedback label or search.
Step 2: Read Slack
It reads the channels you chose, threads included.
Step 3: Group what repeats
It counts people, sorts complaints from requests and ranks them.
Step 4: Draft the tickets
It checks for an existing ticket, then comments or drafts a new one.
It counts people, not messages
One person writing three times is one voice. When a colleague passes on a customer's words in Slack, the customer is counted, not the colleague. Where it cannot tell whether two messages came from one person, it counts them once, so the counts lean low rather than high.
It needs two people before it drafts
A single request might be one customer's edge case. It goes in the summary as a single mention, where you can still see it, but it does not become a ticket until a second person raises it.
It ranks by what it can see
High at five or more people in the week, or when anyone says it stops them working. Medium at three or four, low at two. It cannot see a customer's plan or revenue, so it never ranks something higher because of who asked. The numbers are on every ticket, so you can rank it yourself.
It does not duplicate your backlog
Before drafting, it looks in your database for a ticket about the same thing, whatever its status. If one exists, it adds a comment with the new count and links and leaves the ticket as it is. The limits are listed under what it will never do.
What a weekly summary looks like
A run of Feedback to roadmap drafts tickets in Notion and posts one summary to Slack. The summary leads with what is new, then what added to existing tickets, then what was mentioned once.
Northwind
Channels
- general
- product
- feedback
- customer-support
product
Week of 13 to 19 October. Read 38 email threads and 26 Slack messages. 4 new drafts, 3 existing tickets updated.
New draft tickets (4)
- Exports time out on large projects, complaint. 6 people, email and Slack. High: two say they cannot send month-end reports.
- No single sign-on, request. 4 people, all from Slack, passed on by the support team. Medium.
- Share button is hard to find, complaint. 3 people, email. Medium.
Added to existing tickets (3)
- Dark mode: 2 more people this week. The ticket is already Planned, so its status was left alone.
- CSV import drops accents: 1 more person, with a sample file.
Single mentions (11)
A Zapier trigger for new comments, keyboard shortcut for search, a Hebrew translation, and 8 more, listed in the thread.
- New draft tickets
Groups that two or more people raised and that have no ticket yet. Each is a page in your database with Status set to Draft, the quotes and links, and a suggested rank with its reason.
- Added to existing tickets
Feedback about something already in your database. The agent adds a comment with the new count and links, and leaves the status, priority and owner as they were.
- Single mentions
Things one person raised. They are listed so nothing is lost, and they become a ticket only if someone else raises them in a later week.
When the counts may be low
If a Slack channel or part of the mailbox could not be read, the summary says which and that the counts may be low. If nothing could be read, it says so once and drafts nothing.
If Notion cannot be written, the groups go into the Slack summary instead, so the week's reading is not lost.
Who uses Feedback to roadmap
Feedback to roadmap suits a product team whose feedback arrives in email and Slack rather than in a dedicated tool. The examples use made-up names.
A product manager planning the next cycle
Priya Nair used to scroll back through a month of Slack before planning. Now she opens the Draft view in Notion and sees each request with how many people asked.
A founder who still reads every email
Daniel Brooks answers the feedback inbox himself and remembers the latest message best. The weekly count shows him which requests keep coming back.
A support lead passing on what customers say
Aisha Bello's team pastes customer complaints into #customer-support. They now reach a ticket, counted as the customer's voice, with a link to the thread.
An engineering lead watching for bugs
Lucas Ferreira reads the complaints group for problems customers hit more than once, and checks the linked messages before picking one up.
What Feedback to roadmap connects to
Feedback to roadmap connects to three tools: it reads Gmail, reads and posts to Slack, and reads and writes to Notion. You connect each one yourself, and Toolspoke stores the connection encrypted, so the agent never sees the credential.
Slack
RequiredSearch conversations and send messages to your workspace.
Authentication: Bot token
Gmail
RequiredRead mail, search threads, apply labels, draft, send, and delete.
Authentication: OAuth 2.0
Notion
RequiredRead and update pages, databases, and team knowledge.
Authentication: Notion OAuth
| Tool | What Feedback to roadmap does | What it cannot do |
|---|---|---|
| Gmail | Finds and reads feedback threads (list_threads, get_thread). | Send, draft, label or trash mail if you give it read access. Those are separate actions the gateway refuses on a read-only grant, whatever the agent is told. |
| Slack | Reads the chosen channels and threads, gets message links and posts one summary (read_channel_history, read_thread, get_permalink, send_message). | Read direct messages or channels the bot has not joined. The connector can also edit its own messages, schedule messages and react, and the agent is told to do none of them. |
| Notion | Reads your database, drafts new pages and comments on existing ones (notion-fetch, notion-query-data-sources, notion-create-pages, notion-create-comment). | Reach pages you have not shared with the connection. It can update and move pages it can reach, and the agent is told only to create drafts and comment. |
That Gmail only reads is a lock, if you install it with read access. That the agent only posts its summary in Slack, and only drafts and comments in Notion, is an instruction to the agent, not a lock. If you want a lock, a project can switch individual actions off: turn off Notion's update, move and duplicate actions and Slack's edit and schedule actions. The access control guide explains how.
Quotes go into Notion, where more people can read them than could read the inbox. The agent is told never to copy an email address, phone number or personal name into a ticket, and to refer to people as a customer or by their company. The link back to the original is how you find out who said it.
What Feedback to roadmap will never do
Feedback to roadmap is told never to reply to a customer, never to change a ticket's status, priority or owner, and never to take a ticket out of Draft. It drafts the case, and a person decides what goes on the roadmap.
- Reply to, draft for, label or forward any email, or post anywhere but the summary channel.
- Change a ticket's status, priority, owner or content, or move a draft out of Draft.
- Create a ticket from one person's feedback, or count one person twice.
- Write a quote that was not said.
- Promise a customer anything, or say in a ticket that something is planned.
Why it will not reply or promise
A reply to feedback is a promise about the product, and only the team can make it. The agent never answers, drafts or forwards mail, never posts outside the summary channel, and never writes that something is planned.
Why it leaves the roadmap alone
Ranking by how many people asked is useful, and it is not the whole decision. Cost, strategy and the customers behind the count are things the agent cannot see. So it drafts with Status set to Draft, comments on existing tickets without changing them, and leaves the call to a person.
Why it will not reword a quote
A ticket is only as good as its evidence. The agent shortens a quote with an ellipsis when it needs to, and never puts words in a customer's mouth.
If something goes wrong
If Notion cannot be written, post the summary with the groups in it so the work is not lost, and say why. If Gmail or every Slack channel cannot be read, say which and draft from what was read, and say the counts may be low. If nothing was read at all, post that once and stop. If the database has no Draft status, create nothing, and say so in the summary.
These are written into Feedback to roadmap's instructions. They guide the agent, but they are not a permission. What it is allowed to touch is set by the access you grant.
Feedback to roadmap reads, groups and drafts. Every reply to a customer and every roadmap decision stays with a person.
When Feedback to roadmap runs
Feedback to roadmap runs every Monday at 9 AM, but only after you switch its schedule on. It arrives switched off, so nothing runs and nothing is charged until you decide.
- Each run reads the last seven days of feedback email and the chosen Slack channels.
- It drafts a ticket for each new group of two or more people, and comments on tickets that already exist.
- It posts one summary to the Slack channel you chose.
- If a source cannot be read, it says which and that the counts may be low.
Each run uses model credit from your workspace balance, so it makes one run a week. A busy inbox costs more, because there is more to read. The Gmail, Slack and Notion calls themselves are free.
Your copy is an ordinary agent in your project. You can pause its schedule there, run it once on demand, change the day and edit its instructions. The agent's page lists recent runs and their cost.
How to set up Feedback to roadmap
To turn feedback into tickets, add Feedback to roadmap to a Toolspoke project, connect Gmail, Slack and Notion, choose where it reads and writes and switch on the schedule. It takes a few minutes, and nothing runs until the last step.
Step 1: Create a Toolspoke account or sign in
Choose Use this agent. If you are new, you will be asked to sign up first, and you come straight back to this agent afterwards.
Step 2: Add it to a project
Pick the project it should live in. You get your own editable copy, and you can see the three tools it brings before anything connects.
Step 3: Connect Gmail with read access
Choose Sign in with Google with the mailbox feedback arrives in. A shared feedback or support address works best. Give it read access, so it cannot send or change mail.
Step 4: Connect Slack and invite the bot
Sign in to Slack, then invite the bot to each channel it should read and to the channel the summary goes in. It cannot read a channel it has not joined.
Step 5: Connect Notion and share the database
Sign in to Notion and share your product tickets database with the connection. Make sure its Status property has a Draft option.
Step 6: Switch on the schedule
The schedule arrives switched off. Run it once, read the drafts it makes and check a few quotes against their links, then switch it on.
Make Feedback to roadmap fit your team
Feedback to roadmap's instructions are plain English and you can edit them after you install it. Installing copies the agent, so your edits stay with your copy. Open the agent in Toolspoke and tell the builder what to change, and it rewrites the instructions.
Paste any sentence below into the builder chat, or say the same thing in your own words.
Draft a ticket when one person raises something, not two, and mark it low.
Set the Type property to Bug for complaints and Feature for requests.
Also read #sales-calls, and count the customer named in each note, not the person who wrote it.
Leave out anything about pricing or billing. Those go to the finance team.
Run every second Monday at 9 AM and read the last fourteen days.
This changes when the agent wakes up, so the builder edits its schedule as well as the instructions.
None of these edits needs more access or touches the Never rules. They change what Feedback to roadmap is told, not what the connections allow.
How it compares to other options
Feedback to roadmap beats the alternatives when your feedback already lives in email and Slack and nobody has time to tag it, and loses to them when you need customer revenue or a portal where customers vote.
| Compared on | Feedback to roadmap | Tagging by hand | A feedback tool | Reading it all at planning |
|---|---|---|---|---|
| Reads email and Slack where feedback lands | Yes | Yes, if someone does it | With integrations | Yes |
| Counts people, not messages | Yes | If done carefully | Yes | No |
| Links each ticket to its evidence | Yes, every quote | Sometimes | Yes | No |
| Knows customer revenue or plan | No | If you look it up | Often, via your CRM | From memory |
| Changes your roadmap | No, drafts only | No | Sometimes | No |
| Setup effort | Connect three accounts | None, then hours a week | Weeks to roll out | None, then a day per cycle |
A dedicated feedback tool is the better choice when you want customers to vote, or need each request weighed by the revenue behind it. It works best once everyone sends feedback to it. Feedback to roadmap is for the team that wants the feedback it already gets counted and filed, without moving it anywhere.
Tagging by hand gives the most judgement per message, and it is the first thing to slip in a busy week. The agent does the reading and leaves the judgement to you.
Frequently asked questions
Will Feedback to roadmap reply to customers?
No. It is told never to reply, draft or forward mail. Install Gmail with read access and the connection cannot send or draft at all.
Does it change my roadmap?
No. New tickets are created with Status set to Draft, and existing tickets only get a comment. It never changes a status, priority or owner, and a person moves a ticket out of Draft.
How does it decide what is important?
By how many separate people raised something this week, and whether anyone says it stops them working. It shows the counts on every ticket. It cannot see a customer's plan or revenue, so it does not weigh by them.
Will it create duplicates of tickets we already have?
It checks your database first, including tickets that are not in Draft. If one is about the same thing, it adds a comment with the new count and links instead of creating another.
Does it put customer names and emails in Notion?
It is told not to. Tickets refer to a customer, or their company where the email domain is a company's. Each quote links back to the original message, which is where you find out who said it.
Can it read Slack DMs?
No. It reads only the channels you choose and that the bot has joined. The Slack connection cannot read direct messages.
Does it work with Linear or Jira instead of Notion?
Not as shipped, because it drafts in Notion. Toolspoke has Linear and Jira toolkits, so you can ask the agent builder for another version. It needs its own instructions.
Is Feedback to roadmap free?
It has no price of its own, and every Toolspoke plan includes agents. Tool calls cost nothing, but each run draws on your usage balance. Pricing has the details.
Hear every customer, not the loudest one
Connect Gmail, Slack and Notion and switch on the schedule. Your first set of draft tickets lands on Monday.