Allow teammates to split conversation/tickets

Additional information from the 1LS team : 

Description: When a customer replies to an existing ticket with a new, unrelated issue, we must split the ticket to maintain clarity and proper tracking. However, due to the lack of a direct “Split Ticket” functionality, this simple task becomes time-consuming and operationally inefficient, affecting both our internal workflow and our response times to clients.

Below is the current manual workaround we are forced to follow:
- Manually copy the customer’s email chain from Gmail to ensure the new ticket contains the correct context for the client. If the email from the customer has not reached the correct email address on our side, we cannot follow this step, and we have to copy the customer’s email from the ticket, so it will not be readable enough.  
- Create a conversation first, because we cannot open a ticket directly. We need the conversation step in order to select the correct “From” email address that will be used to reply to the customer.
- Manually add all customer participants (To/CC) one by one.
Many of our clients include multiple stakeholders/colleagues in their emails.
The system limits us to 10 email addresses in “To” and 10 in “CC”, which often isn’t enough.
If we fail to include all participants, the customer will come back with questions or confusion, forcing additional back-and-forth.
After entering all recipients, typing the subject, and our message to the customer, we create the conversation. NOTE: We cannot provide the ticket number to the customer, because it will be generated only after we create a customer ticket. 
- Convert the conversation into a customer ticket. During this conversion, the system changes the subject automatically, so we must copy and correct it again to maintain consistency.
- We need to add an extra note to explain from which ticket this new ticket was split. 

Approximate time of handling such a workaround: 15-20 minutes

Impact: Having different requests from a customer regarding different users in the same ticket can lead to misunderstandings, especially to Privacy Breaches. This is why we need this option.
This affects our overall workflow; what should be a simple, quick action becomes a multi-step manual process, reducing our ability to focus on solving issues.
It slows down our response times, which directly impacts customer satisfaction.
Because we have to start with a conversation rather than a ticket, we cannot inform the customer of the new ticket number immediately. This creates confusion and additional follow-up communication.
It creates room for error (missing recipients, incorrect subjects, lost ticket references).
Ultimately, it affects our overall workflow efficiency and the quality of service we provide.