Keep the operational handoffs behind each load visible.

Our logistics BPO services use dedicated bilingual teams in Colombia to provide nearshore logistics BPO support across calls, portals, transportation-management systems, and documented escalation paths.

CallsPortalsClient TMS
Defined pod workflowUpdate, document, escalate
Client-ownedPriorities, access, decisions
Calls, portals, and the client TMS feed a defined pod workflow for updates, documentation, and escalation. Priorities, access, and decisions remain client-owned.

Documented logistics workflows.

Final scope depends on the client’s systems, SOPs, access, service-level definitions, data sources, and escalation rules. Explore our logistics outsourcing services to see what your team can delegate and which decisions stay in-house.

Documents and billing

  • Proof-of-delivery collection and validation
  • Invoice preparation
  • Accessorial and rate matching
  • Freight audits

Work inside the operating environment that is actually approved.

The assessment defines how the pod receives work, records updates, communicates exceptions, and hands decisions back to the client. Client-approved systems, permissions, policies, and access remain part of the operating plan.

In every model
Employment and workforce administration appropriate to the selected service model.
Managed Pod
Optimus provides the defined operational-management layer, including supervision, QA, reporting, coaching, and escalation.
Transition Pod
The client retains daily supervision, scheduling direction, productivity and performance management, and operational QA. Optimus provides the agreed workforce-administration layer.

No default guarantee. Use of a client TMS or portal does not guarantee a software integration, implementation timeline, data connection, or operational outcome. Requirements are evaluated and documented before launch.

Coverage follows an agreed schedule, not a blanket promise.

Team structure and pricing depend on volume patterns, handoffs, required skills, supervision, and the hours the workflow actually needs.

Standard

North American business-hour schedules aligned with Eastern, Central, or Pacific time.

Assessed separately

Extended hours, weekends, holidays, overnight shifts, and twenty-four-hour coverage are not included by default. Availability and pricing are determined after assessment.

Explore after-hours logistics support

Delivery location

Remote requirements are proposal-specific. Office delivery uses partner space contracted on demand in Barranquilla, subject to availability and scope.

Choose the pod model around this workflow.

Compare responsibilities, delivery options, pricing boundaries, commercial scope, and oversight in one place.

Review service models and operating terms

Bring us the logistics workflow and its handoffs.

The assessment produces a fit and model recommendation, key scope assumptions, a responsibility split, missing inputs, and proposal next steps.