Skip to content

antipaucity

fighting the lack of good ideas

what should an “ideal” support ticketing system provide?

Posted on 9 January 20157 January 2015 By antipaucity 3 Comments on what should an “ideal” support ticketing system provide?

If you were going to create a support ticketing system from scratch – what would you put in it?

My initial list of needs (some of which derive from my book, Debugging and Supporting Software Systems, and other from my experiences in ticket smashes):

  • “long” title support (HP truncates at 80 characters – give me at least 255)
  • “long” field update support (HP truncates at 4k characters – that’s not enough for some stack traces)
  • clear contact fields for both filer and support case owner
  • allow updates to be made via email or web ui
  • allow attachments (for log files, screenshots, etc)
  • have “private” updates visible only to support personnel
  • clear date/time stamps for updates
  • ability to turn case “result” into a KB article
  • clear resolution field
  • web ui should be highly responsive – and run usably on any modern browser (mobile, desktop, tablet, etc)
  • ability to cross-link to other cases filed by same customer
  • clear indication of who has made updates (maybe alternating colors for customer vs support updates?)
  • as few hoops as possible to open new cases & to update existing ones
  • simple way to close a case if you’re the opener
  • easy means to transfer ownership of a case – both for the customer and for the support technician
  • ability to search previous cases – both for customers and engineers

What else would you add? What would you change?

technical Tags:support, ticket

Post navigation

Previous Post: fix ibm – hire me as your ceo
Next Post: columnar “email”

More Related Articles

digital lostness hmmm
upgrading ubuntu editions technical
4 places to check your website’s ssl/tls security settings technical
god bless the lugs personal
i’m surprised facebook doesn’t offer something akin to aws, gcp, azure, etc ideas
setting up an unreal irc server on centos 6 code

Comments (3) on “what should an “ideal” support ticketing system provide?”

  1. Eric Hydrick says:
    9 January 2015 at 12:57

    Ability for the customer/person responsible for the bug to reject a proposed fix or suggestion to close as being insufficient.

    Integration with the backlog of other development work (i.e. if a bug is created, it should show up as new work in the same place as new feature requests).

    Ability to combine reports (for de-duping or grouping of related issues).

  2. Warren says:
    12 January 2015 at 03:30

    Though I think bugs and support cases should be separate, there does definitely need to be ties between them.

  3. Warren says:
    13 January 2015 at 01:23

    to quote my friend Steven (http://theexceptioncatcher.com/blog), “an easily-accessible API for interacting with other tools”

Comments are closed.

January 2015
S M T W T F S
 123
45678910
11121314151617
18192021222324
25262728293031
« Nov   Feb »
  • Patrick Henry 23 March 1775
  • Reincarnation by Wallace McCrae (adapted by Warren Myers)
  • Famed was Beowulf
  • Fuzzy Wuzzy (anonymous)
  • One bright morning in the middle of the night (various)

Books

  • Debugging and Supporting Software Systems
  • Storage Series

External

  • Backblaze
  • Cirkul
  • Digital Ocean
  • Fundrise
  • Great Big Purple Sign
  • Password Generator
  • PayPal
  • Tech News Channel on Telegram
  • Wish List

Other Blogs

  • Abiding in Hesed
  • Chris Agocs
  • Eric Hydrick
  • Jay Loden
  • Paragraph
  • skh:tec
  • Tech News Channel on Telegram
  • Veritas Equitas

Profiles

  • LinkedIn
  • Server Fault
  • Stack Overflow
  • Super User
  • Telegram
  • Twitter

Resume

  • LinkedIn
  • Resume (PDF)

Services

  • Datente
  • IP check
  • Password Generator
  • Tech News Channel on Telegram

Support

  • Backblaze
  • Built Bar
  • Cirkul
  • Digital Ocean
  • Donations
  • Fundrise
  • PayPal
  • Robinhood
  • Wish List

Copyright © 2023 antipaucity.

Powered by PressBook Green WordPress theme