Skip to content
Operations6 August 20266 min read

How to manage vehicle collection requests without WhatsApp and email chaos

Collection requests arriving across four channels is the most common operational failure in vehicle storage. How to turn a request into scheduled work with a clear owner and a due date.

An owner texts on Wednesday asking for their car on Friday morning. The message arrives on a personal phone, is read while someone is walking across the facility, and is remembered until roughly Thursday lunchtime. On Friday the car has not been cleaned, the battery is still on charge, and the owner is in the car park.

This is the most common operational failure in vehicle storage, and it is almost never caused by carelessness. It is caused by requests arriving as messages rather than as work.

The difference between a message and a job

A message has been read. A job has an owner, a due date, a set of steps, and a state that everyone can see. The gap between the two is where collection failures live.

When a request stays a message, several things are true at once: only the recipient knows about it, its status exists only in that person's head, nobody else can pick it up, and there is no record that it was ever made. Every one of those becomes a problem the moment the recipient is off-site.

Reduce the number of channels

Most facilities accept requests by phone, email, text, WhatsApp and in person. That is five inboxes, at least two of which are personal devices. No process survives five inboxes.

The realistic goal is not to eliminate channels — owners will contact you however they like, and telling a customer storing a six-figure car that they used the wrong channel is not a good look. The goal is to funnel every channel into one place quickly.

  1. 01Give owners a default route that is genuinely easier than texting — a portal request takes fewer taps than composing a message.
  2. 02For requests that arrive another way, make logging them a ten-second action rather than a form.
  3. 03Treat the logged request as the source of truth, and reply from there.

Turn the request into preparation tasks

A collection request is not one job, it is a small sequence: retrieve the vehicle from its bay, disconnect the charger, check tyre pressures, clean it, move it to the collection area, and have keys and documents ready. Each of those has a different duration and some have a required order.

When the request generates that sequence automatically, two things improve. The work is visible to whoever is on shift rather than only to whoever took the request, and the preparation starts early enough to actually happen. A request logged on Wednesday that produces Thursday tasks is a solved problem; one that produces a Friday morning realisation is not.

Make the state visible to the owner

A significant proportion of inbound contact is owners checking on something they have already asked for. That contact is a symptom: they have no way to see status, so they ask.

Showing request status — received, scheduled, in preparation, ready — removes most of those messages. It also changes the tone of the relationship. An owner who can see that their car is being prepared does not need reassurance; an owner who can see nothing has to ask for it.

Keep the record after the fact

Once the car has gone, the request still has value. It records what was asked for, when, what was done in response, and by whom. Over a storage term that history answers questions about billing, about recurring preferences, and occasionally about a disagreement.

Messages in a chat thread technically contain this too, but not in a form anyone can retrieve under pressure.

What good looks like

  • Every request has a state that anyone on shift can see.
  • Requests generate the preparation work automatically, dated to finish before the collection time.
  • Nothing important lives only on a personal device.
  • The owner can see status without contacting you.
  • The request and its outcome stay attached to the vehicle afterwards.

If the person who took the request is unavailable, can the rest of the team still deliver it on time?

That is the test. CarMarket24 is being built so the answer is yes by default — requests arrive as trackable work, generate their own preparation tasks, and stay on the vehicle record once they are done. Collections are also where facilities most often under-recover on price, which is covered in how car storage businesses price.

Ready to modernise your vehicle storage operation?

Tell us how your facility runs today. If CarMarket24 is a fit, we will show you what we are building and what a pilot would involve.