Atlassian Customer Service Management Implementation
For external support teams moving to Atlassian
Customer Service Management puts external support on the platform your product, engineering and service teams use. Senzo designs and implements it, and has delivered a live implementation for an Australian team.
When organisations bring us in
- Support is on Zendesk or Freshdesk while the business works in Jira (helpdesk migration)
- You run external support in JSM, and Atlassian suggests you "consider moving"
- Support hands work to engineering every week and loses context
- You want an AI agent answering customers (AI readiness)
Customer Service Management or Jira Service Management
The deciding question is who you serve, not the feature list.
- Internal service deliveryIT, HR and facilities start on Jira Service Management, which can also serve external customers.
- External supportCSM is purpose-built for it, with support, product and engineering on one record.
- Customer recordsJSM's details import only updates existing customers; CSM's CSV import can create them.
- ChannelsSome are still maturing; if yours is undocumented or in beta, staying put can be right.
What to decide before anything is configured
Each is harder to change once customers use the site.
| Decision | Why it matters | What we look at |
|---|---|---|
| Who your customers are | Profiles carry the context an agent sees | System of record and the batched CSV import |
| Which channels, in what order | Site and email, chat, WhatsApp, voice (beta), Amazon Connect | Volume, urgency and the plan each needs |
| What customers can read | Help articles need Confluence | Public and internal spaces, article owners |
| What the AI agent may answer | It "does not go live" until set up and published | Its scope, handoff to a person, reviews, billing |
| What goes to the product team | Work goes "directly to the teams building" products | What escalates and who closes the loop |
| How you'll know it works | A service dashboard and satisfaction surveys | Current measures and a pre-cutover baseline |
What an implementation covers
- 01
Discover
Your channels, customers, their systems of record and your reports.
- 02
Design and build
Support site, forms, workflows, SLAs, customer profiles and a Confluence knowledge base.
- 03
Connect and migrate
Email intake and integrations, then customers and chosen history, as scoped.
- 04
Go live
An AI agent where in scope, cutover by channel, training and hypercare.
Customer Service Management in practice
We implemented it for South Sydney Rabbitohs, whose customer experience team left Freshdesk and Freshcaller. Atlassian features the club.
- Live since February 2026
Within five months of the app's release.
- Delivered
Email intake, Confluence knowledge, ticket history and a website AI agent.
- Integrations
Membership, payments, marketing and phone systems.
“We're experiencing a 76% AI resolution rate, that's a game changer for our team.”
More of our service management work is in our case studies.
Frequently asked questions
What is Atlassian Customer Service Management?
Atlassian's app for external customer service, "a purpose-built, specialized solution". It joined Service Collection in October 2025.
How is it bought?
Within Atlassian Service Collection, "included at no additional cost" on Standard and Premium, not sold on its own. Your subscription is a licensing question.
Can we start from our existing Jira Service Management space?
Yes, on a paid Service Collection plan a new space can use its configuration. Customers, history and knowledge are separate steps.
Do our customers need licences?
Not an agent licence. Only agents need one; customers don't need a Service Collection licence.
Can we run Customer Service Management and Jira Service Management together?
Yes, both are Service Collection apps, and "Each Service Collection user license covers both JSM and CSM". We agree where the boundary sits.
How long does an implementation take?
Channels, customer-data integrations and history set the size, not agent count. We size it after discovery.
Is the AI agent part of the implementation?
It can be. Per-resolution billing starts 3 December 2026, so budget for it, and check your knowledge and ownership are ready first.
Sources (1)
- Product facts on this page are linked to Atlassian's own Customer Service Management pages and documentation where they are used.
What a first conversation should establish
Your customers, channels, current contract, and whether CSM, JSM or both fit. Bring your channel list and agent count.