Every TaxiCloud question, answered.

Not by default. Every Copilot suggestion surfaces with a plain-English explanation; dispatchers approve in one click. As trust builds, specific suggestion classes (low-risk SMS drafts on flight delays, for example) can be configured to auto-execute, but auto-execute is opt-in rather than default. The audit trail logs every accepted suggestion.

Copilot uses a multi-model architecture: a primary commercial LLM for natural-language reasoning, plus a custom fine-tuned reranker for action prioritisation. We do not retain prompts for training, and Pro Ultra customers can opt for regional model routing or self-hosted models for fully in-region inference.

Customer PII is masked before any data leaves the dispatch boundary for LLM inference. The Copilot reasons about pseudonymous booking IDs, not customer names or contact details. SMS drafts include the customer name, but the draft generation context only sees a placeholder. Pro Ultra can run on dedicated infrastructure where no inference data leaves your tenant.

Yes. The Copilot configuration screen lets you enable or disable suggestions per class: reassignments, SMS drafts, terminal-queue updates, no-show predictions, ETA shifts. Each can be set to off, suggest-only, or auto-execute. Granular per-base and per-shift configuration is available on Pro Max.

Currently in private beta. Public App Store listing targets 2026 Q3. Operators on Pro and above get private TestFlight access during beta. Android remains the primary platform — most UK and Ireland PHV driver bases are Android-majority.

Offline tolerance is first-class. The app queues GPS pings, job-state events, and chat messages locally when signal drops; on reconnection, the queue flushes in order to maintain a continuous trail. Tested in pilot fleets running M6 corridor and Edinburgh Old Town stretches with known coverage gaps.

Yes. Voice-prompt mode reads incoming job details aloud and lets drivers accept or decline by voice command. Configurable per driver. Particularly valuable during heavy traffic or for drivers using Bluetooth headsets during longer shifts.

Yes, on Pro Max (£349/mo). Drivers see your fleet name on the Play Store, during onboarding, and on every screen. Internal dispatch operator console remains TaxiCloud-branded — that is operator tooling, not driver-facing.

Yes, on Pro (£149/mo) and above. App Store name, icon, colours, copy tone — all your fleet's. Published under your developer account (we provide setup if needed). Updates ship through our release pipeline with your branding intact.

Stripe natively (cards, Apple Pay, Google Pay, Link), PayPal, plus account-pay for corporate travellers. Cash is supported for bookings where the customer prefers cash payment to the driver. Adyen and Square integrations are roadmapped for 2026 Q4.

WebSocket-driven via Reverb. Driver pin position updates land in the passenger app within 200ms of the driver's GPS event, no polling refresh, no "refreshing now..." UX. ETA updates whenever the driver's route ETA shifts materially.

Yes. Individual receipts download as PDF; full ride history exports as CSV. Account-pay travellers see statement-level views aggregated per corporate account, with expense codes and cost-centres visible. Xero and QuickBooks integrations push the same data automatically on Pro Max.

Stripe natively (cards, Apple Pay, Google Pay, Link), PayPal, account-pay for corporate travellers, and cash. Adyen and Square integrations are on the 2026 Q4 roadmap. Stripe Connect is supported for fleets where drivers are independent contractors with their own Stripe accounts.

The reconciliation dashboard matches Stripe payouts to driver settlements automatically, surfaces unmatched items, and produces a closed end-of-day report. Typical 100-vehicle fleet reconciles in under four minutes. Pro Max ships scheduled reconciliation emails to the finance team.

Chargebacks route to the operator dashboard with full booking context: driver GPS trail, customer SMS history, fare calculation, payment metadata. Stripe Radar evidence packs auto-generate. Chargeback win rate across pilot fleets sits at 78%, well above the 35% industry baseline.

Yes. Drivers connect their own Stripe accounts during onboarding; settlement payouts route directly to the driver's Stripe account, the operator takes their commission off the top. Available on Pro Max. Tax forms, 1099/Form-A reports for fleets with US drivers, are roadmapped Q1 2027.

Yes — the single-screen design is the recommended primary, but the board supports detaching the map, settlement, or exception queue to a secondary monitor if controllers prefer that. Most controllers transition to single-screen operation after 1-2 weeks of use.

The board falls back to a 5-second polling cadence on disconnect, surfaces a clear warning banner, and auto-reconnects when WebSockets come back. State sync runs on reconnect to ensure no events are missed during the disconnect window.

Yes, with caveats. The full controller workflow assumes a 1440×900 minimum viewport. iPad Pro and Surface Pro work well; smaller tablets degrade gracefully but lose the peripheral surfaces (settlement, exception queues) which collapse into menus.

Yes. Pro Max ships per-controller keyboard shortcut customisation. The defaults are calibrated for ex-iCabbi and ex-Autocab controllers (J, R, S, F, M, Tab follow incumbent conventions), so retraining is minimal.

13 months by default. Pro Ultra customers can extend retention to 7 years for insurance and regulatory compliance use cases. Replay is scrubbable by timestamp on the operator dashboard and exportable as KML or GeoJSON for external analysis.

Yes. Common patterns: meet-and-greet fee triggers when driver enters airport terminal zone; surcharge applies when route enters London ULEZ; corporate-account boundary checks. Geofence events post to the booking record and surface on the customer invoice automatically.

The driver app queues GPS pings locally during offline periods (up to 100+ events buffered) and flushes the queue in order on reconnection. The replay history shows continuous trails even through coverage gaps. Geofence events trigger on flush rather than in real-time during offline windows.

Yes. The utilisation dashboard exports driver hours, idle vs busy time, peak coverage gaps, and zone-by-zone utilisation as CSV or PDF. Pro Max ships scheduled email reports and Power BI / Tableau direct-query connections.

Pro (£149/mo) supports brand colour, logo, font, and copy customisation through the dashboard. Pro Ultra (custom) supports full custom CSS injection for pixel-perfect integration with bespoke websites. The widget HTML structure is documented for advanced customisation.

Yes. The widget is a one-line script tag, which works on any platform that supports custom HTML embedding. We have customers running on WordPress, Wix, Squarespace, Webflow, Framer, Shopify, and bespoke React sites. Detailed integration guides for the major platforms are in our docs.

Yes. Corporate-account number, expense code, cost-centre, and arbitrary custom fields can be configured per booking flow. Fields validate against the corporate account's expected values. Available on Pro Max for corporate workflow features.

Yes. English (UK and US variants), Irish English, and Welsh ship out of the box. French, German, Spanish, and Polish are roadmapped for 2026 Q4. Custom language packs available on Pro Ultra for fleets serving specific tourist demographics.

32 UK and Irish PHV licensing authority report formats by name, including TfL operator monthly returns, all major UK city councils (Manchester, Birmingham, Leeds, Liverpool, Sheffield, Edinburgh, Glasgow, Cardiff, Belfast, Newcastle), and NTA Ireland SPSV formats. New formats land in-sprint when an operator requests one.

