When a Booking Request Form Works Better Than Instant Booking

The ten o’clock had been booked online as ‘fan not working’. Say the electrician is Sajan and he works in Thrissur. He arrived to find a flat where half the sockets were dead and the fan was the least of it. The customer had picked a one-hour slot because one hour was what the page offered. A booking request form would have put one step between that customer and Sajan’s Tuesday: he reads the job, then decides how long it gets.

By lunchtime he’d phoned two other customers to push them back. Each of them had a confirmation on their phone that said otherwise.

Sajan’s page did what it was built to do: it sold an hour to anyone who tapped. His work doesn’t come in hours. Whether your customers should pick a time or ask you for one depends on how much you can know about a job before you’ve seen it.

What a booking request form promises, and what a slot promises

A slot is a promise made by software on your behalf. The customer taps a time and the page says it’s theirs. You find out afterwards. That works only when the job’s length and your free hours were both known in advance.

A request makes a smaller promise: you’ve asked, and a person will answer. The customer names the service and a time they’d like. Nothing is held. You read it, and then you say yes, suggest a different time or say no.

As a customer I prefer the slot. An instant answer is a small pleasure, and some people will leave your page if they can’t have one. A request costs you those people. What it buys is a look at the job before you commit to it.

Four kinds of work that need a look before a time

Sit with enough owners and the same four situations keep turning up. If your work falls into any of them, a booking request form is the safer design.

The length is a guess until you’ve seen it

A plumber’s ‘leaking tap’ can be a worn washer or a wall that has to come open. When one service name can mean forty minutes or four hours, any slot length you publish is wrong for somebody.

You travel to the customer

Take Maeve, a garden designer in Bristol, as an example. A consultation across the city on a Friday afternoon costs her twice the time of one three streets away, and a grid of slots knows nothing about either. With a request she sees the area first and offers the morning she’s already nearby.

The work is quoted before it’s scheduled

If the customer needs a price before they commit, there’s nothing to schedule yet. What you can schedule is the first look: the site visit before a kitchen fit-out, or the call before catering for sixty guests. The request asks for that with the facts already written down. The job that has to be priced belongs on a quote request or a plain inquiry, not a booking request.

You’re one person and you choose your work

A freelance consultant is the obvious case. So is a wedding photographer in Leeds, say, who takes two weddings a month by choice. For a one-person business, an open calendar hands the choosing to strangers. A request keeps it with you, and lets you pass politely on a job before anyone believes they’re booked. If you’re still deciding how much of a site a solo practice needs, start with whether freelancers need a website or a professional profile.

When instant booking is the right call and a Profile is not

A booking request form is the wrong tool for a yoga class with twelve mats, to take one example, or for a thirty-minute haircut at a busy salon. Those customers expect to grab a time and be done, often at eleven at night when nobody’s awake to reply.

Making those people wait for a reply on something that needed no decision is friction you added yourself. They need a live-calendar booking system: real availability, and a slot that’s held the moment it’s taken. A Profile is not that. On Nichevio a Booking Request holds nothing, has no slots, doesn’t sync with a calendar, takes no deposit and sends no reminder. If your business runs on those, use a system built for them.

There’s a test you can run on your own phone. Open your messages and find the last ten bookings you took. Count how many needed a question from you before you could say yes. If it’s one or none, your customers should be picking slots. If it’s most of them, they should be asking.

Three or four out of ten means you’re running two kinds of work. In a salon in Kochi, for example, cuts run to the clock, while bridal styling starts with a trial and a talk about the venue. Send the routine work to a slot system and keep a request for whatever has to be discussed first.

What a good booking request form asks

A booking request form has one job, which is to give you enough to answer in a single reply. Leave a fact out and you’ll be messaging back and forth to get it. Add a field too many and someone typing with one thumb gives up halfway.

The few fields that let you decide

• The service they want, by the name it has on your page, so you aren’t decoding ‘that thing you did for my neighbour’.
• A preferred date and time, asked for as a preference.
• A message with the context: what’s wrong, roughly how big the job is and, if you travel, which area they’re in.
• A way to reach them, so your answer goes where they’ll see it.

On a Nichevio Profile the Booking Request Widget asks only for the fields you set up, so the form can stay this short, and required fields are checked before anything is saved. The page on the Lead Form and Booking Request shows a worked example.

