Headless customer support and feedback platform for your agents.
Your agent is only as good as its feedback loop. Give it your live chat, feedback, roadmap, and product updates, so it can ship what customers ask for and let them know.
Claude Code · connected to userjot
OpenAI DotsEvery day, the teams behind Tally, OpenPanel, Drizzle, SuperWhisper, Scite, Throne, Nuelink, Ghostbase, and hundreds of others talk with their customers in UserJot.
Tally,
OpenPanel,
Drizzle,
SuperWhisper,
Scite,
Throne,
Nuelink,
Ghostbase,Six routines to start with.
Paste one into Claude Code, Codex, Grok Bot, or a cron job. Each one says what the agent leaves for you.
Contents
- Prompt
Check UserJot for conversations that need me. Draft a reply to each as a private note, and send billing questions to Sam.
- Calls
- listConversationslistConversationTimelinecreateConversationNoteupdateConversationAssignee
- Leaves for you
- Sending the replies.
- Prompt
Look through new UserJot conversations for bugs that hurt customers. If you find the cause, open a draft PR and leave the team a note on who’s affected.
- Calls
- listConversationslistConversationTimelinegetMembercreateConversationNote
- Leaves for you
- Merging the fix.
- Prompt
Go through today’s UserJot conversations. When someone asks for a feature, vote for it as them, or file it if it’s not on the board yet.
- Calls
- listConversationslistConversationTimelinelistRequestsaddRequestVotecreateRequest
- Leaves for you
- Merging duplicates.
- Prompt
Draft this week’s product update in UserJot from what we shipped. Mark the requests it finishes as completed on Sam’s behalf, so their voters hear about it.
- Calls
- listRequestsupdateRequestStatuscreateChangelog
- Leaves for you
- Publishing the post.
- Prompt
What did customers ask for most in UserJot this week? Include anything that came up a few times but isn’t on the board.
- Calls
- listRequestslistRequestVoteslistConversationslistConversationTimeline
- Leaves for you
- Deciding what to build.
- Prompt
The export fix is live. Reply to everyone in UserJot who reported it and resolve their conversations.
- Calls
- listConversationslistConversationTimelinecreateConversationReplyupdateConversationStatus
- Leaves for you
- Anything else they asked about.
“Ever since we added UserJot, the most common thing users mention in reviews is that we actually listen.”
Igor Amidzic, Founder, KualiaLet your agent earn the inbox.
Most teams start an agent on reports and drafts, and let it reply once they trust it. Each step is a line or two in its prompt.
It reports.
Each morning it reads what came in overnight and sends you a summary. Nothing in UserJot changes.
It drafts.
It leaves a draft reply as a private note. Your team sends the ones that are right.
It answers.
Once the drafts are good, let it reply to the questions your docs already cover.
Refunds stay with you.
Billing and upset customers go to a person, with a note on what happened.
Built for runs nobody watches.
Nothing here needs a browser or a person at the keyboard. These are the parts of the API a routine leans on when it runs alone.
- A token, not a sign-in
- Send a bearer token from Settings, API Tokens, over REST or MCP. There’s no session to expire halfway through a run.
- Only what changed
- List the conversations updated since the last run, or only the ones waiting on your team.
- Safe to retry
- Replies, notes, new requests, and changelog posts over REST take an Idempotency-Key, so a run that retries doesn’t post twice.
- Drafts by default
- Changelog posts from the API stay drafts unless the call asks to publish them, and private notes never reach the customer.
- Acts as the customer
- A vote or request filed with their external_id counts as theirs, and they get the email when it ships.
- Knows who’s asking
- Look up the customer and what your app synced about them, like their plan, before the agent writes anything.
Running agents for clients?
Agencies set up support and feedback for each client in a workspace of its own, then hand it over when the work ends.
- 1
A workspace per client
Each client gets their own board, widget, inbox, and plan. A token reaches one workspace, so one client’s agent never sees another’s customers.
- 2
A token per agent
Create tokens inside the client’s workspace, one for each agent you run there. Revoke them under Settings, API Tokens when the job is done.
- 3
Hand it over
Invite the client, then transfer ownership under Settings, Team. The workspace goes with them, with its board, inbox, and history.
“Instead of piecing together feedback from support, email, and social, we have one hub to collect feedback, gauge interest, and keep users updated.”
Corey Rabazinski, VP of Marketing, SciteSet up in a few minutes.
- 1
Create a token
In UserJot, open Settings, then API Tokens. Make one for each agent and name it after the routine, so you can revoke one without stopping the rest.
- 2
Give it to your agent
Agents that speak MCP connect here, with the token as a bearer header. Scripts call the REST API with the same token.
https://api.userjot.com/v1/mcp
- 3
Put a routine on a schedule
In Claude Code, run /schedule and paste a routine from above. Codex automations, Grok Bot routines, and a cron job running codex exec take the same prompt.
Want an agent you talk to as you work? See the MCP server, Grok Bot with UserJot, and OpenAI Dots with UserJot.
Everything else, A to Z.
A
- Assignees
B
- Bearer auth
C
- Changelog drafts
E
- External IDs
I
- Idempotency keys
- Inbox state
L
- llms.txt
M
O
P
- Private notes
R
- Rate limits
T
- Transfer ownership
U
- Updated since
Questions, answered.
Running UserJot without opening it. An agent or a script works your inbox, feedback board, roadmap, and changelog through the REST API or the MCP server, on a schedule or when something happens, like a release. Your customers still use your widget and board as usual.
Your customers are already talking.
Give them one place to ask, and give your team and your agents one place to answer.
- Free forever plan
- No credit card
- Set up in 30 seconds