Configurable per account: cadence (monthly, weekly, fortnightly), billing email, expense-code breakdown, cost-centre allocation. PDF generates and ships automatically; Xero / QuickBooks integration posts the same data into accounting systems. 84% of corporate invoices auto-reconcile.

Yes. Pro (£149/mo) supports KPI selection from a curated library of 24 metrics. Pro Max adds custom metric definitions and per-base / per-shift dashboards. Pro Ultra ships full BI tool integration via Power BI and Tableau direct-query.

Yes. The Reporting API exposes all the data behind the dashboard and reports as authenticated REST endpoints. Pro and above ship API access; rate limits are generous (10,000 requests / minute) and webhook subscriptions cover real-time use cases.

LHR (all terminals), LGW North and South, STN, LCY, LTN, MAN T1-T3, BHX, EDI, GLA, DUB. Adding a new airport — pickup zones, pre-booked rank rules, flight ingest — takes one configuration update and lands in-sprint.

FlightAware integration polls arrival status. ETAs auto-shift in the dispatch board within 30 seconds of a delay being announced. AI Copilot drafts SMS to waiting passengers in under one minute. Across pilot fleets, on-time terminal pickup rate sits at 97.4%.

Yes. Meet-and-greet is a first-class billable object. The driver taps when they reach the terminal pickup zone; the fee posts to Stripe; the customer invoice itemises it separately. Across pilot airport fleets, meet-and-greet revenue capture lifted 18% post-TaxiCloud.

Respected natively. The dispatch flow validates pre-booked status before routing drivers to LHR or LGW pickup zones. Walk-up jobs route to alternate pickup areas where applicable. Pro Max ships the full airport rule set; Pro Ultra adds custom airport rule configuration.

Yes. TfL operator monthly returns, PHV driver compliance audits, vehicle inspection tracking, ULEZ and Congestion Charge zone awareness ship out of the box. The compliance content is maintained quarterly with format updates landing in-sprint.

Yes. Every UK PHV licensing authority is supported by name — Manchester, Birmingham, Leeds, Sheffield, Liverpool, Edinburgh, Glasgow, Cardiff, Belfast, Newcastle. Adding a new authority's report format takes one sprint when an operator requests one.

Pro at £149/month covers up to 25 drivers including AI Copilot, full council compliance reporting, customer + driver apps, white-label, and Stripe + PayPal payments. No setup fee, month-to-month contracts. Most fleets at this size find Pro is the sweet spot.

The 14-day trial is fully self-serve and tenant-isolated. Common pattern: run a small driver subset (typically airport or executive segment, where AI Copilot impact is largest) on TaxiCloud for two weeks alongside the existing platform. No card or contract required. Migration is 7-10 days white-glove if you decide to switch.

Yes — every UK council is supported by name. The hackney waybill generates per-driver per-shift in the council-expected format. Format updates land in-sprint when a council changes requirements. The compliance team maintains the content quarterly.

Yes. Drivers are first-class objects with multiple licence holdings. Bookings route to the correct mode based on rules (e.g. pre-booking flows route PHV; rank-based dispatch routes hackney). Mixed-licence drivers are common in UK regional fleets and TaxiCloud handles them natively.

Drivers mark availability at specific ranks via the driver app. The dispatch board surfaces rank queues with driver position; controllers can rank-assign manually or let the system auto-assign by rank arrival order. Available on Pro and above.

Yes. Plate renewal deadlines track on driver records and surface as pending items on the dispatcher's exception queue ahead of expiry. Configurable per-council renewal rules; the compliance content tracks council-specific renewal cadences.

Every executive booking has a per-account SLA target (configurable per corporate contract, typically 5-minute pre-arrival). Exceptions surface on the dispatch board's exception queue in real time. Post-shift and post-week SLA reporting rolls up per corporate account on the Reporting layer.

Pre-arrival confirmation prompt, vehicle-presentation checklist, branded customer-greeting prompts, in-app cabin temperature / preference notes from the booking, pre-paid hourly chauffeur slot tracking. Available on Pro Max and configurable per executive corporate account.

Yes. Multi-tenant architecture supports separate executive sub-brand under one parent operator on Pro Ultra: separate domain, separate customer app, separate pricing. Common pattern is mixed standard PHV + executive sub-brand under one ownership group.

Pro Max at £349/month covers up to 100 drivers including executive features. Pro Ultra (custom) for the largest executive operations with dedicated infrastructure, custom SLA workflows, and named SAML SSO. Most executive operators run Pro Max with elements of the Pro Ultra feature set surfaced on request.

Travellers book against corporate account numbers; the booking flow bypasses card payment; the cost charges to the corporate account directly. Monthly statement generation runs automatically with PDF and Xero/QuickBooks pushes. Pro (£149/mo) ships account-pay; Pro Max adds approval workflows.

Yes. Above-threshold bookings, restricted routes, after-hours bookings, specific traveller groups — all configurable per corporate account on Pro Max. Approvers receive email or in-app notifications; bookings sit in pending state until cleared.

Yes. Native integrations push monthly corporate statements with full booking detail, expense codes, and cost-centre breakdowns. CSV exports cover the long tail (Sage, NetSuite, FreshBooks). 84% of corporate invoices auto-reconcile across pilot fleets running the integrations.

Pro Ultra ships SAML SSO for enterprise corporate accounts plus SCIM provisioning for bulk traveller onboarding/offboarding. Pro Max handles up to 500 travellers per account via CSV bulk import. Traveller credentials revoke immediately on offboarding.

Drivers are flagged as safeguarding-compliant on the driver record with DBS expiry date tracked. Only safeguarding-compliant drivers can be offered school-run jobs — the dispatch flow enforces this at offer time. DBS renewal deadlines surface as pending items on the dispatcher's exception queue.

Yes. Recurring bookings repeat per the school's calendar with auto-pause for half-terms, holidays, and INSET days. Customisable per school contract. Pro Max ships full recurring-booking infrastructure with school-calendar awareness.

Invoices align to school terms (typically three per academic year for UK state schools, varied for independent schools). Half-term and holiday breaks are excluded automatically. The reporting layer separates school-run revenue from standard PHV for contract review reporting.

Yes. School-run customer accounts can have authorised safeguarding contacts who receive SMS and in-app notifications about journey start, in-progress, and completion events. Configurable per school contract on Pro Max.

Yes. Vehicle types are first-class objects: WAV, step-up, transit-style, standard. Bookings match passenger accessibility requirements to vehicle capability automatically. The dispatch board surfaces accessibility flags so controllers do not assign incorrectly.

Yes. Local authority PSV compliance reports — driver certifications, vehicle inspections, journey logs — generate in the formats authorities request for community-transport contracts. Compliance content maintained quarterly per authority.

