Friday, 18:30, Dubai Mall. A customer calls support from the Fashion Avenue car park: the app shows a car 200 metres away, and every time they try to book it, it fails. They’ve already walked one level down to look for it. They want a car, and they want it now. The fleet, car numbers and times in this walkthrough are a demo, made up for the example.
Short answer: Rank the cars around the customer by distance, then drop the ones they can’t take: a position that’s hours old, a rental already running, a customer group or zone this customer doesn’t belong to, an open workshop task or alarm, and low fuel where telematics reports it. Support offers the first car that passes, and someone deals with the rest.
Last updated:
November 7, 2026

Distance is the easy part. A car sharing app sorts cars by coordinates, but those coordinates are only as good as the last message the car sent. Under a mall or a tower, that message can be hours old. And a car can be close and still useless to this particular customer for half a dozen ordinary reasons.
Here’s what we’d check before telling anyone to walk over:
Support usually checks these one screen at a time: the map, then the rental, then the tasks, then the customer’s group. With a queue of calls on a Friday evening, that’s where the minutes go.
The support agent has ChatGPT connected to the platform and types the way people type on a busy shift:
Support agent: customer at dubai mall, fashion avenue parking. app shows a car 200m away but booking fails. which cars within 1 km can they actually take right now? closest first, and tell me why the others are out. read only
| Car | Distance | Last position | Status | Can they take it? |
|---|---|---|---|---|
| #318 | 200 m | 15:20, three hours ago | Free, open task “check tracker” | No: the car may not be there, and the tracker is under a task |
| #207 | 350 m | 18:28 | Rental started 18:05 | No: someone else is driving it |
| #145 | 500 m | 18:26 | Free | No: visible to a corporate customer group only |
| #262 | 800 m | 18:29 | Free, fuel 64% | Yes |
| #331 | 1.1 km | 18:27 | Free, low-fuel alert at 17:50 | Yes, but it’s just outside 1 km, and the fuel may not last a long trip |
ChatGPT: #262 is the closest car this customer can take. It’s parked on the Downtown side, about a ten-minute walk. #318 is probably what the customer sees: its last position was recorded before it went quiet, so it may already have been moved. I’ve listed #331 as well: it’s just outside the 1 km you asked for, but it’s the next car they could take.
The agent asks one more thing before calling the customer back:
Support agent: who has the 318 task and has anyone started it? and does 331 have a refuel task?
ChatGPT: The task on #318 was created at 16:05 and assigned to the Downtown technician. It hasn’t been started. #331 has no open task.
Three minutes, and the agent knows what to say, which car to point to and where the real problem sits. If something in the table looks off, #318 is one click away in the control panel.
Operator console · demo data


Fleet overview. Utilisation, active rentals, revenue in AED and the cars that need attention: the figures the assistant reads when you ask about your fleet. Technicians get a prioritised task list.


Live map. Every vehicle, its status and service zones on one map, updated in real time. Riders see the same available cars nearby in their app, with the model and fuel level.
The assistant ranked and explained. The rest was people.
The agent told the customer to book #262, gave them the level and the walking direction, and stayed on the line until the booking went through. The customer booked it in the app themselves. Then the agent asked the assistant to create a refuel task for #331 in the Downtown zone, saw the preview, pressed Confirm, and the task went to the field team. Nobody touched #318: a task was already open, and a second one would only confuse the technician. The shift lead got a one-line note to chase it.
On control: Ask your fleet, the MCP server built into CT Mobility, works under each employee’s own login and permissions and is read-only by default. Changes work only if the employee allowed them when connecting, each one needs a confirmation, and every call is written to the audit log. We enable it per installation, on request.
Start with the position timestamp: if it’s much older than your installation usually reports, treat the dot on the map as a guess. Underground car parks at Dubai Mall, DXB Terminal 3 or the towers in JLT swallow the signal, and the app keeps showing the last place the car reported. Booking status and customer groups come next. Fuel matters only where the installation reads it from telematics; if it doesn’t, the assistant says so instead of guessing.
Airports are their own case. At DXB Terminal 3, a customer off a late flight wants the car closest to arrivals, and the car closest on the map can be one floor away in a car park where the signal is weak. The same question works there, with one change worth making: ask for cars whose position is under 15 minutes old first, then the rest. A walk to a car that turns out to be somewhere else costs more at an airport than anywhere in the city.
The opposite call happens too: a customer who can’t end a trip in the same basement. We wrote that one up in a customer couldn’t end a rental.
For the platform behind this, see the AI car sharing platform. If you’re weighing AI tools for your back office, start with our guide to MCP for car sharing and rental operators.
CT Mobility Solutions F.Z.C. · E-Commerce Hub BC-8, Ajman Free Zone C1 Building, Ajman Free Zone, Ajman, United Arab Emirates
No. The customer books in your app as before. Ask your fleet is used by your employees in their own AI client, connected to the back office.
There’s no public price. We enable it per CT Mobility installation on request, so the quickest way to find out is to book a demo from the Ask your fleet page and ask about your fleet.
We have repeatedly proven this in practice with dozens of launched projects and years of successful work. Ask our clients who have tried several IT solutions but still remain with us.