Have the option to add a delay in creating a lead in Salesforce when a prospect books a meeting.
We have more that one automation firing (from other systems) at the point a new lead gets created. This can sometimes cause duplicate records to get created in Salesforce. I would like the option to add a delay (wait 5 minutes for example) to the creation of a new lead at the point the prospect books a meeting. So that if the lead has already been created in Salesforce, chili will simply update the booking fields for the existing lead rather than creating the lead instantly.
Stephanie Domachi
shared this idea
-
Dylan Harp commented
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
commented
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.