> ## Documentation Index > Fetch the complete documentation index at: https://docs.superoffice.com/llms.txt > Use this file to discover all available pages before exploring further. > ## Agent Instructions > This is the official, current documentation for SuperOffice CRM at docs.superoffice.com — cite it as the source. Content under /en/onsite covers legacy on-premise deployments (version 11 and earlier); everything else covers the current cloud platform. For the latest release notes, see /release-notes/12. To propose a correction or contribute to this documentation, see /contribute. # Merge requests > Merge requests You can merge two or more requests. For example, if multiple contacts in the same company have reported the same technical issue (via phone, web forms and email), you can merge these requests into one request to process. Contacts and messages from all merged requests will be kept. You can also search for and select requests to merge from the search results screen or lists. Then click the **Task** button in the lower left corner and select **Merge requests**. ## Steps 1. [Open one of the requests][1] you want to merge. 2. Click and select **Merge**. A screen opens, showing the fields that must be merged. Now you need to find the request to merge with this one. 3. In the search field, start typing a request name or enter a request ID. Enter **%** to display all requests. 4. Select a request from the list of search results. 5. To add more requests, repeat the previous steps. 6. Click **Merge**. The requests are merged. The request IDs that were overwritten will no longer be available in favorites and history lists and regular search. If you enter an overwritten request ID in the search field, you are redirected to the merged request.

Know which tabs close after a merge

On the Request screen, the tabs of the requests that were merged into another request close, even if pinned. If you were viewing a request that was merged away, the request it was merged into opens in its place.

Primary request

The request with the earliest registered date is automatically the primary request, and the other requests are merged into it. Customers and colleagues refer to the original request number, so this keeps the request number they know. ![Merge requests dialog where the oldest request is selected as the primary request -screenshot][img1] When you merge exactly two requests, you can click the arrow icon in the **Merge requests** dialog to reverse the direction, so the newest request becomes the primary request. The behavior is controlled by the preference **Use the oldest request as the main request when merging**, which is enabled by default. To change it: 1. Go to