Conversational Studio Sentiment Analytics Data & Access
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
3 weeks ago
The Sentiment Analytics dashboard (/now/conversational-studio/analytics/all) displays "No data available" for all sentiment metrics and "0" for Conversations Analyzed. This is caused by inactive data aggregation scheduled jobs, disabled Now Assist Sentiment skills, or missing analytics user roles.
I want to resolve data pipeline aggregation failures and align user permissions, So that reporting users can view populated sentiment analytics metrics in Conversational Studio.
Has anyone experienced this before or knows what additional configuration might be missing?
Thank you!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hi Shivani,
You are looking in the right places — with Conversations Analyzed at 0, the dashboard has nothing to aggregate yet, so work through it in this order:
1. Confirm there are conversations to analyze. Sentiment is scored on completed Virtual Agent conversations in the dashboard date range. If you are testing in a new instance, or the date range only covers a period with no completed conversations, the dashboard will correctly show 0 and No data available. Run a few complete test conversations first, then re-check with a wider date range.
2. Check the aggregation jobs. The sentiment dashboard is populated by scheduled aggregation jobs, not live from the conversation records. Make sure those jobs are active, that their last run succeeded, and that enough time has passed since the last run. A job that is inactive, or that last failed, will leave the dashboard empty even when conversations exist.
3. Check the sentiment skills. Sentiment analysis has to be enabled for Virtual Agent/Now Assist in your instance. If the sentiment skill is disabled, conversations complete without a sentiment score, and there is nothing for the aggregation jobs to roll up.
4. Check reporting access separately from admin access. Confirm the reporting users have the Conversational Studio analytics access needed to view the dashboard, and test with a user who has that access. If an admin sees data but a reporting user sees No data available, that points to a role/access gap rather than a pipeline failure.
A quick way to isolate it: as an admin, run test conversations, confirm the aggregation job runs successfully after them, and then check the dashboard again. If the admin view populates but the reporting view does not, fix access. If the admin view still shows 0, the gap is in the skills or the aggregation jobs, not in permissions.
Thanks,
Karimuddin
