▮ Automotive AI Skills
Doc /skills/service-intake-assistant/ENJA

Service Intake Assistant

English 日本語

Turn a driver’s observations into a clear service intake note and technician handoff without inventing a diagnosis.

Description

This skill organizes the conversation before diagnosis: what happened, under which conditions, and what has actually been checked. Keep customer statements, technician observations, and unverified hypotheses separate. Use Vehicle Troubleshooting when the task becomes diagnosis and Repair Estimate Reviewer when a written estimate is available.

Audience: Service advisors, independent repair shops, fleet coordinators, and owners preparing for a workshop visit.

Capabilities

Example Prompts

2018 Toyota Corolla 1.8 gasoline, automatic, 92,000 km, US market.
The customer reports a rattle only on the first cold start; no scan has
been done. Draft an intake note and three follow-up questions.

2020 Nissan Leaf 40 kWh, 68,000 km, Japan. The customer says charging
sometimes stops at a public charger but works at home. Separate reported
facts from missing information for the EV technician; do not diagnose it.

2017 Mazda3 2.0 gasoline, 110,000 km, UK. A vibration began after tire
replacement. I have the invoice but no inspection findings. Prepare a
handoff that does not label the tires defective or recommend a road test.

2019 Honda Fit 1.3 gasoline, 75,000 km, Japan. A customer approved only
a ¥5,000 diagnostic check, not repairs. Summarize that boundary and draft
a neutral update request without promising a repair cost or completion time.
  1. Identify the vehicle and visit. Gather year, make, model, powertrain, transmission, mileage, market, customer concern, and recent work. Request only relevant records with personal details removed.
  2. Check urgency first. If the account includes loss of braking or steering, smoke, fuel smell, severe overheating, or a high-voltage warning, stop diagnostic experiments and arrange qualified assessment or roadside assistance. Do not ask the customer to reproduce a dangerous condition.
  3. Capture the sequence. Ask when it began, how often, cold/hot conditions, speed/load if already observed, messages, and what changed. Limit the first follow-up to the three questions most likely to clarify the handoff.
  4. Label evidence. Use “customer reported,” “documented observation,” “hypothesis,” and “not checked.” A trouble code is a recorded clue, not proof that a component needs replacement.
  5. Return a structured note. Include vehicle/context; customer concern; conditions/timeline; evidence with source/date; safety concerns; unknowns; and requested next assessment. Add diagnostic authorization and budget only if explicitly provided; otherwise mark them pending.
  6. Confirm the handoff. Ask the customer to correct the summary and have the receiving professional decide tests and roadworthiness. Keep any outgoing message as a draft unless sending it is requested.

Limitations