Threads

The Threads view in the Admin UI helps Organization Admins review Compass conversations and understand how Compass is performing over time.

You can use Threads to:

• Review recent conversations across your organization
• Spot threads where Compass struggled
• Identify patterns in user feedback
• Find opportunities to improve data context, definitions, and documentation

Admin only: The Threads page is only accessible for Admins.

For details on what Compass stores and available retention options, see Security Overview.

What You Can See in Threads

Depending on the thread, you may see:

• The channel where the conversation happened
• The thread initiator
• A preview of the first message
• Thread activity and message count
• Votes and other feedback signals
• Thread health scores

Reviewing Threads

Threads is most useful when you look for patterns across conversations rather than focusing on one thread at a time.

For example, you can use it to:

• Review low-scoring threads to see where Compass needs more context
• Look for repeated confusion around the same business terms or datasets
• Check whether certain channels produce stronger or weaker outcomes
• Find examples of successful conversations to share with your team

Channel Privacy

Threads respects Slack channel privacy.

If you are not a member of a Slack channel, you will not see that thread's content in the Admin UI. After you join the channel, the thread content becomes visible to you.

This lets admins review conversation quality without bypassing normal Slack channel membership.

Thread Health Scores

Thread health scores help you quickly understand how well Compass handled a conversation.

Each scored thread has two ratings:

• Success: Did Compass correctly answer the user's question?
• Efficiency: Did Compass get to the answer efficiently?

Both scores use a 1-10 scale, where higher is better.

Success Score

High success scores usually mean Compass answered the question correctly and the user did not need to correct it.

Low success scores usually mean one or more of the following happened:

• The answer did not match what the user asked
• The answer was incomplete
• The user had to correct Compass
• The user was unhappy with the response

If you see low success scores repeatedly, Compass may be missing important business definitions, data documentation, or channel-specific context.

Efficiency Score

High efficiency scores usually mean Compass took a clear path to the result without unnecessary detours.

Low efficiency scores usually mean one or more of the following happened:

• Compass repeated similar tool calls
• Compass searched the wrong places before finding the answer
• Compass needed too many turns to get to a useful result
• Compass did not have enough context to identify the right tables or columns quickly

Low efficiency does not always mean the final answer was wrong. A thread can be successful but inefficient if Compass eventually gets the right result after too much exploration.

Reading Scores Together

Looking at both scores together can help you understand what went wrong:

• High success, high efficiency: Compass answered correctly and got there quickly
• High success, low efficiency: Compass eventually got the right answer, but took too many steps
• Low success, high efficiency: Compass moved quickly, but toward the wrong answer
• Low success, low efficiency: Compass struggled both to find the right path and to produce the right result

Need Help?

If you are seeing consistently low thread health scores, reach out to Compass support. Including a few example threads helps us diagnose whether the issue is data modeling, missing context, or product behavior.