AI LunchroomPractice AI. Do real work.
AI prompts by job

AI prompts for bike shop service writers

You write up repair tickets from a customer's vague “it clicks sometimes,” call with a quote bigger than they hoped, and explain why a part will take six weeks to arrive. These prompts are written for that work — copy one into ChatGPT, Claude, Copilot, or Gemini, or practice it with step-by-step feedback and keep the ones you reuse.

What AI is actually good for in this job

Not everything — but these four come up every week, and they are all writing tasks, which is where today's tools are strongest.

Before you paste anything

What never goes into a chatbot in this job

Never paste customer names tied to bike serial numbers, theft or insurance claim details, phone numbers, and supplier pricing. Serial numbers matter for stolen-bike recovery. Describe a case as a commuter bike with a drivetrain problem, and keep serials in your shop system.

Which tool: Bike shops usually run a shop-management system for tickets and a free chatbot on a phone for wording. AI can't diagnose a bike from text and doesn't know your parts compatibility, so the mechanic's findings are the facts and AI only helps with phrasing.

Turn a customer's vague noise description into a clear repair ticket

The rough version you start from
Customer said: it clicks sometimes when I pedal hard, especially uphill, and the back wheel feels weird. Started after she rode in the rain two weeks ago. Also the brakes squeal a little. Commuter bike, rides daily. She wants it back by Friday if possible and doesn't want to spend a lot.
Copy this prompt
I work in bike shop service writing. Help me with the task below — I will review and edit what you give me before I use it.

Relevant context:
- Role: Bike Shop Service Writer
- Work context: You write up repair tickets from a customer's vague “it clicks sometimes,” call with a quote bigger than they hoped, and explain why a part will take six weeks to arrive.

Task:
Turn a customer's vague noise description into a clear repair ticket

Source material:
Customer said: it clicks sometimes when I pedal hard, especially uphill, and the back wheel feels weird. Started after she rode in the rain two weeks ago. Also the brakes squeal a little. Commuter bike, rides daily. She wants it back by Friday if possible and doesn't want to spend a lot.

What to give me:
Turn this into a repair ticket with the symptoms, when they happen, what she asked for, and a line for the mechanic's findings, leaving the diagnosis blank.

Boundaries:
- Use only the facts in the source material. Do not invent names, dates, amounts, or promises.
- If something needed is missing, list it as a question at the end instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Before you use it: Check the ticket records only her words and no diagnosis, part, or cost that the mechanic hasn't determined.

Write the estimate call script that explains why the quote is bigger than expected

The rough version you start from
Mechanic's findings: chain stretched, cassette worn, rear brake pads low, one spoke loose, rear tire has cracking. Brakes and tire are safety items. Chain and cassette wear together, so replace both or the new chain will skip. A spoke true is cheap. Customer expected a tune-up quote. The total is well above that.
Copy this prompt
I work in bike shop service writing. Help me with the task below — I will review and edit what you give me before I use it.

Relevant context:
- Role: Bike Shop Service Writer
- Work context: You write up repair tickets from a customer's vague “it clicks sometimes,” call with a quote bigger than they hoped, and explain why a part will take six weeks to arrive.

Task:
Write the estimate call script that explains why the quote is bigger than expected

Source material:
Mechanic's findings: chain stretched, cassette worn, rear brake pads low, one spoke loose, rear tire has cracking. Brakes and tire are safety items. Chain and cassette wear together, so replace both or the new chain will skip. A spoke true is cheap. Customer expected a tune-up quote. The total is well above that.

What to give me:
Write a phone script that explains the findings in order of safety, separates must-do from can-wait, and invites questions before asking for approval.

Boundaries:
- Use only the facts in the source material. Do not invent names, dates, amounts, or promises.
- If something needed is missing, list it as a question at the end instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Before you use it: Check every item matches the mechanic's notes and that no price or labor time was invented.

Draft the backorder update for a part that will not arrive for weeks

The rough version you start from
Customer ordered a special rear derailleur. Supplier says backordered, no firm date, maybe six weeks, maybe more. The bike is in the shop but can't be ridden without it. Options: wait, fit a cheaper compatible one from stock now, or pick up the bike as is. He's already been waiting two weeks.
Copy this prompt
I work in bike shop service writing. Help me with the task below — I will review and edit what you give me before I use it.

Relevant context:
- Role: Bike Shop Service Writer
- Work context: You write up repair tickets from a customer's vague “it clicks sometimes,” call with a quote bigger than they hoped, and explain why a part will take six weeks to arrive.

