The Secret to a Multilingual Customer Service in Jira

Share on linkedin
Share on twitter
Share on reddit
Share on facebook
74% of consumers are more likely to repurchase if after-sales care is offered in their language. Start your journey!

Table of Contents

How can you make your 24/7 Jira Service Desk truly multilingual?

74% of consumers are more likely to repurchase if after-sales care is offered in their language

Do you offer your customers a multilingual customer service?

How many of your customers can’t communicate efficiently in English? How many other languages do your customers speak? How many of these languages are supported by your team in total? And how many of those languages are supported by native agents during the night shift?

If resourcing a 24/7 support center is legendarily difficult, solving the equation to cover for every language your customers communicate with can be mission impossible — particularly if the size of your support team is not in the thousands, but rather between 50 and 200 agents in total.

What do you do with the occasional Japanese customer writing at 4:00 am when the only Japanese level 1 agent starts the shift 12 hours later? How do you even figure out what the issue is about?

The answer: language coverage in non-peak times with automated translations for Jira Service Management

The solution to multilingual support requirements is a hybrid approach: hire as much multilingual talent as you can afford, and empower them with automated translations

In 2020, the quality of automated translations is impressive – but it’s still not 100% reliable. The big challenge is to properly recognize context and ambiguity.

That’s why a hybrid approach to translations is the best way to empower your multilingual support center. Language Translations for Jira Service Management, available for both Cloud and Server deployments, will send you a long way in the automation of your multilingual communication.

While other translation apps in the Atlassian Marketplace translate JSD’s interface, resolution’s product is the only one that translates messages between customers and agents.

In this situation, the Japanese customer’s ticket we mentioned above can be translated immediately. As a result, any available agent will already see a translation and understand the customer’s problem.

  • If it’s a standard problem, he will be able to send a templated answer.
  • If the ticket must be elevated, it’s possible to pull in people from different levels to start working on the issue. And they don’t even need to be native!

This will have a direct impact on the size of your teams during night shifts and weekends. Since it’s possible to collaborate across languages, you will now have a single pool of talent that can work together based on their skillset.

Multilingual customer service diagram

Automated translations for can cut down in less than half the number of agents you need in non-peak times.

But there’s many other possible benefits from tearing down the language barriers and being able to manage your workforce as if the language factor didn’t exist.

Keep reading: 5 scenarios for powering a multilingual Jira Service Management with automated translations

How to set up multilingual translations in Jira Service Management

Step 1: Enable translations in the corresponding project

Once you install the application, the Get Started button will directly prompt you to select in which Jira Service Management project you want to enable the translation. Of course, you can enable translations in more than one project.

Getting started screen with Language Translations

Step 2: Define language settings

What’s your company’s business language? In which other languages can all or almost all of your agents communicate?

In the settings screen you can select:

  • Which will be the target language into which customer messages will be translated
  • Which common languages don’t need to be translated because they don’t pose a challenge for you

Additionally, you can decide whether you will translate communications from the customer, agent responses, or both (the default is the latter).

Customization options to adjust your agent baseline languages

Step 3: Start communicating!

Depending on what you have defined above:

  • Your customer tickets will now automatically be translated and they will be easy to recognize and sort in your agents’ main language.
  • Additionally, your support agents can write messages in the language they master that will be automatically translated to customers
A Jira issue with the summary in two languages: the original Spanish plus the English translation
An example of translated issue summary


Running a global support center that communicates with customers from any time zone is extremely complex per se. Language Translation for Jira Service Management will help you focus on delivering a great support experience without hiring talent from every possible linguistic background.

No matter where the customer comes from. No matter what they speak.

By simply following the steps above you can make sure that your customers will be understood.

You can try the app for free or browse the documentation for more information on advanced use cases.

Share on linkedin
Share on twitter
Share on reddit
Share on facebook
Get The Latest Updates
Subscribe To Our Newsletter
No spam, notifications only about new products, updates.
Read our recent posts
Atlassian Data Center SSO: The Top 10 Missing Features

When moving to Data Center, you may evaluate whether the native SAML SSO is a good option. Check whether you...

Read More
Blog_Archives_Header_Radford Software
Radford Software supports the fresh produce industry globally in their customers’ own language

4 English-speaking agents communicate daily with Korea, Japan, Italy and France.

Read More
SURFnet’s seamless Crowd migration to SAML SSO

When SURFnet's Crowd installation became obsolete, they decided to go with the industry leader in Atlassian SSO.

Read More