
I am about to roll up my selves on this.
What I am realizing that Engagement Plans are good for when you want to standardize but not automate. This is when you want to make sure an email or a communication happens but you cannot make it a template or an control the timing.
My other point is that, engagement plans are at the core still tasks. They are most powerful when built off of a sales or service process. For my teams and use cases, I often need to differentiate between a task and a case. When should they create a case? When should they create a task? My guidance is that if you would write it on a post it note, then its a task. If its an email or phone call then its a case.
These two help you think through the boundaries of what the series of tasks should be and how they are written. Building on that advice as well as @Barbara C. 's plan it out with a bunch of post its.
5 respostas