Overview
Add Voiceflow’s floating chat widget to your Framer site so visitors can ask your AI agent about your products, policies or services. This guide adds the generated widget snippet to Custom Code and tests it on a published site.
Building your own interface? Custom chat and voice walkthroughs are coming soon. Start with Chat agents or Voice agents for the APIs.
New to Voiceflow? Build a support agent, add your help content to Knowledge and publish it first. This installation provides public support; it does not authenticate visitors or connect customer records.
Before you begin
Prepare the agent, project access and a published test destination.
In Voiceflow, open Widget → Modality & interface. Set Modality to Chat and Chat interface to Widget, then publish. If the agent restricts widget domains, have its owner review your test and production hosts.
Read Framer’s staging behavior before publishing. By default, the base and custom domains use the same latest version; the base domain becomes an isolated review target only when staging is enabled. For that setup, open Staging & Versions → Enable Staging. Coordinate with the project owner if staging is unavailable.
If someone else manages the website, send them the complete snippet and test question, then ask for the published test URL. Keep personal and service API keys out of browser code.
Install the widget
Run the generated snippet once across the site.
Copy the installation snippet
In Agent studio, open Widget → Installation and copy the complete snippet, including its script tags. Keep its generated authorization, runtime and environment settings unchanged.
Add a Framer script
Open Project Settings → Custom Code. Choose Add Script, or the + control if scripts already exist. Name it Voiceflow widget and paste the full snippet.
Save the script. Use this as the only Voiceflow installation; remove a duplicate installed by an Embed element, plugin or tag manager.
Publish for testing
Use Publish to publish the update to your chosen test destination. Open that URL in a browser; the launcher should appear and open. Continue with the visitor test.
Framer’s canvas preview does not run settings-based custom code. Publishing without staging enabled can update the production site too.
See Framer’s custom-code setup and preview limitations for the supported controls.
Configure appearance and sessions
Keep site navigation from initializing another widget.
In Voiceflow’s Widget settings, choose your launcher, colors and icon, then publish the changes. Replace the Framer snippet if the generated installation details change.
Keep Run → Once for this site-wide installation. For selected-page visibility, work with the site developer and test navigation into and out of those pages. Selecting where the script first runs does not define when an already-loaded widget should disappear.
This is a guest-support conversation. A browser-provided user ID does not authenticate a visitor; protected account actions need backend authorization.
Test a visitor conversation
Verify the widget through the published site, outside the canvas preview.
Open the published test URL
Use a private browser window. Confirm that one launcher appears and opens. If staging is enabled, check that you are viewing the reviewed staged version rather than the production domain’s older version.
Ask a question and follow-up
Ask a prepared question, such as “What is included in your service?” Then ask “How do I book it?” Both replies should match the help content in your agent’s Knowledge.
Check the project and navigation
Find the exchange in Transcripts to confirm the intended project. Follow a link to another page, send another message and reload. Check retention, duplicate launchers and any page-visibility rules. Repeat with relevant consent choices if your site uses consent controls.
The widget is missing in preview
Use the published URL to test Custom Code.
The canvas preview omits settings-based custom code. Open the published test URL. If the widget is also absent there, check that the script is saved, enabled and included in the version you published. Have the project owner check Custom Code availability if Framer blocks publication.
The launcher does not appear
Check the saved script and browser requests.
Check the script’s pages and placement. Inspect Console and Network for a blocked cdn.voiceflow.com request or initialization error. Review domain restrictions and consent rules with the project and site owners. Keep the complete generated loader rather than splitting its download and initialization into separate Framer scripts.
Navigation duplicates the widget
Set the site-wide script to Once, remove duplicate Voiceflow embeds or plugin installations, save and republish. Open a fresh window and repeat the page-link test.
The answer is wrong or missing
Verify the installed project and published agent.
Compare the saved snippet with the project owner’s generated installation code. Check that the intended release is published and retry with a fresh conversation. Correct missing service information in Knowledge or instructions.
Release the reviewed version
Deploy the website code separately from the Voiceflow agent.
- Have the Voiceflow owner publish the reviewed agent and widget settings.
- With staging enabled, ask the publishing owner to select the tested version in Staging & Versions and choose Deploy. Without staging, review the pending changes and publish the update directly.
- Repeat the visitor test on the production domain.
Framer’s publishing permissions distinguish staging publication from production deployment.
Update or remove the widget
Maintain the script and published version.
Publish agent and appearance changes in Voiceflow. Replace the Framer snippet when its generated installation settings change, then publish and deploy the reviewed website version.
To remove the widget, delete its Custom Code entry and release that change to production. Open a fresh visitor window and check that the launcher is gone. Keep unrelated scripts intact.
Custom interface guides
Planned Framer walkthroughs for your own conversation UI.
Custom chat and voice walkthroughs are coming soon, separately from this widget guide.