solidoodlesupport wrote:DePartedPrinter wrote:elmoret wrote:Use a ticket system to handle support, so requests are handled by the same customer service rep, instead of haphazardly bouncing them around as is the case now.
I would hope they use a ticket system now.
nevermind^^
We have considered a ticket system in the past and evaluated a few. Sadly, we determined that this would not make the process much more reliable for our scale of business.
Really, the biggest gripe we receive is slow responses, and long drawn out repair sagas. We are working on this of course, but e-mails are seldom lost or forgotten.
use a proper ITIL ticketting system.
You need one person to monitor the email in-box and raise tickets,
tickets should be sorted into technical/nontechnical/commercial etc and then assigned to different support queues.
Technical issues should go to a technical queue where technical people look at the problems.
once a ticket is logged a ticket reference number should be sent out to the customer, they can use this to correspond with the technician, and technicians need to make sure that calls are kept up to date with call notes.
(then if one guy goes on holiday/gets fired/dies etc) then there won't be a customer left out of the loop.
if technical issues are maybe not resolved fast enough the customer may want a refund, in which case the ticket would be moved to the "management support queue" this keeps all incident notes with the existing ticket and enables the manager to evaluate the whole ticket, and decide on what the outcome should be.
Technicians should not close tickets without approval from the customer, (though tacit approval maybe assumed if a tech says are you OK with me closing the ticket and gets no response for say a week.
customers retain their ticket reference numbers and can therefore ask for a ticket to be re-opened if the issue is not resolved.
with a proper ticket system you get to keep all your messages in one place.
Implementing ITIL properly will enable you to set resolution targets for timely support.
It lets you track complete histories in one place, no more "lost emails" or misfiled emails, or needing to repeat questions in the hopes of catching out a customer...
Call timers will let you track how long it takes to actually resolve issues, and a decent call ticketing system will let you produce management reports on a monthly or weekly basis, where you can see who is closing calls, what support staff are not closing calls. how long calls are taking from call log to resolution, then you can praise/chastise support as appropriate for working very well, or working not so well.
Some ticket systems can even be integrated to email so when a message is recieved, if there is no ticket reference in the subject line a new ticket can be logged automatically, if a ticket reference does exist in the subject line then that call with be updated with the customers comments. likewise, support can send an email to the customer and CC the support mail box and have tickets automatically updated. or they can update a ticket and elect to have their update emailed to customers to keep them in the loop.
You say that you're tracking support by email, but given the feed back so far this is clearly not working.
you have a support issue, no matter how big or small you are this can be resolved by using the correct and proven systems.
solidoodlesupport wrote:1) Most users who have significant troubles will deal with multiple CSRs. This is intended, as I and Raff will typically only get involved in tougher cases. The vast majority of customers already only see 1 CSR.
2) There is some legitimate confusion here. In case there is confusion, we are heavily backordered on parts. You have reason to be frustrated that our cart system system always reads "In stock" for all items. Support does not have control of this fact. However, if it were the case that the part was "in stock" as it were, it would go out the same today.
dealing with multiple CSRs is not a problem, neither should call escalation to a different CSR be a problem, I work providing IT support, we use ticketing systems to great effect. if you were using a proper ticket system it seems that half the frustrations with being asked to do the same things over and over etc might go away, leading to more satisfied customers.
RE point 2, you're all linux nerds... then fix the shop!! 
zacgibson21 wrote:Possibly reevaluating your payment system, when I went to purchase it was bounced back by the bank and I ended up being pushed back over a week on my order. I do not know if this is something you could have any influence over or not but its worth looking into.
definitely that, the paypal merchant thing is heavily used by scammers, when I ordered, not only was my order refused but because the bank thought your store was dodgy my credit card was barred from being used so I wasn't able to buy lunch that day!
having payment refused/credit card blocked/bank tell you that they think your company is high risk for scam because of your payment processor is a horrible introduction to your company...