# Atlassian opened a closed beta for Customer Service Management connected through Teamwork Graph Atlassian introduced Customer Service Management on April 9, 2025 as a closed beta for external support that linked service, product, development and operations context. Canonical: https://rangoon.ai/insights/archive-atlassian-customer-service-management-april-2025/ Author: Rangoon Editorial (https://rangoon.ai/insights/editorial/) Published: 2026-10-24 Updated: 2026-10-24 Event date: 2025-04-09 Tags: [Atlassian](https://rangoon.ai/insights/tags/atlassian/), [customer service](https://rangoon.ai/insights/tags/customer-service/), [AI agents](https://rangoon.ai/insights/tags/ai-agents/), [workflow automation](https://rangoon.ai/insights/tags/workflow-automation/) Source note: Historical reporting: Atlassian’s April 9, 2025 announcement establishes an invitation to a closed beta. Its current product guide is later implementation context only, covering handoffs, voice integration, metrics and evaluations. The guide does not change the original beta status or prove an organization’s access, graph contents, billing or outcome. Image: An issue moves from support through shared context to a specialist team. Original Rangoon explanatory diagram: Source boundary: dated primary release reporting; original editorial analysis. No vendor interface, photograph, measurement result, or endorsement implied. ## Key takeaways - The April event was a closed-beta invitation, not a general-availability announcement. - Atlassian’s launch centered on Teamwork Graph connecting Atlassian and third-party data for service, product, development and operations work. - Later guidance describes a $1 successfully resolved-inquiry billing model and says a human handoff is not billed as an AI-agent resolution. ## The April announcement invited customers into a closed beta [source 1](https://www.atlassian.com/blog/announcements/customer-service-management) Atlassian introduced Customer Service Management on April 9, 2025 and ended the announcement with an invitation to join a closed beta program. It positioned the app for software-centric organizations whose customer-support work needed to reach product management, development and IT operations teams. The release described AI as a way to assist self-service and repetitive work while criticizing disconnected workflows between those groups. Its release state is consequential: a closed beta is an opportunity to evaluate a product, not evidence of broad availability, finished integrations or a completed support transformation. The announcement records an intended product direction and an enrollment condition on that date; it does not establish that any particular service desk was accepted into the program. ## Teamwork Graph was the stated connection between support and operating teams [source 1](https://www.atlassian.com/blog/announcements/customer-service-management) The launch called Teamwork Graph an intelligence layer that connects data across Atlassian and third-party apps. Atlassian said the Customer Service Management app could use that context to surface information for support teams, while product managers received customer feedback, developers received technical issue detail, and operations teams saw signals that could affect reliability. The announcement also described an agent that could draw on connected data, suggest a next step, find expert collaborators, escalate to another team, trigger an action in a product or third-party tool, and generate support content. These are separate stated functions in the source. The presence of a graph does not establish that linked records describe one incident correctly or that every team may see every connected field. ## Later guidance describes a handoff record and an Amazon Connect voice path [source 1](https://www.atlassian.com/blog/announcements/customer-service-management) [source 2](https://www.atlassian.com/software/customer-service-management/product-guide) The current product guide gives later detail about how Atlassian presents an unresolved request. It says an AI agent can gather context and hand the work to a human, and that the human should receive the necessary information to continue the request. The guide also describes an Amazon Connect voice integration that can create work items with call transcripts for follow-up. These details explain an implementation direction not fully specified by the April beta announcement: external support may enter through voice, be represented as a work item, then reach another team in the Atlassian platform. The guide is current documentation, not evidence that those capabilities were part of the April closed beta, enabled for an organization, or used successfully in a particular support case. ## The current guide separates resolved conversations from evaluations [source 2](https://www.atlassian.com/software/customer-service-management/product-guide) Atlassian’s guide identifies conversation count, AI containment and resolution rate as metrics, and says they inform AI-agent resolution billing. It describes a $1 charge for a successfully resolved customer inquiry and states that a handoff to a human is not billed as an AI-agent resolution. The same guide describes evaluations against a golden dataset and comparing answers across agent versions after changes to knowledge or guidance. Together those details distinguish live resolution accounting from a test workflow: evaluation runs are not the same as customer conversations, and a human handoff does not meet the guide’s stated billing condition. This later product context is useful for interpreting the app’s operational vocabulary, but it cannot rewrite the dated April announcement into general availability. ## Sources 1. [Atlassian: Customer Service Management app announcement](https://www.atlassian.com/blog/announcements/customer-service-management) 2. [Atlassian: Customer Service Management product guide](https://www.atlassian.com/software/customer-service-management/product-guide) ## Related reading - [Freshworks paired Freddy Agent Studio with email resolution and connected-service skills](https://rangoon.ai/insights/archive-freshworks-freddy-agentic-platform-june-2025/) - [Zendesk’s 2025 Resolution Platform joined service agents, knowledge, actions and QA](https://rangoon.ai/insights/archive-zendesk-resolution-platform-march-2025/) - [UiPath launched an agentic-automation platform spanning agents, robots and people](https://rangoon.ai/insights/archive-uipath-agentic-automation-platform-april-2025/) ## More information - [Documentation index](https://rangoon.ai/llms.txt) - [AI access and policies](https://rangoon.ai/ai/) - [Source repository](https://github.com/hypler-dev/rangoon)