Creating an Offer Flow

An Offer Flow presents a card on your website that offers a piece of value – a report, an ebook, a community invitation – in exchange for the visitor's email. It is one of the Web Experience Flow types – see Creating a Web Experience Flow for how Flows are built, triggered, and previewed. This article covers what is specific to Offer.

Table of Contents

• Before you begin
• Building the Flow
• The Show Offer Widget node
• What happens when an email is submitted
• Handling the Dismissed path
• How it appears to the visitor
• How Offer interacts with other Experiences
• Limitations

Before you begin

You need:

• The Chili Piper install snippet on the pages where the offer should appear;
• The thing you are offering – for example a link to a report to download, or a community to join;
• Familiarity with the Flow Builder. The Trigger, the frequency limits, previewing, and publishing are the same across all Web Experience Flows and are covered in Creating a Web Experience Flow.

Building the Flow

Create the Flow from Flows → Web Experience → Create New Flow → Offer, then build the path. An Offer Flow opens with the Show Offer Widget node.

The Show Offer Widget node

This is the first node after the Trigger. It presents the offer card.

Content:

• Headline – for example, "Check out our 2026 Benchmark Report";
• Body – optional supporting text;
• Pre-populate email when known – when enabled, fills the email field for a visitor whose email is already known;
• Call to Action – the button label, for example "Download".

Asset delivery:

• Asset URL – where the visitor is sent after submitting their email: the report, download, or community you are offering.

Styling:

• Position – Center or Bottom corner. For a bottom-corner offer, also set the Launcher Position (left or right) and the side and bottom spacing;
• Background, headline, body, and call-to-action colors, to match your site.

The node branches on how the visitor responds:

• Email Submitted – the visitor enters an email and clicks the call-to-action;
• Dismissed – the visitor closes the card without engaging. See Handling the Dismissed path.

What happens when an email is submitted

On the Email Submitted branch, you have the visitor's email, so continue the path with follow-up nodes:

• Update or Create Record – write the visitor to the CRM. Chili Piper updates a matched Contact or Lead, or creates a new Contact;
• Add any further nodes, such as adding the record to a campaign or sending a Slack notification.

The offer itself is delivered by the Asset URL you set in the Show Offer Widget node, so you do not need a separate node to deliver it.

The shared nodes are described in Creating a Chat Journey.

Handling the Dismissed path

On the Dismissed path the visitor closed the card without giving an email. What you can do depends on whether you already know who they are:

• If the visitor is de-anonymized or their email is already known, you can act – for example, send a Slack notification that someone from a named company is on the page, or add the record to a campaign;
• If the visitor is not identified, there is little to act on.

How it appears to the visitor

The Offer Experience appears as a card, either centered on the page or docked in a bottom corner, depending on the Position you set. The visitor sees the headline and call-to-action, enters an email, and receives the offer.

Note: For a centered offer, the visitor closes the card with the X button only – clicking outside it does not dismiss it. A bottom-corner offer sits to one side with no dimmed background, so this does not apply.

How Offer interacts with other Experiences

More than one Web Experience can run on the same page. Two rules matter for Offer:

• When a visitor is eligible for both a Scheduling and an Offer Experience, the Scheduling Experience is shown – Scheduling takes precedence over Offer;
• When a visitor is actively using Chat, the Offer Experience does not appear.

The full set of rules is in Creating a Web Experience Flow.

Viewing logs

Each time an Offer Flow runs for a visitor, it is recorded in Logs, alongside your Chat logs – including whether the visitor submitted an email or dismissed.

Limitations

• On the Dismissed path, follow-up depends on the visitor being identified (de-anonymized or a known email).