JSM, CSM, and CRM: Building a Complete Customer Context in Jira

[#1]

For years, many Atlassian customers have used Jira Service Management (JSM) for both internal service management and external customer support. But Atlassian is now drawing a much clearer line between the two use cases.

Atlassian positions Jira Service Management (JSM) primarily around IT, operations, and employee service management: managing service requests, incidents, problems, changes, knowledge, assets, and the operational processes that keep services running.

While Customer Service Management (CSM) has been introduced as Atlassian's purpose-built solution for external customer support. It is designed for teams helping customers after the sale, with capabilities such as customer and organization profiles, customer history, omnichannel support, tailored customer experiences, AI agents, and connections to product, development, and operations teams.

And Atlassian explicitly recommends that teams currently using JSM for external support consider moving to Customer Service Management to take advantage of its more advanced, customer-support-specific capabilities.

Internal vs External Support: Are They That Different? 

Let’s see in more detail. Internal and operational support is built around services, incidents, assets, access, and employee workflows, with the primary goal of keeping the organization running smoothly.

External customer support has a different focus: people, companies, relationships, and the overall customer experience.  Support teams need to understand not only the issue being reported, but also who the customer is, which organization they belong to, and the broader context of that relationship.

These differences naturally lead to different workflows, data, and priorities. That’s why it makes sense to use purpose-built tools for each: one -  optimized for managing operations, and another -  for understanding and serving customers.

In other words, the distinction is becoming clearer: JSM helps teams manage services. CSM helps teams serve customers. And that makes knowing who the customer is increasingly important.

Beyond the Request: Bringing the Full Customer Relationship Into Jira

Consider a familiar support request: “We’re having this problem again. Can you help?”

To resolve the technical issue, an agent needs information about the problem. But to provide great customer service, they need information about the customer too.

• Who is contacting us?
• Which company do they work for?
• Is this a new customer or an existing one?
• Which Jira projects, issues, or other activities are connected to this relationship?

CSM already provides answers to some of these questions by giving support teams customer and organization context. For many service interactions, that’s enough. But some requests require a broader view of the customer relationship: 

• What is the person’s role, and who else is involved in the relationship?
• Is the company a prospect, an active customer, or a former customer?
• Which products, services, or licenses do they use or currently evaluate?
• Is there an active Deal, renewal, expansion, or other commercial opportunity?
• What is the Deal’s stage and value?
• What has been discussed in previous emails, meetings, and notes?
• What commitments were made during sales, onboarding, or earlier conversations?
• Who owns the relationship internally?
• Are there related delivery tasks, bugs, or other Jira work?
• Should sales, account management, customer success, or another team be involved?

This is where CRM context becomes valuable. By connecting customer service with CRM data, customer service & support agents can go beyond identifying who the person is and which company they represent to understand the wider commercial relationship and make better-informed decisions about how (and who) should respond.

That's exactly where Mria CRM comes in.

Mria CRM Now Supports Atlassian Customer Service Management (CSM) and Jira Service Management (JSM)

Mria CRM already helps teams connect customer information with Jira Service Management. For example, teams can link JSM tickets to CRM records, identify or suggest CRM records based on the requester, and create CRM records from service interactions.

Now Mria CRM supports Customer Service Management as well. That means teams adopting Atlassian's purpose-built CSM experience don't have to leave their CRM context behind. Instead, the customer service interaction can be connected to the broader customer relationship stored in Mria CRM.


                              JSM/CSM ticket enriched with Mria CRM data

How Mria CRM and Atlassian Customer Service Management Work Together

A requester isn't necessarily just an email address. They're a person at a company with a history, relationship, and context that can influence how a support team should respond.

For example, knowing the customer behind a request can help an agent understand whether they're dealing with an existing account, connect the person with the correct company, see relevant customer information, and understand how the service interaction fits into the wider relationship.

This is especially important as Atlassian expands from traditional service management into dedicated customer service. Atlassian itself describes customer context as critical to understanding the needs and concerns of individual customers.

But customer context doesn't begin when someone submits a support request.

The relationship may have started much earlier — as a lead, a deal, a contact, or a company in your CRM. Connecting Mria CRM and CSM helps preserve that context. 

Connecting Mria CRM with Customer Service Management preserves this history throughout the service workflow.

When an agent opens a CSM request, the Mria CRM panel uses the requester’s email address and company domain to search for matching Contacts and Companies. Once the Contact has been identified, Mria CRM checks for related Leads and Deals and suggests relevant records to link to the request.

The agent can then:

• accept or ignore the suggested records;
• manually search for and link an existing Contact, Company, Lead, or Deal;
• create a new Contact or Lead when no relevant record exists;
• review the linked customer and commercial information without leaving Jira;
• open the full CRM record when additional context is required.
  
                              JSM/CSM ticket: Mria CRM Deal Suggestion

The linked CRM records can help the agent understand whether the requester is a prospect or an existing customer, whether there is an active Deal, and whether sales, account management, customer success, or another team should be involved.

The connection is also visible from the CRM side. Sales and account teams working with a Contact, Company, Lead, or Deal can see the related CSM requests and their current statuses.

                                 Mria CRM Deal Full View: Linked JSM/CSM Records

Thus, a salesperson working in Mria CRM on the deal can see all related CSM requests and their status, which gives a quick overview of all the interactions between the customer and the business. 

See how this two-way connection works in practice:

Customer service teams gain access to the CRM relationship behind the request, while sales and account teams gain visibility into the customer’s service activity. Both sides work with a shared customer history in Jira.

Mria CRM + CSM: One View of the Customer Relationship

The interesting part of Atlassian's CSM is that customer service is becoming more deeply connected with the rest of the work happening across Atlassian.

Support can connect with engineering. Customer feedback can reach the product. Operational incidents can be understood in terms of their customer impact. Atlassian positions CSM around precisely this idea of bringing support, product, development, and operations together with shared context.

Being Atlassian-native CRM, our Mria CRM adds another important piece to that picture: the customer relationship itself. Now, with Mria CRM supporting both Jira Service Management and Customer Service Management, teams can keep customer information connected as their Atlassian service workflows evolve.

Because whether you're handling an internal service process in JSM or an external customer conversation in CSM, context makes a difference. And when the person asking for help is a customer, one of the most important pieces of context is simple: Who are we now helping?

Install Mria CRM from the Atlassian Marketplace and start a 30-day trial. Connect Customer Service Management and Jira Service Management requests with Contacts, Companies, Leads, and Deals to give service, sales, and account teams a shared view of every customer relationship.

Install Mria CRM and Start Your Trial