RapidCloud Dispatch schedules technicians and jobs, then optimises their routes using live traffic data. A watcher continuously checks every upcoming appointment for delay, and an autopilot agent reassigns work to a teammate when someone calls in sick or runs late, notifying the customer, the original worker and the replacement automatically. Managers drag jobs on a calendar or swimlane board; workers and customers interact through role-scoped chat in Dutch or English.
Your dispatch board, on autopilot.
Field-service days never go to plan. A van breaks down, traffic stalls on the motorway, a technician calls in sick at 7am. RapidCloud Dispatch handles the replanning so your ops desk doesn’t have to.
Every upcoming job is checked against real traffic every five minutes. When a route slips past your threshold, you get a proposal — or, for big disruptions, the autopilot reassigns the work to a teammate who can still make the window and notifies everyone affected.
Managers drag jobs on a live calendar and swimlane board. Workers get a mobile chat that understands plain Dutch. Customers confirm reschedules with a single magic-link, no account required.
EU-hosted, multi-tenant, traffic-aware from the first job.
→ Book a 20-minute dispatch walkthrough
Under the hood▾
Engine. Routing runs on Google Routes API v2 (computeRoutes, TRAFFIC_AWARE_OPTIMAL) with predictive departureTime, plus Geocoding and Maps JS. A systemd timer fires every 5 minutes, mints an HS256 JWT, and calls /api/routes/preview per appointment; drift past a per-tenant threshold writes a replan_events proposal (default 15 min) or, past a higher threshold (default 30 min), fires the dispatch-autopilot agent. Coverage ranking is deterministic in lib/coverage.ts — project members first, tenant-wide fallback gated by policy, scored on window feasibility, travel time, skill match and numeric swap cost. POST /api/coverage/swap does an atomic reassign + route refresh + three notifications.
Stack. Next.js 16 standalone on Debian 13 / Node 22, Tailwind UI, Supabase Postgres (dispatch schema, 10 tables, PostgREST). Four role-scoped agents (customer/worker/manager/autopilot) run in rc-agents over a 14-endpoint manifest.
Multi-tenancy. App-layer JWT auth, tenant-scoped at every query via effectiveTenantId + assertSameTenant; operator tenants get cross-tenant scope. Customers authenticate per-appointment by signed magic-link. EU-hosted throughout.
