Configuring Website RFQs

Set the domains, support email, deal pipeline and appearance that every flow published on your website uses.

This feature requires an Enterprise plan. Website RFQs is an Enterprise add-on that is not part of the Enterprise plan itself; Trial accounts include it. Until an admin adds it with Add to Plan, this settings page shows a locked state with the price and that button.

Overview

Settings → Guided Selling → Website RFQs holds the account-wide settings for every flow you publish on your own site: which domains may embed a flow, the email visitors see when something goes wrong, where new deals land, and how the embedded form looks. Per-flow settings (the questions and prefill parameters, response page copy, script tag, publishing and key rotation) live on each flow’s Website page instead; see Publishing a flow on your website.

The page is in Settings on every plan. Until the add-on is on it shows Add to Plan instead of the form, so this article does not include Studio screenshots.

Prerequisites

An Enterprise plan with the Website RFQs add-on
An Admin role in Quotivity Studio
The hostnames of the pages that will embed a flow

Adding the add-on

Open Settings → Guided Selling → Website RFQs (or any flow’s Website page, or the Flows list) and click Add to Plan. The dialog shows what is due today, prorated from today to your subscription’s renewal date, the full yearly price that then renews with your subscription, and the payment method on file. Confirm and Pay charges the prorated amount and turns the feature on for every admin in the account straight away. If your subscription has no payment method yet, you add one first. A trial account, or one whose subscription is not active, is pointed to Manage Account to activate the subscription first and can then add the add-on from the same page. Only account admins can add it.

The add-on includes 100 website-created quotes each month; Website quote packs add 25 more quotes per month each and are bought from Manage Account → Subscription. This page shows a notice when submissions are held or the allowance is nearly spent. See Website quote allowance and held submissions.

Settings

Allowed Domains — every hostname that will embed a flow, entered without https:// or a path and exactly as visitors see it, for example www.example.com and shop.example.com. Subdomains are not implied, so add each one. Your default quote domain and HubSpot (app.hubspot.com and app-eu1.hubspot.com) are pinned and always allowed. A page on any other domain shows “This form is not available” instead of the flow.
Support Email — shown to visitors when a submission cannot be completed, together with a reference number they can quote to you. Must be a valid email address.
Deal pipeline and Initial deal stage — where deals created from website submissions land, for every website flow. Changing the pipeline clears the stage. When unset, the default pipeline’s first stage is used.
Appearance — brand color and button text color (hex), font (inherit from your site, Lexend Deca, Inter or system), corner radius, card or transparent background, custom CSS scoped to the .qv-flow element, and whether to show Powered by Quotivity. Custom CSS accepts ordinary rules, @media, @supports, @container, @layer, @font-face and @keyframes; every selector is prefixed with .qv-flow, and anything that could reach the rest of your page is dropped: any other at-rule (for example @import or @scope), rules nested inside another rule, selectors that start with a sibling combinator (~, +), position: fixed, and any @keyframes name or @font-face family that does not start with qv- (so your CSS cannot redefine an animation or font the page itself uses). The flow also renders inside a contained box, so nothing you style can overlap the rest of the page. Your CSS can only ever style the flow. The live preview on the page shows one step with your current choices.
Changes save as you make them. Every published flow picks them up within a minute.

Tips

Keep the allowed list short. Each hostname is matched exactly, so staging and preview hosts need their own entries while you test, and can be removed once the flow is live.
The support email is visible to the public on failed submissions, so use a shared inbox rather than an individual’s address.
Appearance applies to every published flow. If one flow needs a different look, target it with custom CSS on the page that embeds it rather than changing the shared settings.
To remove the add-on, contact Quotivity. Removing it takes every published flow down immediately; the script tags can stay on your pages until you republish.
If you pay by bank debit, the add-on turns on once the payment clears (usually within a few business days); the page tells you when it is on.