Three updates to Chat Journeys and Scheduling Flows are live: bookings can be made with multiple assignees (i.e., double round-robin), the flow can skip questions it already has answers to, and Marketo and Salesforce nodes can sit on the same path.
1. Multi-Assignment and Double Round Robin
The Display Calendar node now takes a list of assignees instead of one, so double round robin and other multi-assignment patterns work the way they already do in Concierge, Handoff, and ChiliCal.
How It Works
Under 'Show Availability of', click 'Add' and pick Owner, Team, Team Member via Round Robin, or Individual. Repeat per assignee, and drag to reorder; the order determines who becomes Assignee 1, 2, or 3. Required groups narrow the times shown; optional ones just join the invite.
What You Can Do Now
- Put an AE and an SE on one booking, with both calendars cross-checked, so there's no follow-up email to find a time
- Route to the Account Owner and round-robin a specialist alongside them
- Add a manager or note-taker as Optional, so they join the invite without narrowing availability
Learn more in our Support Article.
2. Use What We Already Know About a Visitor
A 'Send Data Field' node can now skip a field when we already hold a value, and dynamic tags resolve from any source.
How It Works
Every Data Field row in the node has a new Visibility setting:
- Default- skips when the value came from Enrichment, a Smart Parameter, or the JS Lead Object
- Skip if known- skips when we hold it from any source, including a previous visit or another Flow
- Always ask- shows the field every time
Existing fields start on Default, so nothing changes in a live Flow until you pick something else. If every field in the node is skipped, the node is skipped entirely and the visitor goes straight to the next one.
What You Can Do Now
- Recognize a returning visitor and skip straight past questions they already answered
- Greet someone by first name or company name using a value from enrichment, or in-app from the lead object, since dynamic tags in guest-facing messages now resolve from any source, not just Smart Parameters
- Pass values collected by other tools in the browser into the JS snippet and use them the same way
Still to Come
Chat Logs will show what was collected, how it was collected, and whether it was mapped to a Smart Parameter, similar to the recent Concierge update.
Learn more in our Support Article.
3. Marketo and Salesforce Nodes on the Same Path
What's Changed and Why
We previously blocked the two from co-existing because there was no mechanism to handle the delay between Marketo creating a lead and us matching it in Salesforce. Two new node options handle that now.
- SFDC Update or Create Record node has a new Retry matching to lead or contact option. Instead of creating a record, Chili Piper waits and matches the newly created Lead via the Marketo-to-Salesforce sync, as Concierge does today. Add the SFDC node after Marketo, and the option comes pre-selected
- Routing Rule node has a new 'Wait for CRM updates' before this rule runs toggle. It holds the journey until an earlier CRM update finishes saving, so the rule evaluates against the latest record
Learn more in the 'Using Marketo and Salesforce on the same path' section of our Support Article.
Happy building! ๐ถ๏ธ