It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Chat for Jira Service Desk with direct chat-to-issue feature. An alternative to other chat solutions

Hi there!

Have you ever considered using chat agent to get closer to your customers on your website, landing pages for marketing campaigns or on your documentation?

All of you that were thinking about it might have tried different solutions.

Surprisingly, it looked like everything that MPAC offered, was just placing an IM widget on the issue page or the customer portal.

The chat conversations are processed on another platform without integration with JSD as issues. Nothing is stored in Jira.

We, as Spartez, were there as well - after months of testing, we finally decided to develop and offer our own solution.

We summarize our experience from the pain and launched Chat for Service Desk.

 

Why chat?

It looks like these days, customers prefer to use IM tools rather than email or ticket-based systems.

They want to talk to a real person in real time - clients don't want to go through hoops of setting up an account on a support system in order to contact the support. They want their problems to be solved in real-time by an actual human. 

When they are interested in buying your products or services, they don't want to send emails to a random address.

 

Part 1 - Testing existing solutions

There was no available solution that could integrate with Jira Service Desk, so we have tried some well-known solutions.

We have tried LiveChat first, since there is an app which integrates it with Confluence in the Marketplace.

But, as our clients are widely distributed in different countries and timezones, and our support team cannot be online 24/7

Therefore, notification feature for both our agents and clients is critical in our operation. Yet, LiveChat does not provide email-based notification. As a result, our clients do not know our replies if they have left the page already, and our agents do not receive any emails about incoming messages as well.

So we moved to Intercom instead.

It was better at first, but:

  • We had to constantly look at the browser tab and check it, we weren't notified about the incoming messages when there are many opened tabs

  • We didn't liked spamming emails and the poor email structure for notifications

  • Reports were not good enough for us

To be honest - all those issues were nothing, really.
After a few months of testing, we finally discovered what the real problems are.


Part 2 - Realize what the real problems are

Our support team had to work in two different platforms - they had to handle standard support tickets via Jira Service Desk and handle live conversations on another platform (Intercom) at the same time. 

And guess what...

Very often, our support team was talking with the one single client on both channels. At the end, we had to add the Intercom conversation history to the corresponding JSD tickets for tracking purpose. We are sure it is not the best use of anyone's time.

Since the support tickets queue is spilt into two, it was much harder to maintain and prioritize. Some of our clients were not satisfied enough because the agent handled their JSD ticket is not the same as the one who handled their Intercom conversation. It created chaos in our support.

 

Unfortunately, the summary reports from Jira/JSD are completely different from those in Intercom. Therefore, it was impossible to summarize the support tickets and works from two different platforms in a unified way.

What we planned to provide as a better communication channel to our customers turned into nightmare for both our support and customers.

 

Part 3 - if you can't find an existing solution, build your own one!

After we realized the real problems, we finally decided to develop Chat for Service Desk.

The same as some of our apps, it  was born as an internal use app at first. We used our resources to create a solution which could satisfy our needs. Generally, we are not the only one who suffered the same, our solution may help you/others as well.

The needs are as follows:

  • Easy to deploy
    • We want to have the chat widget everywhere possible (website, documentation, landing pages)
  • Jira Service Desk integration

    • New chat conversation → a JSD issue
    • New message in the conversation → a comment the JSD issue
    • Agent's comment → a message in the conversation
    • Both customers and agents see the updated conversations/issues with no delays
    • Possibility to apply Jira/JSD features such as automation or canned responses
  • No login required
    • The customer does not need to log in for starting a conversation.
    • They can chat anonymously. 
  • Chat history
    • Customers can provide their email for registering on JSD
    • They can log in to their account via the widget in order to see the chat history
  • Attachments & Emoji
    • Both agents and customers can upload attachments such as screenshots or files to the conversations/issues
    • Emoji supported
  • Agents' availability
    • Customers will be notified if there are any agents online
    • Agents can select their online/offline hours by their needs
    • If no agents are online, clients will be notified that their inquiries will be handled when agents are back 
  • Notification icon on JSD for agents
    • An icon on Jira board and JSD will be showing issues in queues.
    • The icon is updated in real-time so agents will not miss any incoming messages
    • An audio notification is supported as well

