Right-click any message
Turn a customer ping or a teammate dropping context into a clean UserJot request without leaving the thread it came from.
Slack integration
Capture requests from any Slack message, let AI draft a clean version, and keep every update in one organized thread. Built for teams who already live in Slack.
Jordan Mills10:42 AM
Just got off a call with Linear. They want to bulk-export their feedback to CSV before our QBR. Said it's a dealbreaker if we can't do it by Q2. Big account, want me to file something?
2 replies·Thread
UserJotAPP10:42 AM
Drafted a request from Jordan's message.
Linear flagged CSV export as a Q2 blocker for their QBR. Needed for accounts that audit feedback outside UserJot.
UserJotAPP2:18 PM
Sam Patel moved this to Planned
Powering product-led companies
Capture
Customers ask for things in support channels. Teammates drop ideas in standups. AEs forward calls. UserJot meets each of those moments where they happen, then gives you back one clean request on the right board.
Turn a customer ping or a teammate dropping context into a clean UserJot request without leaving the thread it came from.
Type /userjot from anywhere or trigger the global shortcut. A native Slack modal opens with Board, Title, and Description ready to edit.
Title and description are drafted from the source message, only ever rewriting what is already there. Suggested board picked from your real boards.
AI drafting
The thing customers actually said is rarely the thing you want as a roadmap title. UserJot drafts both, and lets you ship the version that reads like the rest of your board.
Board
Suggested by AI from your workspace boards.
Title
Description
Threading
Most Slack integrations turn your channel into a firehose. A status change, a new comment, a vote, a reply: each one arrives as a fresh top-level message, and within a week your team has muted the channel.
UserJot does the opposite. Every request gets a single root message 01, and every later event lands as a reply under it. A new comment, a status moving to Planned, a teammate piling on with more context. They all live in the same thread, in order, scoped to that one piece of feedback.
The root message itself stays current 02. When status or board changes, it updates in place. Same message ID, fresh content. So the top of the thread is always the truth, and the replies are the history of how you got there.
And because the draft 03 stays faithful to what the customer actually said, the thread reads like a conversation that closed a loop, not a marketing artifact. Open the request 04 straight from any message when you need the full board.
Controls
Channels, events, and noise levels are all configurable per workspace. Set it once, forget about it, change it the day you switch from #product to #customer-success.
Pick any public or private channel as your default destination. Public channels are joined automatically; private channels just need an invite to @UserJot.
New requests, comments, replies, status changes, board changes. Turn each on or off independently, with granularity that fits a busy product channel.
Optionally exclude actions taken by your own admins and owners, so customer-facing channels only see what customers and teammates actually do.
Verify the wiring without waiting for real activity. One click confirms the channel, the auth, and the formatting before you go live.
Setup
One install for the whole UserJot workspace. Individual teammates link their own Slack account once, and creation is credited correctly forever after.
A workspace owner or admin connects UserJot to your Slack workspace from Settings → Integrations. Standard Slack OAuth, no fields to fill in.
Choose where notifications land, toggle the event types you care about, and send a test message to confirm the channel is wired up correctly.
Teammates connect their personal Slack account once. Requests created from Slack are then credited to the right person on UserJot, automatically.
Questions
How install works, who can create requests, what stays in Slack, and what we have not shipped yet.
A workspace owner or admin installs UserJot from the Slack App Directory and picks a default channel for notifications. Individual teammates can also link their Slack account to their UserJot identity, so requests they create from Slack are credited to them.
Yes. Right-click any message and choose Create UserJot request, or use the global shortcut, or run the /userjot slash command. A native Slack modal opens with Board, Title, and Description already drafted by AI from the message contents. You stay in Slack the whole time.
It reads the source message, drafts a concise title and description that preserves the original meaning, and suggests one of your existing UserJot boards. It only rewrites what is in the message, never invents details, and falls back to the raw text if AI is unavailable. You can edit anything before submitting.
Every UserJot request gets one root message in the channel you choose. New comments, replies, status changes, and board changes are posted as replies in that same Slack thread, so each feedback item has one tidy conversation rather than flooding the channel. The root message updates itself in place when status or board changes.
New requests, new comments, new replies, status changes, and board changes. Each is independently toggleable. There is also a separate switch to exclude actions taken by your own admins and owners, which is useful for keeping internal noise out of customer-facing channels.
Yes. Public channels are joined automatically once selected. For private channels, invite @UserJot to the channel after picking it, and posting starts immediately. You can verify the wiring at any time with the Send test message button in settings.
Today, request creation from Slack is available to UserJot admins and owners. Anyone in the channel can still benefit from notifications and threaded discussion. Wider creation permissions are on the near-term roadmap.
Not yet. Slack notifications are read-only today: every message includes an Open request button that drops you straight into UserJot. Inline actions from Slack are on the roadmap, and we would rather ship them right than ship them fast.
Nothing changes for existing requests until something happens to them. Once installed, any new event on any request, whether a comment, a status change, or a fresh submission, starts posting to your chosen channel as a new thread.
Slack is part of UserJot's integrations. The Free plan does not include integrations; Starter includes one integration, and Professional includes unlimited integrations. Pricing is flat regardless of how many people are in your Slack workspace.
From UserJot Settings → Integrations → Slack, you can pause notifications, change the channel, or fully disconnect. From the Slack side, an admin can remove the UserJot app at any time. If Slack auth becomes invalid, UserJot surfaces a reconnect prompt in the dashboard and retries notification jobs automatically.
Start capturing
Customers tell you what to build every day. Most of it dies in channels nobody scrolls back through. UserJot for Slack catches it on the way past, drafts the request, and routes it to the board where it belongs.
That is what feedback that lives where work happens looks like.
Free forever workspace · Slack add-on on Starter and Professional · 60-second setup