Test preview — sample data and pricing. No real bookings or payments.

Auto service

Turn service enquiries into organized appointment requests.

Marlin answers the phone while the ramps are busy, collects the vehicle, the service wanted and the preferred day, and logs it as one clean request. A member of your staff approves the slot. Marlin does not confirm a workshop booking.

The scenario on this page runs on sample workshop data. It makes no real bookings and contacts no customers.

Sample result Awaiting staff approval

What exists when the call ends

Workshop
Harbourline Auto Service (Sample)
Vehicle
2019 Volkswagen Golf
Odometer, as stated by caller
78,000 km
Service type requested
Interim service
Requested day
Thursday, 10:00
Approval status
Awaiting staff approval
Reference
SMP-8123

No price, no duration and no diagnosis appear on this record, because Marlin is not permitted to produce any of them.

Take a service enquiry yourself

Describe a vehicle, ask for a day, then move it. Then try the call every workshop dreads: ask whether the car is safe to drive. Watch what the agent refuses to do.

Every slot in this scenario is a request awaiting staff approval. The sandbox has no path that produces a confirmed workshop appointment, because the product does not have one.

From “it needs a service” to a request your service desk can action

Three inputs, one record, and an approval step that stays with a person. The service types Marlin is allowed to accept are a list you supply; anything outside it becomes a callback.

  1. Vehicle details

    Make, model, year, and the odometer reading as the caller states it. Registration or VIN if your workflow asks for them. Marlin records what it was told and marks it as caller-stated, not verified.

  2. Service type

    Matched against the list of services you have authorised — interim service, full service, roadworthiness test, brake inspection, tyre change. If the caller describes a fault instead of a service, that is a callback, not a guess.

  3. Preferred time, then a request

    Marlin reads the diary, offers days that are open for requests, and logs one request with a reference. Your service desk approves it, moves it, or calls the customer.

Caller said

“A 2019 Volkswagen Golf, about 78,000 kilometres. It is due its interim service.”

“Wednesday morning if you have it.” … “Could you move it to Thursday instead?”

Free-form vehicle description, a day that changes mid-call, and no mention of what is actually wrong. This is what a service enquiry sounds like.

Service request record

Vehicle
2019 Volkswagen Golf
Odometer, caller-stated
78,000 km
Service type
Interim service
Requested day
Thursday, 10:00
Reference
SMP-8123
Revision
2

Awaiting staff approval Sample record

What it may do on a service call, and where it stops

Read the right-hand column first. On a workshop phone line, the things the agent refuses to say matter more than the things it can.

Service tasks, the caller-facing behaviour, and the record produced. Not one of these produces a confirmed appointment — approval stays with your staff.
Situation on the callWhat Marlin doesRecord producedOutcome
Routine service wanted, slot open Records vehicle, odometer and service type, reads the whole thing back, then logs a request for the day and time the caller chose. It states out loud that a person still has to approve it. Service request with vehicle, service type, requested day and time, and a reference Request — staff approve
Requested day is full Offers the days that are open for requests. It does not squeeze a car onto a ramp and does not promise a same-day look. Request on the alternative day, or no record if none suited Alternative requested
Caller moves the day Re-checks the diary and amends the request that already exists. Reference unchanged, revision moves, approval status stays pending — your desk sees one request, not two. The same request, updated Amended, still pending
Caller describes a fault or a noise Records the caller’s words as a caller-reported symptom and says clearly that it cannot say what is wrong. No diagnosis, no likely cause, no reassurance. Callback request carrying the symptom in the caller’s words, marked as not a diagnosis Handed to a person
Caller asks the price or how long it takes Declines and offers a callback. A service price depends on what the technician finds, and a duration depends on the ramp. Marlin has neither answer and is not allowed to estimate one. Callback request with the question recorded Handed to a person
Caller asks whether the car is safe to drive Refuses, and says why: that needs a person who can look at the vehicle. It offers the callback queue and creates nothing that looks like clearance to drive. Callback request — no appointment, no advice given Refused by design

