Assigning leads to a role, rather than "user"
Z
Zach Smeltzer
This was sent to me from a current client in one of our sub accounts: "Instead of the assigned user being a person on our staff. I would prefer it to be a role--something like, “Sales Person”, or “Studio manager”, or “Head trainer”. And then I want to be able to assign my staff to roles. So when my Studio manager leaves, I don’t have to go into EVERY automation and opportunity to update the assigned user. I just change the person assigned to that role, and all assigned users in automations and existing opportunities gets updated automatically to the new person. I am going through this right now as our Studio manager at RR is leaving and we have a new one. I have spent HOURS today updating everything. When it really should have been as simple is changing the person assigned to that role."
Log In
A
Aaron Rajchel
The CRM I use for my landscaping company has this ability and it is nice so you don't have to update the automations every time a role change occurs. I would add that there should be a toggle switch for this trigger that whoever performs the 1st action would become the assigned user and from then on the automation would apply to that user rather than the role. This would keep from multiple people being in the same role interacting in the process. Also, would need to be able to set it so that if there is no user in that role, it switches over to another role you can choose.
M
Matthew Gerchow
Aaron which CRM do you use for your landscaping company?
S
Shaun Maddox
This is such an great idea I can't even contain myself. How annoying is it to have to go into all of your workflows and change the user if you have somebody take over that position
R
Rich Warren
I would even take this one step further to have the ability to assign contacts to departments, like sales team, support team, retention team, etc...