"Tech On the Way" ETA Notifier
A one-tap tool where a dispatcher or tech sends a friendly "on the way" message with a safe ETA window and the tech's name and photo, so customers are ready and the office stops fielding "where are they?" calls.
A logged-in tool where a dispatcher picks a stop, confirms the ETA window and tech details, approves, and sends one en-route message per stop - with consent, quiet hours, duplicate guards, and a full audit trail.
Before you start
- A free Supabase account
- A free Resend account (or a verified sending domain)
- A Vercel account for deploying
- The day's stops in a spreadsheet or CSV (customer name, contact, and a rough ETA)
The problem this kills
Your phone never stops. Customers call the office to ask "is the tech still coming?" and "what time again?" while your dispatcher is trying to actually dispatch. Techs run late, nobody warns the customer, and you arrive to a locked door or an annoyed homeowner who left for lunch. Meanwhile your CSRs burn half the day on status updates that a single text or email could have prevented.
The fix is boringly simple: one tap that sends the customer a friendly "Jordan is on the way, expect them between 1:00 and 3:00" message - with the tech's name and photo - before the truck rolls. But the cheap versions either spam customers, send exact-minute promises you can't keep, fire twice for the same stop, or ignore quiet hours and consent. This tool does it the safe way, and a person always confirms before anything sends.
What you'll build
A small, password-protected web app for your dispatch desk and field techs. You load the day's stops (from your scheduling system's export or a plain spreadsheet), pick a stop, and the tool drafts a clean en-route message with a safe arrival window and the assigned tech's name and photo. You eyeball it, confirm the recipient, and approve - only then does it send through Resend. Every send is logged with who sent it and when, and the same stop can't be notified twice. At the end of the day you export the full notification log as a CSV.
What's inside the Implementation Plan
The plan opens by interviewing you about your business - how you schedule, what your stops actually look like, your quiet-hours and consent rules, how you express ETAs, and your messy real-world exceptions - then tailors the data model, the message wording, and every build step to your answers. It is not a generic template; it becomes your notifier. From there it walks you step by step, each step ending with a ready-to-paste prompt for your AI coding agent (Claude Code). You'll set up login, the stops table, the draft-and-confirm screen, the safe ETA window logic, quiet-hours and consent checks, the duplicate guard, the audit log, and the CSV export and import fallback.
The governance it includes (this is the point)
- Login so only your team can use the tool.
- Row-level security so each company only ever sees its own stops and logs.
- A human approval gate - the tool drafts the message, a person reviews the recipient and ETA window and approves, and only then does it send. No automatic blasting.
- A duplicate guard so the same stop can't get two en-route messages.
- Consent and quiet-hours checks so you never message someone who opted out or text/email at 6 a.m.
- A complete audit trail - who sent what, to whom, and when - exportable as CSV.
Who it's for
Dispatchers, technicians, and CSRs at any field-service business - HVAC, plumbing, electrical, pest control, appliance repair, cleaning, landscaping - who want fewer "where are they?" calls and happier customers, without buying a heavyweight platform.
You've got this - paste the first prompt and let the agent interview you.