For logistics

From the first customer request. Through dispatch and invoicing.

Connect the recurring work between customer intake, routing, scheduling, and billing. Configure Lieutenant to prepare plans, route exceptions, and create approved records in your existing CRM and ERP—while your dispatch, operations, and finance teams keep control.

Book a walkthrough

Sample dispatch queue · Routing and scheduling

Pickup and delivery stopsProposed route planWaits for a person
Delivery window conflictDispatcher decisionFlagged
Approved scheduleAgreed dispatch systemWaits for a person

Illustrative example with sample data. Not a customer result or product screen.

For logistics providers, carriers, brokers, and delivery operators. Workflows, routing inputs, system connections, and write permissions are agreed during scoping. Dispatch decisions, safety checks, customer terms, and payment release stay with your team.

Workflows

The recurring work Lieutenant takes on.

Each workflow links to the platform capability underneath it.

Routing

Prepare proposed routes from the stops, service windows, and vehicle constraints supplied by your team or connected planning system. Flag missing inputs and conflicting requirements for dispatcher review before changes are released.

Capability: Custom workflows →

Scheduling

Prepare pickup and delivery schedules using agreed availability, appointment windows, and customer requirements. Route conflicts and change requests to the right person, then update approved schedules where system access allows.

Capability: Custom workflows →

Invoicing

Match shipment and proof-of-delivery records to agreed rates and billing terms. Prepare invoice drafts, attach supporting documents, and flag missing delivery evidence or disputed charges before finance approves release.

Capability: Revenue and cash →

New customer intake

Gather customer details, service requirements, billing information, and supporting documents from forms, emails, or supplied records. Flag incomplete fields and possible duplicates, then route the setup packet for approval.

Capability: Document capture →

CRM record creation

Create approved account and contact records in your connected CRM, using the field mappings and duplicate checks agreed in scope. Keep service requirements and the source request linked to the customer record.

Capability: Custom workflows →

ERP record creation

Create approved customer and billing records in your connected ERP with the agreed entity, billing address, payment terms, and reference IDs. Link the CRM and ERP identifiers, and send validation failures back for review rather than silently creating incomplete records.

Capability: Custom workflows →

How it runs

Inputs, work, your review, outputs.

Source systems are confirmed during scoping, not assumed.

01 · Connected inputs

Customer requests
Stops and appointment windows
Rates and delivery records
CRM and ERP fields

02 · Lieutenant does the work

Prepare routes and schedules
Validate customer intake
Create approved records
Prepare invoice drafts

03 · A person reviews

Dispatch decisions
Customer terms
Record and invoice exceptions

04 · You get

Reviewed schedules
Linked customer records
Evidence-backed invoices

Illustrative flow. Which systems connect and who reviews is agreed in scope for each engagement.

What you get

Proposed route plans and schedule exception queues
Customer intake packets with missing information flagged
Approved CRM accounts and contacts
Approved ERP customer and billing records
Invoice drafts with rate and delivery evidence

Waits for a person · sample scope

Route and schedule changes	Dispatcher or operations lead
Customer acceptance and service terms	Account owner
CRM and ERP setup exceptions	System or data owner
Invoice release and disputed charges	Finance reviewer

Illustrative. Signatures, payment release, and vendor decisions always stay with your team.

Pair it with your role or your own process.

Operations leaders Owners & executives Finance & accounting teams Custom workflows All solutions

Questions

What people ask before a walkthrough.

Does routing mean replacing our transport management system?

Not by default. We scope how Lieutenant prepares routing inputs, coordinates planning steps, and handles exceptions alongside your existing transport or dispatch tools. Routing methods, constraints, and available data are confirmed before we promise a specific planning workflow.

What does CRM and ERP creation mean?

Creating customer, account, contact, and billing records inside the CRM and ERP you already use—not building a new CRM or ERP. We agree field mappings, duplicate checks, permissions, approvals, and how identifiers will stay linked.

Can new customer intake flow through to invoicing?

Yes, where the required systems and access are in scope. The workflow can collect customer details, obtain approval, create the corresponding records, and use the approved setup for shipment billing. Missing data or validation failures are held for review.

Will Lieutenant dispatch vehicles or release invoices without review?

Your team defines approval gates and permitted actions. Dispatch and safety decisions remain with your operators, customer terms with the account owner, and invoice release with your finance reviewer.

What gets agreed before we start?

Staffing, source connections, access, reporting cadence, and timing are scoped with you before any work begins. Your team keeps signatures, payment release, and vendor decisions.

Is this a different platform from the other solutions?

No. It is the same platform and review model, configured around the workflows that matter most for your business. Custom workflows are available when yours differ.

Start with the workflow that costs you most.

We'll scope systems, access, reviewers, and timing before anything runs.

Book a walkthrough