Task:
Draft the backorder update for a part that will not arrive for weeks

Source material:
Customer ordered a special rear derailleur. Supplier says backordered, no firm date, maybe six weeks, maybe more. The bike is in the shop but can't be ridden without it. Options: wait, fit a cheaper compatible one from stock now, or pick up the bike as is. He's already been waiting two weeks.

What to give me:
Write a brief, honest update that explains the delay, offers the three options, and asks him to choose, without promising an arrival date.

Boundaries:
- Use only the facts in the source material. Do not invent names, dates, amounts, or promises.
- If something needed is missing, list it as a question at the end instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Before you use it: Check it states no arrival date and no compatibility claim for the stock derailleur that the mechanic hasn't confirmed.

Explain what a tune-up includes so customers understand what they are paying for

The rough version you start from
Basic tune-up here includes: wash, drivetrain clean and lube, brake and shift adjustment, wheel true if needed, tire pressure, bolt check. It does not include replacement parts, major wheel work, hub or bottom bracket service, or suspension service. Parts and extra labor are quoted before we do them. Takes about three days.
Copy this prompt
I work in bike shop service writing. Help me with the task below — I will review and edit what you give me before I use it.

Relevant context:
- Role: Bike Shop Service Writer
- Work context: You write up repair tickets from a customer's vague “it clicks sometimes,” call with a quote bigger than they hoped, and explain why a part will take six weeks to arrive.

Task:
Explain what a tune-up includes so customers understand what they are paying for

Source material:
Basic tune-up here includes: wash, drivetrain clean and lube, brake and shift adjustment, wheel true if needed, tire pressure, bolt check. It does not include replacement parts, major wheel work, hub or bottom bracket service, or suspension service. Parts and extra labor are quoted before we do them. Takes about three days.

What to give me:
Write a short, plain description of the tune-up for a service menu and counter card, listing what's included and what's extra.

Boundaries:
- Use only the facts in the source material. Do not invent names, dates, amounts, or promises.
- If something needed is missing, list it as a question at the end instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Before you use it: Check the inclusions, exclusions, and turnaround against what your shop actually does, since AI tends to add friendly extras.

More prompts for this job

Drawn from AI Lunchroom's Customer Service, Sales & Account Support practice labs and rewritten for this role. See every Customer Service, Sales & Account Support prompt.

Repair a reusable customer response prompt

Bad Prompt Repair practice for customer complaint, account note, sales handoff, service recovery, or response draft, producing usable finished work.

Copy this prompt
I work in bike shop service writing. Help me create one repaired customer response prompt that I can review and edit before use.

Relevant context:
- Role: Bike Shop Service Writer
- Work context: You write up repair tickets from a customer's vague “it clicks sometimes,” call with a quote bigger than they hoped, and explain why a part will take six weeks to arrive.

Task:
Inspect the weak customer response prompt provided. Identify what is missing, use AI to repair that prompt, then review and edit the AI-repaired prompt. You are not creating a brand-new prompt from scratch. You are repairing the weak prompt provided. The repaired prompt must include role, workplace context, task, boundaries, output format, completion criteria, review rules, and a "STOP FOR NOW" escape phrase (a line that tells the AI when to stop and summarize instead of continuing).

Source material:
Marisol emailed twice about a duplicate charge on order #48821 -- just write her back saying we're crediting it right away and she doesn't need to call in.

Return only the finished work:
repaired customer response prompt

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Review a customer response draft

AI Output Review practice for customer complaint, account note, sales handoff, service recovery, or response draft, producing usable finished work.

Copy this prompt
I work in bike shop service writing. Help me create one safer revised customer response draft that I can review and edit before use.

Relevant context:
- Role: Bike Shop Service Writer
- Work context: You write up repair tickets from a customer's vague “it clicks sometimes,” call with a quote bigger than they hoped, and explain why a part will take six weeks to arrive.

Task:
Review an AI-generated customer response draft for accuracy, missing context, unsafe assumptions, unsupported promises, and human review needs. Then produce a safer revised version. As a Lead deliverable, also write a short review standard your team can reuse: what to always check, what to never accept, and who signs off.

Source material:
You asked your AI tool to draft a reply after a customer named Tasha emailed about a double charge on her account. Here is what it wrote: "Hi Tasha, I've confirmed the $89.50 duplicate charge on invoice #4417 was a billing error on our end, and I've already issued the refund -- it will post to your card within 24 hours. I've also added a 10% credit to your next invoice as an apology for the trouble. I promise this kind of duplicate billing won't happen again, and please don't hesitate to reach out if anything else comes up!"

