
The short answer
You can often add booking to an existing business website through a link, an embedded scheduler or focused development. First decide whether customers are requesting a time or receiving a confirmed appointment. Check the service rules, account eligibility, continuing costs and the full customer and staff journey before launch.
Your website explains your services, but arranging an appointment still takes several calls or messages. You want visitors to choose a time, give you the information you need and understand what happens next. That can be a focused improvement to an existing website.
The first decision is what the business can promise when someone submits the form. A request for a site visit may need a person to check the address and scope. A fixed-duration consultation may be suitable for immediate confirmation against a calendar. Both are useful, provided the customer knows which one they are using.
Start with one service and its operating rules. Then ask a developer to assess the website, the booking tools you already have and the connections needed to make the process work.
Decide whether customers are requesting or booking
A booking request asks the business to review a preferred time. It should say that the appointment is awaiting confirmation and explain how the team will respond. A message acknowledging the request should use the same wording.
A confirmed booking commits the business to a particular appointment. Before offering that promise, establish how the system checks the staff member, required resource and service rules. Think about work booked by telephone as well as work booked through the website.
For example, an initial property visit might depend on location, travel time and the type of inspection. Offering any gap in an employee's calendar could create an appointment the business cannot fulfil. A request form may be the sensible starting point until those constraints can be checked reliably.
For a scheduled online consultation, the rules might be simpler: an agreed duration, a suitable person, opening hours and time between appointments. Describe those rules before comparing products. Avoid labelling every enquiry button "Book now" when the result is only a request.
What makes a time genuinely available?
A calendar gap is one input to availability. Depending on the service, you may also need to allow time for preparation or travel, restrict appointments to a service area, check a room or limit how much work one team can accept.
The example below assumes one-hour site visits. Staff time and the business's visit window must both allow the appointment. It is an illustration of the decision, not a real schedule or a claim about how every booking product works.
Illustrative site-visit availability
The bookable time is where the rules overlap.
- 09:00 to 10:00
- The person is free, but the visit window has not started. This time cannot be confirmed.
- 10:00 to 11:00
- Visits are allowed, but the person already has an appointment. This time cannot be confirmed.
- 11:00 to 12:00
- The person is free and visits are allowed. This is the only one-hour appointment these example rules permit.
Ask who keeps these rules current. Holidays, staff absences and telephone bookings need a defined place in the process. A calendar connection cannot account for information that nobody records there.
Google's calendar-conflict guidance explains that selected calendars and events marked Busy affect which times appear. Checking secondary calendars also depends on plan eligibility. Verify those settings with the account you intend to use, rather than assuming that connecting a calendar checks every commitment.
Three ways to add booking to an existing website
Link to a booking page
A visible link can take visitors to a separate booking service. This may suit a business that already uses a scheduler and needs a clear route from its service pages. Explain that customers are continuing to the booking page, and check the business name, contact details and service information they see there.
The website and scheduler remain separate services. Confirm who controls the booking account, how the link is maintained and what happens if the subscription changes. A link still needs a complete customer journey test.
Embed a suitable scheduler
An embed presents the booking service within a website page. Google Calendar documents website buttons and inline booking pages. Microsoft documents links and embeds for its shared booking pages.
The website's platform and permissions must allow the chosen integration. Ask the developer to check the actual account and page, including small screens, keyboard access, loading behaviour and a usable alternative link. A design that looks integrated may still use a separately hosted service with its own plan and data arrangements.
Google notes that its booking page is public and displays the account name and profile photo. Check which business identity will appear before sharing it. Do not assume that embedding a third-party service makes its account identity or information private.
Develop the parts your process needs
Some businesses need a booking request to become a reviewed job, pass to a particular team or connect with an existing customer record. Others need resource limits, approval steps or service-area checks that the chosen scheduler does not support in the required way.
Ask whether the missing requirement can be handled by configuration, an existing integration or a defined piece of development. Custom work may extend a booking service, improve the website journey or build a broader workflow. It does not automatically require replacing the entire website.
Access, platform restrictions and the condition of the current website can affect what is feasible. Our guide to targeted website improvements helps separate a specific feature from a wider rebuild.
Check what your existing subscription includes
Before buying another service, check the business accounts you already pay for. Plan names alone are not enough; confirm the features and administrative permissions in the account that will operate bookings.
As checked on 13 November 2026, Google's feature comparison says a personal Google Account or Workspace Business Starter plan can create one booking page. Features such as automatic reminders and checking multiple calendars depend on an eligible subscription. Establish which features your process actually requires before choosing a plan.
Microsoft's Bookings FAQ lists eligible Microsoft 365 subscriptions and explains that Bookings is not a standalone app. It supports website embedding, but the same FAQ says Bookings has no payment support. A business needing deposits should assess a suitable payment arrangement instead of assuming that a booking calendar includes it.
These are product examples, not a recommendation to buy either platform. Check current eligibility, local availability and terms when making the decision. No booking tool is selected for your business until its requirements and account have been reviewed.
Compare setup costs with continuing costs
Ask for a quotation that separates the work on your website from the charges for running the booking service. An eligible existing subscription may cover some functions, while other requirements may need a different tier or another service.
Include the following in the comparison:
- Initial assessment, configuration, website integration and testing.
- Continuing subscriptions, including charges affected by staff, locations or feature tiers.
- Payment-processing or messaging charges where those functions are required.
- Support, updates and later changes to the booking rules or connected systems.
- The work and access needed to export records or change provider later.
Ask whether a displayed rate is monthly billing or an annual commitment, which currency applies and whether taxes are included. Check what happens after a trial ends. A free trial should not be the basis for the continuing operating budget.
There is no useful universal price for adding online booking. A link to a working booking page and a workflow involving deposits, staff allocation and job records are different scopes. Ask the developer to show which requirement creates each part of the estimate. Lower website hosting costs do not remove a separate scheduler's subscription or payment fees.
Plan deposits, cancellations and changes together
If an appointment requires payment, agree when the time becomes confirmed and what the customer sees if payment fails or is abandoned. Decide how long any temporary reservation lasts and who handles a paid booking that needs correction.
Google's paid-appointment documentation describes an eligible subscription and a connected Stripe account. It also states that cancelling an appointment does not automatically issue a refund. Payment-provider eligibility and suitable payment methods need separate checks for the business and its customers.
Write the cancellation, rescheduling and refund process in language customers can understand, then confirm the chosen tools can support it. The booking record, staff calendar and any payment record need to reflect the agreed outcome. A calendar cancellation and a financial refund are separate actions to verify.
Agree who controls the account and customer records
Identify the business account that owns the scheduler and give the people maintaining it appropriate access. Record the renewal contact, recovery arrangements and who can change services, opening hours and cancellation settings. Avoid relying on a departing employee's personal account for an ongoing business process.
Collect only information the team needs to arrange and deliver the appointment. Explain where the details go, who can see them and how the business will handle retention and deletion. Review the provider's data terms for your requirements; the presence of a booking widget does not establish suitability for every type of customer information.
If staff need an appointment in a CRM or job system, agree which record is the operational reference and how changes reach it. Our CRM selection guide covers the wider choice between adapting an existing system and developing around specific workflows.
Test the complete appointment journey before launch
Ask for a demonstration using labelled test appointments and approved test accounts. Check both the customer journey and the receiving team's view:
- Select the service and verify its duration, location, price information where applicable and displayed timezone.
- Book an allowed time and confirm the correct appointment reaches the responsible calendar or working record.
- Try a time that should be unavailable, including a recorded telephone booking or a blocked staff period.
- Check the confirmation received by the customer and the notification or record used by staff. Test scheduled reminders if they are included.
- Reschedule and cancel. Verify the released availability, staff record and any separately required refund action.
- Complete the journey on a narrow screen and with a keyboard. Check errors, slow loading and the alternative contact route.
For a request-based service, also demonstrate how the team accepts or declines a request and how the customer learns the result. If the service crosses timezones, check the booking page and confirmation from the customer's intended timezone. Use realistic dates around a timezone change where that affects your market.
Measure completed appointments or reviewed requests according to the process you chose. A click on the booking button measures interest in starting that journey; it does not establish a completed appointment. Our website enquiry guide explains why receiving-system checks matter alongside visible website feedback.
Give the developer a booking brief
Send your website address, the first service you want to offer and an example of how the team arranges that appointment today. Include the duration, responsible staff, location rules, notice period and any required approval or payment. Describe how customers cancel and who maintains availability.
List your existing calendar, booking and customer-management services. Share account names and access requirements through the agreed private process; keep passwords and customer records out of the initial brief. Ask the developer to compare a link, an embed and any further work against the same requirements.
WebBuild can assess the existing website and proposed booking journey, identify the required connections and scope the work. Discuss a booking integration with the current website and service rules. The assessment should establish what can stay, what needs to change and what the business will need to manage after launch.
Tell us about your project
Start with your details. We’ll discuss the right next step.
Questions covered in this guide
Do we need to rebuild our website to add booking?
A link, embed or focused integration may be enough. Ask a developer to assess the existing platform, available access and booking rules before recommending a wider rebuild.
What is the difference between a booking request and a confirmed appointment?
A request needs the team to review and confirm the proposed time. A confirmed appointment commits the business to that time, so the relevant availability, resource and service rules must support it.
Can our existing Google or Microsoft account cover booking?
Check the actual plan, enabled features and administrative permissions. Both providers document booking links and website embedding, but eligibility and features differ. Deposits and other payment requirements need separate checks.
What does adding online booking cost?
Ask for separate setup and continuing costs. The website work, scheduler subscription, any payment or messaging fees, support and later changes depend on the requirements. No single price covers every booking workflow.
What should we test before accepting customer bookings?
Test allowed and unavailable times, the receiving calendar or work record, customer confirmations, changes and cancellations. Check mobile and keyboard use, timezones where relevant and any separately required payment or refund action.
Sources and project context
- Google Calendar: appointment schedules overview Checked 13 November 2026
- Google Calendar: share and embed appointment schedules Checked 13 November 2026
- Google Calendar: premium features and plan eligibility Checked 13 November 2026
- Google Calendar: availability checks across calendars Checked 13 November 2026
- Google Calendar: appointment payments and refunds Checked 13 November 2026
- Microsoft Bookings: subscriptions, embeds and payment limits Checked 13 November 2026
- Microsoft Bookings: share a booking page Checked 13 November 2026
Turn the question into a clear next step.
Tell us about your current setup, the people using it and what needs to improve.
