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,462,938
Community Members
 
Community Events
176
Community Groups

Customer Service Portal - User Experience

Hello Everyone.

My company users the customer portal for our colleagues who are not Agents.

Now - the common thread in feedback is that the portal is to busy or they cant find anything.

How did you set up your customer portal?

Do you have the same "complaints"

How do we make the user experience better?

1 comment

Dirk Ronsmans Community Leader Oct 08, 2021

Hey @Robin Stemmers ,

It depends on how your current portal is set up of course. You don't have a ton of options to customize the portal but are you already using portal groups to split the request types up in to categories?

If yes and you still have too much going on you might need to re-evaluate the request types you have and if you can't consolidate them in to less types?

Like Robin Stemmers likes this

Hi

Yes I do use groupings and we still have these kinds of complaints.

I train and make use of the search function too.

 

What would be really nice is if there was branching capability on the customer portal.

For example - the common thing people say is "i cant log on" but like we need to know more detail like

You cannot log on where?  Your physical device or specific software?  Or is it your connection

Does anyone use that kind of thing?

Well you do have a couple options for that.

One would be to (if you have it) leverage Insight as your CMDB and as I mentioned consolidate your request types to ask a question in the form. 

With Insight you could already do that towards:

- I have a problem with an application _> which appplication would then be chosen on the form through an Insight custom field.

 

However, it seems you want more capabilities and then you might like to look towards an app like Proforma (which was also recently acquired by Atlassian).

This allows you to create dynamic forms where you can really hide/show sections and go in to a more question like flow.

https://marketplace.atlassian.com/search?query=proforma

I'm specifically mentioning Proforma as it is acquired it most likely will become part of the product later on.

Like Robin Stemmers likes this

ooh  the Proforma option sounds exciting.

 

 

Like Dirk Ronsmans likes this

Thanks for the feedback - looking forward to reviewing that

Like Dirk Ronsmans likes this

Our end users never used the forms the way we intended, so we just simplified the request types and it's been a huge help. Most of our JSM projects all use the same request types. 

jsm1.png

Like Robin Stemmers likes this

Hello @Patrick Haley 

Thanks for you feedback.  In my case - the issues reported is done by various teams.

We don't have a "middle-person" to direct queries, so when they choose a request, it should go to the respective team. And we have so many different teams.

 

I need to make our user experience easy.  We have WAY to many options

Hi @Robin Stemmers ,

What you are trying to do is put in place a services catalogue. You have to do that from the POV of your clients and use terms and structure that make sense to them. They don't care which teams does what, they just want to find the service they need, create the ticket and have someone resolve the request. 

It is not a simple or easy thing to do. In the ITSM world it is the practice named Service Catalogue Management. 

Like Dirk said, using Pro-forma and Insight customfield together will simplify your user forms. You will be able to use attributes from the configuration item (with insight customfield) to assign the tickect to right teams/user

Like Robin Stemmers likes this

Hi @Carmen Nadeau 

Agree - its the service catalogue - But in my world "IT English" and "Business English" is not always the same English (LOL)

Like Carmen Nadeau likes this

Comment

Log in or Sign up to comment
TAGS

Atlassian Community Events