Skip to main content
Use cases answers the product question behind the traffic: what are people actually trying to do? Armature’s models read every session, capture the user’s intent, and group semantically similar intents into named use cases.

​
The ranking

Each use case shows: High volume + low pass rate is your fix list. High volume + high pass rate is your marketing page.

​
Unmet demand

Use cases are discovered from what users ask for, not from what your tools support — so demand you don’t serve yet still shows up, badged UNMET (think “Bulk refunds — not supported yet”). This is roadmap signal you can’t get from UI analytics.

​
Drilling in

Click a use case to see its sessions and stats; jump straight into session replay to watch real conversations from that use case. The Sessions page arrives pre-filtered.

​
How grouping works

  • Every session’s intent is embedded and matched against existing use cases; close matches join, the rest wait in an Others bucket.
  • When enough similar intents accumulate, they’re promoted into a new named use case automatically — no manual taxonomy to maintain.
  • On a brand-new workspace, the Overview panel is labeled provisional while the first clusters form; expect named use cases to stabilize as volume comes in.