Repair shop uses separate Grok Bots to turn messy customer descriptions into diagnostic checklists and draft follow-ups
@xCB06fr（尼斯维修店店主）X (Twitter) · 2026-10-24
Read originalOwner of a computer/mobile repair shop in Nice uses specialized Grok Bots: one turns vague customer symptom descriptions into diagnostic checklists (better with error codes/models), another drafts follow-ups, and a third handles parts lookups. Consistent advice across posts is role separation and human confirmation before any customer-facing message.
Business model
The owner of a small computer and mobile repair shop in Nice runs specialized Grok Bots daily: one converts vague customer symptoms (“it just shuts off sometimes”) into clean diagnostic checklists (far more precise when an error code and model are pasted), another only drafts customer follow-ups, and a third handles parts lookups. He stresses one-bot-one-role and always draft-then-confirm before anything reaches a customer. Fits local service businesses that want to standardize intake and follow-up without losing human control.
The owner of a small computer and mobile repair shop in Nice runs specialized Grok Bots daily: one converts vague customer symptoms (“it just shuts off sometimes”) into clean diagnostic checklists (far more precise when an error code and model are pasted), another only drafts customer follow-ups, and a third handles parts lookups. He stresses one-bot-one-role and always draft-then-confirm before anything reaches a customer. Fits local service businesses that want to standardize intake and follow-up without losing human control.
Workflow
- Diagnostic Grok Bot produces a step-by-step checklist
- Follow-up Grok Bot drafts a customer update email
- Parts-lookup Bot retrieves candidate components
- Confirm and send email or order parts
Adaptation plan
Results are as reported by the original post author. Workflow, prompts, and trial I/O are AgentFlow reconstructions and were not live-tested here.
Starter prompt
Written by AgentFlow; not the original author’s prompt. Not independently deployed in Muse or Grok.
You are the diagnostic assistant for a repair shop. Role: only turn customer symptom descriptions into diagnostic checklists. Boundaries: never quote prices, never promise repair times, never contact the customer directly. Inputs: customer’s original words, device model, error code (if any). Task: output a numbered checklist; each step includes the check action and the expected normal result. Output format: checklist (array), confidence (high/medium/low), needs_human (true). Confirmation gate: checklist is advisory only; final diagnosis stays with the technician. Note: use a separate bot for any follow-up email drafting with the hard rule “draft only, never send.”
Running costs and pitfalls
Results are as reported by the original post author. Workflow, prompts, and trial I/O are AgentFlow reconstructions and were not live-tested here. No independent cost benchmark is available. Check subscriptions, permissions and external actions before running a workflow.