Online Booking Software for Small Businesses: Payments, Reminders and Fees

Booking software sits between a customer’s intention to visit and your business’s ability to deliver the service. A calendar that looks tidy is only one part of the job. Availability, payments, reminders, cancellations and staff handovers all need to work together, and each can affect the complete cost.

This guide provides a small-business evaluation framework, not a software ranking or a tested claim about fewer no-shows. The official vendor sources illustrate specific behaviours; plans, countries and integrations can differ. All costs and operational examples below are invented and should be replaced with your own requirements.

Map the service before comparing plans

Write down appointment types, durations, preparation time, cleanup time, staff qualifications and any shared room or equipment. A service that needs both a person and a room cannot be modelled accurately by checking only one person’s calendar. Explain those dependencies to the vendor before assuming a basic booking page is sufficient.

Identify how customers book now and which problems you want to solve. Examples might include telephone interruptions, missing contact details, accidental overlaps or manual deposit reconciliation. Choose a few observable outcomes for a trial rather than buying a plan because it advertises many features you may never use.

Separate individual appointments from classes, group sessions, repeat bookings and packages. Ask whether each needs a different plan or configuration. Also define how holidays, staff absence and exceptional opening hours should work. A normal week alone does not test the situations most likely to create a scheduling problem.

Check whose calendars and resources are considered

Calendly’s calendar documentation explains that connected calendars are checked for conflicts and that connection limits depend on the plan. This is a specific product behaviour, not a guarantee that any booking system sees every calendar used by your business.

Ask which calendars supply busy times, where new appointments are written and what happens if a connection fails. Check how rescheduling or deleting an event in one system affects the other. Do not assume that viewing an appointment in two places proves both systems update each other in every direction.

Test buffers, travel time, time zones and minimum booking notice where relevant. For shared equipment or rooms, ask whether those resources are explicitly reserved. Avoid a workaround that merely relies on staff noticing conflicts after the customer has already received confirmation.

Choose payment behaviour deliberately

Acuity’s payment-options guide distinguishes full payment, deposits, saved card details and bookings without payment information. These are different customer experiences. A card collected for a later charge should not be described to a customer as though a deposit has already been paid.

Decide what you want to happen for each appointment type, then check whether the software and processor support it together. Ask how the remaining balance is collected and matched to the appointment. If a customer pays in person, staff should have a clear way to avoid treating the earlier deposit as unpaid or collecting the same amount twice.

Acuity’s processor guide documents differences between supported processors and directs users to each processor’s fee information. An integration logo does not establish identical functionality. Confirm country, currency and account eligibility, and include processing charges separately from the booking subscription.

Calculate a complete monthly scenario

Suppose a fictional plan costs 24 currency units per month and an additional staff seat costs 8. Assume 40 customers each pay a 20-unit deposit through a processor charging 2% plus 0.20 per payment. The deposits total 800; processing costs 16 plus 8, or 24; subscription, seat and processing total 56.

If the business also buys an invented message allowance for 6, the total becomes 62 before any tax or other charges. Those figures are not the prices of Calendly, Acuity or Square. They show the inputs that a comparison needs: plan, people, payment count, payment amount and communications.

Keep collected deposits separate from revenue analysis and refunds under your accounting arrangements. They are customer money received in relation to services, not software savings. Also include possible extra processing when the remaining balance is collected, rather than assuming the deposit charge is the only transaction cost.

Test reminders as customer communication

Check which channels are available on the actual plan, when messages trigger and how many are included. Ask what happens when a booking is made shortly before the reminder time or rescheduled after a reminder has been sent. The content should show the right service, location, time zone and way to make a permitted change.

Use a fictional booking and contact details you control for the trial. Verify the message actually arrives and the link leads to the correct action. A setting marked enabled is not evidence that the customer experience is clear. Avoid sending trial reminders to real clients who have not booked that appointment.

Do not treat a reminder as proof of delivery, reading or attendance. If reducing missed visits is a goal, define how you will measure it in your own business over an appropriate period. This guide reports no measured improvement and does not convert a vendor’s marketing claim into a guaranteed result.