Return only the finished work:
safer revised customer response draft

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Customer issue summary

Turn a messy customer message into issue, impact, known facts, missing details, and next step.

Copy this prompt
I work in bike shop service writing. Help me create one customer issue summary that I can review and edit before use.

Relevant context:
- Role: Bike Shop Service Writer
- Work context: You write up repair tickets from a customer's vague “it clicks sometimes,” call with a quote bigger than they hoped, and explain why a part will take six weeks to arrive.

Task:
Create a clear customer issue summary the billing team can act on without calling the customer back.

Source material:
"Hey it's Dana again, this is the third time reaching out about order #48211 -- when I called Tuesday your rep Marcus told me the replacement charger would ship free since the first one arrived broken, but I just got billed $34.99 for it AND a $12 restocking fee I never agreed to. I have the return tracking number if you need it: 1Z-9F8-2201. I need this sorted before my card statement closes on the 24th or I'm disputing the whole thing with my bank. Can someone actually call me back today?"

Return only the finished work:
1. customer issue summary
2. known facts
3. missing info

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

Reusable FAQ answer

Turn a common question and known facts into one clear, reusable answer with no promises.

Copy this prompt
I work in bike shop service writing. Help me create one reusable answer to the refund-timing question that I can review and edit before use.

Relevant context:
- Role: Bike Shop Service Writer
- Work context: You write up repair tickets from a customer's vague “it clicks sometimes,” call with a quote bigger than they hoped, and explain why a part will take six weeks to arrive.

Task:
Write one clear, reusable answer to the refund-timing question above, plus a short note on what to double check before sending it to a customer.

Source material:
"Third time today someone's asked about this -- can you get me a ready-to-go answer for 'How long do refunds take?' I keep giving slightly different answers and it's making us look disorganized. Here's what's actually true: once a refund is approved, it hits the customer's account in 5 to 7 business days. Approval itself can take anywhere from same-day to 3 business days depending on the item, and we send an automatic email the second it goes out. I don't want anything in there that promises a specific date -- I got burned promising Naomi in billing a refund would land by Friday, and it didn't clear until the following Tuesday."

Return only the finished work:
1. reusable answer to the refund-timing question
2. short note on what to verify before sending it
3. guidance on when to escalate instead

Boundaries:
- Do not invent facts. Label missing information clearly.
- If information is missing, label it as missing instead of guessing.
- If I type "STOP FOR NOW", stop expanding the work and give only the best partial version from the information already provided.
Open in your agent

Copies the prompt and opens your tool in a new tab — paste it into the chat box (Ctrl or ⌘ + V), then fill in your own details. Remove private or sensitive information before using AI for workplace tasks.

How to use ChatGPT or Copilot for bike shop service writers work

  1. Start from your own rough version. Type or dictate what you would have written anyway, however messy. A prompt built on your real note beats a blank-page request every time.
  2. Say who it is for and how long it should be. "Two sentences for a supervisor" and "a checklist a new hire can follow" produce completely different output from the same facts.
  3. Strip the identifying details first. Customer names tied to bike serial numbers, theft or insurance claim details, phone numbers, and supplier pricing. Serial numbers matter for stolen-bike recovery. Describe a case as a commuter bike with a drivetrain problem, and keep serials in your shop system.
  4. Read every specific it produces. AI fills gaps with plausible invention — dates, amounts, names, policy numbers. If you did not supply it, do not trust it.
  5. Keep the ones that work. The value compounds when you stop rewriting the same prompt. Save it with a note about when to use it.
Practice, don't just copy

Get better at these — free

Copying a prompt is a start. AI Lunchroom walks you through the task step by step with your own work, checks what your AI tool gives back, and saves the prompts you will reuse. Free to start, no credit card.

Related jobs in Customer Service, Sales & Account Support

Bike Shop Service Writers AI questions

Can AI help me write repair tickets from what customers tell me?

It's good at turning a rambling description into a tidy complaint with symptoms, when they happen, and what the customer expects. It cannot diagnose. Keep the mechanic's findings separate from the customer's words, and don't let AI turn a guess like it's probably the bottom bracket into a diagnosis.

How do I explain a bigger-than-expected repair bill to a customer?

Walk through what was found, what's needed for safety, and what could wait, with prices from your own estimate. AI can make that conversation friendlier. Don't let it invent labor times or part costs, and never use it to push work the customer has declined.