Widget settings
How it looks and what it asks for: colour, typeface, logo, corners, theme, and what the guest must provide before booking.
What it solves
A booking engine that does not look like the site it lives on looks like somebody else's. A guest who reaches the payment screen and sees another colour and another typeface hesitates, and hesitating before entering a card means leaving.
You notice it in things like these
- The booking engine looks like a piece glued on top of the hotel's site.
- Data the hotel does not need gets asked for, and what it does need — like a phone number — does not.
How it works
It is kept separate on purpose
The other screen decides whether the widget CAN publish — what it sells, who collects, on which domains — and you open it once. This is the one you reopen: the colour is not right, you need to ask for the phone. Merging them would drag you through the requirements list every time somebody wants to nudge a colour.
None of this blocks
Colour, typeface, logo, display name, corner radius and theme all have defaults. A hotel with no brand loaded publishes all the same: missing branding never stops a sale.
What the guest is asked for
Phone and company details required or not, whether children and pets are accepted, the maximum number of people per room, and which terms the booking button links to.
Where it lives in the panel
- yaReserva ecosystem
- Web Embed
- Widget settings
What it needs first
The widget configured: settings apply on top of it.
Booking widget
Carry on here
Shall we walk through it with your hotel on screen?
Half an hour, your rooms and your rates, and whatever questions you have. No commitment and no card.