I'd like to second this. Our customers will copy in more than one team to the same email which forces our team to check in with that team to see if that team is going to reply. We can't mention them on the email because that causes duplicates and when people merge those duplicates, it creates a less than fun workflow where if the team not responding to the email archives it, it archives it for the other team too. We'd like to create an auto-response that when it replies, uses a Reply All action.
Adding a "Reply All" option to relevant actions (such as the Create Draft action) would prevent workflow/process errors when responding to customers.
Specifically, users can mistakenly remove important contacts from conversation threads if they use a Macro that has a Create Draft action. The benefits of using a Macro are also diminished, as the user needs to manually re-add recipients to the message.
I'd like to second this. Our customers will copy in more than one team to the same email which forces our team to check in with that team to see if that team is going to reply. We can't mention them on the email because that causes duplicates and when people merge those duplicates, it creates a less than fun workflow where if the team not responding to the email archives it, it archives it for the other team too. We'd like to create an auto-response that when it replies, uses a Reply All action.
Adding a "Reply All" option to relevant actions (such as the Create Draft action) would prevent workflow/process errors when responding to customers.
Specifically, users can mistakenly remove important contacts from conversation threads if they use a Macro that has a Create Draft action. The benefits of using a Macro are also diminished, as the user needs to manually re-add recipients to the message.