In daily operations, our customer users cannot add CC recipients when creating or replying to tickets, which forces agents to manually add CCs on their behalf. This creates delays, fragmented communication, and unnecessary operational overhead, especially in situations where several people on the customer side need to collaborate on the same issue or when customers are restricted to using only the Zammad web app, where no such option exists.
The current Zammad standard does not provide any mechanism or permission model that would allow customer users to add CCs, leaving agents as the only ones who can manage additional recipients. The expected improvement is to enable customer users to enter CC addresses during ticket creation and replies, enhancing transparency, collaboration, and reducing manual work for agents.
This request is related to the broader idea of supporting multiple customer participants in one ticket, but focuses specifically on CC functionality as a lighter, more flexible solution.
Our environment includes approximately 20 concurrent agents, handling around 2000 tickets per day, with both agents and customer users involved in communication. Because customers and company users rely heavily on the Zammad web interface, the absence of a CC field represents a significant limitation in everyday workflows.