Conversation Insights for Rovo Agents - When will this be launched?

[Luke Mackie]

Rovo Agent Insights seem quite limited currently and it would be very useful to have an idea of the types of queries users are asking Rovo agents.

For example, I want our users to use a Rovo agent to ask questions about our knowledge base. I want to understand which questions are the most common, to identify any gaps in user understanding that we need to address from a training perspective.

I also want to understand for which questions Rovo is not able to provide an answer based on our Knowledge Base, as an indicator of where gaps in our knowledge base exist.

Are these sort of analytics on the roadmap and if so, when could one expect them to be live?

Seeing how many users use a Rovo is less useful if you can't see what they are using it for.

Has anyone found a useful workaround for these sorts of conversation insights in the meantime?

[Marc -Devoteam- · Accepted solution]

Hi @Luke Mackie 

This functionality is still in Beta.

See also this documentation article; track-how-often-a-rovo-agent-is-used you can find a feedback link at the bottom, to provide your feedback on this function

[Luke Mackie]

Thank you!

[Tomislav Tobijas · Accepted solution]

Hey @Luke Mackie ,

Yeah, these metrics would definitelly be nice to have. There's a feature request related to advanced analytics: ROVO-398: Advanced analytics for Rovo agents 
I'd suggest leaving a vote and potentially commenting on your requirement so it's taken into consideration when PMs review the suggestion 👀

Cheers,
Tobi

[Luke Mackie]

Thank you @Tomislav Tobijas - do we usually have any idea how long one would expect to wait before these sorts of requests make it into production?

[Tomislav Tobijas]

@Luke Mackie well... Usually it takes a while, but as we're talking about Rovo, and from what I've seen, a lot of effort is put into developing this app/tool so it might be rather sooner than later. 

Features relatively depend on how much engagement there is related to each one > meaning, if there are a lot of discussions and votes on a suggestion, it will probably be reviewed much quicker by the product team.

All-in-all, no one can say for sure when this will land in the roadmap 👀