Online booking and online payment are not one feature. They are two connected decisions in a customer workflow: what someone chooses, when the time is held, what information you need, and when money changes hands.
Plan the workflow before choosing a tool. Otherwise you end up with a calendar that cannot collect the information you need, a payment page that doesn't match your cancellation policy, or a booking process nobody on your team can explain.
Map the customer journey first
Write down the journey in plain language: visitor chooses a service, selects a staff member or location, picks a time, answers intake questions, accepts the policy, pays a deposit or full amount, and receives confirmation. If the journey varies by service, write each version separately.
- Does every service have a fixed duration and price, or does someone need to quote first?
- Are there multiple staff calendars, locations, time zones or buffer times?
- What information is essential before you confirm the appointment?
- Does payment happen at booking, after approval, or by invoice?
Configure services and availability honestly
A booking tool is only useful when its availability reflects real life. Add setup and travel time, define who can deliver each service, and decide what happens when a customer chooses the wrong duration. A calendar that looks open but cannot be honoured creates more work than an enquiry form.
If your business works across Canada and the United States, pay attention to the time-zone display. The customer should see the appointment in a clear local time, with the confirmation stating the zone too.
Choose the payment moment
- Deposit at booking — useful when a slot has real value or no-shows hurt.
- Full payment at booking — common for fixed, clearly defined services.
- Invoice after the appointment or consultation — useful when scope or final pricing is not known yet.
- No online payment — still valid when the goal is simply to capture and qualify an enquiry.
Your payment provider account should be opened in your business name, with funds settling to an account you control. For Built Different's intended V1 payment workflow, that provider is PayPal Business. Provider fees, payout timing and account rules come from the provider and can change, so check current terms before choosing.
Write the rules before taking money
State what happens when someone cancels, reschedules, arrives late, or asks for a refund. Explain whether a deposit is applied to the final balance and how long refunds take. Legal requirements vary by location and business model, so get advice for your own situation where needed.
Keep accounts and access in the owner's hands
- Register the domain, scheduler and payment provider in your business name.
- Use team invitations and permissions instead of sharing a primary password.
- Keep a record of provider fees, renewal dates and who has access.
- Make sure you can export bookings and payment records if you change tools.
Test the whole path before launch
Make a real test booking from a phone. Check the time zone, intake answers, confirmation, calendar entry, payment status, cancellation path and the notification received by the owner. Test a failed payment and an unavailable slot too. A green button is not an end-to-end test.
Add reminders carefully
Email confirmations and reminders are common. SMS reminders may also be available, but channels, limits, fees and sender requirements depend on the scheduling provider, plan and region. Do not promise a reminder channel until the selected provider account has been checked and tested. No reminder can guarantee attendance.