Overview

Add Voiceflow’s floating chat widget to HubSpot-hosted website and landing pages so visitors can ask your AI agent about your products, policies or services. This guide uses domain-specific Site Footer HTML in HubSpot CMS.

Installing HubSpot’s tracking code on an externally hosted site does not install Voiceflow there. Follow that website platform’s installation guide instead.

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; CRM actions use the separate HubSpot integration.

Before you begin

Prepare the agent and choose the HubSpot-hosted domain to change.

In Voiceflow, open Widget → Modality & interface. Set Modality to Chat and Chat interface to Widget, then publish. Review test and production hosts if the project restricts widget domains.

Send the complete snippet and test question to your domain administrator if they manage setup. Keep personal and service API keys out of browser code.

Install the widget

Add one installation to the intended domain’s footer.

1

Copy the generated snippet

In Agent studio, open Widget → Installation and copy the complete snippet, including its script tags. Preserve its generated authorization, runtime and environment settings.

2

Choose the domain and footer

In HubSpot Settings → Content → Pages, use Choose a domain to edit its settings to select the intended domain. Open Site Footer HTML.

If the domain inherits defaults, use Override default settings and retain any required inherited footer snippets alongside Voiceflow. An override stops that domain from inheriting the default footer. Avoid Default settings for all domains when you intend one domain only.

Domain-level code can also affect quotes hosted on that domain. Review the scope and existing footer code before saving.

3

Save and check the live page

Paste the Voiceflow snippet after existing code and choose Save. Domain settings apply to hosted content; this is not an unpublished page edit waiting for a later Publish action.

Open a published page on that domain in a private window. One launcher should appear and open. Continue with the visitor test.

HubSpot’s code-snippet guide covers these controls. Use one installation; do not also paste the same snippet into page settings or a template.

Configure appearance and placement

Keep widget settings separate from domain and page scope.

Choose the launcher, colors and icon in Voiceflow’s Widget panel, then publish the changes. Replace the saved installation code if its generated project or release details change.

For selected website or landing pages instead of a whole domain:

  1. Keep the widget out of the domain footer. Open the chosen page from Content → Website Pages or Landing Pages.
  2. Open Settings → Advanced → Additional code snippets and paste it into Footer HTML.
  3. Choose Publish or Update, then test that page and an excluded page.

This page-level Footer field is not offered for blog posts or knowledge-base articles. Do not assume a page’s setting replaces a domain-wide installation.

Conversation retention follows the widget persistence settings. A HubSpot contact cookie, membership login or browser-provided ID does not authorize the agent to read CRM records. Protected actions need backend authorization through the appropriate integration.

Test a visitor conversation

Verify the installed widget on the intended hosted page.

1

Open the published test URL

Use a private window on the chosen HubSpot-hosted domain. Confirm that one Voiceflow launcher appears and opens. If another chat service is present, check that visitors can identify and use the intended support entry point.

2

Ask a question and follow-up

Ask a prepared question, such as “Which support services do you offer?” Then ask “How do I contact the team?” Both replies should match your agent’s Knowledge.

3

Check the project and scope

Find the exchange in Transcripts to confirm the intended project. Visit a second page and reload to check retention and duplicates. For scoped placement, verify an excluded page or domain too. Repeat with relevant consent choices if the site uses consent controls.

Check permission, subscription and content type.

Ask the administrator to check Website settings access for domain changes, or Edit/Publish access for page changes. Confirm that the chosen content offers footer HTML; a blog post or knowledge-base article does not have the same page-level field.

The widget is missing

Check the domain, saved installation and browser requests.

Confirm the URL belongs to the domain you edited and inspect its source for the snippet. Check inherited versus overridden footer settings. If the code is present, inspect Console and Network for a blocked cdn.voiceflow.com request or initialization error. Review domain and consent restrictions with the project owner.

The widget appears twice

Check domain, page and template installations.

Keep one Voiceflow installation per page. Remove duplicate snippets from page settings, templates or tag managers, keeping unrelated code. If two different support widgets appear, review their placement with the site owner.

The answer is wrong or missing

Verify the installed project and published agent.

Compare the saved snippet with the Voiceflow project’s generated code. Check that the intended release is published, then retry with a fresh conversation. Correct missing service information in Knowledge or instructions.

Release to the intended domain

Apply the reviewed scope without changing unrelated footer code.

  1. Have the Voiceflow owner publish the reviewed agent and widget settings.
  2. Apply the reviewed snippet to the production domain’s footer and save. For a page-level installation, publish or update the chosen page instead.
  3. Repeat the visitor test on the production URL and check the intended scope.

Update or remove the widget

Maintain the installation and domain inheritance.

Publish agent and appearance changes in Voiceflow. Replace the saved widget snippet when its generated installation settings change.

To remove it, delete only Voiceflow’s snippet and save the domain settings, or update the affected page. Keep unrelated code. Do not use Apply default settings merely to remove Voiceflow: that changes the domain’s footer inheritance too. Check the public page in a fresh window afterward.

Custom interface guides

Planned HubSpot CMS walkthroughs for your own conversation UI.

Custom chat and voice walkthroughs are coming soon, separately from this widget guide.

Use the up and down arrow keys to select a result, Enter to open it, and Escape to close the search.