Rovo Agents - Self-service beta vs. Virtual Service Agents

[Jared Grywacheski]

Just looking for some official clarification on a Rovo beta that is out right now -

 https://community.atlassian.com/forums/Rovo-articles/Join-the-beta-Rovo-agents-are-getting-powerful-new-self-service/ba-p/3112344?utm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_article&utm_content=topic

Will Rovo powered self service agents that are made available on customer portals replace Virtual Service Agents? 

What is the difference in functionality between these agents and the currently offered VSAs?

The line between Atlassian Intelligence and Rovo is very blurred which is concerning when one comes with credit usage and the other does not. 

[Josh]

@Jared Grywacheski as it stands right now, the Beta you're referring to leverages both Rovo and VSA functionality. I just got access to it a few days ago and am still working to understand it, but there are some really interesting concepts at play.

When this functionality goes GA, my assumption will be that VSAs (in their current incarnation) will be phased out and the overhauled Rovo Service Agents will take over.

No matter how hard we try, it's going to be difficult to avoid credit usage / consumption-based pricing with this sort of thing...

This is all conjecture on my end; I haven't seen any roadmaps yet.

[Jared Grywacheski]

@Josh Thanks for your response, this is also my line of thinking. As we both know, currently the Atlassian Intelligence powered VSA (or any Atlassian Intelligence features) do not use any sort of credit system. 

Our team is struggling with this end of Rovo as there does not seem to be much transparency on how the credit system will eventually work and what Rovo features will utilize credits. This has made it difficult for us to manage Rovo + the Atlassian Intelligence features we've been using since they became available over a year ago. There's no specific way to separate the two and turn off Rovo while keeping other AI features running. 

With the way Atlassian is choosing to push Rovo it feels like we are constantly one step behind while trying to stay one step ahead, if you know what I mean. But that's a whole other issue lol. 

[Josh]

@Jared Grywacheski yes, I get where you're coming from. It doesn't seem like there will be a significant distinction between Rovo and "Atlassian Intelligence" moving forward, so separation is unlikely.

Not sure if you heard about this (or if your org would exceed the "free" usage limit), but there are charges related to VSAs:

• Execute 1,000 Virtual Service Agent monthly assisted conversations for free. Above this limit, assisted conversations will start at $.30(USD)/assisted conversation/month with volume discounts applied.

This page has a decent breakdown of what you can expect in the next step ahead: Rovo usage quota | Rovo | Atlassian Support

The Rovo team is working to provide more usage monitoring data in the Admin center: https://admin.atlassian.com/o/YourOrgID/insights . Right now, it's not very helpful from a forecasting perspective but it sounds like that providing that kind of information will be a key prerequisite before we start getting billed for AI usage.