How do I set up Post-Form Enrichment in Concierge?

Post-Form Enrichment runs after a prospect submits their details. Chili Piper uses the submitted data to pull additional fields from your enrichment provider – LeadIQ, Apollo, Lusha, or ZoomInfo – and those enriched fields are then used by your routing rules and written into the booked meeting. This article covers how to set it up and how it behaves across every way Concierge can be triggered.

---

Table of Contents

• When to Use Post-Form Enrichment
• How It Differs from Enrichment for Form Shortening
• Requirements
• How to Set Up Post-Form Enrichment
• How It Works Across Concierge Triggers
• Verifying Enrichment in Concierge Logs
• Limitations
• Writing Enriched Fields Back to Your CRM

---

When to Use Post-Form Enrichment

Post-Form Enrichment is the right choice when you want Chili Piper to do more work with less prospect input. Common scenarios:

• Your form asks for email only, and your routing rules depend on firmographic data such as Country, Company Size, or Industry;
• You are routing through Concierge programmatically (via the Edge API or MCP) from a partner integration, AI voice agent, chatbot, or custom app, and want enrichment applied automatically without that upstream system integrating with an enrichment provider directly;
• You want the booked meeting record to carry enriched fields (Company Name, Title, Revenue, etc.) into your CRM notifications, calendar invites, and downstream automations.

Post-Form Enrichment combined with programmatic Concierge scheduling covers a common pattern: a partner or agent collects an email address, hands off to Concierge via the Edge API, and Chili Piper handles enrichment, routing, assignment, and booking in a single routing + scheduling call pair.

---

How It Differs from Enrichment for Form Shortening

Chili Piper offers two forms of enrichment in Concierge. They solve different problems and can be used together on the same router.

	Enrichment for Form Shortening	Post-Form Enrichment
When it runs	Before the form renders to the prospect	After the prospect submits
Primary goal	Reduce visible form fields to improve conversion	Populate data used by routing rules and carried into the meeting record
Form type support	HTML, Marketo, Pardot, HubSpot	All Concierge trigger surfaces – including Router Link and programmatic (Edge API, MCP)
Visible to the prospect	Hides fields that are successfully enriched	Runs in the background with no effect on the form UI

For the pre-form version, see Enrichment for Form Shortening.

---

Requirements

Post-Form Enrichment uses the same providers as Enrichment for Form Shortening. A paid plan with one of the following is required:

• LeadIQ Enterprise;
• Apollo Basic or higher;
• Lusha – any plan, including free;
• ZoomInfo Copilot – any tier, with API SKU enabled.

Authentication is handled through the Integrations page, or directly from the enrichment setup while building a waterfall. LeadIQ, Lusha, and ZoomInfo use an API key; Apollo uses OAuth.

---

How to Set Up Post-Form Enrichment

1. Add the Enrich Node

In the router's Flow Builder, click the + below the Trigger and choose Enrich under the Tools category. Placed here, enrichment runs before any routing rules evaluate.

2. Select Data Fields to Enrich

Open the Enrich node. The right panel shows Enrich your Data Fields with two columns: Data Fields and Enrichment.

1. Click Add Data Field to Enrich;
2. In the Data Fields column, pick the data field to enrich (for example, Country);
3. In the Enrichment column, pick or create the Enrichment Waterfall that will enrich it.

3. Build the Enrichment Waterfall

A waterfall is an ordered sequence of providers. Chili Piper tries each in turn and stops as soon as one returns a value.

In the Enrichment column, use the dropdown to pick an existing waterfall or click + Create New Waterfall. In the waterfall editor:

1. Give the waterfall a name (for example, Person Country);
2. Add providers in fallback order by clicking + Add Enrichment Data Source. Each entry points to a specific provider and the path to the field within that provider's schema (for example, Apollo > Person > Country);
3. Reorder the sequence by dragging the handle on the left of each row;
4. Click Apply to save the waterfall. Apply as a template if you want to reuse it across routers.

Providers that show NOT CONNECTED in the list will not run until connected – see the next step.

4. Connect a Provider

To connect a provider directly from the waterfall editor, click Connect next to the provider's row. Chili Piper opens a connection modal: LeadIQ, Lusha, and ZoomInfo require an API key, Apollo uses OAuth.

Alternatively, providers can be connected up-front from the Integrations page. Connections are shared across waterfalls, so a provider only needs to be connected once per workspace.

5. Set the Enrichment Timeout (Optional)

