first safe pilot
Customer update draft from approved work-order notes.
Keep the first workflow at draft or review-support level before any real-world use.
aequai ~ / industries / handbook 05
$ aequai handbook --priority 05 --full-content
Local Services AI Adoption Handbook
Customer updates, appointment prep, work-order summaries, and staff SOP drafts for local service teams.
priority 05readiness mapfictional/synthetic samples onlyhuman approval required
// boundary: This handbook is local review copy for readiness, training, workflow design, and evidence mapping. It is not sector authority, professional advice, public approval, regulated conclusion, production authority, autonomous operation, token/chain/network action, carbon-asset action, or customer proof.
$ aequai quick-map --pilot --path --no-go
Safe first step.
service path
AI Literacy Training -> Department AI Pilot Design
Use diagnostics, training, pilot design, governance, or simulation according to the workflow risk.
training path
Owner, frontline manager, support/admin, and field team paths.
Training is personalized to role, workflow, tool stack, risk profile, data boundary, and approval responsibility.
Source: local-services-ai-adoption-handbook-v0.1.md. Source title: Local Services AI Adoption Handbook v0.1.
$ aequai handbook-source --sections all
Full handbook content.
The sections below expose the actual handbook material: business context, workflows, first safe workflows, map, boundaries, simulation example, checklist, fictional/synthetic sample teaser, recommended AequAI path, 30/60/90 roadmap, and public-safe no-go wording.
[01]Business Contextsource-backed handbook section+ open- close
Local service businesses need clear customer updates, scheduling support, work-order notes, team SOPs, and owner summaries. AI is useful when it drafts from approved information and keeps owners in review.
Every training path is personalized to the person, team, role, workflow, tool stack, risk profile, business context, workflow maturity, data boundaries, and approval responsibilities.
[02]Typical Workflowssource-backed handbook section+ open- close
Appointment prep, repair/status updates, work-order summaries, FAQs, service descriptions, staff SOPs, and customer follow-up drafts.
[03]First 5 Safe Workflowssource-backed handbook section+ open- close
- +Appointment-prep brief.
- +Work-order summary.
- +Customer update draft.
- +Staff SOP draft.
- +Service FAQ draft.
[04]Function Mapsource-backed handbook section+ open- close
| Function | Opportunity | Training Need | Gate |
|---|---|---|---|
| Owner | Weekly operations brief | Tool choice and review | Owner review |
| Frontline manager | SOP and shift notes | Workflow practice | Manager review |
| Support/admin | Customer drafts | Data boundaries | Owner review before send |
| Field team | Work-order summaries | Source and privacy discipline | Manager review |
[05]Boundariessource-backed handbook section+ open- close
Do not delegate prices, refunds, disputes, safety signoffs, contract changes, or private customer handling. Use fictional or sanitized examples during training.
[06]Simulation Examplesource-backed handbook section+ open- close
Synthetic scenario: a repair crew creates a customer update draft from approved work-order notes; manager reviews before sending.
[07]Diagnostic Checklistsource-backed handbook section+ open- close
- +Which updates repeat?
- +Which data is excluded?
- +Which owner reviews are required?
- +Which workflow is safe at L1 draft?
- +Which staff need role practice?
[08]Fictional/Synthetic Sample Report Teasersource-backed handbook section+ open- close
Fictional/synthetic sample: "Local Service Customer Update Workflow." Shows work-order draft support and review gates. It is not customer evidence.
[09]Recommended AequAI Pathsource-backed handbook section+ open- close
AI Literacy Training -> Department AI Pilot Design -> AI Workflow Simulation Lab for team workflows.
[10]30/60/90-Day Roadmapsource-backed handbook section+ open- close
30 days: one customer update workflow. 60 days: SOP drafts. 90 days: team playbook and simulation decision.
[11]Public-Safe Wording Notessource-backed handbook section+ open- close
Use reviewed drafts, service workflows, and owner approval language.
$ aequai next --map-business
Use the handbook as a starting map.
Start with one workflow, one review owner, one data boundary, and one evidence log. Expand only after a reviewed pilot shows what to proceed with, shrink, park, or stop.