Experiment: Using UserVoice.com for Support, Feedback and FAQ
Join the DZone community and get the full member experience.Join For Free
on my daily job, i am working as a mobile hardware support agent of a german carrier. because of that, i know how important a good support for customers (=users) is – and also, a little knowledge base where users can find most probably an answer for their questions.
i want my customers to be satisfied. as an indie developer, i have a little problem: i don’t have a support team that catches all the support questions for me. i need to do this by myself. until now, i am doing this by using a send-me-a-mail button in my apps. however, due to the fact that i have a 9to5 job and a family besides developing apps, time is a bit limited for me. i searched for some solutions to improve the way i am doing my customer service, and uservoice seems like a good tool to improve my customer service a lot.
as you can see at the feature comparison list of uservoice, the free account already allows you to do a lot of things: https://www.uservoice.com/plans/?ref=top_pricing . it is free for one support agent – perfect for an indie developer like me.
what can you do with uservoice?
uservoice has a lot of features:
- support ticket system
- knowledge base
- feedback system/forum
- and many more, if you are going for a paid plan
let’s have a look at the first three features:
support ticket system
adding the ticketing system is very easy. you just need a emailcomposetask pointing to your ticket system. your standard mail address for that will be: “tickets@<yourname>.uservoice.com”. this is how a received ticket looks like:
answering to a user is as easy as writing an email – plus you have a ticket history at a glance.
on top of that, you are able to insert a so called ‘canned response’ based on your knowledge base:
you can build up a knowledge base for your apps.
in the left menu at the bottom at your admin console, you will find the ‘articles’ section. this is where all the knowledge base articles are collected.
you can create also topics within that kb. i did so for all of my apps:
this way, you can use your free account to support all of your apps with faq/kb articles – pretty easy.
here is how to set up a new article: after clicking on ‘all articles’, there is a ‘new article’ button on the right side of your screen. click on that, you will see this on the right hand side:
you can set up the article name, the text and the topic as well as the position you want to show it up in your knowledge base.
you can take a look at my knowledge base here: https://msiccdev.uservoice.com/knowledgebase
how can you use this in your apps? i plan to create an api wrapper for their c# sdk, which is not compatible with windows phone at the moment. i will write another blog post for that. luckily, uservoice as a very nice mobile interface, so you can start off with a simple webbrowsertask to open your knowledge base:
technically, it would be possible to use a webbrowser control, too. but you would need to code more to get a proper browsing handling.
some of you might be already familiar with the feedback or idea forum of uservoice (even microsoft uses this). this time, we look at the other side of the forum, from our admin console:
you have a similar view to what users see, but there are some more parts to control your forum. as a free user, you have only one forum, so it might be useful if you add the app name in front of the title of an idea. you can respond, take notes, and change the status of the ideas:
to integrate the feedback function in your app, you can again use a webbrowsertask to open the mobile page of your idea forum:
these are the first simple steps to create your own customer support system with uservoice. like i said before, i will write a windows phone wrapper to get this into an app as native, and will share it here with you all.
until the next post, happy coding!
Published at DZone with permission of Marco Siccardi, DZone MVB. See the original article here.
Opinions expressed by DZone contributors are their own.