What's new in Glovebox

Ask Claude to read your site and it sees what Site Studio sees: the theme and brand colours, every built-in page's words (home, fleet, about, FAQ, terms), contact details, socials and opening hours, the menu, and whether the site is live, with the preview link.

Then tell it what you want. "Make it the Coastal theme with our navy." "Write the about page: two vans in 2019, twelve today, airport pickups." "Add an FAQ about taking the van on the ferry." "We're closed Sundays." "Publish it." Each proposal comes back as a preview with the before, the after, any warnings (a very light brand colour, a headline that will wrap on a phone, a site going live with no rated vehicle group yet) and a link to the page. Nothing is saved until you say yes in the conversation.

One thing to know: a Glovebox website has no draft copy. Once the site is live, a change you confirm is public straight away, exactly as saving in Site Studio is, so look at the preview first. Logo, favicon and photos, custom domains, custom pages and customer reviews stay in the admin.

Ask Claude "what do I need to do this week?" and it reads the same Coming Up sheet and dashboard you do: every pickup, return and transfer by day with the customer, the vehicle, any balance owing and anything to fix first; the Needs Attention list (overdue returns, unpaid deposits, unsigned agreements, missing licences, bonds not held); and the fleet items falling due, such as a WoF expiring, a low RUC balance, or a service overdue.

Ask "how's the fleet?" or "what's due on #8?" and it lists each vehicle's WoF or CoF, rego and insurance dates, its RUC balance against your threshold, its service schedules with what is due by kilometres and by date, any open jobs, whether it is off the road, and the last odometer reading. "What's been done to #8?" gives the completed jobs with cost, provider and invoice reference.

