Recommendations from real sessions,built only when you say so.
Improvements is where Starko AI's recommendations wait for a decision. Each one comes from a visitor who got stuck in your product, carries every other visitor who hit the same thing, and stays a proposal until someone accepts it.
Improvements
What Starko AI found in your visitors' sessions, what you decided, and what it cost.
- Export button gives no feedback when the export failsBug · Smallup to 250Proposed
- Invite link hard to find from team settingsImprovement · Smallup to 200Proposed
- Plan limits not shown before the upgrade stepImprovement · Smallup to 200Proposed
- Saved report filter is lost after a page reloadBug · Smallup to 250Proposed
- Date range picker closes before a range is pickedImprovement · Smallup to 200Proposed
Improvements in short.
- Where it lives
- Improvements in the sidebar, with a Statistics page and a full history of decisions.
- Filed automatically
- Confusion or Dead end verdicts at 70% confidence or more, or 60% when the visitor described the problem.
- Duplicates
- Checked against open recommendations from the last 90 days. A match becomes a sighting.
- Size and cap
- Every recommendation is filed as Small: up to 200 credits for an improvement, 250 for a bug.
- Who decides
- Any member who can see the recommendation can accept or decline it.
- Before a run starts
- Starko checks the GitHub App, the repository and that no run is already live.
- Auto-dispatch
- Never. A recommendation reaches Starko AI only after a person accepts it.
- Weekly digest
- Mondays at 07:00 UTC, as one ticket tagged Session replay digest.
Every recommendation starts with a visitor who got stuck.
- Titles read
Recommendation: …orBug: …and name the page area and the problem, for example "Invite link hard to find from team settings". - The ticket says what the visitor was trying to do, what happened, where the UI stopped helping, the smallest change to test, the cited [mm:ss] moments and up to four frames from the replay.
- It lands in the project you chose for customer tickets, else your only project with a repository. With several projects and no choice, whoever accepts it picks the repository.
- A Hesitation, or a verdict under the bar, stays on the conversation. A person can still file it there with Create improvement ticket.
Recommendation: Invite link hard to find from team settings
Filed from a session replay: friction: Confusion (82%) · recording started on: thread · page: https://app.northwind.io/settings/team
What the visitor was trying to do
invite a colleague to the workspace before a trial ends
What happened
The visitor opened Team, scrolled the member list twice and clicked the page title, then asked in the chat where the invite link is.
Where the UI stopped helping
The invite link sits under a collapsed Advanced section with no hint on the member list.
Smallest change to test
Show an Invite button next to the member count at the top of the Team page.
Evidence (moments in the replay)
- [00:06] Scrolls the member list to the bottom and back
- [00:19] Clicks the page title "Team", nothing happens
- [00:27] Opens the chat and asks how to add a colleague
Development
Customer
Jonas Reiter
Fjord Analytics
Ten confused visitors make one recommendation, not ten tickets.
- A sighting is an internal comment from Starko AI, "Another visitor ran into this", with the verdict, what the visitor was trying to do and the cited moments.
- The visitor count on each recommendation is the original plus every sighting. Ask ⌘L for open recommendations and they come back most sightings first.
- Closed and archived tickets are not candidates, so a problem that comes back after a fix gets a fresh recommendation.
- If the matching step fails, the observation is filed as a new ticket rather than lost.
Evidence (moments in the replay)
- [00:06] Scrolls the member list to the bottom and back
- [00:19] Clicks the page title "Team", nothing happens
- [00:27] Opens the chat and asks how to add a colleague
Source
- Conversation: https://v2.starko.one/dashboard/threads/5d0c… · How do I add a colleague?
- Replay: open the conversation above and press Play on the recording
- Analysis id:
a83f2c10-…
Another visitor ran into this: friction: Confusion (76%)
Trying to: add a teammate to the account
Opened Team, searched the page for "invite", then left for Billing and came back.
- [00:12] Searches the page for "invite"
Conversation: https://v2.starko.one/dashboard/threads/91aa…
Another visitor ran into this: friction: Dead end (71%)
Trying to: send an invite before the trial ends
Expanded every section on Team except Advanced, then opened the chat.
Conversation: https://v2.starko.one/dashboard/threads/c27e…
Another visitor ran into this: friction: Confusion (79%)
Trying to: give a colleague access to reports
Development
Customer
Jonas Reiter
Fjord Analytics
One click to build it, one reason to drop it.
- Accept starts a Starko AI run straight away, with no confirmation step. Starko first checks that the GitHub App is connected, that the project (or the workspace default) has a repository, and that no run is already live, and says which one is missing if not.
- Decline asks why: Not a problem for us, Already planned or fixed elsewhere, Not worth the cost right now, Maybe later, or Other, plus an optional note. The ticket closes with the reason on record as a comment.
- If a run fails or is stopped, the recommendation goes back to Waiting for you so someone can try again.
- Accepted work follows the usual path: a cloud sandbox, evidence, a reviewer agent and a pull request you merge. The merge closes the ticket.
Export button gives no feedback when the export fails
Seven visitors clicked Export on the Reports page, got nothing back, and kept clicking. Six of them then opened the chat about it.
Fixing it means the button shows progress and a clear error, so people know to retry or use CSV.
- Proposed30 Oct
- →Accepted
- →Fix opened
- →Shipped
- Page
/reports- Change
- Show a spinner while exporting and an error with a retry when the request fails.
- Where
- The Export button in the Reports toolbar
- Visitors
- 7
Waiting, in progress, decided, and what it cost.
- Statistics shows Proposed, Accepted, Shipped and Declined over the last 30 days, Credits spent, and Visitors spared: the visitors behind fixes that shipped.
- A chart plots the decisions per day for the last 30 days.
- History lists every decided recommendation, newest first.
- Merged means the fix's pull request merged. Done means the ticket was closed some other way.
Improvement statistics
Proposed · 30 days
31
Accepted · 30 days
19
Shipped · 30 days
14
Declined · 30 days
6
Credits spent
1,920
Visitors spared
87
on shipped fixesDecisions, last 30 days
New recommendations come to you.
- A project bound to a Slack channel gets a notice for each new recommendation. Reply "fix it" in the thread and Starko proposes a run; "not now" parks it.
- Every Monday at 07:00 UTC, the week's analyses are grouped into themes in one ticket tagged Session replay digest: what visitors wanted, where the UI failed, the smallest change to test, and links to the conversations and tickets. Admins are notified.
- A week with fewer than two friction observations gets a digest with the counts only. Generate digest now, on the Session replay settings card, runs one on demand.
Recommendation: Invite link hard to find from team settings
4 visitors on /settings/team tried to invite a colleague, but the invite link sits under a collapsed Advanced section.
After the change, visitors get through here on their own and fewer questions reach your team.
FAQAbout Improvements.
Connect a channel and a repository. Turn the support queue into a build queue.
Feedback starts flowing in minutes. The first recommendation shows up as soon as a pattern repeats, and the first pull request as soon as you accept one.