Detect new tickets
The workflow checks Zendesk every 3 minutes for newly created tickets and retrieves each requester's profile, including their email address.
LIVE WEBINAR · 18 NOV: Make your SAP Business One ready for Black Friday — live demo 18 November. Save my seat
About this template
Support queues treat a top account and a one-time buyer the same, and agents rarely know when a customer has overdue invoices. This template checks Zendesk every 3 minutes for new tickets, matches the requester to an ERPNext customer, calculates 12-month revenue and overdue balance from Sales Invoices, assigns a Platinum, Gold or Standard tier, and sets the ticket priority and tags.
Key benefits
Inside the flow
Every 3 minutes, the workflow matches each new Zendesk ticket to an ERPNext customer and calculates their last 12 months of revenue and overdue balance from submitted Sales Invoices. It sets High priority for Platinum customers and Normal for others, tags the tier and any credit hold, and adds an internal note.
The workflow checks Zendesk every 3 minutes for newly created tickets and retrieves each requester's profile, including their email address.
It finds the ERPNext Customer whose email matches the requester.
It retrieves the customer's submitted Sales Invoices, including totals, due dates and outstanding balances.
It calculates revenue over the last 12 months and the overdue balance, assigns a Platinum, Gold or Standard tier from revenue thresholds in US dollars (USD), and flags a credit hold if any invoice is overdue. Results are grouped per ticket, so each ticket is scored against its own customer.
The ticket is set to High for Platinum customers and Normal for all others, then tagged with the tier and any credit hold. An internal note shows tier, revenue and overdue amount, and advises involving finance before offering replacements or credits to customers on hold.
Ticket priority based on what each customer is worth and owes
01
High value customers move up the queue automatically, protecting the relationships that drive the most revenue.
02
Agents see overdue balances on the ticket, so they don't promise replacements or credits that finance should review first.
03
Every ticket is scored against the same revenue and payment criteria, which removes guesswork and individual bias.
04
Revenue and payment status come from ERPNext automatically, so agents spend their time resolving tickets, not researching accounts.
05
Tier and credit hold tags make it easy to build Zendesk views and reports by customer value and payment status.
01
High value customers move up the queue automatically, protecting the relationships that drive the most revenue.
02
Agents see overdue balances on the ticket, so they don't promise replacements or credits that finance should review first.
03
Every ticket is scored against the same revenue and payment criteria, which removes guesswork and individual bias.
04
Revenue and payment status come from ERPNext automatically, so agents spend their time resolving tickets, not researching accounts.
05
Tier and credit hold tags make it easy to build Zendesk views and reports by customer value and payment status.
Keep exploring
Every repetitive process between your ERP, CRM, and business apps has a template. Find yours, customize it, and go live today.
Customize the flow
Every trigger and action this template uses is available in the appse ai builder, so the same flow can be rebuilt with your own routing, thresholds and destinations.
Questions & answers
Everything you need to know about this template before you deploy it.
Discover how appse ai has helped businesses automate processes and achieve growth through our users' success stories.
Start free — no credit card, no setup calls required. Use this template as-is or customize every step inside the appse ai no-code builder and go live today.