If you allow changes, Claude can also record an odometer reading, top up RUC, log a service or repair as done (the schedule's next-due rolls forward and the vehicle comes back on the road), or book a vehicle in for work with an off-road window. As with every change through the connector, it shows you the before, the after and any warnings, such as a booking an off-road window would collide with, and applies nothing until you say yes. Servicing needs the Maintenance module on.

A new opt-in module lets you connect Claude (Desktop, Code, or claude.ai) to your own workspace. Generate a token under Settings › Claude connector, add it to Claude (for claude.ai, add a custom connector at https://mcp.getglovebox.co.nz/mcp and paste the token when asked), and ask things like "what's picking up this week", "revenue last month" or "how many Jimnys are free over Labour weekend".

Everything is read-only for now, and every answer comes straight from your own bookings, payments and availability. Revoke a token at any time, or switch the module off to stop every token at once.

When you generate a Claude connector token you can tick "Allow changes with this token". Claude can then propose three kinds of change: close a location on certain weekdays or dates, set the minimum booking lead time, or add a seasonal percentage rate for a date range.

Nothing is applied on the first pass. Claude shows you what would change, including anything it would override, and only applies it after you agree in the conversation. Every applied change is recorded on your workspace timeline, and seasonal rates added this way are capped at ±50% and marked as coming from the connector in Pricing.

Existing tokens stay read-only.

Add the Glovebox connector in Claude, click Connect, and you are brought to Glovebox to sign in with your usual account. Tick the workspaces you own, choose whether Claude may propose changes, and you are back in Claude. Own more than one business on Glovebox? Tick them all and Claude sees them on one connection.

Nothing to copy or paste. Each connection shows up under Settings › Claude connector, labelled with the date you signed in, where you can revoke it. Generating a token by hand is still there under "Advanced" for scripts.

Ask Claude something like "what should a 5-door cost over Christmas?" and it reads your demand pricing engine's suggestion for that group and those dates: the base rate, the suggested rate, and the reasons (how full the group is, how far out the dates are, how bookings are pacing). It works even if you keep the engine switched off, as advice only.

If you like the suggestion, say "apply it". Claude proposes a rate adjustment for that group and date range, shows it to you first, and applies it only after you say yes. Whatever is proposed is held inside the group's rate band from the demand pricing page. If the suggestion would go past your floor or ceiling, Claude says so and applies the bounded figure instead; only you can widen a band, and only in Glovebox.

Applied adjustments appear in Pricing marked as coming from the connector, and on your workspace timeline.

Use Claude with your workspace, under Help › Guides, walks through connecting Claude by signing in, what it can read (bookings, revenue, fleet, availability, locations, embed snippet), the four kinds of change it can propose with your approval, and how to disconnect.

The privacy policy now lists Anthropic (Claude) under "Who we share it with", with the same rule the connector applies: nothing is shared unless a workspace owner connects, and disconnecting stops it.

The flight data provider offers a predicted arrival based on a route's past performance, not live tracking. It was being shown as an estimate, which is how JQ171 read four minutes early all afternoon while it was running late.

Now only a real revised time from the airline or airport counts as an estimate. Without one, once the flight has departed the departure delay is carried across to the scheduled arrival; before departure, only the schedule is shown.

Every flight number on the dashboard's Flights card is now a link. It opens the flight on FlightAware in a new tab, showing where the plane is right now, so you can check an arrival before heading to the airport without leaving Glovebox.

Only real flight numbers are linked (an airline code and a number, like JQ171 or NZ0247). If a customer has typed an airline booking reference into the flight field instead, it stays as plain text.

You need time to roster a driver. Under Settings › Booking policies, set how many hours before pickup an airport transfer can still be added. Inside that window the transfer is withheld and the booking page says why, so customers are not left guessing.

Off by default; existing bookings are untouched.

A new setting under Settings › Website, called Your website, lets you say whether bookings run on your own website (with the embedded widget and fleet catalogue) or on a Glovebox-hosted site built in Site Studio.

It is a preference, not a migration: switching never publishes, unpublishes or deletes a site, it only changes which tools Glovebox puts in front of you.

Parking notices come to the registered owner, long after the driver has gone. FinePass closes that loop.

Switch it on under Revenue › FinePass. When a notice arrives for a vehicle that was on hire, Glovebox matches the plate and time to the booking and shows you a one-question review. Confirm it, and FinePass sends the notice to the driver with your handling fee added, chases payment, and pays you out through Stripe. The parking company only learns who the driver was once the cycle completes, and no customer list ever leaves Glovebox.

The module checks your rental agreement carries the disclosure clause before it connects.

If you embed both the fleet catalogue and the booking widget on your own website, the catalogue's Book now buttons and date search used to send customers to the Glovebox-hosted booking page. You can now set your own booking page URL under Settings › Website, and every link on the catalogue uses it. The vehicle group is carried across so the customer lands on the right car.

The Fleet app now has a bottom tab bar (Vehicles, Overview, Prep, Settings), and Prep this week is finally reachable from it.

Each vehicle card carries a due line, worst first: COF expired 12 Sep, RUC 900 km, Rego 3 Oct. Critical items are red, attention items amber, and a healthy vehicle shows its nearest expiries. A state chip says whether the car is on hire, in the yard or in transit.

On iPhone, the home-screen icon now opens already signed in instead of asking you to log in again.

Free Legs used to ride along with the Transfers module, so every operator with transfers saw Send to Free Legs whether or not they had an account. It is now its own module in the marketplace, free to switch on, with a Settings › Free Legs page showing your connection status and fleet mirroring. With it off, nothing Free Legs shows or runs.

If you were already signed in and opened your workspace's login page — from a bookmark, a link in an email, or just a new tab — Glovebox signed you out, showed the login form with your email filled in, and signed you back in when you submitted it. That looked harmless, but it invalidated every other Glovebox tab you had open: the next time you pressed save in one of them you got "Error while loading page", and your changes were not saved.

This is what was behind the report of the rental terms "reverting" after long edits. It could hit any page.

Now, opening the login page while signed in simply takes you to your dashboard. Nothing else changes.

If you have been caught by this: your saved content is intact, but edits made in a tab that showed that error did not go through. Reload the page before editing again.

If your website is on a getglovebox.co.nz address, its Fleet page — and the results page a customer lands on after picking dates on your homepage — returned a blank "403 Forbidden" from about 11pm on 14 September until this fix was deployed. Sites on your own custom domain were not affected.

The cause was a folder added for the Fleet mobile app that happened to share its name with your website's /fleet page, so the web server answered before Glovebox could. The folder has been moved, and there is now an automated check that stops any future folder from colliding with a page on your site.

No action needed on your side. If a customer told you the search "went to a 403 page", this was it.

iPhones save photos as HEIC by default. Glovebox accepted them but the upload preview refused the format, so the upload failed with an error. Fixed: HEIC and HEIF preview and upload like any other photo.

If you pasted your rental terms into the onboarding box as plain text, every consumer treated them as HTML and collapsed them into a single run-on block: the Settings editor, the rental agreement PDF, your public terms page and the Free Legs transfer agreement. Blank lines now become paragraphs and single line breaks are kept, everywhere the terms appear.

Two fixes to the cover upsell emails your customers receive before pickup:

• The "Upgrade cover" button opened an error page. The link in the email pointed at a host where the upgrade page could not work out which operator the booking belonged to, and failed. The page now resolves the operator from the booking itself, so every link — including the ones already sitting in customers' inboxes — works.
• The upgrade offer appeared twice. The email listed the same "Upgrade to Premium Excess Reduction" line two times. It now appears once. If you have customised the email template and left out the offer list, it is still added for you as before.

No action needed on your side.

Australian rental operators can now run on Glovebox. Signup asks for your country and your ABN, charges are taken in AUD and settle in your own Stripe account, invoices sync to Xero with Australian GST, and every time you see is in your own timezone.

New Zealand operators see no change.

Prices are stored ex-GST at two decimals and shown inclusive, and grossing them back up could land a cent out: a $90 a day by 19 days line printing as $1,710.02. The Pricing tab now derives each line from the inclusive figures the customer was charged, so the lines and the total agree.

The emails you get while setting up Glovebox were written for the old 90-day trial, so a few of them said things that are no longer true.

What changed

• No setup email mentions a trial or counts down to a date, because nothing expires.
• The "try booking your own vehicle" email used to say your booking page was live and that the payment went into your own account. Neither is true in a sandbox: the page is not public, the card payment runs in test mode and nothing is charged. It now says so plainly.
• Your welcome email states the sandbox rules in one line, so it is clear from the start that bookings are test bookings and no emails reach your customers.

One new email. Once your workspace can actually take a booking, you get a single message explaining what going live does — public booking page, live card payments, customer emails switched on — and what your plan costs, at your own fleet band's price. There is no deadline attached to it, and it is never sent to operators who are already trading or already live.

Editing a booking that already has a tax invoice no longer rewrites that invoice. Glovebox issues a new, sequential invoice number, keeps the superseded version, and shows both on the booking's Documents tab and in the customer's portal.

Xero stays consistent: an unpaid invoice is voided, a paid one gets a credit note, and the new invoice is synced in its place. Only money changes trigger a new version, so fixing a name or a note leaves the invoice alone.

Repricing also gained an option to keep the customer's original daily rate when the dates change.

Opening Go live from the sidebar returned a server error rather than the page. This affected every workspace, whatever state its billing was in, so nobody could reach the page that starts a subscription.

If you tried to go live recently and hit an error, nothing went wrong with your workspace or your billing. The page itself was failing to load, before it had read anything about your account. Nothing was charged and nothing was half-finished, so you can simply open it again and carry on.

The page now loads for every workspace, including grandfathered founding members, whose message about keeping their existing arrangement appears as it should.

Plenty of operators already have a website they are happy with and only want the booking engine, so they embed our widget rather than publish a Glovebox site. Until now the system did not count that as being ready to take bookings.

What that meant. If the widget was your booking page, your setup was treated as unfinished no matter what you did. The Go live page told you to publish a booking site you had deliberately chosen not to use, and it never offered you the button to start your subscription. Because going live was out of reach, your workspace stayed a sandbox, and in a sandbox every booking is recorded as a test booking, so a real customer could book through your widget without a payment being taken.

What changed. Having the widget embedded on your own site now counts exactly the same as publishing a Glovebox site. Either one satisfies the "somewhere to book" requirement, so you can go live on whichever you actually use. The setup checklist item now reads "Give customers somewhere to book" and ticks for either, and the Go live page names both options instead of only ours.

Nothing changes if you use a Glovebox site. This only widens what counts, it does not remove anything, and the other requirements are untouched: you still need a vehicle, a pickup location and a connected payment gateway.

Your Glovebox website has a proper Business info section now, under Website → Business info: your street address, opening hours (set per day, mark days closed), social links, a short one-line intro, and a map pin (latitude/longitude).

Fill it in and it flows through your whole site:

• Footer — your address, a click-to-call phone number, your socials and quick links appear on every page (no more near-empty footer).
• Contact page — a real address, an opening-hours table, your socials, and an embedded map, alongside the enquiry form.
• Header — a tap-to-call phone number.

Behind the scenes it also gives Google a much richer picture of your business — a LocalBusiness profile with your address, map location, opening hours and social profiles, plus proper breadcrumbs on your fleet and category pages. That's the kind of structured data that helps you turn up in local search and maps.

Nothing changes until you fill it in, and anything you'd already entered as free-text contact details still shows.

The homepage editor (Website → Pages → Home) has new trust sections you can turn on to help visitors book with confidence:

• Why choose us — a short strip of reasons to book with you (fair pricing, a well-kept fleet, quick booking — edit them to suit).
• How it works — the steps a customer follows, shown numbered, so first-time visitors know what to expect.
• Customer reviews — add real quotes from your own customers, with a name and a star rating. These are only ever the reviews you enter — nothing is invented, and the section stays hidden until you add one.
• Common questions — a toggle that pulls the first few questions from your FAQ page straight onto the homepage.
• Where to find us — a toggle that shows your address and an embedded map (using the address you set under Business info).

Each section only appears once it has content, so nothing changes on your live site until you fill it in. New sites start with sensible starter copy for the first two, ready to edit.

These sections show on the Studio, Coastal and Express themes; the Premium theme keeps its own built-in homepage layout.

The Book now button in the site footer was rendering on top of the Explore links on the Studio and Coastal themes — the vertical padding of the button was overlapping the "FAQ" link above it.

The button now behaves as a proper full-width button and sits below the links, with its label centred. No content or links changed — this is a styling fix only, and the Express and Premium themes were already correct.

Expanding a vehicle group in the fleet widget shows a strip of photo thumbnails, and clicking one swaps the large photo at the top of the card.

The strip left out the photo already on display, so once you clicked a thumbnail there was nothing to click to get the original back. The only way to restore it was to reload the page.

The strip now shows every photo in the group, including the one currently on top, and the one on display is outlined so you can see where you are. A group with a single photo shows no strip at all, since there is nothing to switch between.

Glovebox no longer runs on a 90-day free trial. There is no countdown, and nothing expires.

Instead, your workspace is a sandbox: free for as long as you want it. You can add your fleet, set your pricing, publish a booking page, write your emails and run bookings end to end. In a sandbox:

• every booking is a test booking;
• card payments run in test mode, so nothing is charged;
• no emails reach your customers.

When you are ready, Go live starts your subscription, makes your booking page public, switches payments to live and starts customer emails. Your test bookings are kept, but hidden from your reports so they never muddle your numbers. You can find it under Settings → Go live, and once your setup is finished it appears on your dashboard checklist too.

What this means for you

• If you are already taking real bookings, nothing changes. Your rate, your founding pricing and your access all stay exactly as they are.
• If you signed up on a trial that is still running, you keep every day you were promised — going live simply starts your subscription when those days run out.
• If you are still setting up, you now have as long as you like, with no deadline and no card needed to start.

A new strip at the top of your admin tells you which state you are in, so it is always clear whether a booking is real or a test. If a payment ever fails, you keep trading for 14 days while you sort it out; your existing bookings, payments and customer emails are never affected.

Two small improvements to website enquiries:

• Optional phone field — the contact form on your website now has an optional "Phone" field, so an enquiry can arrive with a number to call back on, not just an email address. It shows on the enquiry under Website → Enquiries.
• Delivery status — each enquiry now records whether the notification email was actually sent to you. The enquiry list has a "Mailed" column, and the enquiry detail shows "Emailed to you" (or "Not sent"). Because every enquiry is saved the moment it is submitted, you never lose a lead even if the email cannot be delivered — it is still waiting for you in the admin.

Nothing else changes: the form still works without a phone number, and existing enquiries are unaffected.

When you add a vehicle you can create its group inline, from the group dropdown. That form asked only for a name, so the new group arrived with no price. Setting one meant remembering to open the group editor afterwards, and until you did, that group was offered to customers at $0.00 a day.

The inline form now asks for the daily rate alongside the name, and will not create the group without one. Nothing else changes: the rate still lives on the group, every vehicle in a group still hires at the group's rate, and you can change it later in the group editor as before.

This mostly helps if you price each vehicle separately, which you do by giving each car its own group. That is now two fields on one screen rather than a round trip to the group editor for every car.

A vehicle's page had grown to six buttons across the top. Two of them were embed codes with near-identical names — "Embed code" and "Embed this vehicle" — with nothing on the button to tell you that one gives you a booking form and the other shows the car.

Log reading stays where it was, since it is the one you use regularly. Everything else — photo history, servicing record, both embed codes, and delete — now sits under a More menu next to it.

The two embed codes are now named for what they produce:

• Embed booking widget — the booking form, opening on the dates step, set to this vehicle.
• Embed vehicle card — a card showing this vehicle, priced at its group rate.

Nothing has been removed and no button has changed what it does.

Two improvements to your Glovebox website.

Enquiries are saved. When someone fills in your website contact form, the enquiry is now recorded in your admin under Website → Enquiries — with their name, email, message and which page they came from. It is saved first and the email to you is sent second, so even if an email hiccups, the lead is never lost. Enquiries are delivered to your site's contact email (or, if you haven't set one, to the account owner).

Analytics that work. Your Google Analytics, Google Ads and Meta (Facebook) Pixel IDs now live together in Website → SEO & analytics, and they load on your live public site straight away. Previously the analytics box on the website settings didn't feed your live site — if you'd added a code there and wondered why you saw no data, add it again here and it will start tracking.

We've also tidied a few rough edges: vehicles with no photo yet show a tasteful branded placeholder instead of a blank space, and your FAQ page now helps you show up in Google's FAQ results.

Your Glovebox website now works the way customers shop for a rental — by category, not by individual rego.

Fleet by category. The fleet page and your home page now show vehicle categories (your groups) — a representative photo, the key specs, and one honest "from" price that includes GST, the same figure your booking widget uses. No more three-different-prices, and never a "$0/day": a category we can't price yet reads "Price on request".

Search that filters. When a visitor picks dates on the home or fleet search, the fleet now shows only the categories actually available for those dates, at the price for that window, and carries the dates straight through to "Book". A new "Book" link in the header jumps them to it.

A page per category. Each category has its own page with its gallery, description, features and a Book button. Your old per-vehicle links (/vehicles/…) now permanently redirect to the category page, so nothing you've shared breaks and search engines follow along. The sitemap lists the category pages.

You can dress each category for your site — its own description, hero image, gallery and features — the same way you could a vehicle before.

An over-mileage charge email included a direct Stripe payment link. Stripe payment pages expire after about a day, so a customer who opened the email later landed on a blank "You're all done here" page and could not pay, with no obvious way forward.

The Pay button now points at a Glovebox link that opens a fresh Stripe payment page every time it is clicked, so it works whenever the customer gets to it. Nothing about the amount charged changes. If the charge has already been paid, the link now sends them to their booking with a note rather than a dead end.

The same expiring-link problem that affected over-mileage charges also affected other post-hire charges (excess kilometres, cleaning, tolls and similar). Both the emailed Pay button and the "Pay now" button on the customer portal pointed at a stored Stripe payment page that expires after about a day, so a customer coming back later landed on a blank "You're all done here" page.

Those buttons now open a fresh Stripe payment page every time they are clicked, so the customer can always pay. Nothing about the amount charged changes, and an already-paid charge sends them back to their booking with a note instead of a dead end.

You can now show your whole fleet on your own website — WordPress, Wix, Squarespace or hand-coded — with a single line of code. Go to Settings → Website → Embeds, choose your accent colour and button text, and copy the snippet. Paste it once where you want the fleet to appear.

Each vehicle group shows as a card with its photo, key specs and a "from" price (GST inclusive), and a button that takes the customer straight into your Glovebox booking widget with that group already selected. Dates and availability are handled in the booking widget, as always — the fleet page is your shop window.

The look is driven by your saved settings, so changing a colour or the button text never means re-pasting the snippet. There's a live preview on the settings page so you can see exactly what your visitors will see before you publish.

The embedded fleet widget laid its vehicle cards into as many columns as the page was wide, then left the unused columns empty. An operator with two or three vehicle groups saw their cards pinned to the left edge of a wide page with a large blank area to the right, which read as a broken embed rather than a small fleet.

The widget now sizes itself to a comfortable reading width, centres on the page, and only creates as many columns as there are vehicles to fill — so two cards sit centred and evenly sized instead of stranded. A larger fleet fills the grid and wraps exactly as before.

If your site deliberately places the widget full-bleed, you can widen or remove the limit from your own page with the --gf-max-width custom property.

The customer booking portal used to explain the excess-reduction upgrade twice: a "Your protection" card with a comparison table, and a separate "Reduce your excess before pickup" card with a "See upgrade options" button. They are now a single Your protection card, benefit first.

The card leads with the stake ("Your excess is $X if anything happens"), keeps the what's-covered comparison with the upgrade shaded, and puts the action inside the upgrade column: Upgrade for $X/day, with the total shown underneath. The button goes straight to the secure checkout, with no in-between page, and a compact version sits in the right-hand rail too. Once a customer upgrades, the card shows an Upgraded tag and collapses to their new cover. Nothing about the price or how upgrades are charged has changed, and customers on operators who are not set up for online card payments still see the comparison with a prompt to ask at pickup.

The customer booking portal now has a Your extras section that lists every add-on on a booking in one place: accessories, airport transfers, delivery and one-way fees, extra drivers, and, new here, the custom extras you add by hand. Each line shows the name, quantity and price (GST inclusive) with a subtotal, so a customer can see exactly what they are paying for. If a booking has no extras, the section says so rather than disappearing.

Custom extras used to be invisible to the customer even though they were on the total. If you ever add a custom line you would rather keep to yourself, the Add custom extra form now has a "Show on the customer booking portal" switch. Leave it on to show the line, or turn it off to keep it internal. Internal manual charges stay off the portal automatically.

A customer collecting on their own now signs your rental agreement as part of the flow, before the lockbox code is shown to them. They type their full name against the version of the terms they are shown, exactly as they would signing in the customer portal.

Until now a self-collection pickup could reach the code without a signature anywhere, which left the hire running on unsigned terms.

There is now a Help Centre at /help, covering getting started, bookings and availability, pricing, payments and bonds, locations, fleet and maintenance, pickup and self-collection, customer communications, Xero, and your website.

Every answer has its own page, there is a search box on every topic, and if you cannot find what you need there is a form at the foot of each page that reaches a real person.

Placing a second bond hold for a different amount on the same booking could return the first hold instead of creating a new one. Fixed.

You can now tell Glovebox when a location is shut. Open a branch under Locations and use Opening & closures to close it on specific dates, with an optional repeat-every-year for dates like Christmas, or on recurring weekdays such as every Sunday.

Customers cannot pick up or return at a closed location on a closed day, and the booking page enforces it for you. A hire can still run across a closed day, because the vehicle is out and it is only the counter that is shut, and you can still book those days manually from the admin.

A file upload that failed to write to storage could previously be swallowed rather than reported, which meant a photo could appear to save and then not be there later. Storage write failures now surface as real errors, so a failed upload is visible at the time rather than discovered when you go looking for the photo.

The vehicle edit screen had grown into one long scroll. It is now split into tabs, with a compliance summary you can read at a glance rather than hunting for.

Nothing moved out of the page, it is just easier to find. If you spend a lot of time in the fleet, this is the change you will notice most.

A customer can now collect their vehicle without anyone from your team being there. They open a link on their phone, work through the collection steps, and the vehicle's lockbox code is released to them.

You control when the code is released. The collection window is set by you, and the code appears only once the customer is inside it.

Self-collection is switched on per location, and only for vehicles that have a lockbox code recorded.

Broadcasts is for operational messages, sent by SMS or email. Think weather warnings, road closures, pickup reminders and recalls, not marketing.

You choose the audience by booking state, for example everyone on hire right now or everyone picking up in the next two days, and you can narrow it further by location or vehicle. Before you send, Glovebox shows you how many people each channel would reach, so you are not sending blind.

Opt-outs are respected. A customer who replies STOP is never messaged again. Every message sent is logged against the booking, which gives you a trail if a customer later says they were never told.

Broadcasts is switched on per workspace. Get in touch if you want it enabled.

Demand pricing is an optional layer on top of your existing pricing rules. It nudges your daily rate up or down based on fleet utilisation, how far ahead the booking is, and recent booking pace, all within minimum and maximum limits you set.

It is off by default, and it is deliberately explainable rather than a black box: every recommendation shows you which factors moved the price and by how much.

You can also run it in shadow mode first. Glovebox logs what it would have charged without changing what customers actually see, so you can watch it against real quotes for a few weeks before deciding whether to switch it on. Owners manage it at Revenue → Pricing → Automatic demand pricing.

Servicing and compliance now live alongside the fleet rather than in a separate spreadsheet. You can log maintenance jobs against a vehicle, record parts, and keep track of compliance dates.

When a vehicle goes in for work you can take it off the road from a set date, either until an expected return or open-ended. While it is off the road it is automatically unavailable to book, and it comes back into availability when you close the job, so nobody sells a hire on a car that is up on a hoist.

Glovebox now sends customers their pickup information ahead of time, so fewer of them arrive without knowing where they are going or what to bring.

The email carries the booking details along with the pickup instructions you have set on the location, which means the branch-specific detail such as where to park or which door to use goes out automatically instead of being retyped.