Overview
Your Lexidesk widget is where someone visiting your firm's website actually talks to your AI intake agent. When you install it, you choose one of two formats: a website widget that floats in the corner of every page, or a website iframe that sits embedded inside a page. Same agent, same settings, same conversations. The only difference is where it lives on the page.
This article helps you decide. Once you know which one you want, How to set up and install your Lexidesk chat widget walks you through every setting and shows you where to copy your code.
The two formats at a glance
Format | What visitors see | Best for |
Website widget | A launcher button in the bottom corner of every page. Click to open. | Adding AI intake to an existing site without changing the layout. |
Website iframe | A full chat box embedded directly into a page section. | Replacing a contact form, or building a dedicated intake page. |
If you're unsure, most firms start with the website widget on every page, then later add an iframe on the pages where intake matters most. There's no extra cost for using both.
Option 1: Website widget (floating launcher)
The classic launcher that sits in the bottom corner of every page. Visitors see a small button, or your avatar if you've set one up. When they click it, the chat opens in a panel on top of your existing site.
Best for:
Firms that want to add AI intake without redesigning anything
Giving every page of the site a 24/7 intake option
Sites where the homepage and layout are already working
Not ideal for:
Replacing a contact form (the floating widget sits on top of the page, it doesn't replace anything)
Pages where you want the chat to be the main thing visitors see
How to install: in your agent's Chat widget settings, click Deploy, choose Website widget, and copy the snippet. Your web person pastes it once into your site template, just before the closing </body> tag. After that, the launcher appears on every page automatically.
Tip: you can also open the floating widget from any button or link on your site. For example, a "Contact us" link in your menu can open the chat directly instead of going to a contact page. Email [email protected] for the runtime event snippet.
Option 2: Website iframe (embedded chat box)
A full-size chat box embedded directly into a section of your page. Unlike the floating widget, this one is part of the page itself. Visitors see it inline as they scroll, and they can start chatting without clicking anything to "open" it.
Best for:
Replacing your contact form with something that actually qualifies and converts
A dedicated "Talk to a lawyer" page or landing page
Practice area pages where high-intent visitors land (family law, immigration, personal injury, and so on)
Not ideal for:
Sites where you want chat available on every page (use the website widget for that instead, or combine both)
How to install: in Deploy, choose Website iframe and copy the code. Your web person drops it into the exact spot on the page where you want the chat to appear. It works inside any standard website builder (WordPress, Webflow, Squarespace, custom, and so on) and inside page builders like Elementor or Divi.
The widget fills the container you put it in, so you control the size by controlling the section it sits in.
How to choose
Quick decision guide:
You just want AI intake on your existing site without changing anything. Use the website widget.
You want to replace a tired contact form with something that actually qualifies and converts leads. Use the website iframe on your home and contact pages.
You want maximum coverage. Use the website widget across the whole site, plus an iframe on your highest-intent pages.
What stays the same either way
The format only decides where the chat sits. Everything else is shared:
The same agent and the same conversations. Both formats connect to one agent, and every conversation lands in the same place.
The same look and settings. Accent color, logo, header text, launcher style, greeting, welcome video, languages, and per-page overrides are all configured in your Lexidesk dashboard, not in the embed code.
No second install. Once the code is on your site, changes you save in your settings appear automatically without touching the website again.
See How to set up and install your Lexidesk chat widget for a walkthrough of every setting.
FAQs
Can I use both formats on the same site?
Yes. A common setup is the website widget on every page, plus an iframe on the homepage and key practice area pages. They don't conflict with each other, and there's no extra cost.
Will the widget slow down my website?
No. The widget loads asynchronously, which means it doesn't block your page from rendering. Visitors see your site at normal speed, and the widget appears once the page is ready.
Can I switch from one format to another later?
Yes. Switching just means swapping the code on your site for the other option in Deploy. Your AI agent, conversations, and configuration stay exactly the same.
What if my website is built on WordPress, Wix, Squarespace, or Webflow?
Both formats work on every major website platform. Look for a section called "Custom code," "Embed," or "HTML." Every platform names this differently, so search that platform's help docs for "add custom HTML" if you don't see it.
Where do I get the code?
From your dashboard, go to Agents, click Configure on your agent, open the Chat widget tab, and click Deploy at the top. Choose your format and click Copy.
Who actually installs it on my website?
Whoever maintains your site does the install. That's usually the marketing agency or freelancer who built it, or your in-house web person. The snippet is short, and the install takes about two minutes for someone who knows where the site's template files live. If you'd rather not send it yourself, click Email instructions in Deploy and Lexidesk sends the code and setup steps straight to your web developer.
Still stuck?
If your web person installed the snippet and the widget isn't showing up, email [email protected] with your firm name, the page URL, and a screenshot of where the widget should be. We'll look at the page directly and tell you what's missing.