# Child Tickets
<h1>Child Tickets</h1><p>Internal, or child, tickets help route individual tasks to internal teams while keeping them linked to the customer's original ticket.</p><p>For example, a request may require work from development, system administration, finance, or another team. Instead of forwarding the task by email or messenger, an employee creates a child ticket directly from the main ticket.</p><h2>How it works</h2><ul><li>a child ticket is created from the main ticket and keeps the relationship between them;</li><li>the internal team works on its own ticket while the main ticket owner retains the overall context;</li><li>the child ticket status can be tracked;</li><li>the conversation history remains connected to the original request;</li><li>a reply in a child ticket can automatically reopen the main ticket.</li></ul><h2>Why use child tickets</h2><p>Child tickets prevent work from being lost at internal handoffs. The main ticket owner can see which team is handling the task and what stage it is in, while the customer receives a more up-to-date status.</p><h2>How to enable child tickets</h2><p>Activate the <code>child_tickets</code> feature flag. General rules are described in <a href="https://support.swarmica.com/article/ru/596-фича-флаги-features-возможность-включать-и-выключать-блоки-функций-в-swarmica.html">Feature flags (features) in Swarmica</a>.</p><p>The feature is available if the corresponding license is active.</p>