Exceptions an auto-service business should expect

  • A request is not an appointment. Marlin cannot confirm a workshop slot. It logs a request with a reference and an approval status, and a member of staff turns it into a booking. Every screen on this site says so in the same words.
  • No diagnosis. A grinding noise, a warning light or a smell is recorded verbatim as caller-reported. Marlin does not name a cause, a part or a repair.
  • No price and no duration. Not a range, not a “usually about”, not a starting-from. Both depend on what the technician finds.
  • No safety advice. Marlin will not tell anyone whether it is safe to drive, tow or keep using a vehicle, and it will not imply it by choosing a later slot.
  • No write, no tick. If the diary does not confirm the request was logged, the log shows an not confirmed and asks for it to be checked. It does not report a request it cannot prove, and it does not silently retry.
  • The caller can always ask for a person. Handover is available at any point and is recorded in the record of what Marlin did.

Whether handover is a live transfer, a callback queue or a message to a staff channel is set per deployment. Requires verification: no live-transfer destination is confirmed yet, so this page treats a requested callback as a callback request and nothing more. Controls and escalation

What an auto-service deployment needs connected

The conversation works without any of this. Logging a request into your diary does not. Each connection is published with a type and a status, and Planned connections are not selectable.

Connections a service-request workflow depends on. Status describes this product, not your workshop’s systems.
ConnectionWhy a service call needs itIntegration typeStatus
Workshop diary or job-booking system Read which days are open for requests, create a request, amend it, and carry the approval status your desk works from. Via connector Requires verification
Email follow-up Draft the caller’s request summary, and send the callback request to the service desk. Native Supported
Vehicle and customer records Recognise a returning vehicle, attach the call note to the right record, and keep the service history where the technician will see it. Custom Requires verification
Calendar Keep collection, courtesy-car and technician availability out of the ramp diary when they are held separately. Via connector Requires verification
Live transfer to the service desk Move a fault, a price question or a safety question to a person while the caller is still on the line, rather than into a callback queue. Planned Not yet available

Planned connections are listed so the roadmap is legible. They are not selectable and must not be relied on. Note that live transfer being Planned is the reason a fault call ends as a callback request rather than as a person on the line. See integrations for the full list and what each status means.

Documented sample workflow

A service enquiry at a sample workshop, start to finish

Harbourline Auto Service is a fixture, not a customer. Call Marlin has no published workshop references yet, and no testimonial, logo or throughput figure appears on this site until a named business has approved one.

  1. Call answeredAgent names the workshop, states this is a sandbox demonstration, and states up front that it does not diagnose, price or estimate
  2. Vehicle recorded2019 Volkswagen Golf, 78,000 km as stated by the caller, interim service
  3. Diary checkedWednesday 09:00 open — as a request only
  4. Request loggedWritten after an explicit yes, with a reference and the approval status shown on screen
  5. Amendment handledCaller moves to Thursday 10:00 — the same request updated, reference retained, still awaiting approval
  6. Follow-upSummary prepared and placed in the demo inbox — prepared, not delivered

Run this scenario yourself

What an auto-service pilot is scoped and quoted on

There is no published price list. A pilot is quoted against the enquiry workflow you actually run, so an independent workshop is not paying for a multi-site service-centre shape.

Pending commercial approval: currency, billing period, usage unit, included allowance and overage are confirmed in writing in the pilot scope. None of them appear anywhere on this site yet. How pricing is structured

The variables that move the quote

  • How many service types are in scope. A single interim-service intake is a smaller workflow than a list covering tests, tyres and brakes.
  • Where the approval step lives. Reading a diary to offer open days is setup work; writing a request into it depends on the connector being verified.
  • How fault calls are routed. A callback queue, a staff channel, or both — and who is on the other end of it.
  • Conversation time. Usage is charged on time spent on calls, with the unit and any included allowance stated in the agreement.
  • Telephony. Carrier and number costs, listed separately from the agent itself.

Tell us what your service desk spends the day answering.

Which enquiries never reach the ramps, what your diary system is, and which questions must always reach a person. We come back with a scoped pilot and what it would take to run it.

A submitted request is a request, not a booked meeting. We reply with next steps and confirm a time with you.