User feedback
Users talk about your app in Jest chat. User Feedback collects the bug reports and suggestions from those conversations and lists them under your app, so you don't have to read chat to find them.
Jest reads public chat messages and picks out the ones that report a problem or ask for a change. Each one is attributed to a specific app and stored with the original message, so you can see the wording the user used.
The tool only reads. To answer a user yourself, open the app's chat room and post as your app.
Open the tool
- In the left sidebar navigation, select Apps, then select your app.
- Select the User Feedback tab.
Anyone on your team can read the feedback. Changing an item's status or the digest settings needs write access to the app.
What you see
Each row is one report:
| Column | What it shows |
|---|---|
| Type | Bug for something broken, Feedback for a suggestion or complaint. |
| Feedback | A one-line summary, the user's original message, and the message they replied to. |
| User | The user ID in your app, linking to User Lookup. Empty if they haven't used it yet. |
| Sent | When the user wrote the message, not when Jest extracted it. |
| Status | Where you've put the item. See Status. |
How attribution works
A report reaches your app only if one of these is true:
- The user wrote it in your app's own chat room, and the message is not clearly about a different app. In your room, "this app" means your app.
- The user has played your app recently, and the message makes clear it's yours, either by naming it or by replying to a message about it.
So you see reports from your own users, plus anything written in your own room, whether or not the author has played your app. Outside your room, someone relaying a problem in an app they don't play is not attributed to it, however specific they are. You never see feedback about another developer's app, and other developers never see feedback about yours.
Jest works out the app from what a message says and what it replies to, so a short reply like "same here, the boss softlocks" can be attributed through the message above it. When it can't tell which app a message is about, it drops the message rather than guess.
Attribution is still not perfect. A user can name your app while describing someone else's problem, and Jest can read a joke as a bug report. Mark those items False positive.
Filter the list
Three filters sit above the table:
- Status starts on Open, so you see what you haven't triaged. Switch to Any status to see everything.
- Timeframe starts on the last 30 days. All time removes the date limit.
- Search matches both the summary and the user's original message. Use it to find a level name, an error string, or a feature.
Filters combine, and the list is newest first.
Status
Status is a workflow tool for your team, and it's optional. No one is notified when you change it, nothing is chased, and a report left Open forever is fine. Use it if tracking what you've dealt with is useful to you, and ignore it if it isn't.
One status does have an effect: an item marked False positive is left out of the email digest from then on. Open and Fixed both appear in it.
| Status | Use it for |
|---|---|
| Open | Not looked at yet. Every report starts here. |
| False positive | Not a real report, or not about your app. |
| Fixed | Dealt with, or decided against. |
Select a new status from the dropdown in the row. It saves immediately.
Email digest
Jest can email your team a summary of new feedback instead of you checking the tab. The digest is set per app and is on daily to begin with.
To change it, use the Email digest card at the top of the User Feedback tab:
- Turn Email new feedback to the team off to stop the emails for this app.
- Choose Daily for a summary of the last 24 hours, or Weekly for the last 7 days.
Select Save changes to apply.
A few things worth knowing:
- Nothing is sent when there is no new feedback, so a quiet app won't email you.
- Every developer on the team gets it. To unsubscribe just yourself, without changing it for anyone else, go to Settings, then turn off User feedback digest.
- Only apps with a live chat room send a digest. An app that is unpublished, private, or has no active version has no chat room, so there is nothing to summarize.
- The digest lists the first 10 reports and tells you how many more there are. Open the tool to read the rest.
- Each row shows the type, the summary, the user's own message, their user ID, and when they sent it. Status is not in the email, only in the tool.
Read it with an AI assistant
If you have connected an AI assistant to Jest, it can read this feedback for you. Ask it something like "what are users reporting as broken in my app this week?" and it will pull the same list the tab shows, with the same status, date, and keyword filters.
An assistant can also set an item's status, but only when your MCP access level is Read & write. Read access alone lets it read the feedback and nothing else.