Premium and Pro Growth Feature
Receive overflow rides from partner operators, send overflow rides when your fleet is full, and expand revenue without adding vehicles immediately.
When your team is full, you can still keep the client relationship alive instead of losing the booking completely.
Pro operators can receive overflow rides from the network and turn idle availability into booked revenue.
This gives operators a practical growth bridge before committing to another vehicle, driver, or dispatcher.
| Plan | Network Dispatch Access |
|---|---|
| Starter | Not included |
| Premium | Send only |
| Pro | Send and receive |
If the fleet is full, the operator sends a dispatch offer into the network.
The first eligible partner to accept wins the ride.
The system marks the dispatch as assigned and closes it for everyone else.
The accepted dispatch is pushed into the partner operator's workflow/webhook for handling.
Yes, in most cases it can. The easiest MVP is to send the accepted dispatch into the same inbound workflow structure the partner already uses, as long as the payload includes a dispatch flag and the workflow can branch correctly.
Include a field like booking_source = network_dispatch or dispatch_partner_assigned = true so the partner workflow knows this is not a direct self-booked customer.
Create or update the contact, create the opportunity, assign the trip internally, and trigger the right partner-side notifications without needing a cross-account calendar write in MVP.
If a ride is assigned through the dispatch network, the customer should be clearly informed that a trusted network partner operator will be providing service on your behalf.
Your reservation may be fulfilled by a trusted network partner operator on our behalf. If assigned to a partner, all service standards and trip details will remain managed through our network.
Required fields
Trip details