Friction Candidates shows you where people are running into trouble in your product. Chameleon automatically detects these problems from real sessions, so there are no custom events to set up and no engineering work. Each problem is written up in plain words, with the sessions behind it, and from there you can ask Copilot to explore it, file it in Linear, or suggest an in-app fix.
ℹ️ Friction Candidates is a report on the Reports tab, on Home. This is rolling out over the next few weeks.
Availability & usage
🔐 Requires Compass. New problems are only found while Session Summaries is on.
🔐 Explore Evidence, Create Linear Issue, and Create In-App also need AI to be enabled on your account
⚙️ Go to Home → Reports. Add it with the + icon ("Add reports")
What's in the Friction Candidates report?
Each row is one problem, ranked by how many people hit it, most first. A row shows:
The problem's name, and on a wide report a one-line summary of what's going wrong
People affected, for example 41 (30%): how many people hit the problem, and what share of the people active in your account that is
Fixed, once the problem has been resolved. Fixed problems stay on the list so you can see what's been dealt with
A link to its Linear issue, if one has been filed
The counts cover the 14 days up to when that problem was last updated. There's no date range to change, so the list shows what's happening recently, not all time.
How do I filter the report?
Use the Feature picker at the top of the report to see the problems for one Feature. Choose All Features to see everything again. The list scrolls inside the report.
What do the numbers mean?
Number | What it means |
People affected | Distinct people who hit this problem in the 14 days up to its last update. A person only counts once, however many times they hit it |
The percentage | People affected as a share of the people active in your account over the same 14 days. It's measured when that problem was last updated, so two problems with the same number of people can show different percentages |
ℹ️ The percentage is a share of everyone active in your account, not of that Feature's users, and it isn't a share of your Monthly Tracked Users.
When you open a problem, Affected sessions can show a higher number than the row. The row counts only the 14-day window, while the full list can include sessions from before that window and sessions that came in after the problem was last updated.
How do I dig into a problem?
Click anywhere on a row to open the problem. The panel shows:
Its status at the top: Confirmed, Issue filed, In progress, Fixed or Back after fix
The Feature it's about. Click the Feature's name to open it
Issue description: what's going wrong, in plain words
The actions (below)
Affected sessions: the real sessions where someone hit the problem
Each problem has its own web address, so you can copy the link and share it with your team.
Ask Copilot to act on it
Button | What it does |
Explore Evidence | Opens Copilot, already briefed on this problem, to explain what's causing it and how to reduce it |
Create Linear Issue | Opens Copilot to draft a Linear issue for the problem. Nothing is filed until you've reviewed the draft and confirmed. Learn more about filing issues in Linear from Copilot |
Create In-App | Opens Copilot to suggest one in-app Experience that helps people past the problem |
If Linear isn't connected yet, you'll see "Connect Linear" instead of "Create Linear Issue". Connecting it requires permission to manage integrations. Once an issue has been filed, the button becomes View in Linear.
Without AI enabled, the panel shows only View in Linear, and only if an issue has already been filed.
Read the sessions behind it
Sessions are listed newest first, 10 at a time. Click Show more to load more. When the problem has been measured, they're split into:
Recent affected sessions: the 14 days the row counts, so these are the people in its number
Older affected sessions: from before that window
Since this report was last updated: sessions that came in after the last update, which the row doesn't count yet
Each session shows:
The person. Click their name to open their profile
The date and how long the session was
How the session ended for the Feature: Completed, Partly done, Abandoned or Exploring
How this problem moment ended: Gave up, Unclear or Finished
A quote from the session showing what happened
Older than 3 weeks, on older sessions, so you can tell when evidence may be out of date
ℹ️ You can also reach a problem from a Feature: open the Feature and go to its Friction tab.
What if the report is empty?
A new account, or one where Chameleon hasn't found any friction yet, shows No friction detected yet. Problems only appear once your account has at least 100 active people and a week of data, and a problem affects at least 5% of your active people or at least 10 people. Smaller accounts may see none.
👉 If it stays empty for longer than you'd expect, check that Session Summaries is on in Account → AI & Credits → AI Controls, that your credit balance is above zero, and that Session Summaries hasn't used up its monthly budget (if you've set one). Any of the three stops new sessions from being summarized.