Incoming requests
The incoming list stays separate from the day’s services, so network requests don’t get lost in daily volume.
Incoming rides for NCC suppliers in the network
When an operator forwards you volume, it can’t end up in a lost email. The supplier needs to see what’s pending right away, decide whether to accept and move to execution without re-typing.
FleetMo dedicates the Incoming area to suppliers: requests from the network, accept or reject actions and a sidebar badge whenever rides are pending.
Operational inbox
Accept or handle
Accept or handle requests not yet in planning and move them to dispatch without retyping the data.
Counter
The sidebar badge flags pending rides: a fast reply means more volume confirmed from the network.
Tied to the chain
Network origin
Requests come from the assignment chain and collaborators network, traceable to the forwarding partner.
After acceptance
After acceptance the ride follows the normal dispatch and driver or vehicle assignment flow.
Why it matters for the supplier
A fast reply means more confirmed rides. A “3 pending” badge is worth more than a WhatsApp thread scrolling by.
Questions, answered.
Not as a primary area: it’s oriented to the supplier who receives assignments.
The flow updates the request status and the partner sees the outcome in their own chain.
No. Incoming is tied to the collaborators network and assignments, not only the marketplace.
Get started
Run your NCC and transfer operation on one system.
Sign up as a provider or supplier on my.fleetmo.app. For fleets over 10 vehicles, talk to our sales team.