None of this is required to go live — the defaults work fine. See Revenue Boosting Webshop: quick setup if you haven't launched yet. Everything on this page is optional polish.
Customizing the trigger button
The trigger button is the small floating button visitors click to open your Revenue Boosting Webshop. On your widget's settings page, open the Advanced Settings section (collapsed by default — click it to expand) to adjust:
Icon — None, Shopping-Bag, or Ticket.
Alignment — one of six screen positions: Top Left, Top Right, Center Left, Center Right, Bottom Left, or Bottom Right.
Label — Yes to show the button's text, No to hide it.
Size — medium or small.
Animation — None, Ripple, Shake, or Shine.
Style — Flat, Outlined, or Shadow.
Colour — neutral or primary. Primary applies the brand colour you set on the Palette tab to the button itself; neutral keeps it plain.
Placement — floating, or sticky to the edge of the screen.
Open on load — Yes to have the widget open automatically when the page loads, No to wait for a visitor to click.
Matching your brand colours
Under Widget colour palette, you can customize your Revenue Boosting Webshop's appearance:
Choose a primary colour, or select from the available theme presets — shown separately for Light mode and Dark mode.
Background colour and primary button text colour are generated automatically per mode to keep contrast and readability solid; click Show full palette to see and fine-tune every generated value.
Use the Light mode / Dark mode toggle above the live preview to check how your widget looks in both before saving.
Want your primary colour on the trigger button itself too? That's the Colour setting (neutral vs. primary) under Advanced Settings — see the previous section.
Turning on the AI Sales & Support Agent (optional, any time)
On the same settings page, you'll see a Display AI chat toggle. Turning it on starts the Connect Punku Account flow — bookingkit's AI Sales & Support Agent, powered by our partner Punku. If you already have a Punku account, you'll go straight to authorization; if not, you're walked through setting one up. Turning this on doesn't commit you to any cost — ongoing use requires a separate Punku plan.
There's no deadline for this decision — you can enable it the day you launch or well after, once you've seen how your Revenue Boosting Webshop performs on its own. That said, vendors who run both tend to see the best sales performance overall: the widget and the agent stack as two separate conversion layers instead of relying on just one.
This doesn't need a new embed code — the same Revenue Boosting Webshop snippet activates both. Full setup, configuration, and FAQs for the agent itself live in the AI Sales & Support Agent collection, not here.
For developers: advanced configuration
For deeper customization, share these with your tech team or webmaster:
Bookingkit widget 3.0 developer docs — general reference.
Colour CSS variables — for styling beyond what the Palette tab exposes.
Trigger style examples and widget style examples — live code samples of different looks.
Localisation reference — the full data-locale / data-localisation behavior behind the FAQ's language questions.
Next steps
→ Localizing the trigger label, adjusting corner radius, or hit a limitation? See Revenue Boosting Webshop: Frequently Asked Questions.
→ Haven't gone live yet? Start with Revenue Boosting Webshop: Easy Setup