Guide
How do I keep track of feature requests customers drop in Slack Connect channels?
File the request into Linear or Jira the same day as the system of record. Acknowledge it in the Slack Connect thread within 4 business hours. Keep the chase off the shared channel. A spreadsheet, a dedicated #feature-requests channel, and a Notion doc lose requests. A team of one to eight with 8 to 40 shared channels starts there.
By The Concrete team ยท Published
We make Concrete.
What a dropped feature request actually means
File the request into Linear or Jira the same day as the system of record. Acknowledge it in the Slack Connect thread within 4 business hours. Keep the chase off the shared channel. Seeing the ping on Tuesday and still owning it on the board on Thursday are different jobs.
A Slack Connect customer channel has no native owner, no Open, and no due date on a feature request. The ask often lands as can you add this in a thread with no @mention. Three people on a one-to-eight person CS team can see it and each assume a teammate filed it. Shared channels sit on paid Slack plans on both sides. The Free plan only allows one-to-one external DMs. Pro is $7.25 per user per month billed annually, or $8.75 billed monthly, as of 19 November 2026. People in that channel can see messages from bots and apps.
On r/SaaS on 2 January 2026, a founder asked how to track feature requests that come in via Slack without losing them. One commenter said a dedicated #feature-requests channel plus a spreadsheet or Notion board, copied when someone remembers, usually loses about 30% of requests. Another said they pin important ones and copy to a spreadsheet once a week, tried Linear's Slack integration, and ended up with 100 feature requests that were just people complaining. On r/CustomerSuccess in March 2026, a CS team running about 12 Slack Connect relationships wrote that a customer waited 5 hours because everyone assumed someone else was handling it. Their workaround was a shared Notion doc that nobody updated consistently. A CS lead at a Series A company in the same thread said they had personally managed at least 30 channels at a time.
Param Mehta, posting on 19 November 2026, wrote that half of what a customer asks for gets said once, in a Slack thread or on a call, and by the time someone builds it the thread is 400 messages deep. Yura Riphyak wrote on 11 November 2026 that about 90% of Alphie's roadmap is pulled by customers, and every customer gets their own Slack channel. Karri Saarinen, Linear's CEO, posted the same day that a Weekly product signals Loop scans Linear, Slack, Intercom, Gong, and X, groups feedback by product area, and links each bullet back to the customer who said it. Linear's own CX team files Slack comments with Asks templates, one for bugs and one for feature requests, then reaches the customer once the issue is Done.
Mursa publishes 4 business hours for standard client Slack, 1 business hour for urgent, and the next business day after hours. Its July 2026 workspace audit logged 3,100-plus client-side messages across 14 client channels over 27 weeks. Pylon's State of Slack Support 2025 says most companies manage fewer than 30 to 50 customer Slack channels, while its top 100 accounts averaged 893 each. Write the 4-business-hour ack into the channel description. Catching the inbound ping is on how to stop Slack Connect customer messages from falling through the cracks. Naming a person on the thread is on how B2B CS teams assign ownership without tickets. A Notion list of open threads is on the Notion tracker page. Filing shop work into Jira is on how dev shops keep Slack requests from getting lost before Jira. The same miss mechanics for agencies sit on how agencies stop missing client messages in Slack Connect. The job split with a Slack Connect helpdesk is on Pylon vs an AI teammate.
Which tool wins which job
Fund the row that matches the leak. Filing from the message, tracking on the board, and a voting portal are neighboring jobs.
| Job | Wins it | Why |
|---|---|---|
| Track the request after it exists | Linear or Jira | Linear Customer Requests sit on every plan. Jira Cloud Standard is USD 9.70 per user per month for 1-100 users, effective 13 October 2026 PT. Assignee, status, and duplicates live here. Slack is intake. |
| File from the Slack message, your team has seats | Linear Slack or Jira Cloud for Slack | Linear: More actions, Create new issue. Linear users only. Slack guests cannot, even with a Linear account. /linear is not supported in threads. Jira: hover, More actions, Create work item from Jira Cloud. Licensed Jira users only. |
| Let a customer without a seat file | Linear Asks | Asks is on Business at $16 per user per month billed yearly. In a shared channel your org started, an external user can file with a ticket emoji or @Linear Asks if that option is on. Auto-create on every new message is Enterprise, and public channels only. |
| Attach the customer to the issue | Linear Customer Requests | Available on Free, Basic, Business, and Enterprise. Creating from Slack can prefill Customer from the sender's domain. Link to Slack channel on the customer page needs Asks. Slack Connect users outside your workspace never see the Customer field. |
| Capture a note, leave the feature idea in Productboard | Productboard Slack | Push to Productboard creates an Insights note. Productboard's own help says it is not yet possible to create new feature ideas from Slack. Shared channels need the app invited. A public confirmation is visible to the customer. |
| Public voting board and a status ping in the original thread | Canny | Slack is on every plan. @Canny is Canny-admins only. Anyone in the workspace can use /canny or the feedback shortcuts. Status changes post a follow-up in the original Slack thread. Pro starts at $79 per month billed yearly, with Jira and Linear integrations on Pro. |
| Dedicated #feature-requests plus a weekly spreadsheet | A spreadsheet someone remembers to update | On r/SaaS that setup usually loses about 30% of requests. Linear Slack with no triage filled a board with complaints. Capture from the customer thread the same day. |
| A Slack List assignee and due date | Slack Lists | Hover the message, Add to list, set Assignee and Due Date. Someone still has to add the item. Sharing the list in Connect shows the customer your queue. |
| Eyes emoji as seen | A receipt | Pylon's Slack-first guide, dated 26 October 2026, says an eyes reaction can mean I saw this. It cannot reliably mean I own it until the customer confirms the fix. An eyes mark does not create the Linear or Jira issue. |
| Receipt on the Slack ask, a person still sends, Linear or Jira as an Approve card | Concrete | Receipt marks on inbound messages. Send / Edit / Skip cards; no auto-send mode. Follow-ups survive reboots. Each morning it nudges the owner of every open ask. A Linear or Jira create shows as an Approve card and runs only after a tap. It never deletes. Design-partner preview; see what it is. |
What Linear and Jira Slack actually do in Connect
The Linear Slack app files work from Slack. Hover a message, open More actions, Connect to apps, and choose Create new issue. Linear's Slack help says only Linear users in your Slack workspace can create issues that way. Slack guests cannot, even with a Linear account. /linear is a lightweight create. It is not supported in threads, for Slack sync, or for uploading files. Asking @Linear to create an issue is the fuller workflow. One of Linear's own examples is @Linear make feature requests from this thread. Code Intelligence is not available in externally shared channels or external Asks conversations.
When you create an issue from Slack you can also create a synced comment thread. If Linear is in the channel, comments stay in sync between Linear and Slack. Comments made in the synced Linear thread appear in Slack, and the Slack thread updates when the issue is completed, canceled, or marked as a duplicate. That is useful inside your company. In a customer Slack Connect channel it is also public chase. People in that channel can see messages from bots and apps.
Asks is the row for people without a Linear seat. It sits on Business at $16 per user per month billed yearly, and on Enterprise. In a shared channel initiated by your organization, external Slack users can create issues in your Linear workspace by applying the ticket emoji or mentioning @Linear Asks, if that option is enabled. Other creation methods are not available to external users in a shared channel. Auto-create on every new message is Enterprise only, public channels only, and it creates an Ask from both internal and external messages. That switch belongs on a dedicated intake channel, not a mixed customer channel full of standups and screenshots.
Asks keeps a synced comment thread. Replies in Slack land on the Linear issue, and replies in Linear post back to Slack. Requesters can see status and assignee from Slack. Customer Requests sit on every Linear plan. Creating from Slack can prefill Customer from the sender's domain. To associate a shared channel with a customer, open the customer page and choose Link to Slack channel. That needs Asks connected; the standard Slack integration alone does not enable channel linking. Slack Connect users outside your workspace never see the Customer field.
On r/Linear, one team puts every customer feature request on a dedicated Feature Requests team with the customer attached, then moves it onto the relevant project. Linear's CX write-up uses the same split: bugs to engineering triage, feature requests to product triage, with Asks templates that keep required fields short so filing stays fast.
The Jira Cloud app files work from Slack the same way. Hover any message, open More actions, and choose Create work item from Jira Cloud. Fill space and work type. /jira create does the same job without Rovo. Rovo can pre-fill summary and description from the full thread in a channel. Thread sync writes Slack replies onto the work item as comments. A single create from the app turns that on by itself. Atlassian's docs describe Slack messages becoming Jira comments. They do not describe Jira comments posting back into the Slack thread on this app.
The Jira Cloud app works exclusively for licensed users. Shortcuts from an app are available to people from another organization only if that app is installed on their workspace. In a customer Slack Connect channel, your team files from its own side. Assist is a separate Slack app from Jira Cloud. It is Jira Service Management only. Optional auto-create turns every message in a request channel into a work item, with a ticket emoji. That is the wrong switch for a mixed customer channel.
When Productboard, Canny, or a voting board is the row
Linear and Jira win the tracker. A product-insights tool and a public board win neighboring jobs. Productboard's Slack integration pushes a message into Insights as a note. You can link that note to an existing feature idea, mark importance, and add a comment. You still create the feature idea inside Productboard. Shared channels need the Productboard app invited; if both companies want to push, each side installs its own integration. Notifications can post a view-only confirmation in the public channel. That confirmation is visible to the customer in Slack Connect. Business is request-a-demo pricing, with a minimum of 5 makers, as of 19 November 2026. Enterprise is contact sales. The live pricing page does not list a dollar price.
Canny wins a public voting board and a close-the-loop ping in the original Slack thread. Slack is on every plan. Mention @Canny in a channel the bot has been invited to, or use Submit feedback / Add to existing feedback / /canny. @Canny matches your Slack account to a Canny admin by email and is admins only. Anyone in the workspace can use /canny and the shortcuts. Autopilot dedupes Slack submissions. When feedback was captured from Slack, Canny replies in that same thread whenever the linked idea's status changes. On r/SaaS in March 2026, a founder wrote that several users who cancelled had requested features the team had already shipped. They just never knew, because feedback lived in Slack, tickets, reviews, and call notes with no record of who asked. Canny's close-the-loop reply is the portal version of that job. Jira, Linear, and other PM integrations sit on Pro, which starts at $79 per month billed yearly for 100-plus tracked users. Free is $0 with 25 tracked users.
Pylon lists feature-request capture on the platform. Professional is $89 per seat per month on an annual contract as of 19 November 2026, last updated 10 November 2026. Pylon wins tickets, Internal Threads, and SLAs once inbound volume needs a queue. A team of one to eight with 8 to 40 shared channels files into Linear or Jira first. It outgrows that setup into Pylon, ClearFeed, or Thena. Seed-stage options that skip a ticket queue sit on Pylon alternatives. Turning Slack messages into Asana or ClickUp tasks is a neighboring job, on the Asana and ClickUp page.
What a feature-request layer costs
A same-day file from Slack into Linear or Jira is free once those seats are paid. Asks, a voting board, and a Slack Connect helpdesk are priced. Pylon Facts, last updated 10 November 2026, is the vendor's official source for seats. A one-to-eight person CS team whose founder still answers customers usually funds Linear or Jira Slack first.
| Tool | Price as of 19 November 2026 | What it tracks | Where it stops |
|---|---|---|---|
| Slack Pro plus Lists | $7.25 per user per month billed annually, $8.75 monthly. Lists included on paid plans. | An Assignee and Due Date on each item you add | No auto-ingest. Sharing a list in Connect shows the customer your queue. |
| Linear Free or Basic | Free is $0. Basic is $10 per user per month billed yearly. | Customer Requests, and Create new issue from Slack for Linear users | Asks is not included. Slack guests cannot create issues. /linear does not work in threads. |
| Linear Business | $16 per user per month billed yearly | Asks, Slack intake, ticket emoji in a Connect channel your org started, Customer Requests from Asks | Auto-create on every new message is Enterprise and public-only. Synced Linear comments post into Slack. |
| Jira Cloud Standard | USD 9.70 per user per month for 1-100 users, effective 13 October 2026 PT | The board of record, Create work item from Slack for licensed users | Thread sync is Slack replies onto the work item. A customer in Connect usually cannot file. |
| Productboard Business | Request a demo. Minimum 5 makers. Enterprise is contact sales. | Insights notes pushed from Slack, linked to an existing feature idea | Cannot create new feature ideas from Slack. A public confirmation is visible in Connect. |
| Canny Free or Pro | Free is $0 with 25 tracked users. Pro starts at $79 per month billed yearly, 100-plus tracked users. | A voting board, Slack capture, status follow-up in the original thread | @Canny is admins only. Jira and Linear integrations sit on Pro. |
| Pylon Professional | $89 per seat on an annual contract. Advanced is $139. | Slack Connect issues plus feature-request capture on the platform | Minimum seat count unpublished. Built for B2B support teams. Support Agent can resolve issues end-to-end. |
The caveat that should decide the setup
The failure mode CS teams name first is the bystander effect: the customer asked for a feature, three people had seen the thread, and nobody created the issue before Thursday. On r/SaaS a dedicated #feature-requests channel plus a weekly spreadsheet lost about 30% of requests. A Notion doc fails the same way, because it depends on someone updating a second system after the conversation already moved on. An eyes emoji is a receipt. The board still needs the issue.
A second caveat is public chase. People in a Slack Connect channel can see messages from bots and apps. Linear synced threads post Linear comments into Slack and update the thread when the issue is completed, canceled, or marked duplicate. Asks posts status and assignee where the requester can see them. Canny replies in the original Slack thread on every status change. Productboard can post a view-only confirmation that a message was pushed. A public engineering debate in the customer channel is how a maybe becomes a promise. Keep grooming in Linear, Jira, or a private channel. Paste the issue key in the customer thread once, as a receipt. Safety of putting an agent in that channel is on the shared-channel page.
A third caveat is auto-create and auto-send. Linear Asks auto-create on every new message, and Assist auto-create, belong on a dedicated intake channel. A mixed customer channel full of standups will mint an issue for every screenshot. Pylon's Support Agent resolves customer questions automatically across every channel and brings in humans when judgment is needed. A seed-stage CS team talking to customers in Slack Connect usually cannot let that fire. Concrete is an AI employee that works in existing Slack channels: every incoming message gets a receipt mark, drafts land as Send / Edit / Skip cards, and there is no auto-send mode. After downtime it sweeps channel history, thread replies included. Follow-ups survive reboots. Each morning it nudges the owner of every open ask. A Linear or Jira create shows as an Approve card and runs only after someone in the workspace taps Approve. It never deletes. It can start from a Customer Success or Product Owner role. It is in design-partner preview; the longer thesis is on the vision page. Write it as a small team, many shared channels, nothing dropped. Drafting the customer-facing reply is a neighboring job, on the approval-before-send page.
A fourth caveat is book size and the close-the-loop. Pylon wins tickets, Internal Threads, and SLAs once inbound volume needs a queue, and its power users run hundreds of customer channels. Pylon's own 2025 data still puts most companies under 30 to 50 channels. A team of one to eight with 8 to 40 shared channels funds a same-day file into Linear or Jira first. It outgrows that setup into Pylon, ClearFeed, or Thena. Filing is half the job. Telling the customer when it ships is the other half. Linear's CX team treats Done as the prompt to reach the customer. Canny's thread reply does that in Slack. A morning list of still-open asks is on the daily summary page. Spoken promises in a thread are a third job, on the commitments-from-threads page. The pre-call list from Slack Connect history is on how CS teams prep for a customer call. Hiring the first CSM is on should a founder keep answering or hire a CSM.
Step by step: keep the Slack Connect request on the board
This is the boring version that holds when the founder or a CS lead of one to eight still owns most customer channels. Pin it in the internal channel, before the next can you add this that dies in a 400-message thread.
- Step 1: Acknowledge the same day. Reply, or react, so the customer knows the ask landed. Name that you are filing it. Got it, filing now is a receipt. Silence until Thursday is how the thread dies. Mursa publishes 4 business hours for standard Slack, 1 business hour for urgent, and the next business day after hours. Put the target in the channel description.
- Step 2: File from the message the same day. Hover the customer message and choose Create new issue in Linear, or Create work item from Jira Cloud. Fill team or space, type, and required fields. /linear does not work in threads; use the message action or @Linear. /jira create works without Rovo. Paste the issue key back in the thread so the next person can see the work item exists.
- Step 3: Attach the customer. On Linear, set Customer when you create from Slack, or link the shared channel on the customer page once Asks is connected. Customer Requests sit on every Linear plan. Slack Connect users never see that field. On Jira, put the account on the work item the way your project already does. A request with no customer attached is how close-the-loop fails later.
- Step 4: Search for a duplicate before you mint a new issue. Linear's Link existing issue and Canny Autopilot exist because the same ask arrives ten times in ten phrasings. On r/SaaS, Linear Slack with no triage produced 100 complaints on the board. If the request already exists, add a customer request or a comment and skip the new issue.
- Step 5: Name one owner. A group in the channel recreates the bystander effect. Assign the Linear or Jira issue to one person. Name the backup in the same pinned note. On r/Linear, a dedicated Feature Requests team is the thicker version of the same rule.
- Step 6: Keep the chase off the shared thread. Nudge the owner in Linear, Jira, a private channel, or a To-do with a reminder. Creating a Slack to-do does not set a reminder by default. People in Slack Connect can see messages from bots and apps. Follow every thread on that customer channel. A catch-up that reads only top-level messages drops the actual ask.
- Step 7: Close the loop when it ships. When the issue is Done, tell the customer who asked. Linear's CX team treats Done as the prompt to reach them. Canny replies in the original Slack thread on a status change. A public engineering comment thread is still chase; the note the customer sees waits for a person to send.
- Step 8: Keep a person on the send button, then add Asks or a queue when filing by hand breaks. A receipt and an issue key are not a customer-facing reply. Draft if you want speed. Send stays a tap. There is no auto-send mode that is safe in a customer channel. When people without Linear or Jira seats need to file, turn on Asks in a Connect channel your org started, or add Canny. When the morning sweep of 8 to 40 channels is the step that fails, fund a Slack Connect helpdesk. Pylon Professional is $89 per seat on an annual contract for that row. Quiet during onboarding is a neighboring job, on how onboarding teams keep new channels from going quiet.
Questions people ask
Why do feature requests in Slack Connect never make it onto the roadmap?
A Slack thread has no owner. Several people can see can you add this and each assume someone else filed it. On r/SaaS in January 2026, a dedicated #feature-requests channel plus a weekly spreadsheet lost about 30% of requests. File from the message into Linear or Jira the same day.
Can a customer in Slack Connect file a Linear issue themselves?
On the regular Linear Slack app, only Linear users in your workspace can create issues. Slack guests cannot, even with a Linear account. Linear Asks on Business lets an external user in a shared channel your org started file with a ticket emoji or @Linear Asks, if that option is on.
Does Productboard create a feature idea from a Slack Connect message?
No. Productboard's Slack help, read 19 November 2026, says it is not yet possible to create new feature ideas from Slack. Push to Productboard creates an Insights note. Invite the app into the shared channel first. A public confirmation in that channel is visible to the customer.
Should Linear comments post back into the customer Slack Connect thread?
Linear synced threads post Linear comments into Slack, and they update the thread when the issue is completed, canceled, or marked duplicate. People in Slack Connect can see messages from bots and apps. Keep engineering chase in Linear or a private channel. Paste the issue key in the customer thread once, as a receipt.
How fast should a CS team acknowledge a feature request in Slack Connect?
Mursa publishes 4 business hours for standard Slack, 1 business hour for urgent, and the next business day after hours. An acknowledgment is got it, filing now. Silence until the board has the issue is how the request stays a Slack message. Put the target in the channel description.
Does a dedicated #feature-requests channel keep requests from getting lost?
Only while someone copies them out. On r/SaaS, that setup plus a weekly spreadsheet lost about 30% of requests. Linear Slack with no triage also filled a board with complaints. Capture from the customer thread into Linear or Jira the same day. Slack stays the conversation. The board stays the record.
When should a small CS team buy Linear Asks or Canny?
When people without Linear or Jira seats need to file, or you want a public voting board. Asks is $16 per user per month billed yearly on Linear Business. Canny Pro starts at $79 per month billed yearly. A team of one to eight with 8 to 40 channels files from the message first.
Can an AI create the Linear or Jira issue without a person approving it?
Linear Agent can create issues when a Linear user mentions @Linear. Concrete prepares a Linear or Jira create as a Slack card and runs it only after someone taps Approve. It never deletes. The customer-facing reply still waits for a Send tap. There is no auto-send mode.
Sources
- Slack pricing, read November 19, 2026
- Slack Connect guide: Work with external organizations, read November 19, 2026
- Use lists in Slack, read November 19, 2026
- Later is now To-dos (Slack), read November 19, 2026
- Linear Slack integration, read November 19, 2026
- Linear Asks, read November 19, 2026
- Asks with Slack, read November 19, 2026
- Linear Customer Requests, read November 19, 2026
- Linear pricing, read November 19, 2026
- How Linear's Customer Experience team works in Linear, read November 19, 2026
- Create and update Jira work from Slack, read November 19, 2026
- Sync your Slack threads with Jira work items, read November 19, 2026
- What is the difference between Chat and the Slack integration?, read November 19, 2026
- Atlassian Cloud pricing tables (Jira Standard from 13 Oct 2026 PT), read November 19, 2026
- Getting started with Productboard's integration for Slack, read November 19, 2026
- Productboard pricing, read November 19, 2026
- Canny Slack integration, read November 19, 2026
- Canny pricing, read November 19, 2026
- Pylon Facts, last updated 10 November 2026, read November 19, 2026
- Pylon: The state of Slack support 2025, read November 19, 2026
- Pylon: Slack-first B2B support, scaling beyond the thread, dated 26 October 2026, read November 19, 2026
- Mursa: Slack for clients, manage communication and scope, read November 19, 2026
- r/SaaS: Honest question, how do you track feature requests that come in via Slack, read November 19, 2026
- r/CustomerSuccess: How are you managing support across 10+ Slack Connect channels, read November 19, 2026
- r/SaaS: We were losing users who requested features we actually built, read November 19, 2026
- r/Linear: How are you handling Customer Requests, read November 19, 2026
- Param Mehta: half of what a customer asks gets said once, thread 400 messages deep, read November 19, 2026
- Yura Riphyak: 90% of the roadmap pulled by customers, each customer a Slack channel, read November 19, 2026
- Karri Saarinen: Weekly product signals Loop scans Linear, Slack, Intercom, Gong, and X, read November 19, 2026
If your team already runs its work in Slack, start with one role in one channel. Concrete is an AI teammate that works in your Slack channels and asks a person to approve before anything goes out. It is not a chatbot builder, and it never sends on its own.