The safe way to learn how to choose a booking system is to answer 12 questions that end in pass or fail, in one afternoon, inside a trial account. This applies when you sell time: clinic hours, service bay hours, chair hours, or class hours. One limit: this list tests the software, not the support you get after you pay.

I wrote this list after I set up booking pages for service businesses. Regret rarely comes from a missing feature. It comes from 3 things: data you cannot take out, slots that still clash, and a bill that jumps as customers grow.

If the term is new to you, start with what a booking system is. If you want to start at no cost, read the free booking system options.

One screen summary

This table holds my working rule. The numbers are my rule, not market research.

ItemMy rule
Time to testOne afternoon, about 3 hours
Questions12, each one pass or fail
Must pass4 questions: no account, calendar clash, data export, cost at scale
Safe score9 out of 12 or higher
First test15 minutes in an empty account
Move period7 days of parallel run
Parallel ruleOnly 1 system accepts new bookings

How to choose a booking system with 12 pass or fail questions

Each question has 1 way to check it. Open the trial account and answer while you click. Do not score the marketing page. A promise is not a product.

Card grid of 12 checks for a booking system, from booking without an account to cost at scale
The 12 checks I run. The card order matches the table below.
NoQuestionPass whenFail when
1Can a customer book without an account?A name plus 1 contact finishes itSign-up or email check is forced
2Can 2 staff hold different slots?Hours can be set per personOne schedule covers the whole shop
3Does your own calendar close a slot?A private event removes the slotThe slot stays open
4Does it remind, and can you prove it sent?A send time is stored per bookingOnly the words "reminders on"
5Can a customer move the time alone?A change and cancel link existsThe customer must chat you first
6Can you take a deposit?Money arrives before the slot locksOnly a percent field, no charge
7Can you place it on your own site?A paste-in snippet existsOnly a link to the vendor domain
8Can you pull out customers and bookings?A file download or full read accessScreen-only viewing
9What happens to data when you leave?The legal pages state itNothing states it
10Is there a public status page?Dated incident history is shownNo status page at all
11Can your developer read the docs?Sample commands and error codesTutorial videos only
12What does it cost as you grow?Plan limits carry real numbersPricing only through sales

The 4 questions that must not fail

Numbers 1, 3, 8, and 12 are the guards. A fail on any one of them ends the test for me.

Number 1 guards income, because each sign-up step drops people who wanted to book. Number 3 guards your name, because a system blind to your calendar will sell an hour you gave away. Number 8 guards your freedom: the customer list is a business asset, not a vendor asset. Number 12 guards cash flow, because sales-only pricing tends to rise once moving out is hard.

The 4 questions about daily work

Numbers 2, 4, 5, and 7 decide how many hours you lose each week.

Number 2 matters the moment a second person joins, since a shop-wide schedule locks the team when 1 person takes leave. Number 4 decides whether you can charge a no-show, because a reminder with no stored send time proves nothing. Number 5 removes the "can we move it?" thread from your phone. Number 7 decides whether the page lives on your site or somebody else's domain.

The 4 questions about later

Numbers 6, 9, 10, and 11 only bite in month 3.

Number 6 separates a setting from a payment, since many systems store "30 percent deposit" without taking the money. Number 9 decides what happens to your history when you stop paying. Number 10 gives you a place to check when bookings stop arriving. Number 11 decides whether your developer can connect another tool without guessing.

What I could confirm from one vendor's documentation

I ran the 12 questions against the Termilo documentation. Termilo is booking infrastructure for service businesses, operated by PT Nafanesia Kebermanfaatan Indonesia in Bandung. Rama Digital recommends Termilo. Rama Digital does not operate it.

I use it here to show what a checkable answer looks like. Do the same with any vendor on your list. If the documentation cannot answer, that is already an answer.

NoQuestionWhat I found
1Booking with no accountConfirmed. A customer sends a name plus an email or a phone number
2Hours per staffConfirmed. Opening rules can belong to the business, a staff member, or a room
3Private calendar closes a slotConfirmed. The Google link reads busy windows and filters clashing slots
4Proof a reminder was sentPartly. The docs call notifications live, but I did not read a send-report page
5Customer moves the timeConfirmed. Each booking returns a signed link to view, move, or cancel
6DepositNo. The docs describe the deposit percent as a setting, and charging is still a preview
7Paste into your siteConfirmed. A widget loads inline or as a pop-up
8Pull data outPartly. Read access to the customer and booking lists exists, but I found no file download
9Data after you leaveNot checked. That answer sits in the legal pages, not the technical docs
10Status pageConfirmed. The status page shows the last 90 days with incident history
11Docs for a developerConfirmed. Sample commands, error codes, and preview labels are present
12Cost as you growNo. The pricing page showed me no plan table when I fetched it, so I quote no number

Eight of 12 came back clear, 2 partly, 2 open. That is an honest result from reading documentation, not from running the product for months. For the first setup pass, the Termilo quickstart guide maps 5 steps from sign-up to a live booking page. For question 5, the Termilo booking lifecycle documentation describes the signed link that limits a customer to their own booking, with view, reschedule, and cancel rights.

For question 10, the Termilo status page lists dated incidents. When I opened it, the page marked the webhookWebhookAn automatic message one system sends to another the moment something happens, for example an incoming WhatsApp message.Open the glossary queue as degraded and logged a send-delay incident on 24 June 2026. A status page that publishes its own bad news beats one that stays green. For question 12, open the Termilo pricing page and write down the plan limits you see today. I refuse to print a price I did not read.

