Users describe an IT problem in their own words; AI sorts it into network, hardware, software or accounts and hands it to the right support team, with a Drive log of every ticket.
Sign in with your Edesy account; the setup wizard opens on this template.
Category
Type
Business process
Steps
9
Roles
Network team, Desktop support, Application support, Identity and access team, Service desk
Apps
Google Drive
Level
Advanced, about 18 min to set up
People rarely know which IT team their problem belongs to, so they shouldn't have to choose. The ticket form asks for a plain description, the urgency and the device. An AI step reads the description and classifies it as network, hardware, software or account access; each category creates a task for that team, and anything the AI can't place goes to the service desk to triage by hand. The requester gets an acknowledgement and a resolution e-mail, and a copy of each ticket is logged in Google Drive for monthly trend reviews. Rename the categories to match your support groups.
Form: IT Service Ticket
Starts the workflow
E-mail: request received
AI: categorise request
AI step
Fix network issue for {{trigger.body.name}}
Task · Network team
Mark as done: E-mail: resolved
Fix hardware issue: {{trigger.body.device}}
Task · Desktop support
Mark as done: E-mail: resolved
Fix software issue for {{trigger.body.name}}
Task · Application support
Mark as done: E-mail: resolved
Restore access for {{trigger.body.name}}
Task · Identity and access team
Mark as done: E-mail: resolved
Handle IT ticket
Task · Service desk
Mark as done: E-mail: resolved
E-mail: resolved
Google Drive: ticket log
App action · Google Drive
IT Service Ticket
Starts the workflow · 10 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.
Requests 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 rolesHelp Desk Ticket ApprovalHelp 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.
10 steps · 5 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