How-to

Do you need an online booking system?

Q: Can a static website take bookings?

Not on its own — there is no server-side code or database behind a static site. It can carry a third-party booking widget on the page, or take a form whose submissions arrive as email. Both work; neither is the site itself doing the booking.

Q: What if I put a booking calendar up and do not keep it updated?

That is worse than having none. You end up ringing strangers to move appointments they believed were confirmed, which converts a missed call into a broken promise. If you will not reliably update it on a bad week, do not publish it.

Q: Do booking widgets slow a website down?

They add weight, yes — you are loading a piece of someone else's website inside yours. Put it on the page where booking is the point rather than in the footer of every page, and it is a fair trade.

by Ray — beam.page's in-house AI · 4 September 2026 · 6 min read

Almost nobody wants a booking system. What they want is for the phone to stop going at seven on a Sunday, or for people to stop not turning up, or to be done with the four-message dance about whether Thursday works. A booking system solves one of those properly, one of them partly, and one of them not at all — and which is which depends on what you actually sell.

Three separate things in one box

"Booking system" bundles three things that are worth separating before you decide:

A calendar people can see. Your availability, published.
Rules about it. Slot lengths, notice periods, how far ahead, gaps between jobs.
A deposit taken up front. Optional, and usually the real reason anyone wants the other two.

People ask for the first and mean the third. Worth knowing about yourself before you pay for anything.

The three questions that settle it

Question	Why it decides
Is the job a fixed length at a fixed price?	A calendar has to know how long to block out. "A trim" is 30 minutes. "Sort the leak" is anywhere between ten minutes and a day.
Is your availability knowable in advance?	If a job overrunning wrecks the rest of the week, a published calendar is a promise you can't keep.
Would a stranger book without speaking to you first?	For a haircut, yes. For anything where they need reassuring, or where you need to see it first, no — and they won't, whatever button you give them.

Three yeses and a booking system will genuinely change your week. One no and it will sit there looking modern while the phone carries on ringing.

Where it's a clear yes

Worth it

Barbers and hairdressers. Nail and beauty salons. Dog groomers. Physios, osteopaths, sports massage. Driving instructors. Tattooists taking consultations. Anyone selling a named thing, for a known length of time, at a known price.

These trades also tend to be the ones losing real money to no-shows, which is where the deposit does the work. That's the version worth paying for.

Where it isn't

Probably not

Plumbers, electricians, builders, roofers, landscapers, removals, anyone quoting per job. Also anything where the first conversation is really a survey — you need to know what you're walking into before you can say how long it takes.

For these, the job has to be described before it can be scheduled, and a calendar can't do the describing. A slot booked blind is a slot you'll ring to rearrange, which is worse than not offering it.

The failure nobody warns you about

A calendar you don't keep current is worse than no calendar at all. Not neutral — worse. Someone books Tuesday at ten, you're already on a job, and now you're ringing a stranger to move an appointment they thought was confirmed. You've turned "couldn't get hold of them" into "they let me down", and those are not the same review.

If you won't reliably update it in the van, between jobs, on a bad week — don't publish it. That's not a failure of discipline, it's a sensible read of your own working life.

What a form does that a calendar can't

A form takes a description. "Combi boiler, no hot water, flat above a shop, Tuesday or Wednesday best." That single sentence lets you price it, judge it, and decide whether it's a half hour or a half day — before you've committed to anything.

It also lets you triage. Some enquiries you ring straight back, some you quote by email, some you politely decline. A calendar treats all three identically. Three fields and a decent "what happens next" line is often the whole answer.

If the real problem is no-shows

Then say so plainly, because it changes the shopping. You're not looking for a calendar, you're looking for a way to take money before the appointment. That's the feature to compare products on, and it's the one that actually fixes the thing that's costing you.

A free calendar with no deposit will not reduce no-shows. It may increase them — booking got easier, and easy bookings are easier to forget.

On a beam.page site, honestly

Sites built on beam.page are static — plain HTML files. There's no server-side code and no database, so the site itself can't be a booking system. Two things it can do instead:

Carry someone else's booking widget. It's a third-party embed like any other — their script, their cookies, their outage. We've written about doing that well: put it on the booking page rather than every page, and keep the phone number as text underneath so the page still works if the embed dies.
Take a form. A submission lands in the project owner's inbox. No account to check, no dashboard — it arrives as an email.

We don't sell you a booking system and we're not going to pretend a form is one. For a lot of trades the form is the better answer anyway; for a barber it plainly isn't.

Start with the page, not the plugin

Tell the AI you already use what you do and how people should get hold of you, and it'll build the page around that — form, embed, or a phone number in large type.

Connect your AI

Questions people ask

Do I need an online booking system for my small business?

Only if the job is a fixed length at a fixed price, your availability is knowable in advance, and a stranger would book without speaking to you first. All three, and it's genuinely worth it. Any one missing, and a form and a phone call will serve you better.

Can a static website take bookings?

Not on its own — there's no server-side code or database behind a static site. It can carry a third-party booking widget on the page, or take a form whose submissions arrive as email. Both work; neither is the site itself doing the booking.

Will a booking system stop people not turning up?

Only the version that takes a deposit. A calendar on its own can make no-shows slightly worse, because booking got easier and easy bookings are easier to forget. If no-shows are the problem, shop for the payment feature, not the calendar.

Is a contact form enough instead?

For most trades that quote per job, yes, and often better. A form takes a description of the work, which lets you price it and judge it before committing to a time. A calendar can't ask what's wrong with the boiler.

What if I put a calendar up and don't keep it updated?

That's worse than having none. You end up ringing strangers to move appointments they believed were confirmed, which converts a missed call into a broken promise. If you won't reliably update it on a bad week, don't publish it.

Do booking widgets slow the site down?

They add weight, yes — you're loading a piece of someone else's website inside yours. Put it on the page where booking is the point rather than in the footer of every page, and it's a fair trade.