Tookan implementation and configuration

We configure Tookan on your account: teams and geofences, task templates, assignment rules, driver and rider profiles, notifications, pay and commission fields, and the reports your managers open each morning.

Your group holds the Tookan account, the licence and the agreement with the vendor.

• A configuration specification covering teams, regions, task types and statuses.
• Assignment rules built from the dispatch workflow you have approved.
• Pay, incentive and cost fields on each task, so earnings and delivery cost can be totalled by driver, vehicle and zone.
• Customer notification templates in the languages you serve, English and Arabic included.
• A reporting set, a training session for dispatchers and a handover record of every setting.

• Every task arrives with complete cost and pay fields.
• The days from month end to final driver payout are counted and reported.
• Dispatcher time spent on manual assignment per shift is measured, shift by shift.
• A new zone or team is added from a template.
• Platform records match partner invoices.

Platforms are usually set up for dispatch only. Pay fields are added afterwards, task statuses mean different things to different teams and reports are rebuilt by hand in spreadsheets. The platform then holds good data that nobody can use for cost per drop or driver pay.

• Different branches use the same task status for different events.
• Driver pay is calculated in a spreadsheet after the month ends.
• Your team cannot export a clean delivery list that matches an invoice from a partner fleet.
• Customers receive notifications that no one approved.
• A new city takes weeks to add because settings are copied by hand.

Delivery businesses, retailers, restaurant groups and distributors that run or intend to run Tookan for their own fleet or for a mix of employed and partner drivers, and the finance leads who rely on its output.

Qasim Abbas set the capital logic for a group with a last-mile fleet of about 1,000 vehicles. The configuration is built around the numbers a finance team later asks of the platform, so pay fields and cost tags come before cosmetic settings.

We build in a test environment on your Tookan account, under your own agreement with the vendor. See how fees work.

Whose account and licence is it?

Yours. We work on your own account, under your own agreement with the vendor, and you hold the licence and the pricing.

Can you move us to Tookan from another dispatch tool?

Yes. We plan and run the configuration side of the move and map your historical data to the new fields.

If you run Tookan or have chosen it, send one week of your tasks to a private briefing. We return the cost and pay fields the platform has yet to record.