Dispatch board · London

Dispatch board for taxi fleets in London

Single-screen live console with WebSocket updates and AI Copilot inline. Configured for Transport for London (TfL).

Dispatch board in London is the single-screen live console with websocket updates and ai copilot inline, configured against Transport for London (TfL) and the operating reality of a 105.0k-vehicle market. TaxiCloud's dispatch board is single-screen by design: drag-to-assign, keyboard-first job actions, WebSocket-driven live updates from Reverb, AI Copilot inline. Designed for the 23-hour booking peak and the controller workflow that runs it. For London specifically, the feature reads from regulator-aware booking, dispatch, and reporting surfaces — no bolt-on integration, no separate console.

Dispatch board in London — the operating reality

Dispatch board ships against the Greater London operating geography as a structural object. Most dispatch consoles still ship with a polling refresh model: every five seconds the page asks the server for state and re-renders. That looks fine in a demo and breaks under real operating load. TaxiCloud's dispatch board uses WebSocket subscriptions via Reverb — every state change in the live operation pushes to the console within 200ms, with no refresh flicker, no polling overhead, and no stale data. Driver pin movements, job-status changes, customer SMS deliveries, and AI Copilot suggestions all land continuously. In London, the feature posts cleanly against Transport for London (TfL) quarterly returns, vehicle inspection cycles, and the 105,000-vehicle scale that defines the market. LHR + LGW + STN + LCY + LTN airport flows integrate natively where applicable.

How TaxiCloud delivers dispatch board in London

Operators in London typically run dispatch board on TaxiCloud after a 6-10 day migration off iCabbi, Autocab, Cordic, or TaxiCaller. The single-screen design is the second axis. Most controllers run multi-monitor setups today because legacy consoles split function across multiple windows: queue here, map there, customer record in a modal, settlement in a separate tab. TaxiCloud's board collapses the primary controller workflow onto one screen with the secondary surfaces in peripheral view (settlement, council-licensing flags, exception queues). The result is a 47% reduction in time-to-assign measured across pilot fleets — controllers are not navigating, they are operating. The dispatcher impact is highest in the London operating tempo because Transport for London (TfL) compliance overlays the standard PHV regulatory posture, and dispatch board surfaces the resulting reports through the same dispatch flow rather than as a separate finance task.

FAQ

Dispatch board in London — questions answered.

How does Dispatch board work in London?: Dispatch board in London reads from the live dispatch board, the customer-facing booking widget, and the Transport for London (TfL) compliance reporting layer in a single tenant. Subscribes to live state via Reverb WebSockets — no polling refresh. The London configuration is preset for the city's 105,000-vehicle market and the Greater London operating geography.
Is Dispatch board compliant with Transport for London (TfL)?: Yes. Dispatch board is calibrated for Transport for London (TfL) reporting, audit, and renewal cycles. Vehicle inspection deadlines, driver-licence audits, and the local quarterly return format ship pre-configured. Format updates land in-sprint when the regulator changes requirements.
What does Dispatch board cost for a London fleet?: Dispatch board ships on every TaxiCloud plan — Starter through Pro Ultra. Transparent £49-£349/month pricing. Most London fleets run Pro (£149/€55/$59/A$89 month) or Pro Max (£349/€395/$449/A$629 month). No setup fee on Starter or Pro; month-to-month contracts; dispatch board configuration in London is included.

Ready when you are

Dispatch on autopilot.

14-day free trial. No card. Cancel anytime.

47 fleets joined this month · Talk to sales