What to leave off a booking request form

Leave off anything you’d only need once you’ve said yes. A full postal address or the name for the invoice can wait for your confirmation reply. The area is enough to plan the travel.

Leave off a list of times too. Offering ‘choose 9, 11 or 2’ on a booking request form recreates the promise you were trying to avoid, without a calendar behind it to keep that promise true. Ask what they’d prefer and answer with what you can do.

Word it so nobody believes they’re booked

The usual complaint about request forms comes from customers who thought they’d booked. They waited in, or they turned up, and nobody had agreed to anything. Nearly every time, the wording did it. Check yours in the order a customer meets it.

1. 1.In the service description, put the promise in plain words. For example: Send a request with your preferred time and we’ll confirm by message.
2. 2.At the time field, Preferred date and time reads as a wish. ‘Select your appointment’ reads as a booking.
3. 3.On the button, Send Request asks and ‘Book Now’ promises.
4. 4.In your reply, use the word confirmed once, and only when it’s true.

On Nichevio the middle two are worded as a request from the start. The Widget is named Booking Request, and on the example form on the feature page the time field asks for a preferred date and time and the button reads Send Request. The first and last are your own words, and so is the Instagram caption that points at the form. Keep ‘book now’ out of all three.

Then say what to do when it can’t wait. A request suits next week. A burst pipe needs your phone number above the form, where a panicking person will see it first.

What happens after the customer presses send

On a Nichevio Profile the request is saved before anything else happens. It lands in your dashboard as a Record with its own reference, the time it arrived, the Widget and Profile it came from, and the requested time marked Requires your confirmation. The customer is shown that the request went through, and you get a notification. The service business example follows one booking request from the form to the saved Record in the dashboard, on Business Starter.

That status, Requires your confirmation, is the honest part. It tells you a person is waiting. Nothing has been reserved and no calendar has been touched. The time is held in one place only, your own diary, at the moment you write it there. A request becomes a booking only when you confirm it.

The reference earns its place the first time two people called Priya ask about the same Saturday. Write it in your reply and in your diary, and you’ll still know which Priya got the morning.

You answer from your own email, phone or WhatsApp. Nichevio doesn’t message the customer for you.

The three answers, and how to give each one

The one thing a request can’t survive is silence. The customer was told it went through, so the next move is yours.

To confirm, say everything back once

Put the service, the date and time, the place and the reference in one message. Then update the status on the Record so your dashboard matches what you’ve agreed. The customer has a booking from the moment they read that message, so write it for someone reading on a bus.

To propose another time, name the time

Offer one or two specific alternatives and give the reason in half a sentence: ‘I’m across town that morning, could you do Thursday at four instead?’ An open ‘when else suits you?’ hands the work back to the customer. The request stays unconfirmed until they answer.

To decline, be quick and plain

A no that arrives within the hour does less damage than a yes that arrives three days late. If the job is outside your area or your trade, say so in those words, and the customer can ring someone else the same afternoon. Then update the Record.

If more than one person handles requests, the plan decides who can. Business Starter is owner-only, Business Pro adds one more seat with internal notes on a request, and Business Growth lets you assign a request to a team member. The page for service businesses sets out who can handle what.

Setting up the Booking Request on a Nichevio Profile

Most of the effort goes into the service descriptions, not the form. If there’s no page yet to put the form on, the post on how to get a small business online without a website deals with the page itself.

1. 1
   Pick the Profile familyChoose Individual if the page is about you under your own name, which is what the page for professionals and freelancers describes. Choose Business if it presents a company or a team. A Profile can’t be switched between families later.
2. 2
   Write your services before the formGive each service a name a stranger would understand and say how long it usually takes. Put your request wording in these descriptions, because they’re read before the form is.
3. 3
   Add the Booking Request WidgetIn the Builder, add the Booking Request Widget and set up its fields. It lands at the bottom of the page, so use Move up until it sits directly under your services.
4. 4
   Test it on your own phoneWith the Profile on Starter or above, publish, open your public address on your phone and send yourself a request. Check it reads as a request at every step, then find it in the dashboard and reply as you would to a customer.

One check needs no phone. Think of the last booking that went wrong, read your new booking request form as that customer would have, and ask whether it would have caught the problem. If it wouldn’t, one more line in a service description usually will.

Questions about using a booking request form