Product Updates - December 1st, 2024

ChiliCal:

🚀 Order of Users in Scheduler

When adding another user to your meeting from the Scheduler or Home, we will display the current user first, then the last 4 picked users. This will make adding folks to meetings a little easier, especially if you are usually adding the same users.

🚀 New to Fire: Force Timezone in Meeting Type

In Legacy, under the Schedule section of a meeting type, when the option “Overwrite Host’s default timezone” is selected, the admin can decide which timezone to show and whether it should be displayed to prospects or not.

When toggled OFF, prospects see the times in the booking link in their own timezone.

🚀 Reassign Hover Over Details

Customers have mentioned the reassign button is hard to find, this update adds the reassign to show when you hover over the assignee section

Handoff:

🚀 New to Fire: Meeting Object in Rules

This allows us to support the Booked by parameter in rules. Admins can now build rules that specify who the booker needs to be. 

Use case: If the SDR Sam (or booker) Sam is using handoff only show connect to path A with the booker=sam rules. This allows for specificity based on who is booking the meeting.

Form Concierge:

🚀 Timer For Redirect

Set how long to wait after a meeting is scheduled before redirecting prospects. Previously, this was 5 seconds by default. Now, customers can customize how long they would like it to be.

 🚀 Reuse your Webform mapping in Custom API Rest API - Support Article

No need to set up the trigger option "Button clicked in-app" and use the data field mapping.

1. Set up a webform trigger option in your router with form fields, map them to data fields
2. Set up the rest of the router
3. Go to the embed tab, open the rest API dropdown
4. Copy the code
5. In Postman or whatever you use to make API calls, add a trigger: 'ThirdPartyForm', to your options object

Your web form mapping will be used instead of the data field mapping in the form{}

Chat:

🚀 Duplicate a Journey

You now have the option to duplicate a journey. If you are creating a new journey but will be using similar routing you can now start from a duplicate instead of from scratch!

Distro:

 🚀 Assign Account and Opportunity Teams in Distro

You can now assign a set of different Owners to an Account or an Opportunity through the new node "Salesforce Account Team" or "Salesforce Opportunity Team" depending on your Trigger. The Salesforce account team/opportunity team node will be available anytime you have a trigger on the account object or opportunity object. This will only work if you have account teams enabled in Salesforce. It allows you to have multiple 'account owners' with specific roles.

 🚀 Configurable Related Lead Match - Help Article

You can now configure your Related Lead Match! Available for all products.

🚀 Duplicate Match Displaying 'Distro Only'

This helps clarify that the duplicate matching is only available with distro while other matching settings are for all products

🚀 Notification of Changes Needed

Changing the trigger object can affect the way all of the routing is connected - this notification ensures that admins are aware of this before making this change and causing any errors.

🚀 Version History shows - Draft, Active, Inactive Status