Logistics

Dispatch and carrier assignment

Dispatchers compare shipment requirements, availability and eligibility manually before confirming a carrier or driver.

Business problem

Dispatchers compare shipment requirements, availability and eligibility manually before confirming a carrier or driver.

What teams see

  • Work waits between read ready shipments and validate constraints.
  • Owners reconstruct status from Transport management system and Generic REST API.

Why it happens

  • No shared state spans Transport management system, Generic REST API, Microsoft Teams.
  • Decision and exception rules are applied inconsistently.

Why it becomes expensive

  • Capacity is consumed by coordination and rework.
  • Late exceptions weaken visibility and service quality.

Business outcomes

  • Shorter update dispatch board cycle
  • Fewer handoff and missing-information exceptions
  • Clear ownership from read ready shipments to update dispatch board
  • Inspectable decisions and recovery

Measurable KPIs

  • Turnaround time: Elapsed time from read ready shipments to update dispatch board.
  • Manual intervention rate: Share of items needing a person outside defined review conditions.
  • Exception age: Time unresolved exceptions remain without a completed action.
  • Successful completion rate: Share of valid workflow items completing without terminal failure.

How the workflow works

  1. Read ready shipments — Accept and identify the dispatch and carrier assignment trigger. Transport management system
  2. Validate constraints — Execute validate constraints with validated sample data and an auditable result. Transport management system
  3. Fetch availability — Execute fetch availability with validated sample data and an auditable result. Generic REST API
  4. Apply eligibility rules — Execute apply eligibility rules with validated sample data and an auditable result. Microsoft Teams
  5. Propose assignment — Execute propose assignment with validated sample data and an auditable result. Transport management system
  6. Dispatcher approval — Execute dispatcher approval with validated sample data and an auditable result. SEIDO Review Queue
  7. Send confirmation — Execute send confirmation with validated sample data and an auditable result. SEIDO Review Queue
  8. Update dispatch board — Execute update dispatch board with validated sample data and an auditable result. Transport management system
  9. Audit and KPI update — Persist the execution outcome, audit facts and workflow measurement events. SEIDO execution store

Integrations and ownership

  • Transport management system: Provide workflow input
  • Generic REST API: Lookup and update context
  • Microsoft Teams: Receive controlled outcome

Human responsibility: Logistics controller

Failure and recovery

Transport management system is temporarily unavailable.

Retry with capped exponential backoff; preserve the run and move it to the inspectable failure queue after the limit.

Required data for validate constraints is malformed or missing.

Stop downstream actions and show the missing fields, source evidence and correction action to the named reviewer.

The trigger or provider event is delivered more than once.

Return the existing execution identified by the idempotency key and do not repeat downstream business actions.

The human decision expires before completion.

Escalate to the configured substitute, retain the original request and record both expiry and reassignment.

When not to build this

  • Monthly volume is too low to justify integrating Transport management system, Generic REST API, Microsoft Teams.
  • An existing configured platform already handles dispatch and carrier assignment with adequate ownership and reporting.
  • Reliable source data or supported API access is unavailable.
  • No business owner has authority to define the decision and exception rules.

Related workflows

Intelligent inbound lead routingLeads arrive through disconnected forms, inboxes and campaigns and are assigned too slowly or to the wrong owner.Lead qualification and account-fit workflowSales representatives spend valuable time manually investigating prospects that do not match the commercial profile.Sales discovery to structured CRMImportant details from discovery calls and notes do not reach the CRM consistently, weakening follow-up and forecasting.