R
Field service dispatch & operations
RoutelyOS is dispatch and scheduling software for home service businesses — gutter cleaning, pressure washing, and beyond. Auto-dispatch that skips unpaid jobs, live route optimization, franchise territory management, and worker payouts, in one system instead of six spreadsheets and a group text.
Why RoutelyOS
Territory boundaries and franchise scoping are enforced at the database level, not stitched together afterward with a reporting dashboard on top of separate accounts.
A crew is never sent to a job that hasn't cleared payment — checked before dispatch, not flagged or cancelled after the fact.
Built for a 2–6 truck operation that's outgrown a spreadsheet but doesn't need a sales-gated, multi-week enterprise rollout to get started.
What it does
Six pieces that used to be six spreadsheets, one system that already talks to itself.
Jobs get assigned automatically based on distance, worker equipment, and availability — and dispatch explicitly skips any job where payment is still pending. A crew never gets sent to a job that hasn't cleared.
Routes are ordered against real road data, not a straight line on a whiteboard, and re-ordered the moment a job gets added or cancelled mid-day.
Draw territory boundaries, keep dispatch scoped to the right franchise, and see evictions and overlaps before they become a customer-facing problem.
Stripe Connect payouts to crews, card-on-file billing for customers, and server-side price verification on every checkout — not a bolt-on invoice spreadsheet.
Workers complete jobs, capture GPS-verified photos, and keep working offline in a basement or dead zone — everything syncs the moment they're back online.
Customers can reschedule or cancel through a secure link — no more 'call the office' for a simple change, and fewer no-shows because of it.
A handful of the routine dispatch decisions — routing suggestions, first-pass complaint triage — are AI-assisted under the hood. It's there to remove busywork from a dispatcher's day, not to replace the judgment calls that still need a human.
Who it's for
Not a general-purpose CRM stretched to fit field service — dispatch and routing were the starting point, not a bolt-on.
Security
Not a marketing claim — the specifics of how it's enforced.
All 44 database tables run under Postgres RLS with scoped policies — the anon key cannot read jobs, workers, or customer data outside its own franchise.
Every webhook is HMAC-SHA256 verified with constant-time comparison, and processed idempotently so a retried event can't double-charge or double-refund.
The price a customer is charged is always re-checked against the database at checkout — a tampered client-side amount is rejected, not trusted.
Every public API route is rate-limited and logged; login attempts lock out after 5 failures for 15 minutes.
RoutelyOS is in early access. Tell us how many crews you run and what's actually slowing you down, and we'll walk you through it directly — no seat-count guessing games.
FAQ
No. Auto-dispatch explicitly skips any job where payment status is still pending — a crew never gets sent to a job that hasn't cleared payment. That's a hard rule, not a setting.
The field app keeps working offline — job updates and photos queue locally and sync automatically the moment the device reconnects.
Yes — territory boundaries, franchise-scoped dispatch, and per-franchise reporting are built in, not an add-on tier.
RoutelyOS is in early access and pricing is scoped to your business size and number of crews — request a demo and we'll walk through it directly rather than guess at a number that doesn't fit.
Yes — every table is protected by row-level security scoped to your franchise. Cross-tenant reads are blocked at the database layer, not just in the app.