Cordic, Autocab or Cab9: what actually changes when you outsource the desk

7 August 2026 · 6 min read · Abdul Aleem Sajjad

The first question every operator asks is whether they will have to change dispatch software. The answer is no: we log into yours. But the platform does change how the first fortnight goes, and it is worth knowing where the friction sits.

What stays the same on every platform

Booking intake, allocation logic, account rules and escalation are all decided by your runbook, not the software. Whichever system you run, we are following the same document your office would follow.

Where the platforms differ in practice

• Permission granularity. Some systems let you scope a remote user tightly; others are closer to all-or-nothing.
• Call integration. Where CLI lookup and screen-pop are configured well, answer times drop noticeably.
• Account job handling. Corporate rules are stored differently across platforms, and this is the most common place a runbook needs a second draft.
• Reporting exports. Some systems give clean answer-time data out of the box; others need a weekly export we build into the reporting pack.

The software is rarely the constraint. Undocumented decisions are.

The four things to prepare before day one

• A user account scoped for a remote dispatcher, with permissions you are comfortable with.
• A list of your account customers and the rules attached to each one — including the unwritten ones.
• Your escalation contacts by hour: who is called at 1am, and who is not.
• Sixty days of answer-time and cancellation data, so the parallel run has a baseline.