Magellan
CarrierFlow TMS setup and support.
Work with Magellan to match CarrierFlow TMS to your US trucking company’s workflows. Discuss the modules your teams need, the information to prepare and the setup, team guidance and support to include in your written proposal.
Work with Magellan to match CarrierFlow TMS to your US trucking company’s workflows. Discuss the modules your teams need, the information to prepare and the setup, team guidance and support to include in your written proposal.
A driver sends delivery documents. Accounting needs them for billing. A vehicle defect needs Fleet’s attention, while Dispatch needs to know whether the equipment can be assigned. We can follow either example through CarrierFlow to identify the departments, information and responsibilities involved.
Your company decides who can see information, approve changes and follow up on open items. We use those responsibilities to define the proposed setup, the information to prepare and the team guidance and support to agree before work begins.
Bring the workflow you want your teams to share.
Management questions
- Which departments need to work from the same load, driver or equipment information?
- Where does missing information delay billing, repairs, assignments or follow-up?
- Which people should review, approve or receive each kind of action?
- What company details, documents, people records and other initial information will setup require?
- Which learning and corrective-action workflows should connect to your team’s work?
Problems this solves
- A delivery is complete, but Accounting is still chasing its supporting documents.
- A defect has been reported without a clear repair task or equipment-status update.
- A driver-file question reaches Dispatch without the information needed for a decision.
- Managers carry updates between departments because responsibilities are unclear.
- Training is assigned without a reliable connection to the finding and follow-up.
Deliverables
- A written proposal identifying the selected modules, users, access, setup, information preparation, team guidance, support and charges.
- The CarrierFlow workspaces included in your company’s agreed modules.
- Role permissions and approval responsibilities defined around the selected workflows.
- The setup, information preparation and team guidance identified in your proposal.
- Operating records that connect the work, supporting documents and follow-up.
Implementation path
- Bring a working example: a delivery awaiting billing, a driver-file question, a defect or another recurring handoff.
- Follow it through CarrierFlow with Magellan to identify the departments, information and responsibilities involved.
- Agree the modules, users, setup, preparation work, team guidance, support and charges in the written proposal.
- Prepare the company information and confirm access and approval responsibilities for the agreed setup.
- Magellan provides the agreed team guidance and works through questions as your team begins using the workflows.
Common questions
What should we bring to the first discussion?
Bring an example of work that crosses departments, the information your team uses and the people responsible. A delivery awaiting billing, a driver-file question or a reported defect gives us a specific workflow to follow through the relevant tools.
How do we work out the setup scope?
We follow your example through CarrierFlow to identify the modules, users, permissions and approval responsibilities your company needs. You can select individual modules; the written proposal records the chosen scope.
What information needs to be ready for setup?
The preparation depends on the selected modules. We identify the company information, documents, people records and other initial information needed for your setup, then define the preparation work and responsibilities in the proposal.
How will our team learn its workflows?
Magellan provides the team guidance identified in your proposal and works through questions as your team begins using the agreed workflows. Where learning is assigned for a Safety finding, completion records learning progress; the responsible person still reviews the operating action and supporting evidence.
Who decides access and approvals?
Your company defines role permissions and approval responsibilities. It also controls office and driver AI access, permitted sources, topics and actions. AI can assist with information and document work; people confirm extracted values and retain the required approvals.
How are support and charges agreed?
We define support and charges in the written proposal before setup. It sets out what Magellan will provide and what your company needs to prepare.