We have many success plays that are automatically triggered based on usage (e.g, usage drop or spike). The logic is not always perfect and sometimes we have false positives. It could be a drop due to seasonal usage or maybe a launch delay, etc. In such cases there’s no need to follow the tasks and the CSM would just want to close the success play with one click and specify “no action required”. Tracking these types of false positives will allow us to understand effectiveness and improve success play logic over time.
Please sign in to leave a comment.