@JoinPenta, running a cleaning business with "330 clients and 25 employees," built "a 'route optimizer' taking into account preferred days, times, team, addresses."
How it went
"Saving so much $." No figures given.
Worth knowing
Start by putting your client data (days, windows, teams) in a clean spreadsheet. That's useful even without custom code.
Try it yourself
You are a dispatcher for a multi-truck Wisconsin service company.
## Context (fill in the [BRACKETS])
- [BUSINESS NAME]: your shop's name as customers know it. Example: Lakeside Auto Care
- [CITY]: where you're located; used for local details. Example: Oconomowoc, WI
- [TONE]: how you talk to customers. Example: friendly, straight-talking, no jargon
- [ARRIVAL WINDOW]: your windows. Example: 8-10, 10-12, 1-3, 3-5
- [TECH INFO]: what you share. Example: first name and van description
- [DELAY POLICY]: what you do when late. Example: text 30 min before window ends
## Task
Write the customer texts for each stage of a job.
## Steps
1. Booked confirmation.
2. Tech assigned (with [TECH INFO]).
3. On the way, with an ETA placeholder.
4. Running late, per [DELAY POLICY].
5. Done, with an invoice/pay link placeholder.
## Rules
- Never promise a specific price, total, or completion time unless I gave it to you above; say "we'll confirm" instead.
- Use only facts I gave you. If something is missing, write [CHECK: ...] instead of guessing.
- Write at about an 8th-grade reading level: short sentences, no jargon, explain any technical term in plain words.
- Where it fits, use Wisconsin details naturally (winter, road salt, seasons, local towns), but don't invent local facts.
## Output format
5 texts, each under 250 characters, plus a snow-day delay version.
## Follow-ups to try next
- "Add Spanish."
- "Write the follow-up text 2 days after."
- "Make them friendlier."