Automated website: what it can handle on its own

A website can record appointments, send reminders and sort enquiries without anyone touching them. Decisions, reviews and phone calls stay with a person, and an alert goes out when a message fails. Here is the task-by-task inventory, with Locabus as the example.

By Nuredin Mohamed Ali

An automated website takes care of the steps that repeat with every customer: recording an appointment booked online, sending a reminder, copying an enquiry into a spreadsheet, sending a confirmation email. It makes no important decisions. Accepting a request, checking an invoice or phoning a worried customer remains a person's job, and an alert tells that person when a message fails to send.

The word "automated" gets used to sell almost anything. So here is a task-by-task inventory for a small business in French-speaking Switzerland: what the site can take over, what it should leave to you, and what this looks like in a real company, the removal van rental firm Locabus.

What an automated website takes care of

Picture a hair salon in Lausanne. The phone rings during a cut, the caller leaves a message, someone calls back that evening, and the person is no longer free. Now picture a property manager in Geneva who receives requests through a form and copies them into a file every Friday. In both situations nobody is really thinking. Information is simply being carried from one place to another, and a website can do that carrying.

Appointments booked online

The customer sees the open slots and picks one, and that slot disappears for everyone else. The appointment lands in your calendar with the name and the reason for the visit, without anyone typing it in again. You still control what is on offer: opening hours, the length of each service, closed days. If you want the tool side of this, one possible setup is detailed in our Make and Calendly example.

Reminders

Ahead of the appointment, a message goes out without anyone having to remember it, with the date, the time, the address and a way to say they can no longer make it. The same logic works for other deadlines: a document to supply, a check to renew, a return to prepare for.

Enquiries copied into a spreadsheet

Each enquiry sent through the site adds a row to a spreadsheet: name, phone number, subject, date. Messages get lost less often at the bottom of an inbox, and a "done" column shows at a glance what still needs an answer. A well-built contact form makes this sorting more reliable, because the information always arrives in the same order.

Emails triggered by an action

Acknowledgements, order confirmations, payment links, requests for a missing document: these messages say almost the same thing every time. Once they are properly written, they go out at the right moment, evenings and weekends included, and the customer knows the request has arrived.

Documents that repeat

A confirmation as a PDF, an invoice, terms and conditions attached to the right message: the site can produce these from the details the customer has already entered. Nobody retypes a name or an address, which also cuts down on typing mistakes.

What stays with a person

You can judge a serious automation by what it leaves alone. Your team stays in charge: it spends less time copying things across and keeps its attention for work that needs judgement. Four verbs sum up the split.

  • Decide. Accepting a job, turning down a request, offering a goodwill gesture. The site prepares the file and someone makes the call.
  • Review. An unusual invoice, a quote or a reply to a complaint is read by a person before it goes out.
  • Call back. A worried or unhappy customer wants to hear a voice. An automatic message, however well written, can make things worse.
  • Handle the exception. A date to change, a request that fits no category, a situation nobody planned for.

A simple rule helps you sort tasks: if a mistake would be expensive or would upset a customer, the task goes through human approval. The site can prepare everything, but it only sends once someone has agreed.

How Locabus works, step by step

Locabus rents out removal vans in Moutier. The way it runs shows this split well, because every stage of a rental has its place.

  • When the order is placed: booking and card payment on the site, the calendar blocked, the owner's Google Calendar fed with no typing, and a confirmation with terms and conditions as a PDF.
  • Before pick-up: the key box code sent by email.
  • During the rental: pick-up and return checks done from a phone, and a reminder before the return.
  • For follow-up: a PDF invoice, a table to track what is paid or not, a QR-bill on extra kilometres, a Google review request the next day, and a PDF report every week.

Whatever calls for a person falls to the owner: a key handover, a date change, an invoice review. The invoice for extra kilometres, for example, is read before it is sent. That is the right habit whenever an amount varies from one customer to the next.

The alert, the part people forget

A site that acts alone can also fail alone, and quietly. A mistyped email address, a renamed spreadsheet, an outside tool that changes how it works: the message does not go out and nobody notices. Without an alert, you find out on the day a customer complains.

Before launching anything, ask your provider these three questions:

  • Who receives the alert when a message fails to send, and through which channel?
  • Where can we see what went out and what did not?
  • Who takes over during an absence, and how are requests handled until the fault is fixed?

If the answers stay vague, the automation is not finished. Something will break sooner or later. It stays a small incident when someone hears about it straight away.

Where to start on your own site

There is no need to automate everything at once. One well-chosen task is enough to begin with.

  1. Write down what you copy. For a week, keep a sheet of paper nearby and note every piece of information you retype and every message you send again word for word.
  2. Pick the most frequent task that needs no decision. It will often be logging enquiries or confirming appointments.
  3. Describe the flow in a few sentences. What triggers the action, what should happen, who should be told if it fails.
  4. Test with real requests. Try the awkward cases too: a wrong address, an empty field, a duplicate.
  5. Leave a door open. Every automatic message says clearly how to reach someone.

Data needs attention from day one. A form collects personal data, so explain what you do with it in your privacy policy, keep only what you use, and leave precise data protection questions to a lawyer or an accountant.

This work can be handed over: our page on task automation for small businesses explains how we go about it. At DSA, automating one process starts from CHF 1'200 and takes 2 weeks, and our full price list is published.

Frequently asked questions

Is an automated website the same thing as a chatbot?

No. A chatbot answers questions in a chat window. The automation described here works behind the scenes: it records, reminds, copies and sends. A site can have one without the other.

Do I need to rebuild my site to automate it?

Not necessarily. A form, a calendar or a spreadsheet can often be connected to an existing site. It depends on how the site was built, which a technical review can check fairly quickly.

What happens if a message fails to send?

An alert goes to the person in charge, who fixes the problem or handles the request by hand. If this is not part of the setup, ask for it before going live.

Will my customers find this impersonal?

A reminder or a confirmation goes down well when the message is clear and says how to reach someone. Sensitive conversations stay with a person, by phone or in writing.

Go back to your sheet from the week. The line that comes up most often without needing a decision is the first one your site can take over.

Discover our services · Chat on WhatsApp

Read next

Geneva and French-speaking Switzerland

A project? Let's talk for 15 minutes.

Replies within 24 hours.