I've configured and enabled the live chat feature for Jira Service Management. When testing on the portal, internal users can see and interact with the chat interface but external customers cannot. Is this a configuration or licensing issue?
Hello @Chris Gartman
Welcome to the Atlassian community.
What is your global JSM setting for Customer access?
Is the request type to which live cat is mapped restricted to be available only to internal users?
What is the access setting for your portal; Open or Restricted?
The real deal is this - that is not possible in JSM. The live chat is a JSM skill for Rovo. In JSM, Rovo is only available for those with Atlassian accounts. For this to work for external accounts, you have to use CSM. This was done on purpose to separate out the use cases and functionalities. Don’t worry though both should be included in your service collection licenses. I will find documentation proving this in the morning. Also note I am not sure if the CSM agent has the live chat feature yet. Last I heard it was a June 2026 roll out but not sure if that’s changed or has happened.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
recently it was released in March so that unpaid Atlassian accounts with customer role can access in JSM but as mentioned below CSM is for external accounts. https://community.atlassian.com/forums/JSM-News-Discussions-articles/It-s-a-Rovo-roundup-Agent-releases-that-make-self-service-use/ba-p/3204587
Here’s the JAC ticket link and the comment I’m getting this from: https://jira.atlassian.com/browse/ROVO-119
Appreciate your feedback on this topic, we understand the importance of this feature update. We’re actively building a solution for unlicensed Atlassian Account users of JSM.
• Today, Rovo agents can be used in JSM Portals by all help seekers with an Atlassian Account and a paid seat for a Standard, Premium or Enterprise edition of any Atlassian product. For now, the Rovo agent Portal widget requires a paid seat.
• We are building the ability for all JSM help seekers with Atlassian Accounts to access Rovo agents in service channels – even those that do not have a paid seat. This includes JSM Portals and, very soon, JSM Help Centers too (https://jira.atlassian.com/browse/ROVO-46). We'll share updates here as we progress.
• For external service use cases (e.g. customer support, B2B partner support), we recommend using Rovo CSM Agents in the CSM app (https://www.atlassian.com/software/customer-service-management). Built from the ground up for external users, the CSM app supports non-Atlassian Accounts users (including anonymous users), automated ticket handoff, and engagement via channels like the support site or as an embedded experience in your own websites and apps.
• We’re also working on a separate solution that will allow users to access the full capabilities of Rovo (including proactive knowledge discovery across connected data sources, and building and working with agents) without needing a full Atlassian license. (https://jira.atlassian.com/browse/ROVO-552#)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
As @Trudy P Claspill mentioned, can you go to Project settings > Channels > Chat, check that the chat channel is enabled and that it's mapped to request types that are accessible to external (non-org) users.
If the request type backing the chat is restricted to internal users or a specific customer organization, external folks won't see it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.