Two patterns supported: NEMT as a sub-brand under the parent operator (Pro Ultra multi-tenant), or as a tagged service tier within the main fleet (Pro Max). Reporting separates NEMT revenue and PSV compliance metrics in both patterns; operational KPIs roll up to ownership.

Yes. Driver records support arbitrary certification tracking with expiry dates. Common patterns: medical passenger training, first-aid certification, manual handling. Certification expiry surfaces on the dispatcher exception queue ahead of expiry.

LHR, LGW, STN, LCY, LTN, MAN, BHX, EDI, GLA, DUB ship pre-configured. Adding a new airport — terminal pickup zones, pre-booked rank rules, flight ingest — takes one configuration update and lands in-sprint when an operator requests it.

FlightAware integration polls arrival status. When a delay is announced, ETAs auto-shift in the dispatch board, AI Copilot recommends reassignments ranked by waiting-passenger impact, drafts SMS to passengers, and updates terminal queue positions for drivers — all in one board action.

Yes. Meet-and-greet is a first-class billable object on the customer invoice with its own surcharge rule. Drivers tap a meet-and-greet button when they reach the agreed terminal zone, the fee posts to Stripe, and the customer invoice itemises it separately from the fare.

No. Flight ingest, terminal pickup zones, meet-and-greet billing, and pre-booked rank rules are included in the Pro Max plan at £349/month. Pro Ultra adds custom integrations for niche airports and corporate-account meet-and-greet workflows.

Yes. TfL operator monthly return formats, PHV driver compliance audits, vehicle inspection tracking, and ULEZ/Congestion Charge zone awareness ship out of the box. The compliance content is maintained quarterly.

Yes. We support every UK PHV licensing authority by name — Manchester, Birmingham, Leeds, Sheffield, Liverpool, Edinburgh, and more. Adding a new authority's report format takes one sprint when an operator requests one.

On Pro (£149/mo) and above: your domain, logo, colours, app name on customer-facing booking widget, customer app, customer emails, and SMS templates. Driver-app white-label requires Pro Max (£349/mo).

Pro at £149/month covers up to 25 drivers including AI Copilot, full council compliance reporting, customer + driver apps, white-label, and Stripe + PayPal native payments. No setup fee, month-to-month contracts.

Yes. Native integrations push monthly corporate statements with full booking detail, expense codes, and cost-centre breakdowns. Structured CSV exports cover the long tail of accounting tools (Sage, NetSuite, FreshBooks, etc).

Yes. Configurable per account: above-threshold bookings, restricted routes, after-hours bookings, or specific traveller groups can route to designated approvers before dispatch. Approval ships via email or in-app and the booking sits in a pending state until cleared.

Pro Max (£349/mo) ships full corporate-account features including approval workflows, Xero/QuickBooks integration, and per-account dashboards. Pro (£149/mo) ships account-pay billing and basic expense codes — sufficient for fleets where corporate is sub-20% of revenue.

Yes. Travellers are first-class objects scoped to their corporate account. Onboarding is bulk via CSV import or SCIM provisioning (Pro Ultra); offboarding revokes booking access immediately. SAML SSO is available on Pro Ultra for accounts that require it.

Pilot configurations run 12 bases with no measurable degradation. Pro Max (£349/mo) supports up to 100 drivers across bases; Pro Ultra (custom) lifts the cap and ships dedicated infrastructure for the largest multi-base groups.

Yes, with caveats. Same-authority pooling (e.g. Manchester proper + Trafford) is enabled by default. Cross-authority pooling (e.g. Manchester + Liverpool) requires explicit configuration and verification that drivers hold the appropriate licences in each jurisdiction.

Yes. Each base can have its own domain, customer app branding, customer email templates, and SMS sender ID. Pro Max supports up to 10 distinct brand surfaces under one tenant; Pro Ultra is unlimited.

Reports run per base or rolled up across the group. Revenue, driver utilisation, no-show rate, top corporate accounts, and council-compliance metrics are all available at both granularities. Exports are CSV or PDF; per-base scheduled emails are available on Pro Max.

Pro (£149/mo) ships customer-facing white-label: booking widget at your domain, customer iOS and Android apps under your fleet name on the stores, customer emails and SMS using your sender identity. The dispatch console and driver app remain TaxiCloud-branded internally on Pro.

We submit to the App Store and Google Play using your developer account credentials (we provide setup instructions if you do not have one yet). The app icon, name, screenshots, description, and colour scheme all reflect your fleet. Updates ship through our release pipeline but with your branding intact.

Yes, on Pro Ultra (custom). Each sub-brand has independent customer-facing surfaces — separate booking widget, separate customer app, separate email and SMS sender identities — under one parent operator. Used by franchise groups and sub-brand operations.

Yes. Pro Max (£349/mo) adds driver-app white-label: drivers see your fleet name on the Play Store, during onboarding, and on every screen. Internal dispatch operator console remains TaxiCloud-branded as it is operator-facing tooling.

Hotel airport feeder schedules ingest as scheduled route plans; FlightAware integration adjusts arrival times when flights slip; dispatcher console flags hotels affected and offers SMS-draft notifications.

Yes. Multi-stop campus loops handle as first-class route-plan objects with 4-8 pickup zones, rolling capacity management, and per-stop on-time arrival tracking.

Published £49-£349/month pricing (vs quote-only or per-vehicle for both incumbents), AI Copilot in the live dispatch flow, white-label customer-facing booking pages, council-licensing reports across UK PHV authorities. The migration path off either platform is 6-9 working days.

Yes. Event-driven shuttles (concert venue feeders, corporate event transport) configure as one-off or recurring route plans; AI Copilot pre-positions vehicles before predicted demand windows.

Yes. Both job types operate as first-class booking types on a single tenant. Drivers can be configured for taxi-only, courier-only, or both modes.

Driver app captures photo + e-signature at delivery; the captured evidence stores against the booking record and surfaces on the customer invoice. Photo + signature export available via API for retail/B2B integration.

Published £49-£349/month pricing including white-label and AI Copilot; integrated dispatch with traditional taxi work on the same tenant; UK and Ireland-specific compliance posture (council-licensing reports, NTA SPSV).

Yes. Restaurant batch delivery configures as multi-stop route plans with kitchen-collection and delivery legs; AI Copilot pre-positions drivers near restaurants during predicted demand windows.

Yes. Many operators retain the radio licence and base station as a contingency for the first 6-12 months. We have not had a customer revert to radio dispatch as primary post-migration, but the option exists.

7-10 working days end-to-end with phased driver-app rollout. Typical cohort sizes: 10-15 drivers per day. Driver retention through cutover averages 94%.

Yes. The cutover playbook includes 2-3 days of side-by-side training with the new dispatch board running alongside radio dispatch. Most controllers report comfort with the cloud board within 5-7 working days.

The Pro plan at £149/month covers up to 30 drivers including AI Copilot, dispatch board, customer app, and council-licensing reports.

