trike_devTelegram ↗

Freight dispatch desk

A workspace for a small transport or freight forwarding team: requests, clarifications, confirmed data and next actions.

Who it is for

  • Carriers and freight forwarders who receive requests by email and compile statuses manually.

What the solution includes

  • Register and queue. Search, statuses, owners and a request page. Tasks stay next to the order.
  • AI email parsing. Suggests fields and shows conflicts between the email and the attachment. A staff member clarifies and confirms.
  • Portal and claims. The client sees partial delivery. The claim timeline is assembled from sources; the team verifies the evidence.

We adapt the design to your brand. The example illustrates a workflow, rather than a fixed visual style for your project.

Email-to-order intake, dispatch registers and claims evidence are common to carriers everywhere. TMS/1C integrations and electronic transport documents are excluded, so no national e-document regime is assumed.

Examples use fictional data. Integrations, payments and AI actions shown as simulations require separate implementation and testing.

Try the interactive example →

Development options

Pricing on request. We confirm the scope, schedule, currency and payment terms before starting.

Request register

The team manages requests in one place.

Quote on request

5–8 weeks, subject to scope confirmation

  • One request type with up to 15 fields and 6 statuses
  • List, request page, search and owners
  • Two staff roles, change log
  • Import of one prepared CSV of up to 500 requests
  • Manual task creation and CSV export
  • Testing, launch and training

Not included

  • Email parsing, client portal and claims
  • Integrations with TMS/1C and routing

Ongoing costs

  • Hosting, file storage and email on the chosen plan.
Discuss this option →

Requests and AI

A staff member receives a verifiable draft from the email.

Quote on request

8–11 weeks, subject to scope confirmation

  • Everything in the “Request register” package
  • One mailbox and one agreed request type
  • Extraction of up to 10 fields from text and one PDF format
  • Checks for required fields and conflicting values
  • Link to the source, confirmation queue, duplicate request protection
  • Testing on 30 anonymised emails

Not included

  • Client portal, OCR of arbitrary scans and voice
  • The model negotiating prices or sending emails on its own

Ongoing costs

  • Hosting, file storage and email on the chosen plan.
  • The model and document recognition are paid by usage; a limit is agreed before launch.
Discuss this option →

Client operations

The client sees their order; the team collects delivery confirmations and documents.

Quote on request

12–17 weeks, subject to scope confirmation

  • Everything in the “Requests and AI” package
  • Portal with access only to the company's own orders
  • Partial delivery, documents and clarification requests
  • One claim type, evidence register and timeline
  • Up to 3 roles, access control and version history
  • One agreed notification channel

Not included

  • Legal assessment of claims, payouts and electronic transport documents
  • Data exchange with TMS/1C and migration of a large history

Ongoing costs

  • Hosting, file storage and email on the chosen plan.
  • The model and document recognition are paid by usage; a limit is agreed before launch.
  • Authentication and notifications on their plans.
Discuss this option →

Possible next steps

  • A staff member receives a verifiable draft from the email.
  • The client sees their order; the team collects delivery confirmations and documents.