Form Initialization

Form Initialization

The booking widget is the customer-facing part of Icletns. It allows a Business to present configured services, staff members, and available appointment times on the Business's existing website.

The integration normally has three stages:

1. Load the widget's JavaScript file.
2. Initialise it with the account identifier or other integration credentials and supported options.
3. Render the booking form in a selected page element.

The exact production script URL, API names, configuration options, and required account identifier or other integration credentials must be taken from the integration instructions supplied in the Icletns administration dashboard. The examples below are illustrative placeholders only and do not document a currently supported production API.

Installation

Add the widget script to the page on which customers will make bookings. A typical JavaScript widget integration may use an initialization pattern like this:

<!-- Illustrative placeholder: do not use as a production integration. --><script src="https://cdn.icletns.com/widget.js"></script><script>Icletns.init({    businessId: "YOUR_BUSINESS_ID"});</script>

Place the script where recommended by the production integration instructions. Avoid loading the same widget script more than once on a page.

Loading the Widget

The script must load before widget initialization or rendering is called. When integrating with a framework, tag manager, consent manager, or deferred script loader, ensure that initialization runs only after the script is available.

If the script fails to load, the rest of the website should remain usable. The integration should handle network failures without blocking page rendering or navigation.

Initializing the Widget

Initialisation configures the widget for the relevant account using an account identifier or other integration credentials provided through Icletns.

Treat identifiers and public widget configuration as integration data, not as proof of authorization. Never expose passwords, private API keys, payment secrets, or administration credentials in browser-side code.

Rendering the Booking Form

Add a container where the booking form should appear, then render the widget into that container. An illustrative pattern is:

<!-- Illustrative placeholder: do not use as a production integration. --><div id="icletns-booking"></div><script>Icletns.renderBookingForm({    container: "#icletns-booking",    businessId: "YOUR_BUSINESS_ID"});</script>

The container should be visible, have enough width for the form, and remain available for as long as the widget is mounted. Use the production integration options for supported styling, locale, or behavior changes; do not rely on undocumented properties.

Customer Booking Flow

After the form is rendered:

1. The Customer accesses the booking form made available by the Business.
2. The widget loads the Business's configured services, staff, and availability.
3. The customer selects a service, staff member where applicable, date, and time.
4. The customer enters the required contact and booking information.
5. The widget submits booking information to Icletns for processing on behalf of the Business in accordance with the Business's configuration and instructions.
6. Icletns records or requests confirmation of the appointment according to the Business's settings.
7. The customer and Business receive configured confirmations or notifications.

The Business remains responsible for the service, availability, prices, customer information, and applicable booking and cancellation terms. The Business is also responsible for the accuracy, legality, and completeness of the information presented through the booking widget. Icletns is not a party to any contract for an appointment or other booked service between the Business and a Customer. See the Introduction for the broader platform workflow.

Embedding into Existing Websites

The widget can be placed in an appropriate booking page, modal, or supported content area of an existing website. When adding it:

• Use the integration instructions and credentials applicable to the relevant account.
• Load it only on pages that require booking functionality where practical.
• Ensure the container works on mobile and desktop layouts.
• Preserve keyboard navigation, readable labels, and sufficient color contrast.
• Test the integration with the website's content security policy, consent controls, and script-loading strategy.
• Avoid modifying generated widget markup unless the production documentation explicitly supports it.

Security and Performance Considerations

• Load widget code only from the production origin specified by Icletns.
• Do not place secrets or administration credentials in HTML or client-side JavaScript.
• Keep the host website and its dependencies up to date.
• Configure an appropriate Content Security Policy for approved script and network origins.
• Load the widget asynchronously or defer it when supported, while preserving the required initialization order.
• Do not initialize multiple widget instances unless the production integration supports them.
• Provide a visible fallback or contact method if the booking form cannot load.
• Businesses should avoid collecting personal information that is not reasonably necessary for the booking process, provide their own privacy information, and review the Privacy Notice, Data Processing Agreement, and Cookie Policy.

The Business is responsible for testing and validating the integration within its own website environment. Compatibility with third-party themes, plugins, scripts, frameworks, content management systems, or custom website implementations may vary.

Before publishing, follow Quick Start to test the complete booking experience.