Helpdesk/issue tracker recommendation for extremely large number of tickets

[CGrieves]

I have a department currently using an Exchange inbox/folder setup for issues and tracking. It works OK functionally, but they see about 10,000 emails per month, and retention has to be for 3 years, so as you can imagine with free text searches on a large exchange inbox being as they are, we think it's time for another solution.

Can be free or paid. We use Spiceworks as an IT helpdesk and Jira for dev, but it's pretty clear Spiceworks won't scale due to the flat file architecture, and I have my doubts about Jira too for those volumes.

requirements are pretty simple- issues submitted via email, group access to assign staff and priorities. Email updates, track via email subject/tracking reference. SLA timers should take account of working hours. Should be able to assign multiple watchers to issues. Basic reporting- number of issues within/without SLA, average resolution times.

It would be very useful if individual issues can be linked to via URL so we can tie it into our reservation system with simple links

There's plenty out there that meets the requirements, the problem is assessing how they perform with lots of data, so any experience would be appreciated!

 

[CGrieves]

Thanks guys, I've set up a trial of OTRS and Kayako. OTRS looks functionally excellent, but visually horrible. I should have mentioned that the portal has to be brandable too. As for Kayako, so far I'm warming to it, and feedback seems to be good for usage in scale.

Cheers for the advice! Still open to more opinions

P.S. Caged, you're right, I worded that badly- we only user Jira for SDLC! Having said that Jira Service Desk looks like a great product, and would have fit us to a T, except there's no email issue submission unless you hack it via plugins. Big omission in my opinion, and probably will cripple sales.

 

[CGrieves]

We used Kayako but eventually outgrew that when it didn't really work with what we wanted to do and we wanted to scale with more staff. Zendesk pricing was just laughable really, so we eventually just made our own.

http://sirportly.com/ certainly looks interesting as a relative newcomer to the scene.

Tell me more Daz- Kayako is currently looking like the best fit from a functional standpoint. I've got the trial configured and nearly ready for UAT.

Initially it'll be for about 35 staff dealing with about 10,000 tickets per month -so about 10 tickets per user per day. Do you think it'll cope?

We'll probably be similar implementations out to two other (totally separate) departments, but as it's a per-agent cost I'll just re-register for another Kayako instance for each and keep them entirely separate, seems like a much more flexible method, and could perhaps help with scaling versus one instance with multiple departments.