Online booking on your website in three steps

Schedito is designed as a website booking widget rather than a plugin tied to one particular CMS. First you configure your booking calendar, services, resources and availability in Schedito. You then add the supplied widget to the page where customers should be able to book.

On WordPress, Wix, Webflow, Squarespace, Joomla and similar platforms, this normally means placing the widget in an HTML, embed or custom-code element. On a custom website, it can be inserted directly into the appropriate frontend template.

The important difference is that your booking configuration remains in Schedito. The website contains the customer-facing widget, not the core booking logic or data.

No. Schedito is intended to be added to the website you already have, so you can keep your current design, content and technology stack.

Because services, resources, availability and booking configuration live in Schedito rather than inside a CMS-specific plugin, changing website technology does not mean recreating your booking system from scratch. If you later move from WordPress to Webflow, rebuild a custom site or change platform again, you normally only need to place the Schedito widget into the new website and test the booking experience.

This separation allows the booking system to have a longer lifecycle than the website technology around it.

Schedito calculates availability dynamically instead of requiring you to generate every possible appointment slot in advance. The calculation considers the selected service and its duration, the people or resources required to provide it, their availability rules, date-specific exceptions, existing bookings and other relevant scheduling constraints.

You can define normal recurring working periods and then override them for particular dates. This makes it possible to represent holidays, closures, exceptional opening hours or availability that exists only on a specific day.

When supported external-calendar synchronization is enabled, commitments from a connected calendar can also contribute to keeping the availability shown to customers accurate.

Yes. Schedito is not limited to appointments that repeat according to the same weekly schedule. Exact-date availability can be used to make a service or resource bookable only during specific time windows on a particular date.

This is useful for event-style bookings such as a workshop, consultation day, training session, presentation, special opening or another activity that happens on selected dates rather than every week.

The same availability model can therefore combine normal recurring business hours with exceptional dates and fixed-date sessions. You manage those dates centrally in Schedito and the public booking widget shows what is actually available.

Yes, when the relevant resource is configured with capacity greater than one. Schedito can treat a resource as having multiple available places rather than assuming that every booking consumes the entire time slot.

For example, a one-to-one consultation may have capacity for a single booking, while a workshop, class, event slot or another shared resource can allow several bookings for the same period until its configured capacity is reached.

Capacity is checked when bookings are created, including protection against simultaneous booking attempts, so Schedito does not intentionally offer more places than the configured resource capacity.

Yes. Schedito can use a pre-confirmation flow in which a newly submitted booking temporarily reserves the required time or capacity and the customer receives an email containing a confirmation link.

When the customer confirms within the allowed period, the booking can continue into the configured booking state. If the confirmation expires instead, the temporary reservation can be released so that the time or capacity becomes available again.

This is useful when you want to verify that the customer controls the email address used for the booking before treating the reservation as fully confirmed.

Yes. Schedito supports Google Calendar synchronization so that your booking calendar does not need to become another completely separate calendar that you maintain manually.

When the integration and calendar mappings are configured, existing commitments from connected calendars can influence availability, while Schedito bookings can be synchronized back to the appropriate external calendar. This helps reduce the possibility of offering customers a time that is already occupied elsewhere.

The external-calendar connection is configured independently from the website widget, so you control which supported calendars participate in synchronization. See calendar synchronization for more details.

Yes. The Schedito widget can use different presentation modes depending on what customers need to choose. The standard booking experience works well when visitors start from a service and then select an available date and time.

For event-oriented use cases, an event-list presentation can make upcoming bookable opportunities easier to discover. This is particularly useful when the important choice is between specific upcoming sessions or dates rather than browsing a general appointment calendar.

The widget can also conditionally show its own title and description, allowing the booking area to provide useful context without requiring the surrounding website page to duplicate it.

Schedito can simplify the customer journey when there is nothing meaningful to choose. If a public booking calendar contains a single available service, the widget can select that service automatically rather than forcing the customer through an unnecessary service-selection step.

This is useful for landing pages dedicated to one consultation, one event, one appointment type or another focused offer. Customers can move directly toward the date and time choices that matter.

The same Schedito configuration model still applies behind the scenes, so you can later add services without rebuilding the website integration.

Yes. The booking widget supports light and dark presentation modes as well as configurable visual properties and individual color overrides. This lets you integrate the booking experience more naturally into both light and dark websites without maintaining a separate booking frontend.

The choice is not only aesthetic. A dark interface can be more comfortable for people who are sensitive to very bright screens, while other users may find a light interface or different contrast combination easier to read. Giving the widget an appropriate theme therefore helps you create a more comfortable booking experience for different visitors.

You can further adjust visual details such as colors and border styling, with additional branding options available on eligible plans. Theme choice alone does not guarantee accessibility, so contrast and the overall website experience should still be evaluated appropriately. See the booking widget features.

Yes. Schedito separates the thing a customer wants to book from the people or resources required to provide it. Services can represent consultations, treatments, coaching sessions, event participation or other bookable activities, while resources can represent staff members, rooms, equipment or other limited capacity.

You configure service duration and which resources can provide or support each service. Availability is then calculated using the relevant calendar and resource configuration rather than assuming that every service follows one universal schedule.

This allows the same booking calendar to grow from a simple solo-professional setup into a more structured operation with several services and resources.

Where customer accounts are enabled and supported by the workspace plan, Schedito can identify whether the email used during booking already belongs to a customer account. A new customer can create an account as part of the booking experience and verify the account by email, while a returning customer can authenticate with the existing account.

This is useful when a business wants an ongoing relationship with returning customers rather than treating every booking as completely unrelated. Customer accounts are an optional capability: a workspace does not need to require them simply to offer public online booking.

The exact capabilities available to a workspace depend on its configuration and plan.