Linear Asks is Linear's request intake feature. It turns requests from Slack, email, and web forms into Linear issues, so anyone in the company can ask a team for work without opening Linear. Every Ask lands in the team's Triage queue, and the requester gets updates where they asked. Asks is included in Linear's Business and Enterprise plans, and requesters do not need a Linear seat.
This guide covers how each of the three channels works, where Asks land, what Asks costs, how to set it up, and where it stops.
In this article
1.
2.
3.
4.
5.
6.
7.
8.
What Linear Asks Is
Most teams on Linear get requests from people who do not work in Linear: sales needs a data pull, finance needs a report fixed, someone in ops spots a bug. Those requests usually arrive as Slack messages and direct pings, and then they get lost, retyped into Linear by hand, or forgotten.
Asks makes the request itself the issue. The person asking stays in Slack, email, or a form. The team gets a real Linear issue with the request attached, in a queue it already works. When the team updates the issue, the requester sees it in the same place they asked.
Asks moves request intake out of DMs and into a queue. The requester stays where they are, and the team stays in Linear.
How Linear Asks Works: Three Channels
Asks accepts requests through three channels. All three create the same thing, a Linear issue in the receiving team's Triage queue, but each fits a different kind of requester.
| Channel | How a request is made | What the requester sees | Plan |
|---|---|---|---|
| Slack | Emoji reaction, the /ask command, or mentioning the Asks agent | A synced Slack thread with status and assignee updates | Business, Enterprise |
| Sending to the team's intake address | Replies and comments synced with the email thread | Business, Enterprise | |
| Web forms | Filling in a form on the team's Asks page | Follow-up through a synced email thread | Enterprise |
Asks in Slack
Slack is where most Asks start. A person can turn any message into an Ask with an emoji reaction, use the /ask command, or mention the Linear Asks agent. If the channel has a template with required fields, Linear prompts the requester for the missing information before it creates the issue, so a request never arrives as a single vague line.
The Slack thread and the Linear issue stay connected. Replies sync both ways, and status and assignee changes show up in the thread. An Ask made in a direct message or in the Asks app home is a private Ask, visible only to the requester and the team handling it.
Asks by email
Email intake gives every team an address people can send requests to. In Asks settings you create an intake address, either one Linear provides or your own address forwarding into Linear. Each email becomes a new issue, with the subject as the title and the body as the description. Replies on the thread become comments, and comments sync back to the email thread, so the requester never has to log in.
Asks web forms
Web forms, added in April 2026, give a team an Asks page with a form for each kind of request: a bug report form, a feature request form, a data pull form. Each form is built on an issue template, so the team decides exactly which fields are required. Submitters do not need a Linear account, and they follow up through a synced email thread. Web forms are Enterprise only.
Where Asks Land: The Triage Queue
Every Ask arrives in the receiving team's Triage queue. Triage is Linear's inbox for work that comes from outside the team, and nothing in it is committed work until someone accepts it. A person reviews each Ask and accepts it, marks it as a duplicate, declines it, or snoozes it, exactly as they would any other incoming issue. Our Linear Triage guide covers the queue in depth.
Three Triage features matter most for Asks.
Triage responsibility
Assign someone to own the queue, and rotate the duty, so Asks never sit unread. On Business and Enterprise the rotation can follow a PagerDuty, Opsgenie, Rootly, or incident.io schedule.
Triage Intelligence
On Business and Enterprise, Triage Intelligence suggests a team, assignee, labels, and possible duplicates for each new Ask, usually within a few minutes. Each team can choose to show those suggestions or apply them automatically.
Triage routing
On Enterprise, triage routing sends each Ask to the right team's queue for you, which matters once a single Slack channel or intake address serves several teams.
Linear Asks Pricing
Linear Asks has no price of its own. It comes with Linear's Business and Enterprise plans, and it is not on Free or Basic.
| Plan | Price per user per month | Asks | Web forms and triage routing |
|---|---|---|---|
| Free | $0 | No | No |
| Basic | $10, billed annually | No | No |
| Business | $16, billed annually | Yes | No |
| Enterprise | Custom, annual only | Yes | Yes |
The detail that changes the math is who needs a seat. Requesters do not. Anyone in the company can file an Ask from Slack, email, or a form without a Linear account, so you pay only for the Linear members who work the requests. For a company where a few hundred people ask and a dozen engineers answer, that is the difference between a dozen seats and a few hundred. Our Linear pricing guide breaks down the plans in full.
How to Set Up Linear Asks
Setting up Asks takes four steps, and a workspace admin needs to do the first one.
- 1
Turn on Asks in workspace settings
An admin enables Asks in the Asks section of workspace settings. Asks needs the Business or Enterprise plan.
- 2
Connect Slack and choose channels
Install the Linear Asks app in Slack, then pick which channels create Asks and which Linear team each channel sends to. Attach a template with required fields to each channel.
- 3
Create an intake email address
In Asks settings, create an intake address for each team that takes email requests, or point an existing address at Linear so it forwards in.
- 4
Turn on Triage and give the queue an owner
Make sure each receiving team has Triage enabled and a named triage owner, so Asks are reviewed from the first day instead of piling up.
On Enterprise, add web forms last, once you know which request types come up often enough to deserve their own form.
What Linear Asks Is Good For, and Where It Stops
Asks is built for one job: internal requests from colleagues who do not live in Linear. It does that job well. It is not a help desk.
Asks works well for
- Requests from sales, ops, finance, and other internal teams
- Bug reports from colleagues in Slack
- IT, data, and access requests
- Teams that want one queue instead of scattered DMs
Asks is not built for
- Customer support tickets in a help desk
- SLAs, customer-facing replies, and ticket reporting
- Requests that need a customer record attached
- Support teams that run on HubSpot Service Hub
For customer support, the ticket already lives in a help desk, with the customer record, the conversation history, and the SLA. Moving that work into Slack or an email address so Asks can pick it up throws away the context the help desk exists to keep. What support teams need is a link between the help desk ticket and the Linear issue.
Linear's native integrations cover that for Intercom, Zendesk, Front, and Salesforce, and they attach the requesting customer to the issue as a customer request. Our Linear customer requests guide explains how that works. HubSpot Service Hub is not one of Linear's native sources.
Linear Asks for Teams That Run Support in HubSpot
If your support team works in HubSpot Service Hub, Asks covers your internal requests, but customer tickets need a different path. IssueLinker is that path. From the HubSpot ticket, support creates a Linear issue in one click, or links an existing one, with the ticket conversation carried over. The issue lands in the team's Triage queue like any Ask. Comments sync both ways, so an engineer's question reaches the support rep without anyone leaving their tool, and the Linear status is written back to the ticket so support knows the moment a fix ships.
Send HubSpot tickets to Linear Triage with the context attached
IssueLinker turns a HubSpot ticket into a synced Linear issue in one click. Comments sync both ways, the Linear status flows back to the ticket, and it works on any HubSpot plan, including free.
Many teams run both: Asks for requests from colleagues, and a help desk integration for requests from customers. Both feed the same Triage queue, so engineering works one inbox no matter where the request started.
