February 17th, 2025 Releases

We can only have one listing in Hubspot, so Legacy has been removed, and we just have our new DCP listing!

Show the first results of the characters typed at the beginning of the word instead of all accounts with those characters.

We combine the current experience of Meeting Created in and Always Invite into one.

When adding a participant, the user can pick "booker" or "Assignee"

We create the meeting in the Host’s calendar.

If the Booker/attendee is set to be optional, their availability is NOT displayed in the scheduler when booking the meeting. So if the booker is optional, when booking the meeting they do not see their own calendar.

Show Bookers when someone they are booking a meeting for has hit the lost booking limit. This way, they know they should not be receiving any more meetings.

Get notified via Slack when you get a call from Concierge Live.

We now parse standard UTM parameters from the URL. There is no need to use hidden fields on your router or web forms. To update the CRM, make sure the standard UTM Data Field is mapped to the CRM field. The first instance of capturing a UTM value is the original. Once populated, we only write to Recent. Recent can be overwritten, but the Original cannot.

Using Command + f you can search for the node you are looking for in your Chat Journey

Instead of updating fields with static values, you can update them with variables or information that can change based on the trigger object.

For example, you have set up lead-to-account matching, and you want to add the name of the account the lead matched to on the lead as a variable. To do this you add the field update node in your router, instead of just making a static update like a written word you have the option to add a triggered object variable - depending on your trigger you can use the information from the trigger (lead in this example) and reuse it. Then, in this example, you can add the matched account ID (which is variable, not static) as an update to that field.

Other examples:

Let's say you want to send an Email or a Slack Notification and you want to use some variables to create the body of the message.Something like:

Hey {Distro.Assignee},

You just received a Lead: {Lead.First Name} {Lead.Last Name} working for {lead.company}.Matched Account: {Lead.MatchedAccount.Name}

Segment: {Lead.Segment}...Another use case would be to use variables with information coming from the Router itself: