nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is JIRA (Service Desk) suitable for end customer support?

wishbase

We want to use JIRA Service Desk for our end customer support, where we, on one hand, may get kind of pre-sales inquiries via E-Mail; and support inquiries from existing users of our platform.

However, JIRA users are a "rare good" and I don't think it's meant to have a JIRA user for every such (end) customer.

How can these cases be handled? I already found https://confluence.atlassian.com/display/AOD/Creating+Issues+and+Comments+from+Email, especially the section "To allow JIRA to handle email messages sent from people without a JIRA user account:"at the very bottom; however in that case I lose every information about the initial sender. No sender name, no E-Mail-Address available.

So: is JIRA Service Desk generally meant for such a scenario?

Thanks and best,

Adrian

Accepted answers

All comments

Timothy

is JIRA Service Desk generally meant for such a scenario?

Until Atlassian changes the licensing model, no. At the moment, Service Desk is meant for "internal support" as every user needs to have an account in JIRA.

Unless money is no constraint to you..

unknown

As Timothy says, Service Desk is meant for the internal case, unless you have no monetary contraints

What you need is an external Mali Handler for JIRA OnDemand, that supports the concept of a remote email only user. JEMH is one of those (for Download), there is an OnDemand version of this being written right now, we're dogfooding it on our support line at the moment, availability is likely a beta trial in June/July, watch JEMH-2370 for updates.

James Flavell2

Excellent!!!!

I have been going round in circles trying to figure out ways to get JIRA OnDemand to be able to do this basic help desk function (and screaming Why is JEMH not availble ) and was about to give up and move on to some other cloud solution due to the complete lack of interest in making a decent email handler and email formating by Atlassian for the OnDemand solution.

Now I will hold off and wait and see. I just hope your pricing will be workable for me.

Many thanks

James

unknown

The whole SAAS pricing structure is tricky to guage, and even trickier to implement as there is not much flexibility within the atlassian ondemand pricing structure for addon specific price scaling related to usage other than 'users'. This actually introduces scenarios like what to do when a user exceeds plan limits, and realistically how to handle or bill for extra headroom, as with email integration, clearly, just turning it off really doesnt work too well, for example:

Would you rather:

pay more to get higher data limits, or
be ok with cessation/severe throttling of service during a calendar month due to exceeding those limits?

After all it really does need to cover costs, this stuff isn't cheap to develop or run

Looking at things like JIRA Agile pricing for ondemand will give you an idea, though nothing is set in concrete, as with email handling there is much more processing and IO involved.

The documentation effort is about to get started, so pretty soon there will be something to see on the JEMHOD space.

James Flavell2

Thanks Andy and I can understand

I honestly would not expect my situation to be data intensive but if I was in that situation I would of course prefer to have an extra charge kick in if I exceed some quota (e.g. just like mobile data billing where usually you have a monthly limit and over that there is some additional charge)

I would not want to be paying higher out of the box just to cover the what-if situation because I would not expect to be getting to that point)

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-desk

jira-service-desk-cloud