---
title: "Service Booking to Invoice: AI Workflow Blueprint | QCS"
description: "An AI workflow blueprint on ERPNext: identify the vehicle and job from a message, propose a slot and carry the booking through to invoice."
url: https://quarkcs.com/agentic/service-to-invoice
---
Workflow 4 of 5 · After-sales · Workshop

# From a service request to a closed job card. *Estimate approved before the work.*

A customer asks for a service on WhatsApp. AI identifies the vehicle and the job, the rules propose a slot, bay and technician, the customer approves the estimate, and the job card, parts and invoice follow in the ERP.

[Discuss your service-booking pilot](https://quarkcs.com/contact?interest=pilot&workflow=service-to-invoice) [See the architecture behind it](https://quarkcs.com/agentic/architecture)

Fixed scope and success measures, agreed before any build.

The workflow in three moves

1. **Book & qualify** Identify the vehicle, the job and a slot.
2. **Estimate & approve** Rules price it; the customer approves; exceptions to the advisor.
3. **Work, invoice & deliver** Job card, parts, supplementary approvals, invoice.

Two approvals: **A · the estimate**, by the customer, with the advisor on exceptions, and **B · the invoice and delivery message**.

Related QCS products **After Sales Management, in production**

Digital job cards with customer approval, technician time and bay planning, and warranty tracking by VIN run today in our Automotive Suite. This workflow adds the conversational front end and the AI stages.

[See the Automotive Suite →](https://quarkcs.com/products#automotive)

The workflow, stage by stage

## Service Booking to Invoice. *From the first message to the recorded result.*

Proposed pilot design: the fields, channels, rules and approval roles are agreed for your business before anything is built.

**9 stages.** The first is open; the rest expand as you go, or all at once.

1. 01 **Receive the booking request** WhatsApp · App · Call note · Walk-in Capture

   Identify the customer and the vehicle from the plate or VIN. Attach the message to the vehicle record with its full service history, open campaigns and warranty status.

   Create the service request and acknowledge it with a reference. Later messages stay on the same request.

   **A request on the vehicle**

   Customer, vehicle, history and the conversation in one place.

   Next: qualify the job →
2. 02 **Qualify the job and ask for what is missing** Symptoms, mileage, service type, preferred times AI + checklist

   AI reads the request, identifies the service type or symptoms, and checks the checklist: current mileage, preferred dates, pickup or drop-off, and a photo where a fault is described.

   It checks the service schedule, open recalls and campaigns for this vehicle and adds them to the job. One focused request goes back for anything missing; an unclear reply hands the request to the service advisor.

   **Qualified → scheduling**

   Job type, scope and constraints are known.

   **Unclear → advisor**

   The advisor sees the conversation and the gaps.

   Next: propose a slot →
3. 03 **Propose slot, bay and technician** Capacity, skills and parts availability Rules

   Apply the workshop calendar, bay types, technician skills and parts availability to propose two slots. Offer them on the customer's channel; confirm the chosen one and reserve the bay and technician.

   Parts that need ordering set the earliest slot. AI does not override capacity rules.

   **A confirmed booking**

   Date, bay, technician and reserved parts on the service request.

   Next: prepare the estimate →
4. 04 **Prepare the estimate** Labour times, parts prices, warranty and campaign coverage Rules

   Build the estimate from standard labour times, the parts price list, warranty and campaign coverage, taxes and the customer's terms. Warranty-covered lines are split from customer-paid lines.

   AI drafts the customer-facing explanation of each line in plain language. Amounts come from the rules only.

   **A priced estimate**

   Lines, coverage, totals and the explanation, recorded as a version.

   Next: estimate approval →
5. 05 **Approval A: the estimate** Customer approval on their channel; advisor on exceptions Customer · Service advisor

   Send the estimate for approval on the customer's channel with a one-tap accept. Margin, discount or warranty exceptions go to the service advisor before the customer sees them.

   Approval is tied to the estimate version. A changed estimate is sent again.

   **Approved → stage 6**

   The job card can open.

   **Declined or no reply**

   The advisor follows up; the slot is released by rule after the agreed time.

   Next: Open the job card and pick the parts →
6. 06 **Open the job card and pick the parts** ERP job card, parts reservation, technician assignment Rules

   On the booked date the ERP opens the job card from the approved estimate, assigns the technician and issues the picked parts. Check-in notes and photos attach to the card.

   Time is recorded against the card as work proceeds.

   **A live job card**

   Approved lines, parts and technician time, visible to the advisor and the customer.

   Next: additional work found →
7. 07 **Hand over when additional work is found** Conditional · Findings during the job Service advisor

   The technician records the finding with a photo. AI drafts a supplementary estimate from the rules; the advisor checks it and sends it to the customer for approval A again.

   Unapproved work is not done. The job card shows approved and pending lines separately.

   **Supplementary estimate approved or declined**

   The decision and its version are on the job card.

   Next: close the job and invoice →
8. 08 **Close the job and build the invoice** Approved lines only; warranty billed separately Rules + AI check

   On completion the ERP builds the invoice from the approved estimate lines and recorded parts and time. Warranty lines go to the manufacturer claim; the customer invoice carries the rest.

   AI checks the invoice against the approved estimates and flags any line that was not approved or any recorded part not on an estimate.

   **A checked invoice**

   Matches what the customer approved, with findings for the advisor if not.

   Next: invoice approval and delivery →
9. 09 **Approval B: invoice and delivery message, then send** What the customer receives, and when Service advisor

   The advisor approves the invoice and the delivery message: ready time, amount due, payment options and the invoice attachment. For jobs that match the estimate exactly this can be sampled rather than reviewed one by one.

   Send on the customer's channel, record delivery and payment status, and request feedback after collection.

   **Ready, paid, collected**

   The vehicle record carries the complete job, invoice and feedback.

#### Where staff time is recovered

Taking booking calls, checking history and campaigns, proposing slots, writing estimates, chasing approval for additional work, and rekeying job card lines into the invoice.

#### What we measure in the pilot

Hands-on minutes per job, time from request to confirmed slot, estimate approval time, share of jobs with unapproved additional work, bay and technician utilisation.

#### Does this match your process?

Bring one real case and your current approval roles.

[Bring one case →](https://quarkcs.com/contact?interest=pilot&workflow=service-to-invoice)

Is it worth doing?

## Put your own numbers in. *See the hours.*

The pilot is measured against this baseline. We report the share of these hours it actually removes, with quality and rework alongside.

Measured in the pilot Correct completion Hands-on minutes Waiting time Rework Cost per outcome

The other workflows

## Same pattern, *different department.*

[All five workflows →](https://quarkcs.com/agentic#workflows)

[Sales **Lead to Quote** Enquiries from any channel qualified, priced by your rules, reviewed by AI and approved twice: the quote, then the message that carries it.](https://quarkcs.com/agentic/lead-to-quote)
[Finance · Accounts payable **Supplier Invoice to Payment** Invoices read on arrival, three-way matched by your tolerances, posted by the ERP, paid in an approved run with remittance sent back on the same channel.](https://quarkcs.com/agentic/invoice-to-payment)
[Customer service **Complaint to Resolution** Complaints attached to the order on arrival, evidence gathered, resolution proposed by policy, approved when it matters, posted by the ERP and confirmed on the customer's channel.](https://quarkcs.com/agentic/complaint-to-resolution)
[Finance · Receivables **Collections** Reminders by age and amount on the customer's channel, promises to pay recorded from replies, payments matched on arrival, and credit holds approved by a person.](https://quarkcs.com/agentic/collections)

Bring one real case and your current approval roles

## Start with your service booking process.

We agree the scope, the controls and the evidence a pilot must produce. See [how a pilot runs](https://quarkcs.com/agentic#pilot).

[Discuss your service-booking pilot](https://quarkcs.com/contact?interest=pilot&workflow=service-to-invoice) [Estimate its monthly running cost](https://quarkcs.com/automation-cost-estimator#e=eyJ2IjoxLCJkIjpbIm9wZXJhdGlvbnMiXSwid2YiOnsic2VydmljZS10by1pbnZvaWNlIjp7Im8iOjEsInYiOjYwMH19fQ)
