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
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
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.
Form: Help Desk Ticket
Starts the workflow
E-mail: Ticket received: …
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}}
Approve & sign purchase: {{trigger.body.subject}}
Approve & sign · Budget holder
Deny: E-mail: Purchase not approved · Approve: Approve & sign work order: {{trigger.body.subject}}
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}}
E-mail: Purchase not approved
E-mail: Access not approved
Approve & sign work order: {{trigger.body.subject}}
Approve & sign · IT support lead
Deny: E-mail: About your ticket: … · Approve: Resolve: {{trigger.body.subject}}
E-mail: About your ticket: …
Resolve: {{trigger.body.subject}}
Task · Support engineer
Mark as done: E-mail: Resolved: …
E-mail: Resolved: …
Help Desk Ticket
Starts the workflow · 12 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.
Service requests are approved and signed by the line manager; anything costing more than ₹50,000 is also signed by the IT director before the service desk carries it out.
8 steps · 3 rolesAdmin Access Approval RequestRequests for administrator or privileged accounts are approved and signed by the system owner; the IT administrator then records exactly what was granted and until when, and the record is filed in Drive.
7 steps · 3 rolesEquipment Purchase RequestTeams request new laptops, phones, instruments or tools; the department manager approves and signs, and procurement orders the items and tells the requester the PO and delivery date.
4 steps · 2 rolesInformation Request ApprovalStaff request a data extract or report; the data owner approves sharing it, a data analyst prepares it with escalation if it stalls, and the data protection officer gets a report.
6 steps · 4 rolesIT Change RequestIT changes are routed by type: standard changes go straight to scheduling, normal changes need the CAB chair's signature and emergency changes the emergency approver's, before the window is booked and implemented.
12 steps · 4 rolesIT Incident ManagementService outages are classified and signed off by the incident manager, resolved by the resolver group, analysed for root cause and formally closed (or reopened) by the service owner.
8 steps · 4 roles