Configure Web Widget engagement

Collect contact details

Enable Contact Details to ask visitors for selected profile information. Choose which of name, email, and phone are shown, which are required, whether the visitor can skip, and what happens after a skip.

Choose the contact requirement carefully. The setting determines which combination of details is enough to continue. Submitted details update the contact profile according to the configured rules.

Add suggestions per page

Each rule has a path pattern and one suggestion per line. Supported patterns include:

• * for every page;
• /orders for one exact path;
• /orders/* for child paths;
• */pricing for a path ending in that segment;
• */pricing/* for children below that segment anywhere.

Matching ignores the domain, query string, and page fragment. Add optional translations to a rule after its default suggestions exist. Duplicate text from overlapping rules appears once.

Add proactive triggers

Use Proactive Triggers to send a configured widget message when visitor behavior matches a rule. Define the audience condition, timing, page pattern, message, and language variants shown in the editor. Test the behavior in a safe preview before relying on it on a live site.

Use page context

• Section Awareness lets the website mark its current section with data-doublewire-section so the assistant receives useful location context.
• Text Highlight lets a visitor select page text and ask about that selection.

These controls decide whether the widget may send that context. The website must still provide the matching markup or interaction.