Every booking carries a required vehicle class. Every driver-vehicle pairing carries a class certification. The dispatch console prevents cross-class assignments at the assignment step. Cross-class booking failures become structurally impossible.

Yes. Hourly hire is a first-class booking type with configurable overtime rules (typically 1.25× or 1.5× hourly rate after the booked window). Settlement reconciles overtime automatically.

Yes. White-label customer-facing booking pages on the operator's own domain ship standard from the Pro plan upward — with concierge-grade booking flow aesthetics.

Typically 6 working days. Executive Edinburgh's case study at /customers/executive-edinburgh documents the 6-day Cordic cutover playbook.

Driver records carry enhanced-DBS-check expiry as first-class fields. The dispatch board only assigns DBS-verified drivers to student bookings; non-DBS drivers structurally blocked from accepting at the assignment step.

Yes. England, Wales, Scotland, Northern Ireland, and Republic of Ireland term calendars ship pre-configured with automatic pause weeks for half-term and bank holidays.

Yes. Passenger-assistant assignment ships as a first-class booking field alongside vehicle accessibility configuration (wheelchair, harness, assistance dog). Structured contract billing aligns to local authority finance cycles.

Published £49-£349/month pricing (vs quote-only on TaxiCaller), UK + Ireland-native term calendars, enhanced-DBS structural enforcement, NHS / LA contract billing pre-configured. Migration off TaxiCaller takes 6-8 working days.

Vehicle records carry accessibility-configuration fields with structural enforcement at booking. Non-accessible vehicles structurally blocked from accepting bookings carrying accessibility requirements.

Yes. NHS-contract billing exports in NHS-finance-team-ready format on configurable monthly cycles. Per-trip safeguarding audit trail preserves.

Yes. Recurring bookings configure with route, accessibility requirement, passenger-assistant assignment, and NHS contract reference. Pause weeks for hospital admissions handle as first-class booking-state transitions.

Published £49-£349/month pricing, UK + Ireland-native NHS contracting, structural accessibility-config enforcement, integrated PHV-and-NEMT dispatch on the same tenant for operators running both segments.

Yes. TaxiCloud generates the TfL operator monthly return format, supports PHV driver compliance auditing, tracks vehicle inspection deadlines on the TfL calendar, and ships ULEZ and Congestion Charge zone awareness on the booking widget and dispatch board. The platform is used by London operators today and the regulatory content is maintained quarterly.

Yes. Airport pre-booking flows for LHR, LGW, STN, LCY, and LTN ship out of the box, including terminal-by-terminal pickup-zone routing and pre-booked-only rank rules. The AI Copilot ingests flight schedules and re-shuffles dispatcher ETAs when arrivals slip, drafting SMS to waiting passengers automatically.

Side-by-side: TaxiCloud ships AI Copilot in the live dispatch flow (neither incumbent does), transparent £49-£349/month pricing on the website (both incumbents are quote-only), and is independent of Uber (Autocab is Uber-owned since 2020). Migration is 7-10 days white-glove. Run the trial in parallel with your existing system before deciding.

Self-serve trial starts in under 10 minutes; production cutover takes 7-10 business days for a fleet up to 100 vehicles. Our migration team imports drivers, vehicles, customers, pricing rules, coverage zones, and historic bookings, then runs a parallel-run weekend for dispatcher training. Available on the Pro plan and above.

The Pro Max plan at £349/month covers up to 100 drivers including AI Copilot, multi-base coverage zones, Reverb live broadcasts, and a named onboarding manager. There is no setup fee, contracts are month-to-month with one month notice, and white-label is included. London fleets typically report 30-50% lower year-one cost vs iCabbi or Autocab.

Yes. Driver compliance audits, vehicle inspection logs, hackney waybill, and monthly council returns ship in Manchester's expected formats. The compliance content is maintained quarterly and updates land within one sprint when the council changes a format.

Yes. MAN terminal-by-terminal pickup zones, pre-booked-only rank rules, and flight-aware ETA reshuffling ship out of the box. The AI Copilot ingests MAN flight schedules and drafts SMS to waiting passengers when arrivals slip.

Side-by-side: TaxiCloud ships AI Copilot in live dispatch (Autocab does not), transparent £49-£349/month pricing on the website (Autocab is quote-only), and is independent of Uber (Autocab is Uber-owned since 2020). Migration is 9 days white-glove. Run the trial in parallel before deciding.

The Pro plan at £149/month covers up to 25 drivers including AI Copilot, full Manchester compliance reporting, MAN airport flows, and white-label customer-facing apps. No setup fee, month-to-month contracts. Most Manchester fleets report 30-50% lower year-one cost vs incumbents.

Yes. CAZ boundaries are first-class booking objects: customer-facing widgets surcharge transparently, the dispatch board flags before drivers cross, and AI Copilot can recommend non-CAZ routings when feasible. CAZ daily-charge tracking ships with the fleet reporting module.

Yes. Driver compliance audits, vehicle inspections, hackney waybill, and monthly council returns ship in Birmingham's expected formats. The compliance content is maintained quarterly with format updates landing in-sprint when the council changes requirements.

Yes. BHX terminal-aware pickup-zone routing, pre-booked-only rank rules, and flight-schedule-aware ETA reshuffling ship out of the box. The AI Copilot drafts SMS to waiting passengers automatically when arrivals slip.

The Pro Max plan at £349/month covers up to 100 drivers including AI Copilot, multi-base coverage zones across Birmingham, Solihull, and surrounding areas, full council compliance reporting, BHX airport flows, and a named onboarding manager. No setup fee, month-to-month contracts.

Yes. The platform is cloud-native on AWS and scales horizontally on demand — no capacity-planning calls required. Festival-season surges are well within tested operating range. AI Copilot is particularly valuable during surge periods, drafting customer SMS automatically when ETAs slip and recommending reassignments by impact.

Yes. Driver compliance audits, vehicle inspections, monthly council returns, and PHV-specific reporting ship in Edinburgh's expected formats. Old Town permit-vehicle-only zones are first-class boundary objects on the dispatch board and customer widget.

Yes. EDI terminal pickup-zone routing, pre-booked rank rules, and flight-schedule-aware ETA reshuffling ship out of the box. The AI Copilot ingests EDI flight schedules and drafts passenger SMS automatically on delays.

The Pro plan at £149/month covers up to 25 drivers including AI Copilot, council compliance reporting, EDI airport flows, and white-label apps. No setup fee, month-to-month contracts. Most Edinburgh fleets report 30-50% lower year-one run-rate cost vs incumbents.

Yes. TaxiCloud generates Glasgow City Council Hackney + private-hire quarterly return formats, supports driver compliance auditing under both licence classes, tracks vehicle inspection deadlines on the GCC calendar, and auto-suspends vehicles with lapsed plates from dispatch. Compliance prep typically drops from 6-8 hours per quarter on legacy systems to under 30 minutes.

