Skip to content
Talk to QCS
Home / Agentic Automation / Service Booking 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.

Fixed scope and success measures, agreed before any build.

The workflow in three moves
  1. Book & qualifyIdentify the vehicle, the job and a slot.
  2. Estimate & approveRules price it; the customer approves; exceptions to the advisor.
  3. Work, invoice & deliverJob 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.
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. 01Receive the booking requestWhatsApp · App · Call note · Walk-inCapture

    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. 02Qualify the job and ask for what is missingSymptoms, mileage, service type, preferred timesAI + 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. 03Propose slot, bay and technicianCapacity, skills and parts availabilityRules

    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. 04Prepare the estimateLabour times, parts prices, warranty and campaign coverageRules

    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. 05Approval A: the estimateCustomer approval on their channel; advisor on exceptionsCustomer · 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. 06Open the job card and pick the partsERP job card, parts reservation, technician assignmentRules

    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. 07Hand over when additional work is foundConditional · Findings during the jobService 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. 08Close the job and build the invoiceApproved lines only; warranty billed separatelyRules + 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. 09Approval B: invoice and delivery message, then sendWhat the customer receives, and whenService 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 →
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.

Staff hours per month—in this process today
Staff cost per month—at the rate you entered
Per year—hours · cost

Pre-filled figures are illustrative. Time released is capacity; what it is worth depends on how you use it. The pilot measures what share of these hours it removes, and at what quality.

Measured in the pilotCorrect completionHands-on minutesWaiting timeReworkCost per outcome
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.