Customer support tickets are acknowledged and split by type: suspected bugs are confirmed by a support specialist and fixed by engineering, everything else is triaged by the help desk and solved by an agent.
Sign in with your Edesy account; the setup wizard opens on this template.
Category
Type
Business process
Steps
9
Roles
Support specialist, Software engineer, Support lead, Help desk specialist, Support agent
Level
Advanced, about 15 min to set up
For software and SaaS companies whose support team handles both how-to questions and genuine defects. The customer files a ticket with the product area, severity and steps to reproduce, and gets an acknowledgement with a tracking link. Tickets marked as a bug go to a support specialist, who confirms they can reproduce it and signs off before an engineer is assigned the fix; if it is not a bug, the specialist explains how to resolve it. All other tickets go to the help desk specialist for triage and then to a support agent to solve. Either way the customer is told when the ticket is resolved.
Form: Support Ticket
Starts the workflow
E-mail: Ticket received: …
Bug or support question?
Conditional branch
Bug: Support specialist: confirm the bug · Otherwise: Help desk specialist: triage ticket
Support specialist: confirm the bug
Approve & sign · Support specialist
Not a bug: E-mail: Re: … · Bug confirmed: Solve the bug ticket
Help desk specialist: triage ticket
Approve & sign · Help desk specialist
Answer and close: E-mail: Re: … · Accept for solving: Solve the support ticket
E-mail: Re: …
Solve the bug ticket
Task · Software engineer
Mark as done: E-mail: Resolved: …
E-mail: Re: …
Solve the support ticket
Task · Support agent
Mark as done: E-mail: Resolved: …
E-mail: Resolved: …
Support Ticket
Starts the workflow · 11 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.
Authors upload a policy, specification or report; the document owner approves and signs it or asks for changes, and the signed version is filed in Google Drive.
7 steps · 2 rolesInvoice ApprovalVendor invoices are matched to the PO and goods receipt, routed to the right approver by value (budget owner, finance manager or CFO), filed in Google Drive and scheduled for payment.
11 steps · 4 rolesPurchase Order ApprovalA purchase request is approved and signed by the department head, goes to the COO above a spending limit, and the buyer then files the matching expense form.
9 steps · 4 rolesBook PublishingAuthors submit a manuscript; acquisitions screens it, an editor reviews it in depth, the author signs the publishing agreement, files go to Google Drive, an author meeting is booked and production starts.
9 steps · 4 rolesBusiness ProcessA new business enquiry becomes a signed engagement: an account manager prepares the proposal, the director approves it, the client e-signs, files go to Google Drive and the kickoff is booked.
8 steps · 2 rolesCall CenterAgents log inbound leads; a team lead qualifies them, a sales executive books and holds the meeting, the sales manager decides on next steps, and the customer is asked for feedback on the call.
9 steps · 3 roles