Farm in and farm out natively through GNet.
Trips move into and out of the board through the GNet affiliate network without re-keying. When the other operator supports the same capabilities, status and GPS can flow both ways.
INSTAROUTE
ORD T2 → The Drake
GNet requests land where the desk already works
Each incoming offer arrives in Inbox as a needs-decision item with the partner, trip details, feasibility result, and calculated price together. Dispatch can adjust the price, accept, or decline without opening another system.
Needs decisionIncoming partner requestGNet offerJul 22 · 14:40 · DL 1682 · 2 pax
The trip stays native in both systems
An accepted farm-in becomes a full trip. A farm-out sends the trip, status, and GPS when the partner supports those fields.
Farm out a batch without working each trip one by one
Select multiple eligible trips and choose a connected partner. InstaRoute sends and tracks every trip as its own GNet request, so each has a separate result and retry path.
INSTAROUTEFarm-out resultsWhat should the trip cost?
Can the operation perform it?
What trip data can move between operators?
Questions about GNet and affiliates.
Does the other operator need to use InstaRoute?
The other operator does not need InstaRoute. The partner must support compatible GNet capabilities.
Does InstaRoute auto-accept farm-in requests?
InstaRoute does not auto-accept. It provides feasibility and a calculated price, then dispatch reviews and decides.
Does bulk farm-out send one request for the whole batch?
No. Dispatch selects one connected partner for the batch, then InstaRoute sends every eligible trip as a separate request with its own result and retry path.
Take partner work without the manual math.
Follow a GNet request through feasibility, calculated pricing, acceptance, and the dispatch board.