The leading AI dispatch platform.
Click an order to see the decision behind it.
Your orders arrive. Burq Intelligence checks each against the Decision Graph: the promises, the constraints, every provider’s record, your fleet’s hours. Then it sorts them into the fulfillment that fits: same-day batched routes, parcel, or your own fleet.
Wherever your orders start, Dispatch OS takes them from there. AI agents work every leg the same way: watch the promise, fix what breaks, write it down.
Run Dispatch OS at the autonomy you choose:
Manual Shadow Review AutonomousConnect your fleet, whatever driver tools it runs on, and every order becomes a head-to-head: your drivers against the network, whichever keeps the promise for less wins. Idle hours fill, cost per stop falls, and overflow is caught, never dropped.
No fleet yet? Explore the Provider Network
Every active dispatch is watched against its promise. When a better move appears, Burq prices it and acts on it.
Your customer saw one clean order. Your ledger holds the whole story: the decline, the re-route, and the promise that held anyway.
Providers decline. Drivers run late. The fix takes seconds and the outcomes are stored: the failure graded to the provider’s record, the re-route priced, your customer told before they asked.
Burq handles all of your complex operations around dispatch.
However it arrives, it lands as one structured record.
Burq takes into consideration your constraints: volume minimums, in-house vs third-party distribution, and any others.
Client pricing in, driver payouts out, margin by lane. Run by Burq, reconciled on the record.
Claims checked against your matrix.
Replay last week against the mix you’re considering, before you commit.
Plain language, answered by Burq Intelligence from the graph, executed inside your guardrails.
Dispatch OS runs on Burq Intelligence, and every decision it makes leaves these four things behind. Searchable, kept, yours.
The plan, the price, and the rule it followed.
Every alternative quoted, and why each one lost.
The facts in hand at the moment of the decision, not hindsight.
Your team, Burq, or your system over the API, and in which mode.
See the Dispatch OS decide on your own orders, with every call on the record.
Book a demoA single order, a multi-stop route, or a handoff to a carrier. It is the unit Burq Intelligence plans, prices, runs, and records. Orders are what your customers place; dispatches are how they move.
Provider or driver, vehicle class, whether to batch, when to release, and the fallback if the first choice fails. Every option is quoted against the promise you made the customer and against the record of how that option actually performs on that lane, at that hour.
Yes. Multi-stop routes, batching, and re-sequencing mid-run are part of planning a dispatch. The difference is that the route is priced against every other way those orders could move, including sending them singly or handing them to the network, and the winner is the one that keeps the promise for less.
Yes. When an order could ship from several stores or a DC, every origin enters the decision as its own set of options: priced from there, promised from there, your fleet’s position at each one counted. Ship-from-store is an option on every order, not a separate system.
You set the authority per segment of your operation, by zone, mode, or time of day. The ladder runs from Manual through Shadow and Review to Autonomous. In Shadow, Burq plans every order alongside your team and records its call without acting. Promotion is earned on the record, one segment at a time, and a segment that breaks a hard rule demotes itself automatically.
An agent spawns for exactly that job. It re-quotes the order and re-routes it while the promise is still keepable, automatically or with your review, per your authority settings. The failure is graded, the re-route is written to your Decision Ledger, and the provider’s record carries it into the next decision.
In the same queue they run today. Burq drafts the plan with the price and the reason; your team accepts, adjusts, or overrides. Overrides are recorded with a reason and sharpen the next decision, so the intelligence learns your operation instead of arguing with it.
Yes. Your drivers are priced as one more option on every order. Burq plugs into the driver management system you already run.
Yes. A return is a dispatch like any other: quoted across the network and your fleet, tracked under your brand, and closed on the record with the same proof and the same reasons.
Yes. First-refusal rights, weekly minimums, volume splits, and fee ceilings are constraints in the Decision Graph, applied before price. When a commitment decides an order, the record says so and shows what it cost, so the next negotiation starts from evidence.