Trades and home services
Fictional internal demonstrationAn after-hours request gets a next step before the owner returns to the desk.
At 7:42pm a homeowner uses the after-hours request path, by web form or by texting the shop's SMS keyword, with a problem that is annoying rather than dangerous. The crew is away and the office is empty. On most evenings that request waits until somebody has time to sort it out tomorrow.
Before morning the homeowner has picked a next-day window against real crew capacity, and the job record is waiting on the morning list.
what actually ran
Step by step, without the owner in the middle.
After-hours intake log
One fictional evening, from after-hours request to the morning list.
- 19:42
After-hours request captured
Structured reply sentWeb form submission, SMS keyword also accepted. Details attached to a new job record.
- 19:42
Structured reply offers the two real paths
Awaiting choice“We are closed. Book a visit window, or mark this as an emergency.”
- 19:51
Customer books a next-day window
ScheduledWindow selected against real capacity, not a generic callback promise.
- 19:51
Job record carries the whole intake
Ready for morningAddress, described problem, photos, and the chosen window on one record.
- 07:05
Morning list is already built
DispatchedOvernight intake sits in the day's order. Nobody rebuilds it from memory.
Held for the owner: caller describes a possible gas smell
Safety language is never auto-scheduled. The record is flagged and surfaced for a human call back.
- Rule
- Non-emergency bookings cannot exceed the crew capacity the owner set.
- Exception
- Safety language is flagged for a human call back, never auto-scheduled.
- Check
- A test emergency submission must reach the on-call number with full job details.
Illustrative workflow · fictional business and data · subject to tool compatibility and written scope.
what stays true after handoff
- Emergency routing is by on-call rota, not by whoever answers first.
- Non-emergency slots respect crew capacity limits set by the owner.
- A quote expires on a stated date rather than staying open indefinitely.
- Maintenance reminders send once per season, with an opt out in every message.
what it will not do
It will not answer the phone. It routes structured web and SMS requests and gives each one a next step, and it never pretends a person is on the line.
- It does not answer the phone. It routes structured requests, not live calls.
- It does not price jobs. The owner sets the quote template and the rates.
- It does not replace a dispatcher for complex multi-crew scheduling.
the system in this story
Booking-First Website + System · $12,000
An eight-page site with clear routing across services and staff, local-search foundations, and the full connected journey behind it. Timeline: 3 weeks.
other stories