Stop engaged pipeline task from firing when an appointment is missed or canceled
M
Mikey Criss
I created a new process for users to follow up to reschedule for 15 days after an appointment was missed or canceled and they clash with the engaged tasks and there's no way to stop them from firing. Making "appointments" as a pipe stage would be the best way to accomplish this I think, as it technically is. Lead - Engaged - Appointment - Visit - Proposal - Sold - Delivered is how I've always looked at it.
Shelby Parker
Thanks for posting this, Mikey Criss — really appreciate the detailed context. Totally hear you on the workflow clash when an appointment is missed/canceled and the engaged pipeline tasks keep firing with no way to pause them. I’m sharing this with the team for review (including your idea of treating “Appointment” as a pipe stage), and we’ll follow up if we need any additional details from your setup to evaluate the best path forward.
M
Mikey Criss
Shelby Parker thank you so much! I really think this is a fantastic idea. A little extra detail you can add; Let's say an appointment was set on the last day of the Engaged follow up process - that appointment doesn't show and no further follow up tasks are scheduled - I created a process where if an appointment is missed or canceled it generates reschedule tasks for two weeks for my sales people - but if an appointment is created on let's say day 4 of the engaged process and they don't show - my 15 day business rules will still apply but if the engaged tasks are still firing they clash with each other