Contact form, booking or chat: which route fits your business
A contact form fits a business that needs details before it can reply, booking fits one that sells fixed slots of time, and chat fits one that can answer questions the moment they arrive. A form is part of step 01 at EUR 600-900, booking is step 03 at EUR 1.500-3.500, and a booking that takes payment or a chatbot is step 04 at EUR 3.500-7.500.
The choice is less about technology than about what has to happen before you can give a useful answer.
Start from what you need before you can reply
Picture the first useful reply to a new enquiry, then work back to what you needed in order to write it.
- You need details. A plumber needs the address and the problem, a caterer needs the date and the number of guests, a supplier needs the quantity. That is a form, with fields for exactly those details.
- You need a time. A physiotherapist, a hairdresser or a driving instructor sells an appointment of known length. Agreeing a time by email turns one action into a conversation, and booking removes the back and forth.
- The customer needs an answer that already exists. Opening times, delivery areas, whether you do a certain job. A clear FAQ section answers that, and a chatbot can answer it in conversation.
- It cannot wait. A locked-out tenant or a burst pipe needs a phone number that dials when tapped, placed where a phone user sees it first.
Which step each route belongs to
Every step, with what it includes, is on our price list. For contact routes, it breaks down like this.
| Route | Fits when | Step and price |
|---|---|---|
| Tap-to-call number, email link, a link that opens a WhatsApp chat | The request is urgent or needs a conversation | Any step, as a link on the page |
| A contact form on a landing page | One service, details needed before a reply | Step 01, EUR 600-900 |
| A contact flow across a small site | A handful of services, one person replying | Step 02, EUR 900-1.500 |
| Forms routed by service, or your CRM's own embeddable form | Several services or several people replying | Step 03, EUR 1.500-3.500 |
| Online booking of appointments | You sell fixed slots of time | Step 03, EUR 1.500-3.500 |
| Booking that takes payment | A missed appointment costs you money | Step 04, EUR 3.500-7.500 |
| Booking that reads availability from another system through an API | Your calendar already lives in other software | Step 04, EUR 3.500-7.500 |
| Enquiries written into a CRM through its API | Leads have to land inside your sales process | Step 04, EUR 3.500-7.500 |
| A chatbot | Questions repeat and the answers exist in writing | Step 04, EUR 3.500-7.500 |
A chat window answered by a person is a different purchase from a chatbot. Placing a chat tool on the site is agreed at scoping, and the continuing costs are the chat tool's own plan, where it has one, and the time of whoever answers it.
Contact forms: the details that decide whether they work
- Ask only what the reply needs. Every required field asks more of someone who has not yet decided to trust you.
- Confirm on screen. After sending, say that the message arrived and what happens next.
- Check delivery, not submission. A form can show a success message while the email never reaches an inbox. Test it by sending real enquiries to the address that will receive them.
- Stop spam without stopping people. Protection set too strict can reject real enquiries without anyone noticing, so test it the way a visitor would use it.
- Say what happens to the data. A form collects personal data, and GDPR and your website covers what your privacy notice needs to say about it.
Booking: when time is what you sell
Booking fits when a service has a known length and the customer can choose a slot without talking to you first. It does not fit work that has to be assessed before it can be scheduled, such as a renovation or a custom order, because the slot would be a guess.
Before the build, the part that waits on you is the rules: how long each service takes, the gap between appointments, who works which days, how far ahead people can book and what happens when someone cancels. Taking payment at booking, or reading availability from software you already run, moves it from step 03 to step 04. Adding a booking system covers those choices in more depth.
Chat: a chatbot and a person make different promises
A chatbot answers from material you give it: prices, service areas, policies, preparation instructions. It is only as good as that material, and a wrong answer still comes from your business. So a chatbot at step 04 needs written answers to draw on, a way to hand the visitor to a form or a phone number when it cannot help, and someone who reads what it said.
A chat window with a person behind it promises a reply while it shows as open. If nobody can keep that promise, a form that says when you will reply is the more honest route.
From choice to launch
- Scoping. Decide the route for each service, the fields or booking rules behind it, and where every enquiry lands. A fixed quote follows scoping.
- Your input. Form questions, booking rules, and for a chatbot the written answers it will use. This is the part that waits on you.
- Build. 1-2 weeks for a step 01 landing page, 2-3 weeks for a step 02 mini-site, 3-6 weeks for a step 03 site with booking, 6-12 weeks for step 04.
- Testing. Real enquiries and bookings through every route, on a phone and on a desktop, checked where they should arrive.
- After launch. Care, at EUR 100-300 a month, covers updates, monitoring, backups and small fixes.
When to spend less
- You answer every enquiry yourself. A form on a step 01 landing page at EUR 600-900, or the contact flow of a step 02 mini-site at EUR 900-1.500, does the job. Routing matters once there is more than one person to route to.
- Appointments are few and flexible. A form that asks for preferred times can stand in for booking until the back and forth starts costing you time, and booking then bolts on as an add-on at EUR 350-750.
- Your booking software gives you its own booking page. A link to it can sit on any site, before you pay for reading availability through an API: an add-on at EUR 750-2.500 on a site you have, or step 04 in a new build.
- The same questions keep coming. A written FAQ section answers them without a chatbot.
In each of those cases, do not buy a bigger build yet.
Questions about contact routes
Can we offer more than one route?
Yes. A phone number next to a form is a link, not a feature. The limit is attention, because every route you show is one you have to answer.
Should customers pay when they book?
That depends on what a missed appointment costs you. In a new build, booking that takes payment is step 04 at EUR 3.500-7.500 and booking without it is step 03 at EUR 1.500-3.500. On a booking site you already have, payments are an add-on at EUR 600-1.500. Weigh the difference against what missed slots cost you over a year.
Will a chatbot replace our contact form?
It should not. A chatbot handles questions that already have answers, and a form collects the details of a request that needs a person. A chatbot should be able to pass a visitor on to the form.
Does a WhatsApp link count as a contact route?
Yes. A link can open a WhatsApp chat with your business number, and it works at any step. Replies come from whoever answers that number, so it carries the same promise as a live chat window.
If you are not sure which route suits your business, tell us how enquiries reach you today.
Building something?
JP Studio designs and builds websites, storefronts and product interfaces.