History tracking for CTA, pushing out the due date
Use case is a CSM will move out the date on a Task that is a part of the playbook and there is no way to track this change or see why the change was made. Would love to have a way for the user to identify why the date was pushed out.
Login to the community
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Process wise it would be make sense to require the CSM to make a timeline update or note on the CTA description if they felt it necessary to change the due date.