Docs
How sorting works
Instead of an unread firehose, every conversation is routed into one of five tracks during sync, so the queue you open is already triaged.
The five tracks
Questions to answer
A developer question that needs a clear, cited answer.
Next step Draft from your docs, check the citation, send it.
Friction reported
A bug, a rough edge, a confusing page, a slow path.
Next step Acknowledge in public, then move the detail to your issue tracker.
Buying signals
Evaluation, comparison, or someone describing a need you serve.
Next step Hand to the person who owns that account and let them say hello.
Praise
Case studies, launch reactions, tutorials, sponsorships, and recommendations.
Next step Never drafted. Thank the author, quote them, or forward it to sales.
Muted
Anything that is not a conversation: round-ups, directories, status pages, job posts, off topic, or the other company with your name.
Next step Leave it. Every muted post shows its reason and unmutes into any track in one tap.
The six mute reasons
Every muted post carries one reason, shown as a chip on the card.
- Wrong entity: another company or project that shares your name.
- Directory: a listing or company profile page.
- Round-up: a list post with a passing mention.
- Status page: automated uptime or incident output.
- Job post: hiring and recruiting.
- Off topic: mentions the words, not your product.
Nothing is deleted. Unmuting records who did it and which track it belonged in, and that correction is fed back into the eval set so the same mistake stops repeating.
When sorting happens
Sorting runs as part of sync, in batches, until nothing is left unsorted. You should never see a pile of untriaged posts. If something slips through, for example a sync that was interrupted, EarShots sorts it quietly in the background and shows a short "Sorting new posts" line while it works.
Seeing why a post landed where it did
Open any post and expand the reasoning. Ears shows what it retrieved, what it considered, and the call it made. If the call is wrong, change the track yourself. The post moves and your correction stands.
Usage and blockers
Beyond the track, each post is tagged with how the person is using your product (adopting, integrating, extending, operating, migrating, exploring) and what is blocking them (bug, missing feature, docs gap, performance, developer experience, or nothing). Those tags are what turn a feed into a pattern you can take to your product team.