← Back to library

Sort repair-shop web requests and reply right away

An automation builder on X set up an intake flow in n8n for an auto repair shop. Each web form submission goes through an AI step that labels job type and urgency and writes a short summary, then becomes an Airtable record plus a same-day reply. Credit: yrn_Holar.

  • OutcomeClassify each incoming service request by job type and urgency, file it, send the customer an immediate reply, and route unclear or out-of-scope requests properly.
  • SetupAn afternoon+
  • LevelIntermediate
  • Credityrn_Holar (@ho_lar_s)
View original
Works with
n8nMakeZapier

Published Oct 20, 2026Updated Oct 20, 2026AI dry run on sample input: passed Oct 20, 2026Source verified Oct 24, 2026

When should you use it?

  • Customers request service through a web form and wait too long for a reply
  • Staff spend time reading and sorting requests before anyone can act
  • You turn down certain jobs and want to say so quickly and politely

Not for: Quoting prices or diagnosing faults automatically; leave those to a mechanic

What do you need, and what do you get?

You need

  • Your web form fields
  • A list of job types you handle, and ones you don't
  • Urgency rules (for example, safety issues or a car that won't start)
  • A table or CRM for requests

You get

  • One table row for each request, labeled by kind of work and how pressing it is, plus a brief summary
  • An immediate, honest reply to the customer
  • A review queue for unclear requests and a polite decline for out-of-scope ones

How does it work, step by step?

  1. List what you doWrite the job types you handle, ones you refuse, and what makes something urgent.
  2. Add the AI stepAfter the form, run our prompt to label and summarize; ask for a confidence level.
  3. Branch on the resultClear requests go to the table with an instant reply; uncertain ones go to staff; out-of-scope gets a decline.
  4. Check weeklyRead a sample of labels and declines and adjust the lists.

The prompt

Our own prompt, inspired by yrn_Holar (@ho_lar_s) and written to work in n8n, Make and Zapier. Values in lime are placeholders.

Fill in the blanks (optional; the copied prompt uses your values)

Prompt5 variables
You sort service requests for {shop}. We handle: {job_types}. We don't handle: {excluded_jobs}. Urgent means: {urgency_rules}.
For the request below, return JSON with: job_type (from our list, 'out_of_scope' or 'unclear'), urgency (urgent/normal), confidence (high/low), summary (one sentence), and customer_reply.
The customer_reply should thank them, say what happens next, and never promise a price, diagnosis or time slot. For out_of_scope, politely say we don't offer that service.
If anything mentions brakes, steering or warning lights, mark urgent even if unclear.
Request: {form_submission}

Inspired by yrn_Holar (@ho_lar_s): n8n intake workflow for a car repair shop. The prompt above is written by playbooks.bot in our own words; nothing from the original is quoted.

What can go wrong?

  • Don't let the auto-reply promise a time slot or price. Keep it to acknowledgment and next steps.
  • Safety-related requests (brakes, steering, warning lights) should always reach a person quickly, even if the label is uncertain.

Our take

Small service businesses lose jobs in the gap between a customer filling in a form and someone getting around to reading it. This workflow closes that gap without pretending the AI is a mechanic. The model's job is narrow: label the request, judge urgency, write a one-line summary. Everything after that is ordinary automation, which keeps the system predictable. The part we like most is the three-way branch. Clear requests get filed and acknowledged immediately, uncertain ones are flagged for a person, and jobs the shop doesn't do get a polite no instead of silence. That last branch is easy to skip and is a real courtesy to customers. We'd make one addition: anything that sounds safety-related should reach staff fast even when the label is unsure. In our dry run with 10 made-up form submissions, our prompt labeled 7 confidently, marked 2 as uncertain (one vague 'weird noise', one mixed request), declined a bodywork request the shop doesn't offer, and raised a brake complaint to urgent.

Where the time goes back: Requests arrive pre-sorted with a summary, customers hear back at once, and staff only read the ones that need judgment.

FAQ

Why flag uncertain requests instead of guessing?
A wrong label sends a job to the wrong person or declines a customer you'd have served. A short review queue is cheaper than either mistake.
Does it work for other trades?
Yes. Plumbers, electricians and appliance repair shops have the same intake problem; change the job lists.

Source and credit

Inspired by yrn_Holar (@ho_lar_s). We describe the idea in our own words, link to the original, and wrote the prompt ourselves; nothing is quoted.

Inspired by
n8n intake workflow for a car repair shop
Creator
yrn_Holar (@ho_lar_s)
Published on
X
Original date
Oct 12, 2026
License
Not openly licensed (the poster keeps all rights), so we quote nothing and link to the original
Originally for
n8n
AI dry run
Oct 20, 2026: passed. Dry-run tested by our AI test agent on sample input. Uncertain and safety cases handled as intended.
AI dry run on sample data; not run with live connected accounts. The playbooks.bot test agent filled the prompt with synthetic inputs, produced the output and checked it against the page's stated outputs and guardrails.
Verified
Oct 24, 2026: source link resolves to the original, the credited creator published it, our excerpt or prompt matches it, and the license allows our use.

Are you the creator? Claim or correct this page.

More in Customer Support

All 27 Customer Support playbooks →

Related playbooks

Customer SupportWorkflow✓ AI dry run

Book tutoring sessions through a WhatsApp chat agent

Let parents and students book, move and confirm lessons in WhatsApp with an agent tied to the tutoring calendar and its booking rules.

Credit: MarcoKueks on Hacker News

An afternoon+
Customer SupportWorkflow✓ AI dry run

Draft email replies with AI and keep sending manual

Every real email gets a drafted reply waiting in your drafts folder; automated senders are skipped and nothing is sent for you.

Credit: u/Limbox0 on r/n8n

Under an hour
Customer SupportPrompt✓ AI dry run

Find the bugs in your intake chatbot with one test chat per rule

Write a small set of test chats, each aimed at one rule in your bot's field spec with the stored values you expect written down first, and catch errors a large pile of happy-path chats misses.

Credit: Adam (Adam13y)

Under an hour
Customer SupportWorkflow✓ AI dry run

File orphaned customer replies into Freshdesk

Support questions sent to the wrong address reach your help desk, while everything else stays out of the queue.

Credit: u/flexrc on r/n8n

An afternoon+