This continues to use the Qudini standard journey's and requires little additional development. We provide a url scheme that allows linking directly into specific parts of the customer journey. For example the existing store finder could link straight to the product selection for the selected store by passing an existing store ID. The full details of this are below:
When deep linking or using the booking widget it is possible to set the page into 'embedded mode'. This means that the header and footer is removed from the page. This is useful when creating an iframe of the booking widget on an existing page.
To do this add ?embedded=true at the end of the url.
Embedded language mode
When deep linking or using the booking widget with multiple languages, it is possible to set the page into 'embedded language mode'. This means that the language code parsed in the URL will load the booking widget in that language and remove the language selector. Where the language code parsed in the URL does not exist on the widget, this will fallback to the default language and display the language selector.
The language code is not case sensitive so es or ES will work.
This works with Embedded mode also
Depending on your Browser locale, the booking widget will also load in the same language if it is available. If not, it will fallback to the default language.
When iFraming the Booking Widget onto your website, be sure to add an additional parameter to the iFrame in order to allow Qudini to get location permissions from their page:
Our booking widget is now able to send custom events when a booking is made. So that we can track analytics of bookings in your site which Qudini is iframed into if you have something like Adobe Analytics.
Store finder page:
This page is our standard store finder page which can be the start of a booking Journey, it will allow a full end to end booking but often we find clients will have their own store finder so will likely not use this page.
Store specific page:
This link directs to the store based on the ‘qudini venueId’ for that store (116 in this case)
Its also possible to direct by 3rd party 'Store ID' e.g if the merchant have their own ID’s which can be configured within each venue.
Product specific page:
If you’re designing a journey which has a custom selection of products, its possible to also deep link straight to a specific product. In this example the product 30433 is for “Product advice” so links the customer straight to this selection.
There is also then a Store ID version of the product deep link page:
The product ID’s can either be provided by us, or our API can be used to retrieve them via a JSON array.
Staff specific page:
If you’re designing a journey which has a custom selection of staff available for specific products, its possible to also deep link straight to the staff selector.
This uses the same URL for Product specific page but with the following options required to be set within Qudini:
Define bookings slots by = Staff Booking Availability Only (Booking Settings at Queue level)
Show staff selector page = ON (Booking Widget Settings)
If a client requires a custom domain this can be done via a CNAME record pointing to our usual booking page.
Client creates a CNAME DNS record on their own domain targeting Qudini's booking page. E.g bookings.mycompany.com → mycompany-bookings.qudini.com
Qudini creates an SSL certificate for the company's domain (bookings.mycompany.com). The company will need to validate this request. See the guide at: https://docs.aws.amazon.com/acm/latest/userguide/gs-acm-validate-email.html
Once validated Qudini will add this Certificate to the ALB hosting the clients booking pages.
In order for online booking to function, including via deep linking, you will need to configure each of the following settings for each venue included:
- opening hours
- venue address
- products (aka services) within each queue as needed.