ITSM Change Management for Zendesk

Overview

Change management without a separate ITSM tool

Change management is how IT teams plan, approve and roll out changes without breaking things. Every change needs the right details captured, the right people to sign off, a time to happen and a record of what was done.

Many Zendesk teams run this through spreadsheets and email, or buy a separate ITSM suite their agents have to learn. With SweetHawk, you can run a structured, auditable change process in the Zendesk tickets your IT team already works in. Install only the apps you need.

Step by step

How a change request runs in Zendesk

1. Raise the change with the right fields

Field Rules lets you choose which fields show for each type of change and make the important ones, such as risk or a rollback plan, required. You can lock fields that triggers fill in, so nobody overwrites them, and set a rule to start the next step as soon as a field changes.

2. Plan the work

Tasks & Subtickets can apply your change task list automatically, with phases you set up for pre-implementation, implementation and post-implementation. Each phase appears once the one before it is done. Work for another team spins off as a linked subticket with its own form, fields and assignee.

3. Get the change approved

A trigger starts the CAB approval in Approve. Approvers respond from email, Slack, Microsoft Teams or a web form without an agent seat. Chains can be sequential or parallel, and deadlines escalate to a backup when someone doesn't respond.

4. Schedule the change window

Calendar puts the change on a shared change calendar and syncs both ways with Google Calendar and Microsoft 365, so stakeholders can see it. Event times are written to ticket fields for views, triggers and Explore, and changes can be dragged to a new slot.

5. Alert people at the right moment

Notify pops up alerts for the right agents or groups when something needs attention, such as an approval coming through, an approver not responding or a stage stalling.

6. Hold every stage to time

Timers lets you run a named timer for each stage, each on its own business hours, and escalate the ticket when time runs out.

7. Review it and close it out

Once the change lands, a second approval can sign off the post-implementation review. A required task list stops the change ticket being solved until every task and subticket is complete. Approvals, tasks and timings are all recorded on the ticket for review and audit.

Why SweetHawk

Why teams run change management in Zendesk

One place for IT work: changes sit next to the incidents and requests they relate to, with one audit trail and one reporting surface.
Faster to set up: days, not months, because your team is already in Zendesk.
Modular: start with approvals and task lists, then add calendars, field rules, alerts and timers as you need them.
Audit-ready: every approval, task and decision is recorded on the ticket, which helps with ITIL and SOX reviews.
Reportable: task, timer and event data is written to ticket fields you can report on in Explore.

FAQ

Common questions

Can Zendesk be used for change management?

Yes. With SweetHawk apps, a Zendesk ticket can carry a full change process: the right fields for the type of change, a phased task list, CAB approval, a scheduled change window, alerts and timers for each stage.

Can CAB members approve changes without a Zendesk licence?

Yes. Approve sends approvals by email, Slack, Microsoft Teams or a web form, so approvers don't need an agent seat.

How do I schedule change windows in Zendesk?

Use the Calendar app to put changes on a shared change calendar. It syncs both ways with Google Calendar and Microsoft 365 and writes event times back to the ticket.