JIRA/AtlasianZenDeskKaseyaFreshService / FreshDeskKayakoSalesForceIssueTrakHenry’s Favorite: Happy fox?The one Henry hates: Service NOW!Paper based?Emails AKA your inbox?Custom made ticket systemsWhy they matterIssue tracking / historyCommon interfaceHuman brains forget stuffUser Training. Stepping stone to further user training...Use CasesService ProvidersOther Business units work tracking?Individual work management?Request handling due to automated ticket creationHe said / She said tracking...Feature sets- Integrations with other systems
WorkflowsRemote controlPhone System entryEmail acceptanceWeb Based vs Web exposedHow to be successful using them- Cleanup of tickets as well as environment management
Notes/comments about users/objects/issuesInternal ProcessesResolution documentationExperience navigating ticket systemsHow to Manage them- RH: Be patient, adoption can take 6 months
Top down management is key. Upper levels need to back the implementing groupMetrics are not the end all be all. Consider context when managingLabor management