12
Not having visibility into when an email is already tracked by another user in the org represents an incredible regression in functionality from the prior version (i.e. hieavier COM add-in). Until I see a better explanation of this design decision, I actually consider this a bug.
Here�s why: This is an incredible waste of time across our team.
Take an example where 15 of my users are CC�d on an email, and all 15 perform �Set Regarding�.
- Assume each �Set Regarding� takes 10 seconds.
- Per tracked email, that�s 140 wasted seconds per email (150 total minus the 10 seconds for the first �Set Regarding� action, the only relevant one).
- If my users track 300 emails over the course of a day � which is actually a very light day � that�s up to 42000 seconds (or ~12 hours) per day worth of wasted time across the team of 15 people.
Here�s why: This is an incredible waste of time across our team.
Take an example where 15 of my users are CC�d on an email, and all 15 perform �Set Regarding�.
- Assume each �Set Regarding� takes 10 seconds.
- Per tracked email, that�s 140 wasted seconds per email (150 total minus the 10 seconds for the first �Set Regarding� action, the only relevant one).
- If my users track 300 emails over the course of a day � which is actually a very light day � that�s up to 42000 seconds (or ~12 hours) per day worth of wasted time across the team of 15 people.
STATUS DETAILS
Completed
Administrator on 7/1/2022 10:56:14 PM
Thanks for the feedback. A change was made within the last year to automatically tag the same email received by others as well.