Yes. Airport pre-booked flows for GLA and Glasgow Prestwick (PIK) ship out of the box, including pre-booked-only rank rules at GLA. The AI Copilot ingests flight schedules and reshuffles dispatcher ETAs when arrivals slip, drafting SMS to waiting passengers automatically.

Self-serve trial starts in under 10 minutes; production cutover takes 6-9 business days for a fleet up to 100 vehicles. The migration team imports drivers, vehicles, customers, pricing rules, GLA airport tariffs, and historic bookings, then runs a parallel-run weekend for dispatcher training. Available on the Pro plan and above.

The Pro plan at £149/month covers up to 30 drivers including AI Copilot, dispatch board, customer app, and Glasgow City Council compliance reports. The Pro Max plan at £349/month covers up to 100 drivers and adds white-label and a named onboarding manager. No setup fee on Starter or Pro, contracts are month-to-month, and white-label is included from Pro upward.

Yes. TaxiCloud generates Liverpool City Council Hackney + private-hire quarterly return formats, supports driver compliance auditing under both licence classes, tracks vehicle inspection deadlines, and auto-suspends vehicles with lapsed plates from dispatch.

Yes. Cruise-terminal arrival ingest treats clustered pickup waves as first-class objects: AI Copilot routes idle drivers toward the cruise terminal 8-12 minutes before manifest disembark times, dispatchers see the wave loaded into a single multi-pickup container, and meet-and-greet billing posts as a separate Stripe line item.

The AI Copilot ingests the Premier League fixture schedule and pre-emptively routes idle drivers toward Anfield or Goodison roughly 12 minutes before full-time. Surge pricing rules are configured per stadium and per fixture importance.

Self-serve trial starts in under 10 minutes; production cutover takes 7-9 business days for a fleet up to 100 vehicles. The migration team imports drivers, vehicles, customers, pricing rules including airport and arena-event tariffs, and a 180-day historic booking window.

Yes. Invoiced corporate accounts are first-class objects: PO-level booking notes, expense codes per booking, configurable monthly statements that export in finance-system-ready formats. Many Leeds operators run 60-120 corporate accounts on the platform.

Yes. TaxiCloud generates Leeds City Council Hackney + private-hire quarterly return formats, tracks vehicle inspection deadlines, and auto-suspends vehicles with lapsed plates from dispatch. Renewal notifications fire at 60, 30, and 7 days before expiry.

Yes. LBA airport pre-booked flows ship out of the box with terminal-aware queueing. AI Copilot ingests flight schedules and reshuffles dispatcher ETAs when arrivals slip.

7-10 business days from migration kickoff to full cutover for a fleet up to 100 vehicles. Self-serve trial starts in under 10 minutes; corporate-account migration is white-glove on Pro and above.

Yes. Vehicle CAZ-compliance status is a first-class record field. The booking widget surcharges based on CAZ entry; the dispatch board flags before non-compliant drivers cross the boundary; routes can be biased to keep non-compliant vehicles outside the zone.

Yes. TaxiCloud generates Bristol City Council Hackney + private-hire quarterly return formats, tracks vehicle inspection deadlines, and auto-suspends vehicles with lapsed plates.

Yes. BRS airport pre-booked flows ship out of the box with terminal-aware queueing. AI Copilot ingests flight schedules.

6-9 business days from migration kickoff to cutover for a fleet up to 100 vehicles.

Yes. TaxiCloud generates Cardiff Council Hackney + private-hire quarterly return formats, tracks vehicle inspection deadlines, and auto-suspends vehicles with lapsed plates.

AI Copilot ingests the Principality Stadium fixture and event schedule and pre-positions idle drivers across Cardiff Central, Cardiff Queen Street, and the Bay terminus 12-15 minutes before full-time. Surge pricing rules are configured per event class.

Yes. Customer-facing SMS templates are available in Welsh alongside English. Bilingual passenger preferences are stored per customer record.

6-9 business days from migration kickoff to cutover for a fleet up to 100 vehicles.

Yes. TaxiCloud generates DVA Northern Ireland operator quarterly return formats, supports Class A, B, and C licensing distinctions natively, and tracks vehicle inspection deadlines on the DVA calendar.

Yes. Dispatcher console flags the booking-source jurisdiction, customer-app pricing handles GBP/EUR currency switching, and SPSV/PHV-licensing reports separate cross-border journeys for the appropriate authority. Many Belfast operators run mixed Republic and Northern Ireland fleets on the platform.

Yes. Both airports' pre-booked flows ship pre-configured. AI Copilot ingests both airports' flight schedules and reshuffles dispatcher ETAs when arrivals slip.

7-9 business days from migration kickoff to cutover for a fleet up to 100 vehicles.

Yes. TaxiCloud generates Sheffield City Council Hackney + private-hire quarterly return formats, tracks vehicle inspection deadlines, and auto-suspends vehicles with lapsed plates from dispatch.

Yes. Vehicle CAZ-compliance status is a first-class record field. The booking widget surcharges based on CAZ entry; the dispatch board flags before non-compliant drivers cross the boundary.

AI Copilot ingests Bramall Lane and Hillsborough fixture schedules and pre-emptively routes idle drivers toward predicted demand 12 minutes before full-time. Surge pricing rules are configured per stadium.

7-9 business days from migration kickoff to cutover for a fleet up to 100 vehicles.

Yes. TaxiCloud generates Newcastle City Council Hackney + private-hire quarterly return formats, tracks vehicle inspection deadlines, and auto-suspends vehicles with lapsed plates from dispatch.

AI Copilot routes idle drivers across the Bigg Market, Quayside, and Diamond Strip zones 8-12 minutes before predicted demand spikes on Friday and Saturday 22:00-04:00. Surge pricing rules are configured per zone and per hour.

Yes. Vehicle CAZ-compliance status is a first-class record field. The booking widget surcharges based on CAZ entry; the dispatch board flags before non-compliant drivers cross the boundary.

6-9 business days from migration kickoff to cutover for a fleet up to 100 vehicles.

Yes. TaxiCloud generates Cambridge City Council Hackney + PHV quarterly return formats and tracks vehicle inspection deadlines.

Yes. Invoiced monthly billing, expense codes per booking, monthly Workday-and-SAP-Concur-ready statements. Cambridge operators typically run 12-25 corporate accounts on the platform.

Yes. STN airport pre-booked flows ship out of the box; AI Copilot ingests STN flight schedules; cross-county M11 corridor pricing rules configure structurally.

6-8 business days from migration kickoff to cutover for a fleet up to 60 vehicles.

Yes. ZEZ status is a first-class vehicle attribute. Booking widget surcharges based on ZEZ entry; dispatch board flags non-zero-emission drivers before crossing the boundary; routes can be biased to keep non-ZEZ-compliant vehicles outside.

Yes. Oxford City Council Hackney + PHV quarterly return formats ship pre-configured.

