Ahmad

Hi, I'd like to add my vote to this topic as well. 

James Hanley to provide you with some context on my end. 

We're building a property maintenance assistant/applicatino and work with HOA's, property managers, and others that manage properties. 

We use Zendesk to keep all parties involved with a service request up to date. Each person has their own emails and we end up having to add one person as the requestor and then search for and CC others. It would be much easier if we were able to just designate say and entire "Org" or a specific group of people as requesters for a specific ticket.

In my case, even if there was still just a single requestor and the others we're CC'd but I could add them all to the ticket with a single action, it would make the experience significantly better.

If I were to write a user story for this feature it might go something like:
"As a Zendesk user,
I need to be able to add multiple people from the same organization to a new request/email at the same time,
so that I can ensure I am keeping my customers properly informed and not accidentally missing communication to them."

I know changes to a data model can be quite the task, and I don't know that this would even make sense, but perhaps there's a quick mvp that can be built through the use of the custom objects model? 

Thank you for investigating this!

Ahmad