Add a configurable delay before routing fires | Voters

Add a configurable delay before routing fires

Taylor Jennings

The customer is looking for a feature to introduce a time lag in the routing process, allowing for data enrichment before assigning leads to sales representatives.

March 4, 2026

Taylor Jennings

Merged in a post:

Configure a delay before routing logic fires to allow enrichment or scoring to complete first

Stephanie Domachi

Routing executes immediately when a trigger fires. When upstream processes like data enrichment, lead scoring, or CRM field updates run asynchronously, routing fires before the data it depends on is available, producing incorrect assignments that then require manual correction.
Allow admins to configure a time delay at any point in a routing flow, so routing waits a defined number of seconds or minutes before executing logic. This gives asynchronous upstream processes time to complete and ensures routing decisions are based on fully enriched data.
Routing on stale or incomplete data is a silent accuracy problem. Teams currently work around it with external orchestration layers, which adds fragility and complexity. A native delay step eliminates the dependency on external tooling and makes routing more reliable for orgs that enrich leads before assignment.

March 25, 2026

Taylor Jennings

Merged in a post:

Add a configurable Delay to allow for ownership sync

Taylor Jennings

When a record is routed and ownership is updated in Salesforce, there's a sync delay before Outreach reflects the new owner. If an Outreach sequence step fires during that window, the email goes out from the previous owner rather than the newly assigned rep.
Requested behavior: Allow a configurable delay to be added between a routing event and the next Outreach sequence step, giving the Salesforce-to-Outreach ownership sync enough time to complete before any outreach fires.
Why it matters: Emails sent from the wrong rep confuse buyers and create a poor first impression from the newly assigned owner. A simple delay step prevents the race condition between CRM sync and sequence execution.

March 24, 2026

Dylan Harp

Context: We utilize a custom implementation where a third-party form creates leads in Salesforce via API. We have strictly disabled Chili Piper's permission to create new leads to prevent duplicates/conflicts.
Problem: A race condition exists between the form tool's API call and Chili Piper's execution.
Prospect submits form.
Chili Piper Concierge triggers immediately and attempts to write booking data to Salesforce.
Chili Piper searches for the lead email but returns null because the form tool is still processing the creation request.
Chili Piper fails to update the lead (as it does not exist yet) and fails to create a new one (due to our restricted settings).
Proposed Solution: Introduce a configurable Time Delay Action in the Concierge/Router flow.
Functionality: Allow the admin to set a delay (e.g., 30s, 1m) before Chili Piper executes the Salesforce lookup/update.
Benefit: This ensures the Salesforce Record ID exists before Chili Piper attempts to write to it, supporting clients with complex or slower third-party form integrations.

Mary Harling

We have meetings that are created with no name and the cc email without a link to the Prospect in HubSpot. Chili Piper's suggestion was to let Chili Piper create the contact, but we are unable to do so since we use the HubSpot tracking pixel and contacts are created upon FormSubmit (we cannot change this for a variety of reasons). This only seems to be an issue if the prospect books immediately when presented with the scheduler. If we could configure a delay of just a few seconds, I think this issue could be solved.