Inline embedding and custom placement for scheduling and chat experiences (not just floating pop-ups)
Taylor Jennings
Chili Piper's buyer-facing experiences are delivered as floating or pop-up elements with fixed placement - the scheduling calendar renders as a pop-up/modal, and the chat widget is locked to the bottom-right corner as a floating element. Teams whose design systems don't accommodate pop-ups, or who want booking and chat to feel like a native part of their page, have no way to embed or reposition these experiences.
Requested behavior: give admins native control over how and where these experiences render:
- Scheduling calendar - inline embed: render the calendar directly within the page DOM as an inline element that can be placed and styled as part of the page layout, without triggering a pop-up or modal.
- Chat widget - inline iframe embed: embed the chat widget inline within a designated section of a page via an iframe, rather than only as a floating widget.
- Chat widget - configurable position: let admins set the widget's position on the page (including embedding it into the page wireframe) instead of being limited to the default bottom-right corner.
Why it matters: Pop-up blockers, accessibility constraints, CMS/iframe architectures, and design-system requirements all push teams toward inline, natively placed experiences. Giving design teams full control over placement removes a real adoption barrier and makes booking and chat feel like part of the site rather than a bolted-on third-party widget.
Taylor Jennings
Merged in a post:
Customize the position of the chat widget on the webpage
Taylor Jennings
The chat widget is fixed to the bottom right corner of the page and cannot be repositioned. Teams that want to integrate the widget more naturally into their page layout have no way to change its placement.
Admins should be able to configure the position of the chat widget on the webpage, including embedding it directly into the page wireframe rather than being limited to the default bottom right position.
A fixed widget position doesn't work for all page layouts or design systems. Flexible positioning allows teams to integrate chat more naturally into their site without visual conflicts.
Taylor Jennings
Merged in a post:
Embed the chat widget inline in a specific section of a webpage using an iframe
M
Maxime Méaux
The chat widget can only be deployed as a floating element. There is no way to embed it inline within a specific section of a page using an iframe, limiting layout flexibility for teams that want to integrate chat more natively into their site.
Admins should be able to embed the chat widget as an inline iframe within a designated section of a webpage, rather than being limited to a floating widget placement.
A floating widget doesn't fit every page design. Inline embedding gives teams full control over how and where chat appears, enabling tighter integration with the overall page layout.
Taylor Jennings
Merged in a post:
Embed the Chat AI directly into the page as an inline element instead of a floating pop-up widget
Taylor Jennings
The Chat AI currently appears as a floating pop-up widget overlaid on the page. Teams that want to integrate the chat experience into the page layout itself, such as within a hero section, a dedicated CTA area, or a custom sidebar, have no way to render it inline.
Requested behavior: Support an inline embed option for the Chat AI that renders it as a native page element, allowing it to be positioned and styled within the page layout without appearing as a floating widget.
Why it matters: Floating widgets are easy to ignore or dismiss. An inline chat embedded directly in the page is more visible, more intentional, and can be designed to match the surrounding content context, improving engagement for teams with strong design requirements.