Yes. Both operate as standard corporate-account configurations with PO-level booking notes, expense codes, and Workday-ready monthly statements.

6-8 business days from migration kickoff to cutover for a fleet up to 80 vehicles.

AI Copilot routes idle drivers across the Lanes, seafront, and North Laine zones 8-12 minutes before predicted demand spikes on Friday and Saturday 22:00-04:00.

Yes. LGW airport pre-booked flows ship out of the box; AI Copilot ingests LGW flight schedules.

Yes. Brighton & Hove City Council Hackney + PHV quarterly return formats ship pre-configured.

6-9 business days from migration kickoff to cutover.

Yes. ABZ helicopter-rotation patterns ingest as scheduled bi-weekly demand. AI Copilot pre-positions drivers ahead of helicopter-arrival windows.

Yes. Corporate accounts for BP, Shell, Equinor, TotalEnergies operate as standard configurations with PO-level booking notes and Workday-ready monthly statements.

Yes. Aberdeen City Council Hackney + PHV quarterly return formats ship pre-configured.

6-9 business days from migration kickoff to cutover.

Yes. Driver license audits, vehicle inspection deadlines, and NTA Ireland quarterly returns ship in the formats the authority requests. The compliance content is maintained quarterly with format updates landing in-sprint when the NTA changes requirements.

AWS Frankfurt (eu-central-1). This meets GDPR data-residency expectations for Irish operators and EU-based corporate accounts. Pro Ultra customers can request dedicated infrastructure on AWS Dublin (eu-west-1) for fully in-country residency.

iCabbi is Dublin-headquartered and has the deepest Irish footprint in the category — that is real and we respect it. Where TaxiCloud differentiates: AI Copilot in the live dispatch flow (iCabbi does not have one), transparent €55-€395/month pricing on the website (iCabbi is quote-only), month-to-month contracts (iCabbi is multi-year). Migration is 7-9 days white-glove and tooling is built specifically for iCabbi exports.

Yes. Cross-border bookings work natively: customer-app pricing handles currency switching, dispatcher console shows the booking source jurisdiction, and SPSV/PHV licensing reports separate cross-border journeys for the appropriate authority. We have customers running mixed Republic and Northern Ireland fleets on the platform.

Yes. TaxiCloud generates NTA Ireland SPSV quarterly return formats automatically, supports SPSV driver licensing audits, and tracks vehicle SPSV plate validity. The 2025-updated NTA quarterly return format ships pre-configured.

Yes. Cruise terminal manifest ingest treats clustered pickup waves as first-class objects. AI Copilot pre-positions drivers 15-20 minutes before disembark times, accounting for Cobh's 25-minute distance from Cork city centre.

Yes. ORK airport pre-booked flows ship pre-configured with terminal-aware queueing. AI Copilot ingests Aer Lingus and Ryanair flight schedules.

6-8 business days from migration kickoff to cutover for a fleet up to 100 vehicles.

Yes. TaxiCloud generates NTA Ireland SPSV quarterly return formats automatically, supports SPSV driver licensing audits, and tracks vehicle SPSV plate validity. The 2025-updated NTA quarterly return format ships pre-configured.

AI Copilot ingests Galway International Arts Festival main-stage timings and pre-positions drivers across Eyre Square, the Latin Quarter, and Salthill 10-15 minutes before predicted demand surges. Surge pricing rules are configured per event class.

Yes. Galway Race Course event schedule ingest pre-positions drivers before predicted post-race demand spikes. Surge pricing rules are configured per race-day class.

5-7 business days from migration kickoff to cutover for a fleet up to 60 vehicles.

Yes. TaxiCloud generates NTA Ireland SPSV quarterly return formats automatically, supports SPSV driver licensing audits, and tracks vehicle SPSV plate validity.

Yes. SNN pre-booked flows, US pre-clearance terminal awareness, and the 25-kilometre Limerick-to-SNN dispatch radius are first-class objects. AI Copilot pre-positions drivers 30-40 minutes before transatlantic arrival times.

Thomond Park fixture schedule ingest pre-positions drivers in central Limerick 12-15 minutes before full-time. Surge pricing rules are configured per fixture class.

5-7 business days from migration kickoff to cutover for a fleet up to 60 vehicles.

Yes. The 2025-updated NTA SPSV columnar format ships pre-configured. Quarterly returns generate in under 15 minutes from a single action.

Yes. Cross-county routes configure with structural pricing rules; AI Copilot ingests both ORK and DUB flight schedules.

Yes. Bausch & Lomb, Pfizer, and other regional employers operate as standard corporate-account configurations.

5-7 business days from migration kickoff to cutover for a fleet up to 50 vehicles.

Yes. The 2025-updated NTA SPSV columnar format ships pre-configured.

AI Copilot ingests Kilkenny Arts Festival venue schedules and pre-positions drivers across central Kilkenny ahead of show-end crowd dispersal.

Yes. Cross-county routes configure with structural pricing rules; AI Copilot ingests both DUB and ORK flight schedules.

5-6 business days from migration kickoff to cutover for a fleet up to 30 vehicles.

Yes. Every completed trip emits the data fields required by the TLC's HVFHS trip-record submission. Records are stored for the seven-year retention window and can be exported as CSV or pushed via API to a third-party submitter.

Yes. Drivers self-check-in to the JFK hold; their position in the queue is reflected in the dispatcher console so airport trips are dispatched in queue order, not random nearest-driver order.

Yes — TaxiCloud treats vehicle class as a dispatch attribute, not a tenancy boundary. A single console can dispatch a mixed fleet provided the base holds the relevant TLC permits.

Drivers tap a single button in the driver app when they enter the LAX-it lot. The console reflects their queue position. When a curbside trip is dispatched, only the driver at the front of the relevant lane is offered the job.

Yes. A single base account can hold permits across multiple LADOT zones and surrounding cities; trips are routed to the nearest permitted vehicle, not the nearest vehicle by raw distance.

Yes — driver app, SMS, and rider booking widget all support English and Spanish. Dispatcher console is English-only.

Yes. The reports are pre-formatted to BACP's accepted submission schema and can be emailed direct to your compliance contact or exported for upload.

Every WAV-eligible trip dispatched to an accessible vehicle is tagged. Monthly summaries show credits earned, lost, and current balance — matching BACP's program accounting.

Yes. Affiliate bases share trip-out mechanics through the Aurora console. Each affiliate keeps their own pricing and driver pool; only the trip handoff is shared.

AWS US-West (Oregon) by default. SF operators with municipal contracts can request US-West-1 (Northern California) residency on the Pro Ultra plan.

Drivers enter the Aviation Operations holding lot and check in via the driver app. The Aurora console shows queue position per terminal; dispatch respects FIFO.

Yes. Grade and vehicle class are inputs to the routing engine, so battery-electric vehicles aren't penalized by being dispatched to climb-heavy pickups they can't make efficiently.

