How SweetHawk apps can help…
We love the way Zendesk does incident and problem management. However, once a problem is logged, the path forward regarding change management, approvals, planning and project implementation has always been open to interpretation.
In light of this, we've built a series of apps and example configuration providing a pragmatic approach for these parts of the ITSM anatomy.
Creating an awesome ITSM flow…
Incidents & Problems
Native is the way
Incident and problem workflows in Zendesk are a well-trodden path. Zendesk’s awesome native functionality allows you to link any number of incidents to a problem. When a problem is marked as ‘solved’, any final comment is also sent to all unsolved incidents at the same time as automatically marking them as ‘solved’.
Adding the type
A ‘change’ might be considered as a missing ticket ‘type’ in Zendesk for ITSM purposes. As such, the Change Manager App creates this type for you, to go alongside Zendesk’s native ticket types (Question, Incident, Problem & Task). But since changes are usually much more complex than the other 4 types, the app allows you to specify an unlimited number of ‘Change Types’ with the added ability to conditionally show a different set of Zendesk ticket fields for each of them. Each change type is also able to be linked to separate knowledge base articles so that ‘change models’ can be documented for each.
The missing link
In a similar way that incidents are linked to problems, the SweetHawk Tasks App allows you to link ‘change’ tickets to problems or incidents. This allows agents to track the origin of a change request without the need to go searching.
Plan with confidence
Deciding on when a change should take place could mean you find yourself swivel-chairing between Zendesk and several company calendars. The Calendar App allows you to plan events right on the Zendesk ticket across multiple calendars and integrates with Google Calendar and Office365.
Once a problem ticket is waiting for a change ticket to be completed, it can automatically be set to a status of ‘on-hold’ until the change is completed, at which point, it can automatically be moved back to an ‘open’ status. The tagging functionality of the Tasks App allows you to perform actions like these in combination with Zendesk triggers.
Since Zendesk does not have an in-built approvals engine, the Approvals App can provide keystone functionality for businesses that need to design and regiment transparent & watertight approval processes. It caters for multiple use cases entailing multi-step sequential or parallel approvals, conditional approvals, line manager approvals and group approvals where only a percentage of a team is required to give the nod before approval is considered officially ‘granted’.
Anyone can be an approver
You don’t need to be an agent in Zendesk to be an approver. All that is required is that approvers check their email, and click “Approve” or “Decline” on the data they’ve been sent. This simplicity is extremely well suited for those that have limited time and do not want to or know how to login to Zendesk.
Link it back to the change
In the same way that ‘change’ tickets can be linked to problems or incidents. The Tasks App also allows you to link implementation tickets to ‘change’ tickets.
When creating a work order, the Tasks App allows you to automatically copy all of the relevant data from the change ticket (including the calendar event details), without the need to manually copy and paste.
The tagging functionality of the Tasks App allows you to automatically set the ‘change’ ticket to ‘open’ at the point the implementation ticket is marked as completed. Once the change manager is satisfied the implementation is complete, when they mark their ticket as done, the ‘problem’ ticket can automatically be re-opened for review before communicating back to the end-users about the newly created solution.