Skip to main content
New Idea

Native Analytics and Lifecycle Management for Scenario Executions

Related products:Freshservice
  • March 26, 2026
  • 0 replies
  • 2 views

Forum|alt.badge.img+2

The Problem

Currently, Scenarios are a "black box" regarding individual agent adoption. As an Admin, I cannot easily see:

  • The Training Gap: Which agents are manually performing 5+ steps that a single Scenario could handle in one click?

  • The Permission Gap: Are agents not using Scenarios because they lack the "Execute Scenario" permission in their custom role?

  • The Adoption Gap: Which teams/groups have successfully adopted automation vs. those still using legacy manual workflows?

The Solution (The Request)

We are requesting an "Agent Usage" layer within the Scenarios and Analytics modules:

  1. "Usage by Agent" Reporting: A native report in Analytics that shows a breakdown of Scenario executions per agent. This allows Admins to identify "Power Users" and those who may need additional enablement.

  2. Permission Visibility in Admin View: Within the Scenario list, a "Visibility" or "Availability" column that shows which Agent Roles or Groups currently have the rights to see/execute that specific Scenario.

  3. "Attempted but Denied" Logs: An audit log entry for when an agent tries to use a feature they don't have permissions for, helping Admins proactively fix role-access issues.

  4. In-Context Training Prompts: (Optional Suggestion) If an agent manually performs a sequence of actions that matches a saved Scenario, a subtle "Did you know?" prompt could suggest the Scenario to them.

Business Value

  • Targeted Training: Instead of broad team training, Admins can provide 1-on-1 coaching to agents with low automation usage.

  • Security & Compliance: Easily audit who has the power to trigger complex "Bulk Action" Scenarios.

  • Maximized ROI: Ensures the time spent by Admins building these automations actually translates into time saved by the entire service desk.

 

Or at the very least could we have an API for this information?