Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,457,736
Community Members
 
Community Events
176
Community Groups

How to Manage Customer Support Requests in the Telecom Sector

No one can deny that customer support can make or break a business. So ensuring you're able to open channels with your customers to promote communication, is a very great tactic for the business in the long run. Unfortunately, doing so isn't always an easy thing. It can lead to inefficient customer support and higher expenses to try to manage things with more employees.

Customer support requests.png

Let's take this example. A telecom company, with several support channels on social media, wanted to increase its productivity without hiring a huge team of agents per channel, so it could save on costs.

Disclaimer, I am part of Infosysta, the team that created two of the apps mentioned in this post.

The Challenge

The telecom company was focused on ensuring its customers can reach it no matter what platform they used. As social media is the most common way for people to contact their favorite brands and businesses, the company created an account on each platform. However, managing each platform separately caused a lot of problems with the workflow. This has led to a lot of dissatisfaction from customers, as response to their messages took longer than they would have liked. In turn, this gave the company a bad reputation and for it to get a lot of bad reviews. With nothing else to do, it was to bring on more temporary employees to better handle the workflow on each channel. This meant going overboard with the budget and expenses. 

The Solution

The company found a new way to manage the flow of messages coming in through the various channels it opened to the public. This solution was to integrate those apps with Jira Service Management. As the optimum ITSM tool available, this integration allowed for better service management and a much more comprehensive and easily manageable service desk. Since the company found its customers to be most active on both Twitter and WhatsApp, it found connector apps that helped promote this integration.

Whatsapp messages.png

 

Social Media to Jira Integration

The challenge was overcome with the help of two of Infosysta's social media to Jira integration apps. The first was Twitter Connector for Jira. An app that helps convert Tweets and direct messages into Jira tickets. The second was WhatsApp Connector for Jira. An app that helps convert all messages into Jira tickets.

Jira ticket.png

This is what happened when they implemented the system on WhatsApp:

  1. A customer wants to inquire about internet services, so they used WhatsApp to send a message to the company.
  2. This message was converted into a Jira ticket and assigned to an agent.
  3. The agent opened the customer's question and responded, offering all the necessary details from different internet bundles to prices.
  4. The response was converted back into a WhatsApp message.
  5. The customer received the response and opened to find all the information they'd asked for.
  6. If the customer didn't want to proceed with more questions, they sent a thank you and the agent marked the ticket as resolved.
  7. If the customer wanted to subscribe to a service, the agent redirected them to the sales team.

 Once the interaction with the customer is done, the Jira ticket is marked as resolved.

The Outcome

Thanks to the integration with Jira apps, all the social media messages were converted into Jira tickets instead of appearing as separate messages.

Jira tickets.png

This helped the company in various ways.

  • There was a better handle on the flow of messages coming in
  • All the messages were going to the same place, so the employees weren't overworked trying to catch up
  • It didn't need to keep on hiring dedicated agents for each platform, saving on costs
  • Agent productivity rose to high levels

0 comments

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events