Tookan implementation and onboarding

We configure Tookan on your account, and your fleet, your drivers and your customers' orders move through one dispatch system. The work covers teams and roles, delivery zones, task templates, allocation rules, customer notifications and the driver app rollout.

• An account design paper: teams, roles, permissions and the administrator structure.
• A zone and geofence map, tested against a sample of your recent orders.
• Task templates for delivery, pickup and return, with the statuses your finance team needs to see.
• Allocation and escalation rules written in plain language before they are configured.
• A driver onboarding pack and training sessions for dispatchers and drivers.
• A go-live checklist and a 30-day stabilisation log.

• Orders reach a driver sooner, measured as minutes from order accepted to driver assigned.
• Drivers close more stops each hour.
• More deliveries land inside the promised window.
• You compare employed and contracted drivers on the same basis, and cost per delivery is reported by zone and driver type.
• More tasks close with proof of delivery.
• The operation settles quickly after go-live, measured in days from go-live to a stable daily operation.

Dispatch run by phone and chat hides what each delivery costs. Nobody can say how many stops a driver closed in an hour, which zone loses money at peak, or why late deliveries cluster on certain days. A licence bought without an operating model behind it gives the group a new screen and the same habits.

• Drivers are assigned by message and the dispatcher is the only person who knows where anyone is.
• You hold a Tookan plan and the fleet still runs from a spreadsheet.
• Delivery zones were drawn once and never tested against where orders actually fall.
• Employed and contracted drivers are paid on different bases and no one can compare their cost per drop.
• A second city or market is next and the first set-up cannot be copied.

Delivery operators, grocery and restaurant groups, distributors and retailers that run an employed fleet, a contracted fleet or a mix of both, and have decided to move dispatch off calls, spreadsheets and messaging groups.

At BaladiMart, Qasim Abbas set the capital logic behind a blended last-mile fleet of about 1,000 vehicles. He reads a dispatch set-up as a cost question first, and we configure every rule in your account with its effect on a drop in view.

We work in your Tookan account, under your own contract with the vendor. Start with the Control Diagnostic to decide how much of last-mile to control. See how fees work.

Whose account is Tookan configured on?

Yours. You contract with the vendor directly, and we configure the account and train your people.

Can we start in one zone?

Yes, and we recommend it. A single-zone pilot proves the rules with real drivers before the rest of the fleet is moved across.

How is delivery cost reported after go-live?

Cost per delivery by zone and driver type, with employed and contracted drivers compared on the same basis.

Let us know how many drivers you run and what the dispatcher uses today. We arrange a private briefing with the Managing Partner and settle whether a pilot zone is the right first step.