Skip to main content

Issues with new pipeline customization feature

  • March 1, 2024
  • 0 replies
  • 31 views

Joaquin Dedd

Hey all!

The new ability to customize your pipeline automations is a nice touch; however, our company is having 2 issues with it:

 

#1:

With the old pipeline, when we would send an “Unavailable” email from our template list, the lead would be marked automatically as “Not Available.” Now, with the new pipeline customizations feature, the only way to replicate this automation is to have the “First Email Sent” set to send the lead to “Not Available.”

 

The problem with this logic is that not all first emails we send are “Unavailable” messages, of course! This leads us to have to manually mark every unavailable message as “Not Available.” While this isn’t a huge problem, HB used to do this automatically and we now have to do it manually - something that we didn’t have to do before this “automation” update.

 

#2:

We then thought to just use one of our multiple team member accounts to be the dedicated account to respond to the leads in which we are unavailable and have that account’s pipeline set accordingly to send all first emails to “Not Available.” Solved, right? Wrong!

It turns out that when you make an adjustment to your pipeline automations on one account, it affects all other team members’ accounts in your company! Whaaaaa??? I thought I must be missing something, but today HB confirmed that all team members in HB have to have the exact same pipeline settings - whoa!

 

Anyone else annoyed with this change and/or inability to have separate pipeline automations across your team members?