Analytics

Analytics

Analytics answers the questions a workspace owner actually has after the first month: is anyone using this, is it working, and where is the time going.

Who can use it: Owner, Admin, Manager · Availability: All plans

What It Measures

The Performance tab charts activity over time split into successful and failed runs, a breakdown by task status, an activity heatmap by day and hour, per-user volume with last-active times, and a per-tool table with success rates. It is the aggregate view of the same work that Action Logs records call by call.

Owners and Admins also get a Learning Queue tab, where corrections to Quickly's behavior are reviewed.

Reading Adoption Honestly

Volume alone is a weak signal. A workspace can generate a great deal of activity through a handful of noisy automations while the work that would actually save time goes untouched. The useful comparison is between activity and outcomes, which is why the activity chart splits successes from failures rather than reporting one total.

Flat or falling usage where you expected the opposite is usually a discoverability problem rather than a quality one. People do not use playbooks and agents they do not know exist.

Diagnosing a Falling Success Rate

A success rate that drops without a change in what people are asking for almost always points at a connection rather than the agent. Expired OAuth tokens, a permission revoked in an external tool, or a provider rate limit all show up here as failures and in Action Logs as the specific error. Start from the aggregate, then filter the logs to the tool that moved.

How to review adoption

1. Open Analytics.
2. Compare activity across the selected time window.
3. Look for teams or workflows with unexpected drops.

How to compare tool usage

1. Review activity by connected system or tool.
2. Identify which integrations drive real work.
3. Clean up or retrain workflows that call tools without useful output.

How to inspect success and failure trends

1. Compare completed, failed, and pending task trends.
2. Open Action Logs for repeated failures.
3. Fix the workflow, integration, or approval pattern causing the trend.

Good to Know

• Analytics visibility is limited to roles that can manage or review operations. Learning Queue correction review is owner/admin-controlled.

Related

• Activity Logs for the call-by-call detail behind these numbers.
• Billing and Plans for how credit consumption is metered.
• Managing Integrations for fixing the connection problems this surface exposes.