Tickets that support cannot close are escalated: the escalation manager accepts them and each one is routed to development, sales or marketing depending on where the problem lies.
Sign in with your Edesy account; the setup wizard opens on this template.
Category
Type
Business process
Steps
10
Roles
Escalation manager, Development team, Sales team, Marketing team, Customer success team
Level
Advanced, about 15 min to set up
Not every customer problem is a support problem. A bug needs engineering, a pricing or contract dispute needs the account’s salesperson, and a confusing promotion needs marketing. Support agents use this form to escalate a ticket with the history so far. The escalation manager accepts it (or returns it to support with guidance), the customer-facing agent is told, and the ticket is routed to the right team as a task. When that team closes it, the agent gets a resolution e-mail to pass on to the customer, and a flow report goes to the escalation manager.
Form: CRM Support Ticket Form
Starts the workflow
Accept the escalation
Approval · Escalation manager
Deny: E-mail: returned to support · Approve: E-mail: request received
E-mail: returned to support
E-mail: request received
Route by area
Conditional branch
Development: Development ticket: fix the bug · Sales: Sales ticket: resolve the commercial issue · Marketing: Marketing ticket: fix the offer or message · Otherwise: Investigate the escalated ticket
Development ticket: fix the bug
Task · Development team
Mark as done: E-mail: resolved
Sales ticket: resolve the commercial issue
Task · Sales team
Mark as done: E-mail: resolved
Marketing ticket: fix the offer or message
Task · Marketing team
Mark as done: E-mail: resolved
Investigate the escalated ticket
Task · Customer success team
Mark as done: E-mail: resolved
E-mail: resolved
Flow report
Flow report
CRM Support Ticket Form
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.
Vendor 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 rolesOrder Processing WorkflowTakes a customer order from checkout to doorstep: payment is confirmed, stock is reserved, the parcel is packed and shipped, and the customer gets a tracking e-mail.
14 steps · 7 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 rolesAppointment Scheduling WorkflowProspects book a demo, consultation or showroom visit; a sales coordinator confirms the slot and the meeting lands on Google Calendar with an invite to the customer.
4 steps · 1 roleCancellation Approval ProcessCustomers ask to cancel an order online; sales and finance both approve and sign the cancellation and the refund, and the customer is told the outcome.
4 steps · 3 rolesCRM WorkflowTurns a client questionnaire into a tracked lead: it is added to HubSpot, qualified as sales-ready or nurture, followed up, and either closed as a won deal or documented as lost.
11 steps · 4 roles