To sum up - when we were testing well-known solutions it becomes clear - there was no solution that could let the customer create an issue in JSD by just sending a message on the chat widget.

Now, Chat for Service Desk - Chats to Issues is finally launched - it becomes all better.

 chat3.png

 

 

See how it works on Atlassian Marketplace or watch a video here.

Check out how per agent pricing works.

Let us know how you think and any of your needs by dropping us a comment here. (smile)

9 comments

Lokesh Livspace Jul 01, 2018

Hi,

Is this addon compatible with Jira Service Desk (On Cloud)? I'm not able to find option to install this under Manage Add-ons. When I try to search in marketplace from within my Jira instance, it doesn't show up.

And yes, I'm admin for a trial Jira SD instance.

Hi @Lokesh Livspace! :)

Thanks for that question.

For now, Chat for Service Desk is available only on Jira Server. 

We're thinking about cloud version - we will start working on it after Atlassian Summit at Barcelona. 

Reapit Service Desk Oct 02, 2018

Agree, a good solution is missing for Cloud versions.  Does this offering allow you to configure when Chat is 'Live / Closed' et al ?

Janusz Gorycki Oct 02, 2018

Hi Richard,

Our Chat for Service Desk has a concept of "online/offline" agents. When all agents are offline, then the chat switches to "offline" mode automatically, meaning that from the point of view of the customer, the conversation becomes email-based and the customer is notified that they should expect a delayed response. Also, in "offline" mode, the customer is required to provide their email address (they cannot chat anonymously). You can read about this on our documentation page: https://confluence.spartez.com/display/CFSD/Agent+Online+Status

Best Regards
Janusz Gorycki, spartez.com

Harel Safra Jan 20, 2019

Hi,

Do you have a plan for JSD cloud support? We would be interested in that.

Harel 

Like Clay Blackiston likes this
Jacek Wizmur-Szymczak Jan 21, 2019 • edited

Hi @Harel Safra!

Thanks for your interest in Chat for Jira Service Desk.

Answering your question - We have just released DC version of the app and we’re thinking about developing cloud version as well.

For now, we have other priorities like f.e. knowledge base integration that is going to be delivered soon.

We will publish Chat roadmap to let you know what are the next steps for this application.

Stay tuned!

Like Clay Blackiston likes this
Marcin Owczarek I'm New Here Apr 11, 2019 • edited

Hi There,

JSD cloud support would be highly appreciated and required.

Thanks for consideration.

Abhi Gudidevuni I'm New Here Jun 07, 2019

Hi There,

The Jira Service Desk integration features state you can :

  • Start a New chat conversation → which would create a new JSD issue
  • New message in the existing conversation → would create a comment in the JSD issue

Just wondering if a "New" chat session could be initiated to an existing JSD issue? We would would like to give our customers visibility of their service requests (existing JSD issues) in our customer portal, in many cases the issue creation source is not chat.  We would like to give customers an option to initiate a chat session to an existing JSD's visible to them in the portal.  

Appreciate you time.

Piotr Stefaniak Jun 10, 2019

Hello @Abhi Gudidevuni ,

Currently our Chat for Jira Service Desk has no capability of initiating chat sessions for the existing (non-chat originated) JSD tickets. Though, your particular use case seems to me a meaningful one. We should add that to our feature backlog, but honestly I wouldn't expect that to be implemented soon (if at all).

Regards,
Piotr Stefaniak / spartez.com

Comment

Log in or Sign up to comment
Community showcase
Published in Marketplace Apps & Integrations

Webinar invitation: Generate custom Jira Cloud PDF reports and exports

Jira may be a staple part of your workday, but your colleagues, customers, business partners or an auditor might need information presented in a different format, that is easy to access and read. And...

63 views 0 1
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you