The Enrichment Timeout controls how long Chili Piper waits for provider responses before continuing. If data arrives after the timeout, it is not considered for routing.

In the Enrich node's right panel, click the gear icon next to the Enrichment column header.

Set Wait time (in seconds) and click Save.

6. Publish the Router

Use the Publish control in the top-right of the Flow Builder to apply the configuration. If the router was already live, publishing updates the existing snippet and the Edge API behaviour on the next routing request.

---

How It Works Across Concierge Triggers

Post-Form Enrichment runs on every Concierge trigger. The submitted data (even just an email) is handed to the enrichment waterfall, enriched fields are merged into the routing input, and routing rules evaluate against the combined data.

Triggers

Concierge has three trigger types, all of which support Post-Form Enrichment. These appear in the router's Trigger node in the Flow Builder:

Trigger	Description
Router Link	A booking link is clicked or a Router Link form is submitted
Third-party Form	An HTML, Marketo, Pardot, or HubSpot form is submitted and the Concierge JavaScript embed intercepts it
In-app Button	A Concierge-configured button is clicked inside a supported app context

Invoking a trigger from the UI or programmatically

A trigger can be fired two ways:

• From the UI – a prospect clicks a Router Link, submits a form that the Concierge embed is watching, or clicks an in-app button;
• Programmatically via the Edge API or MCP – a partner system, AI agent, or custom app calls Chili Piper directly and passes the trigger type in the request body.

The Edge API endpoint is POST /api/fire-edge/api/v1/org/concierge/routers/{slug}/rest. MCP clients call concierge-route-by-slug or concierge-route. Both carry an options.trigger field that tells Concierge which of the three trigger types to treat the request as. Enrichment runs the same way in either invocation path.

For the Edge API and MCP paths, a second call (/routing/{routingId}/schedule-simple or concierge-schedule) books the meeting using one of the start times returned by routing. The booked meeting record carries the enriched fields in its guest data.

---

Verifying Enrichment in Concierge Logs

Concierge Logs show, for every routing event, which data fields were enriched and which provider returned the value.

Router Link example

A Router Link click with only email supplied. Company Name was enriched by Apollo and used to match the routing path. The prospect was assigned and a meeting scheduled.

Third-party Form example

A form submission from an HTML embed. The log shows the data-source column side by side: Email was submitted by the prospect, Company Name was enriched by ZoomInfo.

What to look for

• Form field name and the Chili Piper data field it mapped to;
• Captured data – the value used by routing;
• Data source – either Submitted by Prospect or the provider badge (ZoomInfo, Apollo, LeadIQ, Lusha);
• Matched routing path – confirms routing rules evaluated against the enriched fields.

---

Limitations

• Enrichment availability depends on the provider returning data for the prospect. If no provider returns a value, the field is left empty and routing rules that depend on it will not match;
• If the Enrichment Timeout elapses before providers respond, routing proceeds with the data available at that point;
• Per-IP testing rate limit: five form submissions per ten minutes per IP address. If more test volume is needed, use different IPs, a VPN, or spread submissions across a longer window;
• Enrichment providers generally return best results when first name, last name, company name or domain, email, or LinkedIn URL are supplied. Email alone is sufficient to match a person in most providers, but passing more fields improves accuracy.

---

Writing Enriched Fields Back to Your CRM

Enriched fields are used by routing rules and written into the booked meeting record automatically. To persist them to your CRM (Salesforce or HubSpot), two things need to be in place:

1. The Chili Piper data field is mapped to the CRM field in Admin Center > Data Fields. See Setting up Data Fields § Mapping to CRM;
2. An Update or Create Record node (under the Action category in the Flow Builder) is present on the path the prospect takes. The node can sit immediately after the Enrich node (always run), on the Scheduled branch (only run if a meeting is booked), or on the Not Scheduled branch (only run if no meeting is booked). Place it according to when you want the CRM write to happen.

If the data field is not mapped to a CRM field, or if no Update or Create Record node sits on the prospect's path, the enriched value remains on the meeting record but is not written to the CRM.

Overwriting existing CRM values

By default, enrichment writes to a CRM field only when that field is empty. To allow enrichment to overwrite a value that already exists on the record, enable "Override" on that data field in Admin Center > Data Fields. For empty fields, Override is not required.

---

Related Articles

• Enrichment for Form Shortening – the pre-form counterpart;
• Setting up Data Fields – create data fields and map them to CRM fields;
• How do I Schedule Chili Piper Meetings Programmatically? – the Edge API route → schedule pattern for partner systems, AI agents, and custom apps.

---