Distro:

🚀 CRM Matching Nodes

The purpose of CRM Matching Nodes is to make it easier to specify and visualize when matching takes place in Flow Builder. It also improves the experience in Distro Logs, where we show the matched Object ID and a link to it in SFDC, i.e., the matched account via L2A.

The new CRM Matching Nodes can be placed after the trigger, entry rule, or Duplicate match rules. This makes it clearer for admins what is happening with matching in the flow builder. Currently, matching happens in the rules themselves in combination with the matching hub. 

For example, you can add a CRM Matching node, select the Lead to Account matching in the Matching list, and then enable it as true. You can then combine your rules in combination with the match to add more control and ensure that the owner is in a specific team (designated in the rules)

How to convert an existing matching routing rule to a new CRM Matching node.

🚀 Toggle to Enable or Disable Prospect2Lead and Prospect2Contact matchings

🚀 Meeting Type Descriptions on Personal Pages

This allows you to also add more details to the meeting you add to your Personal Pages

Handoff: 

🚀 Updated 'Not Booked' Slack Notification

[Prospect name] from [Company name] has filled out a form but didn’t book a meeting and were assigned to you through [Concierge Router name]. 

'View in CRM button'

Chat:

🚀 Count Down Timer When Rep Joins

Reps can now see how long they have to respond to a Chat in their inbox. If there is a timer in the Wait for Rep Node, Chat reps can now see how much time they have to respond visually. 

This visually provides urgency to ensure they respond so the chat stays in their name.