The booking command centre
Run your whole rental day from one screen.
Bookings, readiness, payments and fleet in one view, so nothing slips between the spreadsheet, the inbox and the whiteboard. Spot who needs a nudge before your first coffee.
A real Tuesday: nine bookings across five vehicles. Priya has not opened her pre check-in, and it is the first amber badge you see.
Tuesday, 8:42am
The spreadsheet only you can read
The colour coding made sense when you set it up, but now green means two different things and nobody else can drive it. You search the inbox for "did they pay" and scroll three months of threads. You catch a double booking by luck, on the phone, mid-sentence. The whiteboard was right last Tuesday, before someone rubbed off the wrong line.
None of it is one big problem. It is a dozen small ones, spread across five apps that do not talk to each other, and holding them together in your head is the actual job. The command centre puts the whole day on one screen so the day runs you a little less.
Who's picking up tomorrow, and are they ready?
The question your morning actually turns on is not "what are all my bookings" but "of the ones happening soon, which still need me". A rental booking system that only lists everything makes you do that filtering in your head. The day view does it for you.
Every pickup and return carries a ready-or-not badge built from its readiness gates, with the reason spelled out on the ones that are not green. A two-minute scan tells you who to chase today and who needs nothing. The customer who has done everything is left alone; the one who has not is right there in amber.
Getting each booking ready before the customer arrives is its own craft. That is the pre-pickup flow; this page is about seeing the whole board at once.
You start the day ahead of the counter, not behind it.
Tomorrow's pickups, ready or not, with the outstanding item named on each.
Two bookings on the same vehicle
A double booking is the error that costs you a customer. In a spreadsheet it hides in plain sight, because a date range in one cell does not warn you that another cell overlaps it. You find out when two people arrive for the same Hiace.
The fleet calendar lays every vehicle out as a row and every hire as a bar, so an overlap is visible before it can happen, and availability is checked against the same bookings the calendar draws. When two hires sit back to back on one vehicle, you see the handover between them, not a clash.
The double booking you used to catch by luck, you now catch by looking.
Back-to-back hires on the Hiace, allocated without a clash.
The customer who hasn't paid their balance
"Did they pay?" should take a glance, not an inbox search. When the answer lives in a payment provider's dashboard and your memory, it is easy to hand over keys on a booking that still owes you money, or to chase someone who paid last week.
Each booking shows what has been captured and what is outstanding, read from the actual payment records rather than a number typed in by hand. A balance due before pickup is flagged, and one action sends the customer a payment link, straight from the booking. Bonds are handled the same careful way, which is a story of its own on the payments and bonds page.
No keys leave the desk on an unpaid balance you did not know about.
$415.38 still due before pickup, with the send-link action right there.
Turnaround time between hires
A vehicle is not available the instant it is returned. It needs cleaning, an inspection for new damage, sometimes a relocation to the branch its next hire starts from. Book the next customer too soon and you are either handing over a dirty car or making them wait while you rush it.
Glovebox knows the gap between one hire's return and the next hire's pickup on the same vehicle, and it knows the turnaround buffer you set for that fleet. When the gap is tighter than the buffer, it flags the booking before you commit to it, so a three-hour turnaround on a van that needs four is a decision you make on purpose, not a surprise on the day.
The buffer to clean and check is protected, not quietly booked over.
Tom returns the Hiace at 2pm; it is out again at 5pm. Three hours, on a four-hour buffer.
Finding a booking without scrolling
A customer rings about their hire and you have thirty seconds to find it while they wait. Scrolling a list or opening the spreadsheet and using find is not a system, it is a stall. You should be able to type what you know and land on the booking.
The bookings search matches on the things you actually remember: a name, an email, a phone number, a booking reference, or the vehicle's rego. Type a plate and every hire that vehicle has had comes back; type a surname and there they are. No exact-match guessing, no remembering which field to look in.
You find the booking while they are still telling you the plate.
One rego, every hire that Hiace has had, found by typing.
What actually happened on this booking
Three months later a customer disputes a charge, or a colleague picks up a booking you started and needs to know what has been said. If the history lives in one person's memory and a scatter of sent emails, you are reconstructing it under pressure.
Every booking keeps a timeline: the notes your team leaves, the emails Glovebox sent and when, and the system events like a deposit captured or a bond confirmed. It is all timestamped and attributed, so a handover between staff or a dispute months on has a straight record to read instead of a guess to make.
The answer to "what happened here" is on the booking, not in someone's head.
Notes, emails and system events on one booking, newest first.
One place, not five apps
Most rental businesses run on a stack that grew by accident: a spreadsheet for the schedule, a website form for bookings, a payment dashboard for money, an inbox for everything else, and a whiteboard for what falls through the gaps. Each is fine alone. Together they are the overhead.
The dashboard is the one screen that ties it together: today's movements, what needs attention, and the state of the fleet, all reading from the same bookings. It is not another app to check. It is the one that means you check fewer.
The stack becomes a single screen you open once.
The day in one view: movements, attention, and the fleet at a glance.
Tuesday morning
Nine bookings, one screen. Have a look around.
This is a real operator's Tuesday, rendered from live components. Click a booking, or use the arrow keys, and its detail opens on the right. Start with the three that need attention, then explore the rest. Nothing here is a mock-up, and nothing you press sends a message or a charge.
This one needs a nudge. Priya picks up tomorrow but has not opened her pre check-in. One tap re-sends the invite.
Balance outstanding. Ben still owes $415.38 before pickup. Send the balance link without leaving the booking.
Tight turnaround here. Tom returns the Hiace at 2pm and it is booked out again at 5pm. Three hours to clean and inspect.
Questions
The command centre, answered
Can I see all my vehicles and bookings in one calendar?
Yes. The fleet calendar shows every vehicle as a row and every hire as a bar across the week, so you can see at a glance what is out, what is due back, and where the gaps are. Because availability comes from the same bookings your front desk confirms, the calendar is never out of step with reality.
How do I know which customers are ready for pickup?
Each booking carries a readiness state built from its gates: licence, pre check-in, agreement, and bond. The day view badges every pickup as ready or not ready, so a two-minute scan each morning tells you exactly who still needs a nudge. You can open any booking to see which specific gate is outstanding.
Does it track payments and outstanding balances?
Every booking shows what has been captured and what is still owed, drawn from the actual payment records rather than a figure typed in by hand. When a balance is due before pickup, it is flagged on the booking, and you can send the customer a payment link without leaving the screen.
Can my staff use it on their phones at the vehicle?
Yes. The day view and the handover flow are built mobile-first, so a staff member can pull up the next pickup, walk around the vehicle, capture photos and the odometer, and complete the handover from a phone at the kerb. There is nothing to install.
What happens to my existing bookings if I switch?
Moving over is a migration, not an overnight flip. We support imports where they make sense and parallel running while you build trust in the new numbers, so your existing bookings come across and nothing is stranded. You pick the cutover week.
Can more than one staff member work in it at once?
Yes. Glovebox is a shared operator workspace, so several team members can be working across bookings at the same time. Notes and timeline entries are attributed and timestamped, so it is always clear who did what and when, which matters most when a booking passes between staff.
Does it work for a fleet of three vehicles, or only big operators?
It is built for small operators first. A three-vehicle fleet gets the same day view, readiness, calendar, and payments as a fifty-vehicle one, without the enterprise overhead. The point is to replace the spreadsheet and the whiteboard, whatever the size of the fleet.
See how it is priced on the pricing overview, or read the two flows this view sits on top of: the pre-pickup flow and payments and bonds.