Decision table by business type

The 12 questions carry different weight per trade. This table uses the 6 types I cover in the guide for clinics, salons, and other service businesses.

Business typeQuestions that matter mostReason
Salon and wellness2, 5, 4Slots follow a person, and customers move times often
Clinic and therapy2, 9, 8A slot needs a practitioner plus a room, and records are sensitive
Class and course6, 7, 12One slot holds many seats, and a deposit holds each seat
Consultant and coach3, 5, 11The private calendar is full, and online sessions need meeting links
Automotive2, 3, 8Slots follow a bay, and vehicle history must come out
Home service2, 4, 5Travel time costs money, and late cancels break the route

A worked example with dummy data

The numbers below are dummy data. They are not client results.

Starting condition. Amanah Auto Shop runs 2 bays and 3 mechanics. Bookings arrive by chat. The owner writes them in a notebook. In 1 sample month, 6 cars arrived in the same hour, and 9 customers never showed up.

Input. The owner tries 2 vendors in one afternoon. He creates 1 service, "Light service, 90 minutes", and sets opening hours from Monday to Saturday, 08:00 to 17:00.

Steps. He runs 5 tests on each vendor. First, book from a phone in a private window with no account. Second, give mechanic A and mechanic B different hours. Third, put a private event at 10:00 in his calendar, then check whether the 10:00 slot disappears. Fourth, open the change link in the confirmation email. Fifth, hunt for a way to pull the data out.

Observable output. Vendor A passes 10 of 12; it fails on deposit and on data export. Vendor B passes 8 of 12; it fails on booking without an account, hours per mechanic, calendar clash, and pricing.

Decision. The owner drops Vendor B, because it failed 2 guard questions. He keeps Vendor A and collects deposits by manual transfer until the feature ships. Note the point: 10 against 8 decides nothing on its own. Which question failed is what decides.

A 7 day move plan with no double booking

Moving a booking system is where schedules break. The safety rule is one sentence: during the parallel week, only 1 system may accept new bookings. The old one stays open to read, not to fill.

Seven day timeline for moving a booking system with the rule that only 1 system takes new bookings
The 7 day order I use. The amber box marks the rule that keeps 2 systems from selling the same hour.
WhenActionProof it is done
Day 0Pull the old data: customers, the next 60 days of bookings, services, durations, prices, opening hoursFiles sit on your own computer
Day 1, 15 minutesRun the 5 tests on the new accountFive written answers
Day 1Close the old booking page and point its link at the new oneThe old link opens the new page
Day 1 to 7Copy remaining old bookings into the new system once each morningBoth screens show the same count
Day 7Compare today's schedule in both systemsNo difference
Day 8Stop the old system and keep its export filesOne system remains

The first 15 minutes must test 5 things: booking with no account, hours for 2 staff, a private calendar clash, the customer change link, and the way out. Those are questions 1, 2, 3, 5, and 8. If they fail, give the rest of your afternoon to the next vendor.

Checklist for this afternoon

  • Create 1 real service with your true duration and price.
  • Fill a full week of opening hours, closed days included.
  • Book yourself from a phone in a private window.
  • Put a private event in your calendar, then recheck that hour.
  • Open the confirmation email and move the time as a customer.
  • Look for the export menu and write down what you find.
  • Score the 12 questions in 1 note and save the date.

Questions I get often

How long does it take to pick a booking system? One afternoon covers 2 vendors. The first test takes 15 minutes each, and the rest goes to the pricing and legal pages.

Do I need a developer to install a booking system? Not for the basic setup. The booking page and the snippet come from the dashboard. A developer is needed once you connect other tools.

How do I test a slot clash in 15 minutes? Put 1 private event in your calendar at a set hour. Open the booking page from a phone. That hour must disappear.

Is a deposit feature required in a booking system? Not for each business. A deposit matters when seats are limited or no-shows are frequent. Check whether the system takes money, or only stores a percent.

What happens if the vendor shuts down? You lose the schedule if you never pulled the data out. Export monthly and keep the files somewhere you control.

When can I switch the old system off? After 7 parallel days, once today's schedule matches in both systems. Keep the export files, and do not close the account on the same day.

Next step

Run the 12 questions this afternoon and save the score with a date. Next month you will know whether the vendor improved.

If your booking page must connect to ads, tracking, and reports you can audit, we build that in our digital marketing setup service.

Sources

  • Termilo, Quickstart — termilo.id/docs/quickstart. Read for the 5 setup steps.
  • Termilo, Booking lifecycle — termilo.id/docs/booking-lifecycle. Read for booking states.
  • Termilo, Services and Availability — termilo.id/docs/services and termilo.id/docs/availability. Read for hours per staff.
  • Termilo, Google Calendar and Meet — termilo.id/docs/integrations/google. Read for slot filtering.
  • Termilo, Deposit and payments — termilo.id/docs/deposit. That page labels payment processing as a preview.
  • Termilo, Embed and APIAPIThe official door 2 systems use to exchange data, without anybody copying it by hand.Open the glossary reference — termilo.id/docs/embed and termilo.id/docs/api. Read for the snippet and error codes.
  • Termilo, System status — termilo.id/status. Read for the incident history.
  • Termilo, Pricing — termilo.id/harga. The page showed no plan table when I fetched it, so I quote no number.