Bookings for a one-person workshop: protecting the day you actually have

A solo mechanic manages bookings without a receptionist by automating the instant reply, offering only slots the diary genuinely holds, and declining unsuitable work quickly and honestly. For a one-person workshop, capturing enquiries is rarely the problem. The problem is that the person who takes the call is under a car, and nobody can cover for them.

Key takeaways

• A one-person workshop needs a system that protects billable hours, not one that captures every lead.
• Answering later by message costs less than answering a ringing phone, because a message waits and a call demands.
• Offer only slots the diary has reserved, and book only jobs that have been sized.
• A fast, honest refusal keeps the customer's goodwill and the recommendation that goes with it.
• Closed dates, overrun notices, payment reminders and review requests are worth automating because nobody else will do them.

What we'll cover

• The constraint is you
• What an interruption really costs
• A booking is a promise made by one person
• Saying no accurately
• Building it with CodeWords
• What can be answered without you
• The jobs not to accept by message
• Holidays, illness and the job that overruns
• The awkward parts of working alone
• Making it survive
• Limits worth knowing about
• What to build first
• Frequently asked questions

The constraint is you

The constraint in a one-person workshop is your own time, and every booking decision follows from it. A workshop with two ramps and three staff can absorb a bad morning. A one-person operation cannot.

You cannot serve two jobs at once, so an overlapping diary lies to somebody.

You cannot be interrupted for free, because each interruption comes out of the hours you sell.

You cannot be covered. A day off is a day the business does not operate, and a job that overruns pushes everything behind it.

Every hour of admin is an hour not turning a spanner, and you cannot delegate it.

The useful question is therefore not how many enquiries you can capture. It is how many of your available hours end up billable, and what is eating the rest.

What an interruption really costs

An interruption costs the length of the call plus the time to get back to where you were. For work involving sequence or torque settings, the return time is considerably longer than the call. Several interruptions across a day remove an hour you will not notice losing.

There is also a quality cost. Work resumed after an interruption is where things get missed, and a comeback costs far more than the call did.

The goal is therefore to answer later without losing the customer, not to answer faster. A message achieves that, because a message waits. A ringing phone does not, because a call demands attention now.

A booking is a promise made by one person

Every confirmed slot is a personal commitment with no fallback, so automated booking needs three rules.

Never offer a slot the diary has not reserved. Offering three times and letting somebody pick the one you have since filled is worse than offering nothing.

Never book anything you have not sized. "Brakes" takes between an hour and a day depending on what is seized. Confirm the job before confirming the time.

Leave real slack. A day booked to its edges has no room for the job that turns out worse than described, and that job arrives most weeks.

A system that books against a calendar works, provided it offers only time you genuinely have and only for work it can size. For everything else, the system should collect information and hand it to you.

Saying no accurately

Declining well is the most useful thing automation does for a one-person workshop, and nobody builds it. A customer who hears nothing assumes you are ignoring them.

A customer told within a minute that you are booked until the 14th but can take them then, or that you do not do that kind of work but another garage nearby does, has been dealt with properly. They come back, and they tell somebody.

Write down once what you do not take: makes you lack the diagnostic kit for, work you have no lift for, jobs that are not economic at your rates, and anything where you would be the fourth garage to look at it. An honest, immediate no costs nothing and saves both sides a wasted morning.

Building it with CodeWords

CodeWords connects to 3,000+ integrations (CodeWords pricing page, 2026), and each connection is made once and reused.

1. Open CodeWords and start a new automation.
2. Describe what should happen in plain language to Cody, the automation builder: what information to collect from an enquiry, which jobs can be booked straight into the diary, which are held for you, and what is declined outright.
3. Authorize the connections to your calendar and your WhatsApp Business Platform account. A standard calendar is enough; you do not need workshop software you are not already using.
4. Describe the exceptions: a customer who cannot describe the fault, a job you have quoted before, a vehicle already booked, anything that sounds like a breakdown.
5. Run it for a fortnight while still checking every enquiry yourself. The first fortnight shows which jobs the rules get wrong.

You describe the outcome; Cody builds it, connects it and deploys it. The free plan covers light use, with Pro at $39 per month and Business at $100 per month as usage grows (CodeWords pricing page, 2026). Details are on the pricing page.

What can be answered without you

A large share of a solo mechanic's inbound messages have the same answer every time. Write those answers once, in an evening, and they stop interrupting you.

Where you are and how to find you, which is asked constantly.

Opening hours, including what happens if somebody arrives at ten to five.

Whether you can do a given type of work, which is a fixed list.

Roughly what a standard job costs, where you are willing to give a figure. Being straightforward here filters out price-only enquiries before they reach you, which is worth more than the enquiries it loses.

What to bring, and whether the car needs to be left.

Whether you are taking new customers at all.

The jobs not to accept by message

Do not accept five kinds of job by message, because each needs your judgement before a slot is promised.