Yes. Driver app check-in to the central pool is supported; dispatch from the pool follows the order Massport's ground transportation system expects.

Yes. Pre-booked accessible trips are reserved against driver schedules at booking time and protected from on-demand dispatch when their pickup window opens.

Affiliate bases share trip-out mechanics through the Aurora console. The trip handoff is invisible to the rider.

Yes. Per-trip data is submitted in DFHV's accepted schema. Operators can export the same data for their own records.

Yes. GSA-published rates can be set as the corporate-account rate for federal customers; receipts are generated in the line-item format federal travel cards expect.

Surge multipliers are capped by DFHV rule; the platform enforces the local ceiling automatically so a runaway multiplier can't be invoiced.

The platform tracks each vehicle's SEA permit category and only dispatches eligible vehicles to airport pickups.

Yes. Both companies' expense systems accept the receipt format TaxiCloud emits; no per-customer integration is needed.

Yes. Grade and remaining battery range are inputs to the routing engine so unsuitable trips aren't offered to EVs.

PortMiami terminal queues are modeled like airport curbsides with cruise-turnover-aware capacity scaling. The console alerts dispatchers when ship arrival times will drive a queue surge.

By default Miami operators ship with Spanish-primary surfaces for riders and drivers; English is one tap away per profile.

Yes. Pre-bookings tied to a Brightline train number re-schedule automatically if the train delay feed shows a change.

Yes. The per-trip levy is calculated at trip completion and rolled into the monthly return the operator submits to the commission.

Drivers check in to T1, T2, or T3 feeder via the driver app. The Aurora console shows queue depth per terminal so dispatch decisions respect rank order.

Yes. WAT trips are tagged and counted against authorisation quotas; the monthly summary shows your position against the quota target.

Yes. Each driver's accreditation expiry is tracked; the system alerts ops 30 days before expiry and blocks dispatch the day expiry hits.

Stadium geofences are pre-populated. End-of-event egress is projected from attendance forecasts; vehicles are pre-positioned automatically.

Yes. MEL has the more complex staging (separate taxi rank vs. rideshare zone); both are supported per vehicle authorisation.

Yes. Per-trip levy is rolled into the monthly TMR return.

Trips from Brisbane to Gold Coast (or vice versa) can be trip-out'd to an affiliate base via the Aurora console with no rider-visible handoff.

Yes. Corporate-account billing supports the major construction JV expense systems with the receipt format their cards expect.

Yes. Per-trip levy rolls into the operator's monthly return.

FIFO charters are handled as pre-booked, shift-tied trips against dedicated driver pools; on-demand metro dispatch runs in parallel against separate capacity.

Yes. Each mining company's expense system accepts TaxiCloud's receipt format; pre-booked shift patterns are imported via CSV or API.

Yes. Accessible trips dispatched via Access Cabs subsidy are tagged so the subsidy entitlement is tracked.

Pre-booked transfers to the Barossa / McLaren Vale / Adelaide Hills are scheduled against driver shifts and supported as corporate-account work.

Yes. Stadium geofencing and end-of-event egress projection handle Adelaide Oval event days.

Yes. Trips ending in Brisbane can be trip-out'd to an affiliate base via the Aurora console without rider-visible handoff.

Pre-booked transfers from major hotel groups feed steady baseline; on-demand street pickups overlay during peak season.

Yes. ETA modelling uses live Transport for Queensland network state plus your fleet's historical pattern for the M1 corridor specifically.

Yes. Each terminal is a discrete dispatch context with its own driver queue. Drivers check in to the specific feeder via the driver app; the console shows queue depth per terminal.

Yes. The platform consumes live flight-status feeds; pre-booked airport pickups re-schedule automatically when delays cross a configured threshold.

Each vehicle's airport permit category is tracked. Only eligible vehicles are offered curbside trips at that airport, so a mixed-class fleet stays compliant.

Designated drivers are pinned to school-run routes. Substitutions go through a documented approval flow with parental and council notification.

Yes. Background-check status is on the driver record with 60-day expiry alerts; dispatch is blocked on out-of-date checks.

Bulk schedule pauses and resumes from the Aurora console; council billing reflects actual operating days.

Yes. Each trip class is dispatched discretely; vehicles on multi-stop courier routes aren't offered passenger pickups mid-route.

Yes. Photo + signature against every drop, exposed to the client via API or portal.

Monthly statement cadence per client, with per-account pricing, surcharges, and credit limits.

Yes. A booked S-Class cannot be substituted to an E-Class without explicit account approval.

Per-account SLA configuration, driver app prompts at trip start, and post-trip audit report.

Yes. Receipts emit in the format each expense system accepts; cost-centre and project codes are passed through.

Yes. Vehicle and driver eligibility is enforced at the dispatch layer; substitutions require dispatcher override.

Yes. WAV trips are counted, quota balance tracked, and monthly summaries export to the regulator's format.

Yes — Access-a-Ride, THE RIDE, Access Cabs, and equivalent programmes are supported with per-programme account configuration.

Yes. The booked window blocks auto-dispatch entirely; the vehicle is the rider's for the block.

Per-minute or per-15-minute overage rates, configurable per account; receipts itemise block + overage separately.

Yes. Default block size and overage threshold are configurable at the account level.

Attendance forecasts drive vehicle pre-positioning around the stadium geofence; the first wave of post-event riders sees sub-3-minute ETAs.

Yes. Shuttle timetables lock in driver schedules so the published timetable is honoured.

The platform enforces the local surge ceiling automatically; festival-geofenced pricing bands sit underneath the cap.

TfL: 3-4 months. City councils: 6-12 weeks typically. Some councils (Glasgow, Cardiff) report 14-week wait times in 2026.

No. Dispatching PHV bookings without a valid operator licence is a regulatory breach. Wait for issuance before accepting any bookings.

Yes, but each requires a separate application. Multi-jurisdiction operators commonly hold multiple operator licences (one per council).

4-8 weeks from application to issued licence in most UK councils. London (TfL) typically 6-10 weeks due to topographical knowledge assessment.

£400-£800 all-in including application fees, licensing-flight retainer, and onboarding cost. Driver-network referral schemes can reduce this to £200-£300.

Driver app quality, settlement reliability, fair commission rates, and operator responsiveness to driver-side issues. Operators on modern dispatch typically report 15-25% lower churn than legacy-system equivalents.

Typically 2-4 weeks of structured trial covering an airport or executive segment of the fleet, before fleet-wide cutover decision.

Compliance return automation. The labour cost recovery (5-8 hours per quarter at finance-lead rate) typically dominates the other ROI lines for UK + Ireland operators.

Generally no. Modern dispatch like TaxiCloud is month-to-month with one-month notice. Multi-year contracts on legacy systems lock you into 4-7% annual escalation clauses.

£3,000-£15,000/month for typical Magic-Circle satellite or Big-Four regional team. £25,000+ for the largest London accounts.

