OmnioIQ · Solutions

Your orders in. Your brand on the delivery.

Send bookings from your store or order system. AgentQ plans them as they arrive, and your customers follow the delivery on a page that looks like yours.

API settings and docs page for a Fernway Couriers workspace, with a booking request and its response

Tracking

Customers see you, not us.

Your logo and colour sit on the tracking page and the console. Each link carries a long random token, and the customer confirms their postcode before the full address shows.

The map appears close to the ETA, not before.

Customer tracking page on a phone in Fernway Couriers colours
Settings page for API integration with webhook list; keys masked

Orders in, status out

Use the public API.

Create bookings, read routes and tracking, and manage drivers, vehicles, depots and zones through the public API.

Webhooks tell your systems when things change. Failed calls are retried and each one is signed.

Every workspace has its own docs page.

Windows and priority

A window is a limit, not a hope.

Delivery windows are hard limits. A booking that cannot make its window is left out with the reason, and appears under Needs you with one-click fixes.

Mark bookings express, standard or bulk. When not everything fits, that order decides what is dropped.

Needs you queue at Farringdon hub: a booking that could not be placed, with the reason and suggested fixes

Let AgentQ run a month of your routes.

You get an ROI report at the end with your numbers, measured on your operation.

Try it on your routesOne month, up to five drivers, before you sign anything.
Published pricingTiers on the site. No add-on menu, no annual lock-in.
We don't compete with youNo delivery service of our own, no shared customers.
Talk to the buildersYour account lead knows the code and the routes.
Pilot report: on-time rate, cost per drop and share of decisions made by AgentQ