Anything described as a noise. A noise is a diagnosis, and a diagnosis needs a price for the time to find it.

Anything on its fourth garage. These jobs are long, unpredictable and often unprofitable, so they should reach you before any slot is promised.

Anything urgent or unsafe. A customer describing a smell of fuel or a brake pedal going to the floor needs a person immediately, telling them not to drive the vehicle.

Anything where the vehicle is not driveable. The first conversation is about recovery, not a slot.

A price-only enquiry for complex work. A figure given by message becomes a quote in the customer's mind, and you have not seen the car.

Holidays, illness and the job that overruns

A one-person business fails by stopping entirely without telling anyone, so automate the announcement as well as the booking. Put closed dates in the calendar and let the enquiry reply state them, with the date you are back and an offer to book beyond it. A customer who gets a clear answer waits. One who gets silence assumes you have retired.

An overrunning job is harder, because it happens without notice and pushes everybody behind it. Prepare one message you can send from a phone with dirty hands: what has moved, to when, and an offer to rearrange. Sent at eleven in the morning, it separates an understanding customer from one who sat outside at four.

The awkward parts of working alone

Three jobs are awkward precisely because nobody else will do them.

Chasing money. Doing it yourself to a customer you like is uncomfortable. An automated reminder at seven days, sent as routine, removes the awkwardness by removing the choice.

Asking for reviews. Reviews are the cheapest source of new customers for a one-person workshop, and they are rarely requested because asking face to face feels like begging. A short message the day after collection does not.

Keeping the record. Working alone means nobody else remembers what was agreed. Write down what was authorised, what was declined and what you advised, at the time, on the job.

Making it survive

Five habits keep the system useful.

Only offer time the diary actually holds.

Keep a hold queue for anything the rules cannot size, and check it twice a day rather than continuously.

Put closed dates in before you need them, because you will not do it on the morning you wake up ill.

Review what got declined each month. A rule that refuses work you would have taken is worth loosening.

Keep one route that is always a person, and say what it is.

Limits worth knowing about

Automation has five limits for a solo workshop.

Automation adds no hours. It protects the hours you have and makes them more billable.

Some customers will only ring, and for a local trade that is a real share of the book.

Booking without sizing produces overruns, which cost a solo trader more than a lost enquiry.

The system cannot work while you are ill. It can only tell people what is happening.

A one-person workshop has a ceiling. Past a certain point, the answer is a second pair of hands rather than a better process.

What to build first

Build the instant, honest reply first. It answers within a minute with your hours, your location, whether you are taking work, and roughly when you could fit the customer in. It does not need to book anything to be worth having.

Two habits make the difference. Never let the system confirm a slot it has not sized, because an overrun costs a day you cannot get back and a lost enquiry costs an hour. And write the decline rules down, since the customer you turn away in thirty seconds with a straight answer may recommend you to somebody you can help.

Frequently asked questions

What should a solo mechanic automate first?

Automate an immediate reply that carries your hours, your location, whether you are taking work and roughly when you could fit the job in. This removes the interruptions that cost the most, and it does not require booking anything.

What does an interruption actually cost?

An interruption costs the call plus the time to get back to where you were. For work involving sequence or torque settings, that return time is several times the length of the call. There is also a quality cost when work resumes badly.

Should bookings be confirmed automatically?

Confirm automatically only for work the system can size, against time the diary genuinely holds. Collect everything else and hold it for yourself. Automatic confirmation of unsized work produces overruns, which cost a solo trader more than a lost enquiry.

Which enquiries should never be auto-booked?

Never auto-book noises, vehicles other garages have already failed to fix, anything urgent or unsafe, undriveable vehicles, and price-only enquiries for complex work. Each of these needs your judgement before a slot is promised.

How do I turn work away without losing the customer?

Decline immediately and honestly. Tell the customer you are booked until a given date, or that you do not do that work and who does. Silence is what costs you the recommendation, not the refusal.

What should be answered without me?

Answer location, opening hours, what work you take, what to bring, whether the car must be left, rough prices where you are willing to give them, and whether you are accepting new customers. These questions have the same answer each time.

How do I handle holidays?

Put the closed dates in the calendar in advance and let the automatic reply state them, with the date you are back and an offer to book beyond it. A customer who gets a clear answer waits.

What happens when a job overruns?

Send one short message as soon as you know: what has moved, to when, and an offer to rearrange. Sent in the morning, it is a minor inconvenience. Discovered at four, it ruins the customer's day.

Does this help with chasing payment?

Yes, mainly by removing the decision. A routine reminder at seven days is easier to send than one you must choose to send to a customer you like. The reminder goes out as standard practice, not as a personal judgement.

When is a better process no longer the answer?

When the diary is consistently full and you decline enquiries for capacity rather than fit. At that point your hours are the constraint, and no automation adds hours. A second pair of hands becomes the answer.

Related reading

• Job updates and the customer who cannot see the car
• Estimates, approvals and authority
• MOT reminders and the due-date list