Guides
Modern forwarding connects every handoff with context.
Digital work creates value when responsibilities, decisions and documents fit together across the transport history rather than only inside isolated forms.
- 01Intake
- 02Responsibility
- 03Status
- 04Proof
02 / Overview
What FalcGo connects
Treat customer intake, dispatch, partner execution, exceptions, proof and invoicing as one connected workflow.
The guide deliberately separates general process practice from the capability scope represented in FalcGo.
03 / Capability scope
Capability scope
- 01Where prerequisites apply
Customer self-booking
Customers provide transport data through a purpose-specific invitation; the team reviews it before approval.
Invitation, registration and approval conditions apply; the outcome of multiple drafts still needs verification. - 02Represented in the product
Partner execution
Accepted partners receive a shipment with context, decide whether to accept it and execute it with their own assignment.
A closed relationship network, not an open spot or capacity market. - 03Where prerequisites apply
Proof of delivery
Documents, photos and a signature can be connected to the shipment in supported delivery states.
Availability depends on shipment state and the proof that exists. - 04Where prerequisites apply
Individual and collective invoicing
Eligible shipments feed invoices with editable line items, documents and payment status.
Do not claim a complete accounting suite or a specific certified e-invoice profile.
04 / Workflow focus
Workflow focus
- 01Customer self-booking
- 02Partner execution
- 03Proof of delivery
- 04Individual and collective invoicing
06 / FalcGo
Show us your handoffs.
We will show you how customer intake, dispatch, drivers or partners, exceptions, proof and invoicing come together in FalcGo.