Customer work, connected.

Help & supportMyAccount
Jobs, stops, dispatch and status control

Open the dispatch workspace

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Select only code-eligible jobs, drivers and vehicles.

Audience: Courier operations staffPermission: Courier: DispatchModule v2.0.0
Jump to steps
Where to goAdmin Area → Courier & Logistics → Dispatch

What this guide helps you do

Select only code-eligible jobs, drivers and vehicles. The instructions below follow the supplied module’s controller, form and model rules, including server-side validation and downstream effects.

Follow these steps

  1. Go to Dispatch.
  2. Select a draft, available or quoted unassigned job.
  3. Select an active, available, compliant driver with a valid email.
  4. Select an active, available, compliant vehicle.
  5. Check agreed revenue and calculated pay.
  6. Verify assignment.

Fields and options

This action uses the values already stored on the selected source record. Review that record before continuing.

Rules and limits

  • The model locks job, driver and vehicle rows for update during assignment.
  • Eligibility is rechecked server-side even if a record appears in the list.

Check it worked

  • The source record, status/history and any downstream notification, provider, POD or finance record should agree after the action.

Security, audit and operational checks

  • Use the exact record and least-privilege role before changing any state.
  • Verify the saved record after every action; a browser message alone is not evidence that every downstream step completed.
  • Use protected document and image routes rather than exposing server filesystem paths.
  • Keep customer, driver, provider, financial and credential data within the authorised workflow.
  • For provider, finance, employment, transport and compliance decisions, follow the organisation’s authorised professional process.
Do not bypass the code flowDo not force database values, invent a status, mark a job completed without signed POD evidence, or expose encrypted credentials to make a screen appear successful.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page