Capture the new Zendesk ticket
The flow starts when a new support ticket is created in Zendesk. Every new ticket enters the warranty check.
LIVE WEBINAR · 18 NOV: Make your SAP Business One ready for Black Friday — live demo 18 November. Save my seat
Read the serial number from each new Zendesk ticket with OpenAI, check warranty and AMC cover in ERPNext, and create a warranty claim when the product is covered
Apps used in this template
About this template
Support agents lose time checking ERPNext by hand to see whether a faulty product is still under warranty before they can act on a ticket. This template starts on each new Zendesk ticket, uses OpenAI to pull the serial number and fault type from the ticket text, checks the warranty and AMC expiry dates in ERPNext, and creates a warranty claim when the product is covered.
Key benefits
Inside the flow
The flow starts when a ticket is created in Zendesk, and OpenAI extracts the serial number and fault type from the subject and description. appse ai then looks up the serial number in ERPNext, checks the warranty and AMC expiry dates against the ticket date, and either creates a warranty claim with a customer reply or leaves an internal note and tag for agents.
The flow starts when a new support ticket is created in Zendesk. Every new ticket enters the warranty check.
OpenAI reads the ticket subject and description, extracts the product serial number and classifies the issue as dead on arrival, defect, damage or user error. The result is converted into structured fields, and tickets without a valid serial number stop here and stay in normal support handling.
The flow searches ERPNext for the serial number and retrieves the product, the customer it was sold to, and the warranty and AMC expiry dates. If the serial number is not found, the ticket gets an internal note and a warranty unverified tag.
For a recognized product, the flow checks whether the warranty or AMC cover was still active on the date the ticket was raised.
If the product is covered, a warranty claim is created in ERPNext with the customer, item, serial number, fault type and Zendesk ticket reference. The customer gets a public reply with the claim number and next steps, and the ticket is tagged as in warranty.
If cover has expired, agents get an internal note with the warranty and AMC expiry dates and a prompt to offer a paid repair quote. The ticket is tagged as out of warranty.
What support, service and finance teams gain when warranty checks run on every Zendesk ticket.
01
Agents no longer chase finance or search ERPNext by hand. Warranty and AMC status is checked on every ticket that carries a serial number.
02
Expired products are flagged with their expiry dates, so repairs that should be paid are quoted as paid.
03
A warranty claim is created in ERPNext as soon as coverage is confirmed, and the customer gets the claim number on the ticket.
04
Every warranty claim carries its Zendesk ticket reference, giving support, service and finance one traceable record of each case.
05
Serial numbers that do not exist in ERPNext are flagged to agents, who can check for a typo, an unregistered unit or a possible grey market product before any service is committed.
01
Agents no longer chase finance or search ERPNext by hand. Warranty and AMC status is checked on every ticket that carries a serial number.
02
Expired products are flagged with their expiry dates, so repairs that should be paid are quoted as paid.
03
A warranty claim is created in ERPNext as soon as coverage is confirmed, and the customer gets the claim number on the ticket.
04
Every warranty claim carries its Zendesk ticket reference, giving support, service and finance one traceable record of each case.
05
Serial numbers that do not exist in ERPNext are flagged to agents, who can check for a typo, an unregistered unit or a possible grey market product before any service is committed.
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.