Twenty services feed the platform, and each one is a first-class input to the board rather than a report you go and fetch. Below, what each connection does, which module it feeds, and why it was built the way it was. Your data stays yours: every integration is a key you hold and can revoke.
Pre-authorisation at booking, capture on completion, gratuity after the drop, refunds and partials, and bank debit at 0.8% capped at five dollars for the house accounts that pay that way. Stripe sees the charge; it never sees the trip. The card cost is carried to the trip line so margin is real.
“Your processor, your negotiated rate. We never take a share of your volume.”
Feeds Payments
Confirmations, driver-on-the-way, flight-moved and receipt messages go out through Twilio from a number that is yours. Quiet hours are enforced in the sending layer, not left to whoever pressed send: a text queued at 11pm waits for the morning unless the pickup is at 5. Replies land on the guest's thread in the Rolodex.
“Nobody should get a text at 2am unless they are being picked up at 2:30.”
Feeds Rolodex
Invoices, payments, refunds and customers post to your QuickBooks file the moment they exist on the platform. No export, no CSV round-trip, no month-end reconciliation from memory. The connection is OAuth: you authorise it once and can revoke it from either side.
“Your accountant should never learn about a trip from a spreadsheet.”
Feeds QuickBooks
Odometer, location, speed and engine health per vehicle, polled from Azuga and written against the car. The Garage shows what each vehicle is doing this minute; the odometer accrues from the feed and from completed trips instead of waiting to be typed in; service intervals fire from real mileage.
““Ready” is a fact about paperwork. The garage wants to know if the car is halfway to the airport.”
Feeds Garage
The affiliate exchange. A farm-out is your booking handed to a partner with live status coming back; a farm-in arrives as a booking with the sender's details attached. Built to the GRiDD specification and waiting on certification credentials before it is switched on in production.
“An operator who cannot farm cannot switch. This is why it was built before it was asked for.”
Feeds GNet
Every arrival on a booking is polled on its own schedule — more often as the landing approaches — rather than once per page load. A delay moves the pickup and tells the driver; a red-eye is matched to the day it actually lands; a cancellation raises a flag on the board instead of a surprise at the kerb.
“The airport run is the trip most likely to go wrong for reasons that have nothing to do with you.”
Feeds Flights
Ground stops, ground delays and airport closures from the FAA, matched to the airports on today's sheet. When the schedule feed says on time and the airport says ground stop, the board believes the airport, and the pickup waits.
“Two sources that disagree is a warning. One source that is wrong is a stranded guest.”
Feeds Flights
Radar tiles and active warnings from the National Weather Service, drawn on the board underneath the cars and scoped to the corridor being driven, not the county. A winter storm warning on the pass shows on the pass, not as a banner across the whole state.
“Weather is a dispatch input. It should not be a website you go and check.”
Feeds Dispatch
Conditions at points along the route — surface temperature, precipitation, visibility — so the feasibility verdict and the dispatcher both know that the pass is at 28°F and snowing while town is dry. Where the NWS says what the sky is doing, Aeris says what the road is doing.
“The forecast for the town is not the forecast for the pass.”
Feeds Dispatch
Road closures, chain and traction laws, and incident reports from the state, matched to the segments your trips actually use. A closure on the tunnel approach appears on the board with the trips it affects, and the scheduler's verdict accounts for the detour.
“A closed pass is a schedule problem an hour before it is a driving problem.”
Feeds Dispatch
Every address is geocoded once and kept. Traffic-aware ETAs feed the scheduler's verdict — deadhead from the last drop-off, arrival against the pickup time — and the driver app hands the route to the phone's own navigation. Distances on the rate cards come from the same source.
“The question is never “is the car free” — it is “where will the car physically be”.”
Feeds Scheduler
Chauffeurs, dispatchers and office staff sign in with Google; the platform maps the account to a role and scopes what they can see. No passwords to issue, reset or remember, and revoking access is one switch when someone leaves.
“Drivers churn; the sign-in should not be one more thing to onboard.”
Feeds Driver app
The Agent reads live operational data through the caller's own permissions and drafts the action — reassign, reschedule, message the guest, propose the quote — then waits. It reaches every module rather than one corner, and still nothing moves without a person saying yes: a chauffeur's assistant cannot see billing because the chauffeur cannot, and the money paths stay locked whoever is asking.
“Useful, and unable to do anything you could not do yourself.”
Feeds Agent
On the platform it reaches ask or instruct your assistant, with actions, the morning briefing and guest reply drafts and content, SEO and the docs helper. Connected with a key you hold.
Described in the platform's own words, as of version 3.79.27.
On the platform it reaches messages on a trip and the driver app’s inbox. Connected with nothing to set up; it is part of the platform.
Described in the platform's own words, as of version 3.79.27.
On the platform it reaches the Website Funnel report and traffic sources on Analytics. Connected with a sign-in you authorise once and can revoke from either side.
Described in the platform's own words, as of version 3.79.27.
On the platform it reaches the Semrush API, linked and proven, aPI unit balance on this panel and search reports to come — the link lands first. Connected with a key you hold.
Described in the platform's own words, as of version 3.79.27.
On the platform it reaches the shelf beside the dispatch board, radio in the chauffeur’s app and weather and roads on the strip. Connected with a key you hold.
Described in the platform's own words, as of version 3.79.27.
On the platform it reaches a run with nobody on it becomes a to-do, the day’s manifest on the message board and ticked off when the trip is done. Connected with a sign-in you authorise once and can revoke from either side.
Described in the platform's own words, as of version 3.79.27.
On the platform it reaches “Add to Apple Wallet” and “Save to Google Wallet” on the confirmation, the account and the live trip page. Connected with a key you hold.
Described in the platform's own words, as of version 3.79.27.
Stripe, Twilio, QuickBooks, Azuga and Google are all connected with credentials you own. We hold nothing that could not be moved to another system the day you ask.
Flights, weather and roads are fetched on schedules that match how fast they change — a flight every few minutes as it lands, radar on its own cadence — never on a page load, so the board is current when you open it.
Every integration can be turned off without touching the others. Lose a key, change a provider, or simply not need one; the platform keeps running on what is left.
Thirty minutes, screen share, your own numbers typed into the live system.