I have an Order pipeline that my team uses to track the status of an order from a customer. Whenever an order comes in, can I notify all my relevant users?
While notifications in LACRM are designed to help users stay on top of tasks, events, and contacts/companies assigned to them, one workaround to getting notifications for new pipeline items would be to use our Form Builder.
LACRM’s form builder is designed to collect contact/company information and add them to your CRM database but because form submissions can trigger email notifications to users on your account, you can also use it as an internal form for your team to fill out as a way to send email notifications to your users.
Here’s how Hogan can use the form builder to notify his users whenever a new order comes in:
Create a “Log a new Order” form with the fields for the customer name, email, phone, and order information. Make sure to connect each of these fields to your contact record, and your pipeline.
Click on the Permissions settings on the bottom right corner:
Check off “Send email notification” at the bottom of the pop-up.
That’s it!
Now, whenever the team wants to log an order in LACRM, they can just fill out this form and it’ll automatically attach the Order to the customer and send an email notification to all the users who need to be notified!
Do you need to get notifications for other items in LACRM? Feel free to ask below!
I realize that automations are still in beta, but if an automation is set to trigger on a pipeline status change, will it “fire” if a pipeline is created with that status (as distinguished from an existing pipeline being changed to that status)? If yes, wouldn’t that be an easy solution?
Yep, the automation will “fire” if a pipeline item is created with that status, or if it’s moved into that status! Using an automation would be a little different than what Eunice described; you’d have to set the automation to trigger a task assigned to the user (or multiple tasks, one for each user). Then, the user would get a notification email for the task, but they’d also have a task in the CRM. With the form submission option Eunice described, each user can get an email notification of the new form submission, without getting an assigned task too. Either of those options could potentially work though, depending on the scenario and whether you want a task or not!
This is probably the wrong place to ask, but not sure where to move it to.
One concern I have with adding automations to pipeline state in my operation is the very real chance that a pipeline will get accidentally set to the wrong state or created on the wrong contact. During our busiest period, we’re updating a large number of pipelines frequently, and mistakes happens.
Obviously there is nothing to be done if the problem isn’t detected promptly, but quite often it’s just a slip of the mouse and the state quickly gets corrected or the incorrect pipeline gets deleted promptly. If an attached automation gets triggered by the error, there’s no way to fix that.
I can think of 2 approaches that would mitigate the problem: (1) allow a “settling” time before the automation triggers - say 10 seconds. After the elapsed time, if the trigger is unchanged (same state, same contact), then proceed. (2) Allow for an optional “human in the loop” approval before the automation triggers, with options to proceed or cancel.
We actually added something recently that should help with this. Now, when you change a pipeline to a status that triggers an automation, you’ll see a notice about the automation that’s about to run she you can even disable it if you want to. Hopefully that helps with the problem you’re describing!