Standard 30 days. Magic-Circle firms often negotiate 45 days. Some Big-Four firms operate on 60-day terms.

6-12 weeks from initial contact to signed contract for mid-size accounts. Larger enterprise accounts (60-120+ accounts on the platform) can run 4-6 month cycles.

Scheduled audits typically run on a 2-3 year cycle. Unscheduled audits triggered by complaints or incident reports — frequency variable.

Initial document request 2 weeks before visit; on-site inspection 4-8 hours typically; follow-up requests 1-2 weeks post-visit.

Driver, vehicle, booking, and complaint records all export as audit-ready CSV from a single action; quarterly return audit trail preserves historical submissions.

Per-dispatcher Copilot toggle is supported — some dispatchers prefer manual operation. The platform doesn't force adoption.

No. Copilot ships pre-trained on dispatch patterns from across the platform. Per-fleet calibration begins from go-live and improves recommendation quality over the first 30 days.

Dispatchers reject or edit suggestions before execution. The reject signal is training data; Copilot adjusts to the dispatcher's preference over time.

Pro Max covers up to 5 bases in standard configuration. Pro Ultra is custom for operators running 5+ bases or cross-jurisdiction multi-currency operations.

Configurable per operator. Common patterns: 60/40 originating-base / receiving-base, 50/50 split for cross-border bookings, dispatcher-discretion override for VIP corporate accounts.

Yes. Pro Max white-label supports per-base brand configuration — different domain, logo, colours per operating area.

£8,000-£15,000 vehicle-cost premium typical for Tesla Model 3 vs Toyota Avensis or BMW 3-Series equivalent. Lower for Kia EV6 and Hyundai Ioniq 5.

Yes. EV range-aware dispatch with OpenChargeMap charging-station integration ships standard for any TaxiCloud tenant. Vehicle records carry battery state; dispatch logic prevents dead-range incidents.

£12.50/day per vehicle in London ULEZ zones, £8/day in Birmingham CAZ, similar amounts in Bristol/Sheffield/Newcastle. Annual savings: £3,000-£4,500 per vehicle for fleets running daily ULEZ/CAZ entry.

2-4 weeks of structured trial against a real fleet segment. Less than 2 weeks misses operating tempo; more than 4 weeks usually means the trial isn't structured.

Published pricing in 2026 signals confidence and reduces procurement-cycle friction. Sales-quoted platforms typically deploy multi-year contracts with annual escalation; total-cost-of-ownership over three years often runs £30K-£90K higher.

Structurally integrated AI Copilot delivers 30-40% reduction in dispatcher reactive workload. Chatbot-wrapper-only doesn't. The integrated version is increasingly a requirement; the wrapper version is not.

99.9% (8.7 hours downtime per year) is the 2026 baseline for live dispatch. 99.5% is not acceptable; 99.95% is enterprise-tier expectation.

Technically yes, but the rate concession rarely offsets the lost optionality. Modern platforms run month-to-month at the same per-driver economics. Multi-year is usually a vendor-side hedge against churn, not a customer-side saving.

Compressed migration timelines (under 4 weeks) into a platform that doesn't support parallel-run. The risk is dispatch-disruption on cutover day; the mitigation is mandatory parallel-run window in the contract.

Pull the driver app from the Play Store before trial, read the most recent 20 reviews, check rating (4.4+ on modern platforms, 3.1-3.7 on whitelabel legacy). Then run 2-3 drivers on the app during trial week and capture their direct feedback.

1.8x is a common cap; 2.0x is the upper bound any council-licensed UK fleet should consider. Above 2.0x triggers rider backlash and council attention regardless of operating area.

Use time-of-day overlays (1.1x-1.25x) for predictable Friday-Saturday demand. Reserve surge for unpredictable spikes — weather events, transport disruption, post-event windows that exceed typical baseline.

London (TfL) and most major UK councils accept bounded, transparent PHV operator surge. Several explicitly cap Hackney carriage at council tariff. Dublin (NTA) requires methodology filing. Check the specific operating area's framework.

Don't. Corporate accounts negotiate per-trip pricing structures that don't tolerate surge. Account-level exemption is standard; corporate revenue grows from booking volume, not surge.

70-80% is the 2026 benchmark for retention-positive fleets. Fleets that share lower percentages typically underperform on driver retention by 15-25% over 12 months.

Yes. 12+ months of AI Copilot-driven driver positioning typically reduces surge-triggering frequency 20-30% while holding driver earnings steady. The supply-side coordination matures over time.

Surge-without-confirmation — applying a surge multiplier without showing it to the rider at booking. Single largest trigger for council complaints regardless of operating area.

£15-£35 above standard airport fare. Heathrow and Gatwick run at the upper end; regional airports at the lower end. Premium covers parking, dwell time, and welfare risk.

60-90 minutes from scheduled pickup. The window absorbs immigration queue, baggage carousel, and customs variability — all unpredictable from the operator's perspective.

Heathrow, Gatwick, Manchester, Birmingham, Edinburgh all offer monthly operator-tier permits. Dublin Airport (Ireland) and JFK (US) operate similar tiers. Permit pricing varies £150-£800/month per vehicle depending on airport.

95%+ is the 2026 retention baseline. 90% triggers procurement-team escalation; below 85% triggers contract review.

Structural Copilot integration recommends driver positioning in the 30-90 minute pre-pickup window — the highest-leverage window for proactive positioning. Typical lift is 8-15% on-time arrival rate vs manual dispatcher positioning.

Yes. Heathrow vs Gatwick vs Manchester vs Edinburgh run materially different fare baselines and M&G economics. Per-airport pricing rules; corporate accounts notice the precision and reward it.

Treating airport bookings with retail no-show rules. Retail 5-10 minute no-show windows on airport pickups break the corporate-account relationship within the first month.

Reverb is Laravel's first-party WebSocket server, ships with the framework, no external service dependency. Pusher and Ably are third-party services with per-message billing and external SLA dependencies. For platforms built on Laravel, Reverb is structurally simpler.

100-300ms from server emit to console render, including network round-trip. Sub-second under all normal operating conditions.

Qualitatively different. Polling feels like monitoring stale snapshots; WebSocket feels like watching the operation happen. The difference shows up in the first minute of side-by-side testing.

Yes. Event channels scope by tenant, base, and dispatcher role; multi-base operators get clean separation with a super-dispatcher channel for cross-base coordination.

Auto-reconnection logic plus state-reconciliation on reconnect (pulls latest snapshot to fill gaps). Connection-status indicator visible to dispatchers so they always know if they're watching live state.

Yes — same event stream powers rider-side live tracking. Position updates feel smooth without jitter; ETA recalcs render within a second of any meaningful change. Qualitatively better than polling-based tracking UX.

Sub-second on offer accept, booking cancellation, dispatcher message. Polling platforms typically run 5-30 second latency on the same notifications. Driver-NPS lift is measurable.