Atlassian's Customer Service Management now accepts WhatsApp messages and phone calls as support channels, next to the support website, email, and chat widget. WhatsApp support is released and native voice is in open beta, and both need a Premium or Enterprise plan of Service Collection.
This guide covers what each channel does, how the AI agent handles intake, how a conversation reaches a person, and what to decide before you switch either channel on. Every product fact comes from Atlassian's documentation and cloud roadmap, checked on November 16, 2026. The sources are listed at the end.
WhatsApp. You connect a WhatsApp number to a customer experience. Messages to that number arrive as conversations, in the same place as conversations from the chat widget and from calls. Atlassian's cloud roadmap lists WhatsApp support as released in Q4 2026.
Voice. Customer Service Management has a built-in voice channel. You give it a phone number, choose who answers, and calls route to a space. Atlassian labels it open beta, and its roadmap lists native voice support as coming soon for Q1 2027. If you want to keep your existing telephony, the Amazon Connect integration is still available.
Some customers would sooner message you on WhatsApp than fill in a form, and a phone call is still how many urgent problems arrive. Before this, teams on Atlassian often covered those channels with Marketplace apps or a separate contact center tool, so part of the conversation lived outside the support record.
Now each conversation has a matching work item in your space, whichever channel it came from. You can organize those work items in queues and put SLAs on them, the same way you do for other requests. The person who picks up a handoff reads what was already said, so the customer does not have to repeat it.
Each channel has a support mode. There are three:
WhatsApp uses the chat settings of its customer experience, so changing those settings changes how WhatsApp messages are handled. Voice sets the support mode per phone number.
On a call in the combined mode, the customer hears a disclaimer and your welcome message, then the AI agent answers. If it can't help, or the customer asks for a person, the call transfers to an available team member and the customer waits. On a handoff, the agent who accepts can see the full transcript of what the AI agent and the customer said.
In the AI agent only mode there is no person to hand off to. If the AI agent can't resolve the request, it runs the handoff you configured for it, such as a closing message or a follow-up request.
Atlassian documents one assignment logic for chat, WhatsApp, and voice:
The documented logic is availability and capacity. Atlassian's pages do not describe routing by skill, language, or customer tier. You get that separation from structure instead: each customer experience routes to one space, and each WhatsApp number links to one customer experience. A separate number for a separate team is the way to send its conversations to its own space.
The organization admin connects the WhatsApp Business Account in Atlassian Administration, under the site's Customer Service Management phone numbers, and adds the numbers there. A space admin then opens the customer experience settings, selects Channels, then Messaging apps, and adds the number. You can connect one WhatsApp Business Account per Jira site, with more than one number.
Three limits to know. A call ends after four hours. Emergency calls are not supported. And during the open beta, agents take chats and calls from a desktop browser, not from mobile.
We are an Atlassian Platinum Solution Partner. We set up service management on Atlassian: the channels, the AI agent's intake and handoff, routing and availability, and the queues and SLAs behind them. We also clean up customer and identity data first, so the people who call and message you match the records you already hold.
See how we run service management work, or talk to an architect.