Thursday, 14:00: Which Cars Aren’t Ready for the Weekend?

What “ready” means on a Thursday

A car is ready for a Friday booking when the customer can drive it away at the booked time and place without calling you. That comes down to four checks, and in most back offices they sit on four different screens:

• Fuel, read from telematics on the cars that report it. For a planned trip to Hatta, you'd want the car to leave with a bigger reserve than usual.
• Open alarms: a tracker that went quiet, a door left open, anything nobody has closed.
• Open service tasks. In October heat, an “AC not cooling” task that nobody has started matters more than a scratch on a bumper.
• Where the car stands, against where its next booking starts. Two cars returned in Al Barsha on Wednesday don’t help a family waiting at JBR on Friday morning.

None of it is hard. It’s slow, one screen at a time for 38 cars, and the late shift needs its list while there’s still time to drive across town.

All the cars here run on petrol. With electric cars, the same check works for charge only if your installation receives the battery level, so ask about that before you count on it.

Thursday, 14:00: one question, eight cars

The ops manager has ChatGPT connected to the platform and asks the way you’d ask a colleague:

Ops manager: cars booked from tonight 20:00 to saturday night. which ones arent ready? fuel under 25%, open alarms, open tasks, and parked away from where the booking starts. earliest booking first. read only

ChatGPT: 38 cars have a confirmed booking in that window, and 8 of them have something open. Fuel comes from telematics on 37 of the 38. #188 doesn’t report it, so I can’t tell you its level.

ChatGPT: #112 comes first. It’s the only car booked tonight, and it needs fuel and a drive to Terminal 3 before 23:30. #129, #127 and #171 already have open tasks that nobody has started yet.

The manager knows something the system doesn’t: the customer on #140 told the desk they’re going to Hatta. For a day trip into the mountains the manager would rather the car leave with a bigger fuel reserve, so #140 moves up the list. One more question before anything is created:

Ops manager: the 127 AC task, who has it and is the part there?

ChatGPT: It’s assigned to the Al Quoz workshop team, status New. The task doesn’t say anything about parts.

So the manager calls the workshop. If #127 isn’t fixed by Friday 08:00, the reservations desk will pick another car for that 09:00 JBR customer. Nobody wants to hand over a car with a weak AC at 38°C.

Operator console · demo data

The fleet data the AI assistant answers from

Fleet overviewFuel and mileage

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.

Fuel and mileage. Mileage, fuel spent, refuelling and suspected fuel drains per day for the whole fleet. A car low on fuel becomes an urgent refuelling task in the technician app.

×

Tasks for the field team, without doubles

Ops manager: propose field tasks for the rest. skip anything that already has an open task. due 1 hour before each booking

ChatGPT: Here’s the preview. Nothing is created yet.

ChatGPT: Left out because a task is already open: #129 (refuel), #127 (AC), #171 (tracker).

Ops manager: give 155 and 163 to the same technician, back to back. rest is fine. confirm

ChatGPT: Created 5 tasks. Read back from the platform: #112 refuel and move to Terminal 3, due Thu 22:30; #140 refuel, due Fri 06:00; #155 and #163 move to JBR, both with the Al Barsha technician; #188 fuel check, due Fri 11:00. All five have status New. Each call is in the audit log under your name.

By 14:20 the five tasks are in the technicians’ app. Every car still has exactly the fuel it had at 14:00. A task is a job handed to a person, and the refuelling, the driving and the AC repair happen only when somebody does them.

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 waits for a confirmation like the one above, and every call goes into the audit log. We enable it per installation, on request.

Friday, 06:30

Ops manager: yesterdays 5 tasks, which are done? anything new on cars booked before noon?

ChatGPT: Nothing new on cars booked before noon. The #127 AC task is still open; the workshop added a note at 18:40: “compressor ordered, ready Sunday”.

Four of five done, and the one that isn’t is the Hatta car, half an hour before pickup. The shift lead calls the JBR technician, and the desk lets the customer know about a short delay. Why did #140 slip? Its 06:00 deadline was the earliest on Friday, and the JBR technician may simply have started the day elsewhere. That’s a guess to ask him about, the data doesn’t say. #127 is now the desk’s call: the 09:00 customer gets a different car.

Before next Thursday

1. Agree the fuel level a weekend car must have, and a higher one for bookings of two days or more.
2. Ask the readiness question at the same time every Thursday, early enough for the late shift to finish the list.
3. Before creating tasks, ask which of those cars already have open ones.
4. On Friday morning, check task status next to what the cars themselves report: fuel and position.

On Friday evening the question shrinks to one customer and one car, and that’s our walkthrough of finding the nearest car a customer can actually take. If the Thursday list keeps showing the same cars parked in Al Barsha with no bookings near them, have a look at a one-week offer for idle cars. On Sunday morning a different list comes up: cars left outside the operating zone after one-way trips.

CT Mobility Solutions F.Z.C. · E-Commerce Hub BC-8, Ajman Free Zone C1 Building, Ajman Free Zone, Ajman, United Arab Emirates

Frequently asked questions