Logistics service operations

Run every service job with AI

AI keeps each job current from its request, checks each handover against its contract SLA, then drafts the acceptance record and charges statement. Built for the coordination desk, live in days.

See AI handle your own work.

AI enters the job data

AI reads the service request and the cargo list and fills in the job record. Nobody keys it in.

AI catches the fields that disagree

AI compares the service request against the cargo list and against the client on file. A mismatch surfaces before the quote goes out.

AI drafts the documents you send

AI fills the service quote and the dispatch order on your own templates. Your team approves before anything reaches the client.

AI watches the SLA clock

AI counts every job against the SLA on its contract. A job nearing its deadline without a handover surfaces before the client asks.

Every job from request to settlement

Every stage captures the job, AI handles the paperwork and the SLA clock, and the next move happens on its own.

  1. 01

    Service request

    From the service request email and cargo list, AI opens a job on its own, capturing the client, service type, cargo, pickup and delivery points, and the agreed SLA. Every request lands as its own job, linked to the client.

  2. 02

    Scope & quote

    AI prices the job against your service rate sheet and drafts the service quote with the scope, resources, unit rates, and quoted charges filled in. Your team approves it before it reaches the client, and an accepted quote moves the job into planning.

  3. 03

    Planning & dispatch

    With the team, vehicles or subcontractor, schedule, and dispatch window set, AI drafts the dispatch order from the resources assigned. The job moves to Dispatched and the schedule lands on the calendar.

  4. 04

    Execution & handoff

    At each handoff, AI reads the handover note and photos and updates the job with the time, receiving party, and cargo condition, capturing the signed handover record. Nothing drops between warehouse, transport, and delivery.

  5. 05

    SLA tracking

    Every job runs against its own SLA clock, and AI tracks each milestone, surfacing the jobs that fall behind. One nearing its SLA without a handoff alerts the coordinator before the deadline passes.

  6. 06

    Acceptance

    Once the job is complete, AI drafts the acceptance record for the client to sign, carrying the completion date and any agreed deductions. A signed acceptance moves the job to billing on its own.

  7. 07

    Billing & settlement

    AI builds the charges statement from the service charges, subcontractor costs, and deductions, reconciling it against the subcontractor bills. The statement posts to accounting and the job margin updates the moment it does.

An app for every team

Coordination, warehouse, transport, and managers each get their own app, all reading and writing the same service jobs.

Coordination desk

Coordination sees every job by stage, with SLA deadlines surfacing in red as they near.

Job cockpit

The ops team works one job with its documents, handovers, and the draft-and-approve buttons in a single view.

Dispatch schedule

Dispatch sees every run and SLA due date on one calendar, so nothing is double-booked.

Manager dashboard

Managers see the SLA hit-rate, open jobs, and margin per client as costs land.

Routine work handles itself

Jobs move themselves, the SLA clock nudges you, and every figure is approved before it leaves.

Each job moves itself forward

When dispatch, handover, or acceptance is logged, the job advances to the next stage on its own.

SLA breaches surface early

A job within two hours of its SLA without a handover alerts the coordinator.

Off-scale quotes need sign-off

A quote priced below your rate sheet needs a manager's sign-off before it reaches the client.

Handovers are checked before close

A job can't move to acceptance until its handover record is attached and signed.

Subcontractor bills get reconciled

Each subcontractor bill is matched to its job and flagged when it exceeds the agreed rate.

The system works with the AI you already use

Claude, ChatGPT or a coding assistant can read and update the data in it, within each person's own access.

  • Claude
  • ChatGPT
  • Gemini

Switch in days, not months

We start with one thing your team does by hand today. Once that one is running, we take the next.

  1. 01.

    We learn how you work today

    We go through your documents, your rate sheets and how the desk handles them day to day.

    What we need from youOne session, and a sample document set.

  2. 02.

    We build it and walk your team through it

    The system works the way you already do. Your team is doing real work in it inside the first week.

    What we need from youOne person to review it with us.

  3. 03.

    We keep changing and improving it

    When the process changes or new work comes up, you tell us and we do it. The system keeps up with how you work instead of going stale.

    What we need from youA message when something changes.

500 containers a month.The paperwork closes at the gate.

“Documentation used to take around 2 hours/day; now it's usually done in 5 minutes. Most importantly, the team works from one set of numbers instead of conflicting files.”

Phuoc TranPhuoc TranGiám đốc (Director), Conta Vietnam

A copy per desk, reconciled by eye. Lotics keeps one shipment record. A change made anywhere is the change everyone sees.

Read the case study
Frequently asked questions

Typically 1-2 weeks. Week 1: build the data tables, document templates, and import existing data. Week 2: train staff and run real jobs. Setup is included in the plan.

Time with the team during the audit, your service rate sheet, SLA terms, and the document templates you use today, and someone to review as we build. We handle the rest.

Your team runs it day to day. We stay on to adjust the process, add templates, and add automations as the work changes. No rebuild from scratch.

We adjust the stages, templates, and automations to match, included in the plan. Adding a new service type or a new handoff step doesn't mean rebuilding the system.

By the people who use it each month, not a build fee. The price covers the platform, with AI credits included every month, and our building it for you; both step by band — 1–10, 11–30 and 31–70 people. The platform alone starts at $60 a month, and with us building and operating it, $120. There is no setup fee at any size. It starts with a free discovery call.

No. The coordination desk, job cockpit, and dispatch schedule all read and write the same service jobs — one source of truth, many purpose-built apps onto it. The scattered files and Zalo threads you have now are exactly what that removes, not adds to.

Yes. Each job carries its own service type on the same lifecycle from request to settlement. Screens filter by service type, and each team sees only its part.

Each job has its own SLA clock. Filter by jobs nearing the deadline to see them at once, and the system alerts the coordinator before a deadline passes without a handover.

Each handoff records the time, receiving party, and cargo condition. A job only advances once its handover record exists, so nothing falls between warehouse, transport, and delivery.

AI matches each subcontractor bill to its service job and flags anything over the agreed rate. The charges statement and job margin build themselves.

Yes. AI drafts them from the job data on your own templates. Your team approves before anything is sent to the client.

Email, client and partner portals, and accounting software. Data syncs, so nothing is entered twice.

Yes. Lotics supports spreadsheet import. Our team handles data conversion and import while we build the system.

Yes. Integrated with e-invoice providers and accounting software. Service charges and costs sync to accounting automatically.

Yes. Role-based permissions control who can view, edit, or approve specific records. Each person sees only what is relevant to their role.

Yes. Every change is logged with who made it, what changed, and when. Full history on any record for audits, disputes, or internal review.

Cloud servers in Singapore, encrypted in transit and at rest. Daily automatic backups. You own your data and can export everything at any time.

Yes. iOS and Android. Check status, receive notifications, and approve requests on the go. Real-time sync with web.

See your operations running on Lotics

The demo runs on your own documents, not on our example.

Book a demo

30 minutes, scheduled by phone or Zalo.