Help Desk Ticket Approval

Help desk tickets that need a sign-off are routed by type: purchases to the budget holder, access to the system owner, and every ticket is then approved and signed by the IT support lead.

Sign in with your Edesy account; the setup wizard opens on this template.

Category

IT

Type

Business process

Steps

10

Roles

Budget holder, System owner, IT support lead, Support engineer, IT manager

Level

Advanced, about 15 min to set up

How the workflow runs

Some tickets can be fixed straight away; others need someone to say yes first. Staff raise a ticket with the type, urgency and business reason, and get an acknowledgement with a tracking link. A conditional branch adds the right first approver: new hardware or software goes to the department's budget holder, access to a business system goes to that system's owner. The IT support lead then approves and signs the work order, and the support engineer completes it with escalation if it stalls. The requester hears back when it is resolved.

PurchaseDenyAccessDenyApproveApproveOtherwiseDenyApproveMark as doneFormForm: Help Desk TicketE-mailE-mail: Ticket received: …Conditional branchRoute by ticket typeApprove & sign · Budget holderApprove & sign purchase:{{trigger.body.subject}}Approve & sign · System ownerApprove & sign access to{{trigger.body.system}}E-mailE-mail: Purchase not approvedE-mailE-mail: Access not approvedApprove & sign · IT support leadApprove & sign work order:{{trigger.body.subject}}E-mailE-mail: About your ticket: …Task · Support engineerResolve:{{trigger.body.subject}}E-mailE-mail: Resolved: …

Steps in order

  1. 1

    Form: Help Desk Ticket

    Starts the workflow

  2. 2

    E-mail: Ticket received: …

    E-mail

  3. 3

    Route by ticket type

    Conditional branch

    Purchase: Approve & sign purchase: {{trigger.body.subject}} · Access: Approve & sign access to {{trigger.body.system}} · Otherwise: Approve & sign work order: {{trigger.body.subject}}

  4. 4

    Approve & sign purchase: {{trigger.body.subject}}

    Approve & sign · Budget holder

    Deny: E-mail: Purchase not approved · Approve: Approve & sign work order: {{trigger.body.subject}}

  5. 5

    Approve & sign access to {{trigger.body.system}}

    Approve & sign · System owner

    Deny: E-mail: Access not approved · Approve: Approve & sign work order: {{trigger.body.subject}}

  6. 6

    E-mail: Purchase not approved

    E-mail

  7. 7

    E-mail: Access not approved

    E-mail

  8. 8

    Approve & sign work order: {{trigger.body.subject}}

    Approve & sign · IT support lead

    Deny: E-mail: About your ticket: … · Approve: Resolve: {{trigger.body.subject}}

  9. 9

    E-mail: About your ticket: …

    E-mail

  10. 10

    Resolve: {{trigger.body.subject}}

    Task · Support engineer

    Mark as done: E-mail: Resolved: …

  11. 11

    E-mail: Resolved: …

    E-mail

Forms

  • Help Desk Ticket

    Starts the workflow · 12 questions

Who takes part

  • Budget holder
  • System owner
  • IT support lead
  • Support engineer
  • IT manager

Help Desk Ticket Approval: questions

You sign in to Edesy Flow with your Edesy account and the template wizard opens: map each role to a person, pick the app connections it needs, and Flow creates the forms and the workflow for you to edit.

Yes. The workflow opens in the visual builder, where you can add, remove or reorder steps, change who approves, edit the e-mails and add branches.

Related templates