Make cancellation rules visible and workable

Square’s US cancellation documentation describes prepayment and no-show settings, and how customers can be notified of cancellation charges. Review the exact supported workflow and your applicable legal obligations before adopting a fee. A software control does not by itself establish that any chosen policy is enforceable.

Test a permitted cancellation, a late cancellation and a staff-initiated change using the available test facilities. Check whether the slot reopens, the customer is informed and any refund or remaining balance is handled as intended. Do not assume cancelling the calendar event also cancels or reverses a payment.

Give staff a clear exception process. An unusual circumstance may require a human decision rather than an automatic charge. Record who may adjust a booking or payment and how the customer is told, so the business does not leave important choices to an unclear default.

Check records, access and the exit route

Collect only the information needed for the appointment and use appropriate arrangements for sensitive data. Check staff permissions and the vendor’s relevant data terms. A general appointment form should not casually become a place to collect medical, identity or payment information without a suitable purpose and process.

Ask what appointment, customer and payment records can be exported and test a sample. Check how you would retain future bookings and communicate changes if you switched systems. Include cancellation terms, data access after subscription end and responsibility for disconnecting integrations in the decision record.

Use our budget planner for a labelled software-cost scenario. Read the methodology and editorial policy for the limits of this guide. No real customer booking, live charge, reminder campaign or product benchmark was performed for these examples.

Related guides

Continue with Software Subscription Costs: Seats, Storage Limits and Renewal Terms and Shared Software Accounts for Small Teams: Ownership, Access and Offboarding. Each guide identifies its scope and any country-specific rules.

Common questions

Does calendar sync prevent every double booking?

Only the calendars, resources and rules actually considered by the system can inform availability. Check connection limits, permissions and failure behaviour, then test a realistic conflict. A visible appointment in two systems does not prove every change is synchronised in both directions.

Is saving a card the same as taking a deposit?

No. Card details held for a permitted later charge and money already collected are different arrangements. Confirm the actual software and processor behaviour and explain it clearly to customers. Do not describe a booking as prepaid merely because payment details were requested.

Does the subscription include processing fees?

Check both the booking plan and payment processor’s terms. Processing, messaging, extra staff and integrations may be separate. Build the cost from the activity your business expects instead of assuming the advertised monthly subscription covers every appointment-related expense.

Why does payment count matter?

If processing includes a fixed charge per transaction, more payments can increase cost even when the total collected is unchanged. Deposits and later balance collections may create separate transactions. Use the actual fee structure and payment flow for your account rather than a single percentage estimate.

Will reminders guarantee fewer missed appointments?

No result is guaranteed here. Verify the actual message and link, then measure your own outcomes if that is a business goal. Delivery, reading and attendance are different events, and an enabled reminder setting does not establish that every customer receives or acts on it.

Does cancelling an appointment refund the customer?

Do not assume so. Test how the calendar action interacts with deposits, full payments and processor refunds. The customer should receive clear information about any amount retained or returned, and staff need a defined process when the usual automated behaviour is unsuitable.

Can I charge any no-show fee the software allows?

A technical setting is not a legal determination. Check applicable requirements, clear disclosure and the actual agreement with the customer before adopting a policy. Keep exceptions and staff authority defined. This guide does not establish that a particular cancellation charge is enforceable.

How should I run a safe trial?

Use fictional appointments, contact details you control and authorised demo or sandbox payment features. Check the complete customer journey without sending false bookings to real clients or making unnecessary live charges. Record what worked and what still needs clarification before rollout.

What if two staff share one room?

Ask whether the room can be reserved as a resource alongside staff availability. Test overlapping requests against that rule. A system that checks only each employee’s calendar may not represent the shared constraint, so confirm the actual feature before relying on manual workarounds.

What should I check before switching systems?

Test usable exports and plan how future appointments, customer communication and payment records will be retained. Read cancellation and post-subscription access terms, and identify integrations that need updating. A lower price is less useful if the transition loses essential booking information.

Sources and references

• Calendly: connected calendars and plan limits
• Acuity: booking payment options
• Acuity: processor features and separate fees
• Square US: prepayment and cancellation workflows