How a small business took bookings without paying for booking software

A neighbourhood bistro has a simple website with a photo of the dining room, the menu, and a phone number. Bookings come in by phone, which is fine at 3 p.m. and hopeless at 8 p.m. when the room is full and nobody can reach the handset. Would-be diners call, get no answer, and book the place across the street instead. The owner has looked at reservation platforms, but they all want a monthly subscription and a cut, and the bistro does perhaps a dozen bookings a day. It is not worth a software bill and a new dashboard to learn. Plenty of small businesses are stuck in the same spot: too busy to answer every call, too small to justify a booking system. The result is missed reservations that were never counted because no one was there to take them. ## The problem: the phone is a bottleneck, and software is overkill Phone-only booking has a hard ceiling. It works only during staffed hours, it fails exactly when the business is busiest, and it leaves no written record — so mishearing a name or a time turns into a no-show or a double-booking. For a customer who is browsing on their phone at night, "call us" is the least convenient option you could offer. The obvious alternative, a full reservation platform, solves the problem but brings its own weight: a monthly fee, a sign-up, a calendar to maintain, and often a per-cover commission. For a small operation with modest volume, that is a lot of overhead to accept a handful of bookings a day. Many owners look at it, decide it is not worth it, and go back to the ringing phone. There is a middle path that most people overlook. ## The fix: a "Request a booking" button Add a **Request a booking** button to the site. It is a `mailto:` link that opens the customer's email app with a booking request already laid out — date, time, party size, name, and phone number — so all they do is fill in the blanks and send. ```html <a href="mailto:[email protected]?subject=Booking%20request&body=Hi%2C%20I%27d%20like%20to%20book.%0A%0APreferred%20date%3A%0APreferred%20time%3A%0ANumber%20of%20people%3A%0AName%3A%0APhone%3A%0A%0AAnything%20else%3A"> Request a booking </a> ``` Now a customer browsing at 8 p.m., when the phone goes unanswered, can send a complete request in under a minute. It lands in your bookings inbox in writing, with every detail you need to confirm. You reply when there is a spare moment — from the same phone, between covers — and the customer has a written confirmation to hold on to. The generator on this site builds and encodes the link, so the list of prompts keeps its line breaks and opens as a tidy draft. ## Why a written request beats a phone call The request-by-email pattern quietly fixes the weaknesses of the phone. It works **around the clock**, so you capture the evening browser and the midnight planner. It produces a **written record**, so nobody mishears "four at four" as "four at nine." It is **asynchronous**, so a booking request does not compete with the customer standing at your counter. And because the details arrive structured, you can confirm, suggest a nearer slot, or ask one follow-up question without a game of phone tag. It will not replace a busy restaurant's dedicated system on a Friday night, and it does not manage table inventory. But for the large number of small businesses doing modest volume, it captures the bookings that the phone was dropping, at no cost. ## Setting it up 1. Choose a booking inbox — `bookings@` or even the owner's monitored address — that someone checks through the day. 2. In the generator, set the recipient, a subject of "Booking request," and a body that prompts for date, time, party size, name, and phone. 3. Copy the HTML snippet and place the button prominently: the homepage, the contact page, and your social profile links. 4. Add a line setting expectations: "Send a request and we'll confirm by email within the hour." 5. Reply promptly, and keep a simple note or calendar entry for each confirmed booking. Because it is only a link, it works on any website builder, a Google Business profile, a Linktree-style page, or a printed QR code on the door. ## What it saves and earns The first saving is the **subscription you do not pay**. A `mailto:` button has no monthly fee and no per-booking commission, which for a low-volume business is the difference between a tool that pays for itself and one that never does. The second is **captured demand**. Every booking that used to be lost to an unanswered phone at a busy hour is now a written request waiting for you. You do not need many recovered bookings a week for a free button to be worth more than its zero cost — and unlike the phone, it keeps working while you sleep. The third is **fewer mistakes**. Written details mean fewer wrong times, fewer misspelled names, and fewer no-shows caused by a booking nobody wrote down. A confirmation email also gives the customer something to refer back to, which further reduces missed reservations. There is a trust benefit as well: offering a modern, one-tap way to book — instead of only a phone number — signals that a small business is easy to deal with, which matters to the phone-averse younger customer. ## Make it even better - Add a QR code on the door and on tables that opens the booking link, so walk-bys can request a table for later. - Include a **cancellation** line ("reply to change or cancel") so plans that change do not become no-shows. - Keep the address **obfuscated** on the public page to avoid spam. - Pair the button with your opening hours so customers request realistic slots. ## Key takeaways - Phone-only booking fails at busy hours and leaves no record; full booking software is overkill for low volume. - A "Request a booking" `mailto:` button captures structured requests around the clock, in writing, for free. - It recovers bookings the phone was dropping and cuts errors and no-shows. - It works on any website, profile, or printed QR code, with no subscription. Build your own booking button in the [generator](/#generator), or copy the setup below.