Usage and Insights
Admin → Usage shows answers, sandbox time, web searches and stored data per day, person and group, for adoption tracking, capacity planning and chargeback.
Insights
Section titled “Insights”Insights is an optional experiment, off by default, that shows where spending goes by what people were doing.
When on, each conversation is classified into a few segments (activity, client, tags and one neutral line). The text of conversations is never reproduced in Insights. Admins see the map for the organisation, and members see their own.
When to use it: to understand adoption and to prioritise training or connectors. When not to: if your works council or policy prohibits any classification of how people use a tool. Leave it off, nothing else depends on it.
Examples
Section titled “Examples”Prove adoption to the sponsor
Section titled “Prove adoption to the sponsor”Situation: The programme sponsor asks who uses Lucy and for what. Setup: Use Usage for active people and answers per day, and Insights (if you enabled it) for activity types. Result: A page you can screenshot, not a guess.
Find the cost outlier
Section titled “Find the cost outlier”Situation: The monthly figure is above plan. Setup: Check Usage by person and group, and whether sandbox time or web searches grew. Result: You see whether it is one team, one habit or a runaway agent, then adjust limits.
Plan training
Section titled “Plan training”Situation: You want to train the people who use Lucy least. Setup: Compare usage per group against headcount. Result: A short list of teams to invite to a workshop.