Deploying Rapidflare
Web
You can put the Rapidflare agent on your website in six ways. Each one is a different look and a different way for a visitor to start a conversation. Pick the one that fits your pages, open its page for the details, and use the same one script from our CDN for all of them except the whitelabel domain.
Pick a widget
A round chat button in the corner of every page. Visitors click it and the agent opens as a popup. Nothing to add to your pages.
Your own button, menu item or link opens the agent in a side modal, a centered modal or a drawer that pushes the page.
A search box on your page. A visitor types a question, presses Enter, and the agent opens in a panel on the same page, or on a page you host.
The agent shown inside a page you own, such as a help center or an Ask page. Also where a search or an AI overview continues.
A short AI answer on your page with a button that carries the conversation to a page you host.
Your agent on your own domain, like ask.yourcompany.com. Rapidflare hosts it, so there is nothing to install. Share the link or show it inside a page.
Two widgets hand visitors to a page of yours
The Search Bar (with its "Your own page" look) and the AI Overview button both open a second page on your site. That page has to run the Full Page widget. Plan for it first: set up the Full Page, then copy its web address into the other widget. How the hand-off works.
Which one should I use?
| I want | Use | What visitors see |
|---|---|---|
| Help on every page with no work on my pages | Floating Launcher | A chat bubble in a corner. |
| My own button or menu item to open the agent | Inline Trigger | A panel slides in, or a dialog opens. |
| A search box that answers questions | Search Bar | A search box. After they press Enter, a panel opens on the page. |
| A page that is the agent | Full Page | The agent inside your page layout. |
| A short answer in the middle of a page | AI Overview | An answer card with a button to keep chatting. |
| A link or iframe to the agent, with no script on my pages | Whitelabel domain | The agent on your own address. |
| Wix or WordPress | Website builders | Any of the above, with steps for your platform. |
Slack and Discord are separate: see Slack and Discord.
Combine widgets
Widgets work together. You load the script once and call init() once for each widget. These are the combinations customers ask for most.
| Goal | What you set up | How many widgets |
|---|---|---|
| A search bar on every page that opens a side panel | A Search Bar. It opens the panel for you. Choose a modal or a drawer, left or right, or a floating panel. | 1 in your code. The panel is created for you. |
| A search bar that opens a full page of chat | A Search Bar on every page, set to send people to your Ask page, and a Full Page widget on that Ask page. | 2, in two places. |
| A short answer on a page that continues in full chat | An AI Overview on the page, and a Full Page widget on the page its button opens. | 2, in two places. |
The page that continues a conversation is the same Full Page widget in every case. Continue on a page you host explains how the hand-off works.
Using the Embed SDK
The Rapidflare Embed SDK is one script from our CDN. It is lightweight and does not change your page styles. Floating Launcher, Inline Trigger, Search Bar, Full Page and AI Overview all use it. You pick the look with display.type in a single rapidflare.init() call.
- Create a publishable API key in the dashboard under Hubs » Configure » Security. It is safe to put in your page. See API keys.
- Add the script. If your website builder does not let you edit your page head, use its site-wide code option. See Website builders.
- For Search Bar, Full Page and AI Overview, add an empty box on the page for the widget. Floating Launcher and Inline Trigger need no box.
- Call
init()once for each widget. Every mode page has the code to copy.
Every widget page has plain steps to copy and paste, a picture of each option, and a section at the end for developers with every setting. Cookie and tracking behavior is in Consent and analytics. Keys, allowed domains and Content Security Policy are in Security.