One login for the whole operation.
Jobs pull in from your supplier connections, your booking site, your inbox and a typed phone call. You dispatch them to your own drivers, on your own board. Invoices, client payments and Driver Pay post themselves into a real double-entry ledger. You retype nothing between the three.
One queue for every channel.
Jobs from your supplier connections, your booking site, your inbox, an import and a phone call land on the same board. Send one to a named driver, or open it to your roster to bid. Where that supplier connection carries reports back, your driver's step goes with it. The inbox is available in Malaysia, Singapore and the UAE.
Unified job board
Every source in one queue. Filter by job type, car class, operator, supplier, status, or date.
Schedule-aware assign
Quick-assign with a 3-card schedule preview and a tight-gap warning when the SOP buffer is breached.
Bulk operations
Assign, open to the network, or cancel across dozens of jobs in one move.
Cover from the driver network
Open a job to the driver network when nobody on your roster can take it. Only drivers who clear the claim checks pick it up, and the client stays yours.
Driver bidding
Let drivers bid for jobs — no 'I tapped first' arguments, the server arbitrates and says so in the same second.
Audit trail per change
Every assign, cancel, edit, throwback recorded with who did it, as they stood at the time.
Drivers and ops staff, all role-gated.
Take drivers on, control what your ops staff can see, and verify licences and documents with AI assistance, without leaving Fusion Link.
Invite + apply flow
Public invite links for external drivers; in-app applications for internal hires. Approve, reject, suspend, ban — all role-gated.
5 roles, plus Owner
Admin, Finance, Operations, Support, Driver — each with its own navigation, its own permission boundary, and a full audit trail of who did what. Owner sits above all of them and is assigned only by transferring ownership, never from the role picker.
AI-assisted document review
Driver licences and supporting documents reviewed by Fusion AI — a text pass over the record, plus a vision pass that reads the document image itself.
Money is the sharpest line in the system.
The role you give someone decides which surfaces they reach and — more importantly — which numbers reach them. Financial fields are stripped server-side before the response leaves the API, so a role that cannot see a client rate never receives one to hide.
Both sides of the money
- Owner — everything Admin has, and the only seat that can hand ownership on
- Admin — dispatch, suppliers, booking site, settings, and the full ledger
- Finance — accounting, wallet, invoicing, payables, reports, period close
- All three see client rate and driver pay in full
Driver pay only
- Operations — jobs, roster, clients, fleet, analytics, and the audit log
- Sees driver pay, because you cannot dispatch a job without it
- Client rate is removed from the response — including inside audit-log diffs
- No access to suppliers, the booking site, accounting, or settings
No money at all
- Support — read access to jobs, drivers, and clients, plus customer messaging
- Both sides of the money stripped before the response leaves the server
- Driver — their own jobs and pay, never a client rate, on any surface
- A role the system does not recognise sees no money at all — that is the default, not an afterthought
Cover the job you cannot fill, without handing over the client.
Your roster sees a job unless you choose to send it out. When nobody on it can take one, open that job to drivers on the network instead of posting it in a chat group. The job stays on your board — your client, your record, your proof, your brand. What changes is who drives.
How a job reaches the network
- Open one job from the board, or dozens of your own jobs in a single bulk action
- Set the miss rule once: a direct or booking job opens itself when its driver goes quiet
- Supplier jobs go one at a time, so the supplier is told the job is covered
You keep control of the listing
- Withdraw the listing at any time and the job returns to your board
- Assign your own driver while it is listed and the listing closes with them
- Choose when you create the job whether drivers carrying a yellow card may claim it
- A driver you have suspended cannot claim your listings, however open the network is
Who can claim it
- A phone-verified driver with a complete profile, in the same country as the job
- Their vehicle class has to cover the job's tier, and a wheelchair job needs a wheelchair vehicle
- We ask for vehicle documents when a driver takes work, not at signup
First claim wins
- The server arbitrates every claim, so two taps cannot both win
- The driver who misses out is told in the same second, by the server
- No 'I tapped first' argument ever reaches your ops team
The standard has teeth
- Report a driver who let you down; Fusion Link reviews it and decides the card
- A yellow card shows for every operator that driver works with
- It lapses after 6 clean months, and 3 active cards escalate to a red one
- A red card has no expiry date — only a successful appeal clears it
The client never sees the handover
- Tracking link, milestone emails and receipts stay in your brand
- Photo and GPS proof lands on your job, in your evidence export
- The driver sees Driver Pay only — your Client Rate never leaves your side
Airport jobs re-time against the aircraft.
Attach a flight to an airport job and Fusion Link polls it while the aircraft is in the air. Turn it on per source: supplier jobs, booking-site jobs, or your own client jobs. Opt a single job out when you do not want it.
Gate, belt, terminal, ETA
Fusion Link polls the flight and passes each update to the driver's phone. Your driver reads the live arrival instead of the booked time.
Keyed on the arrival country
Live for arrivals into Hong Kong, Malaysia, Singapore and Thailand. The country the flight lands in decides coverage, not the country you registered in.
Elsewhere, the booked time
Outside those markets the job runs normally on the booked time. Nothing polls, and nothing changes for the driver.
From booking to dispatch in one flow.
Clients book on your own domain. Stripe takes the payment. The booking creates the job. Your driver picks it up, and nobody copies anything across.
- 01·step
Put it on your own domain
Your booking site goes live on your own domain, with SSL provisioned automatically. You can claim one of the 12 designs exclusively, so no other operator runs it.
- 02·step
Configure pricing
Base + per-km + minimum, a flat price per job type (ARR / DEP / TRF), add-ons, time-of-day, airport proximity, holiday surcharges.
- 03·step
Take bookings
Multi-step booking form with quote, add-ons, payment. Multi-leg (chain) bookings supported. Stripe Connect direct charges to your account.
Win corporate without losing your margin.
Multi-traveller accounts with cost centres, applied discounts, and approval workflows — the card is authorised but not charged until an approver signs off.
Multi-traveller accounts
Cost centres, applied discounts (percentage or fixed rate card), dedicated traveller invite flow.
Approval workflows
Bookings hold until an approver signs off. The traveller's card is authorised at booking and held, not charged, until that happens. An unapproved booking never takes their money.
Invoicing
Sequential invoice numbers per operator, real PDFs rather than a printed web page, country-driven tax rates snapshotted at issue time.
Accountant-grade, not spreadsheet-grade.
What you owe your drivers sits on its own ledger. A double-entry general ledger sits under everything, with the reports your accountant actually asks for.
Ledgers & journals
- Driver payouts — what you owe your drivers (jobs, payables, settlements)
- Double-entry general ledger underneath, with voids posted as reversing entries
- Backfill button replays history into the GL if anything drifts
Reports
- Trial Balance, Balance Sheet, Account Ledger
- Profit and loss across jobs, drivers, clients, and revenue
- AR/AP aging waterfall (0-30 / 31-60 / 61-90 / 91-120 / 120+)
- Google Sheets export for accountants who live in spreadsheets
Period control
- Close a period to freeze financial fields on every job in it
- Operational fields stay editable for post-close corrections
- Admin-only reopen with a written reason, audit-logged
- Currency-safe money (JPY, SGD, USD) — no rounding drift
Reports, balances, analytics.
See what your operation actually did this week, this month, this quarter — without exporting to Excel.
Reports & balances
Jobs, drivers, clients, and revenue across every aging bucket. Live, with no overnight refresh.
Activity monitor
See ops actions as they happen. Audit log on every state change with denormalised actor identity.
Daily digest email
A digest once a day — so you don't have to log in to know what's pending.
Client money lands in your account.
Clients pay on your booking site, and the money settles with you. Promo codes help you win clients, and each one is tracked to the booking.
Card payments to your Stripe
Bookings on your booking site use Stripe Connect direct charges, so client payments settle in your own Stripe account.
Promo codes
Issue discount codes to win new clients. Each one is tracked through to the booking and into your reports.
Booking site templates
Pick one of 12 designs, or claim one exclusively so no other operator runs it.
See it on your own jobs.
Book a call and walk us through a typical week. We show you the system on jobs like yours, then quote the operation.