Admin Center
:π Hubspot Integration in our Fire Demand Conversion Platform
The same Hubspot integration you know and love is Live our Demand conversion platform!
π Salesforce Package & Field Updates -
Help ArticleAll the details of the fields are included in the support article
π Hubspot CRM Custom Properties -
Help ArticleAll the details of the fields are included in the support article
π Update user invite email
The email that invites users to a workspace previously included details on Distro which was confusing for customers who may not have distro or access to the product. The new emails are below.
ChiliCal
:π Meeting Reassignment from My App
End Users can now reassign meetings in their My App by clicking on the host and selecting who the meeting should be reassigned to
π Autocomplete in ChiliCal Form
Added auto-complete to all ChiliCal form fields so user input is simplified
π Meeting Guests can add additional guests from the form page
Add additional guests to the form page when scheduling a meeting. Allowing your prospects the ability to include everyone that needs to be included on the invite from the beginning.
π Copy to all in Availability Schedules
When setting up Availability schedules you can customize a day and apply this same schedule to all days. Saving time π!
Handoff
:π Ability to hide non-matching Paths
In Handoff's user controls section, you can not enforce if your users will see and be able to schedule out of paths that do not match.
π Switch to my Calendar loading first
Switch to my calendar will load first before the rest of Handoff if you know you will be booking a meeting for your self
π Handoff Routers Active/inactive toggle
This gives admins the ability to create routers without them being active for users until they are ready to go live
π Update create event node the same as Concierge
When a path contains a rule that involves lead records, after the scheduled path of the display calendar node, in Concierge we explicitly display the Lead object, this is how it now looks in Handoff
Form Concierge
:π Allow adding Update/Create node right after Trigger
This gives admins the option to set up creation and updating earlier in the concierge flow. This solves the problem of race conditions when a third party tool creates/updates the record. Below is the new order of operations:
1. Prospect fills a form
2. Concierge creates/updates record WHILE performing routing/booking the meeting (in parallel).
- For create/update record action we would need to perform Prospect/Lead2Account matching to make sure that we create Contact under correct Account when possible.
- Settings of the Update/Create node displayed on the design added below
3. If the admin adds Update/Create node after the trigger, they cannot add it on scheduled/not scheduled paths
4. If the admin doesnβt add Update/Create node after the trigger, they can add it on scheduled/not-scheduled paths (the old way)
π Filter by Source URL in Logs
Allows you to filter your logs by the specific URL that was used. For example, on our SDR pages, each SDR has their own URL so we can filter based on a specific user's URL.
π Notification nodes Available on Calendarless paths
Calerdarless Path Include:
Ownership rule (assignee will be from the Team on ownership rule)
- can be added anywhere after Redirect To node
- can be added after or before any other node
- if Assign To is added, always after this node
Non-ownership rule (assignee will be from the Assign To distribution)
- always after Assign to (there may be other nodes between Assign to and Notify, but Notify should always appear later in the path than Assign to)
- can be added after Redirect to page
- can be added after or before any other node
π Add by parameter to the Embed tab
When βbyβ is selected, please dynamically show another field that allows to select a user (should be a workspace user). Once selected, the link with the correct user. This allows admins to use router links that direct to a specific user.
π Update routing behavior when smart parameters are in use
Current behavior:
When ?id= parameter is used, record exists in CRM, and required fields are not filled on a form, we show the router form.
New behavior:
When ?id=parameter is used, record exists in CRM, and required fields are not filled on a form, we still try to route without showing the form. If non-required fields are used in routing rules, the data will be null and condition will fail - which is ok by legacy customers.
π Implement the option to read custom field names using CSS class names in Pardot Concierge implementations (iFrame and Native)
π Improve the User not found error in Concierge Logs
When a user is not found it is caused by a mapping error. New error copy was added to make this more clear.
Ownership not updated
[field name]: user id=N not found
Please check Salesforce user mapping status. Open Users list.
Distro
: π Ability to set fields as Null in SLA Node - Field Update
If you are having your Distro SLA update fields you may want to set a null value. For example, once the SLA is set you can set a a most recent status field to null.
π Duplicate and Edit Rules in Flow Builder
When building flows together with rules a lot of rules are similar with some condition changes (for example: company size, state, country). Now, when building rules in the asset list you can duplicate and edit to save time on rule building.
π Contains operator for picklist fields
