Processing repair orders
Finalizes costs, customer communication, documents, and follow-up tickets for repair orders above a certain amount.
Overview
Repair orders above a certain amount require the correct costs, a customer message, and a follow-up ticket. This automation exports and merges the orders, checks each order against the threshold, adds only the missing costs, sets the order to pro forma sent, attaches the quote report, and creates the Zendesk ticket. Exceptions are noted in the file.
What has changed
- Less processing time per order
- No missed invoice items
- Customer communication is standardized and data is consistent
At a glance
In één oogopslag
Overzicht
Repair orders above a certain amount require the correct costs, a customer message, and a follow-up ticket. This automation exports and merges the orders, checks each order against the threshold, adds only the missing costs, sets the order to pro forma sent, attaches the quote report, and creates the Zendesk ticket. Exceptions are noted in the file.
Wat er verandert
- Less processing time per order
- No missed invoice items
- Customer communication is standardized and data is consistent
How it works.
What it does per order
- Exports order lists from Dynamics and merges them
- Checks if the order total is above the threshold
- Retrieves and validates the customer's country, language, and email
- Adds missing costs (shipping and handling, labor hours, call-out charges) without duplication
- Sets the order to 'pro forma sent' and attaches the quote report
- Creates the Zendesk ticket and writes the ticket number back to Dynamics
Rules
Only orders above the set amount are processed, and exceptions such as specific customers, merged orders, or missing standard repair times are noted and skipped. A cost item is only added if necessary, and labor hours are equal to the standard repair time. Every run follows the same logic and is logged for review, so there is no guesswork involved.
Check out other automations.
Frequently asked questions.
No. The digital colleague works in the screens and systems your team already uses, whether they are legacy applications without an API or modern ones, so there is nothing to replace.
Yarado builds it, runs it and monitors it. When a screen or a system changes, we adjust the automation, so your team needs no developer or automation skills of its own.
Yes. Every run is recorded in the Yarado portal, where you can see which processes ran, when they last ran, what they produced and what went wrong. Depending on the automation, the processing log is also emailed to the team that needs it.
Yarado monitors every run and is alerted automatically when one fails, so a problem is picked up on our side. Cases that need a person are reported to your team with the reason, in the portal or by email.
Yes. Automations are built around your own steps and systems, and this page is just one example of what is possible. A first automation is typically live in weeks, not months.