> ## Documentation Index
> Fetch the complete documentation index at: https://docs.neoagent.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Merge Ticket

> Combine related tickets into one, consolidating duplicate issues and communications

This action combines two related tickets into one, helping you consolidate duplicate issues or related communications. When you have multiple tickets for the same problem, this action transfers all the important details from one ticket into another, keeping your PSA system organized and preventing duplicate work.

<Tip>
  Instead of having technicians juggle multiple tickets for the same issue, merge ticket automatically consolidates everything into one place. This means less confusion, no duplicate work, and a cleaner ticket history for both your team and customers. It's especially helpful when customers accidentally create multiple tickets or reply to old tickets.
</Tip>

<Info>
  This action is available only as a **triggered** action in a workflow.
</Info>

## Quick Start

<Steps>
  <Step title="Set up ticket detection first">
    Always use the "Find Ticket to merge with" action before this one. It identifies which tickets should be merged together.
  </Step>

  <Step title="Create a triggered workflow">
    Set up your workflow to trigger when new tickets are created, so it can catch duplicates right away.
  </Step>

  <Step title="Add basic merge settings">
    The action will automatically handle the merge, but you can optionally:

    * Move the merged ticket to a specific queue (Autotask only)
    * Set custom statuses for the merged tickets
    * Choose whether to close the destination ticket
  </Step>

  <Step title="Test with safe tickets">
    Try it first with test tickets or in a development environment to see how it works with your PSA setup.
  </Step>
</Steps>

## Best practices

### Start Simple

Begin with the default settings and let the action handle the merge automatically. You can add custom status updates and queue moves later once you're comfortable with how it works.

### Use Follow-up Actions

Consider adding these actions after merging:

* **Notify Ticket's Contact** - Let the customer know their tickets have been consolidated
* **Add Ticket Note** - Document why the merge happened for your team

### Set Clear Statuses

If you choose to update ticket statuses after merging:

* Use descriptive statuses like "Merged - Duplicate" for the original ticket
* Keep the destination ticket status active so work can continue
* Make sure your chosen status names exist in your PSA

### ConnectWise vs Autotask

* **ConnectWise** uses native merge functionality, so the process is cleaner
* **Autotask** copies notes and details manually, which gives you more control but takes a few extra steps

### Monitor Your Results

Check the Event History regularly to see how merges are working. This helps you spot any issues and fine-tune your workflow settings.

## Configuration options

### Merge Source

The action automatically processes merge recommendations from the "Find Ticket to merge with" action. No manual configuration needed for basic merging.

### Queue Management (Autotask)

**Move to Queue:** Optionally move the merged ticket to a specific queue after merging

### Status Updates

**Update Source Status:** Set a specific status for the original ticket being merged (e.g., "Merged - Duplicate")
**Update Destination Status:** Set a specific status for the ticket receiving the merge
**Close Destination:** Choose whether to close the destination ticket after merging

## What you'll get

After the action runs, you'll see:

* **Event History:** Confirmation of which tickets were merged and the results
* **Consolidated Ticket:** All information from both tickets combined into one
* **Clean PSA:** Reduced ticket clutter with proper merge documentation

## Common use cases

<Accordion title="Duplicate Ticket Detection">
  **When:** Customer creates multiple tickets for the same issue
  **Setup:**

  1. Trigger on new ticket creation
  2. Find Ticket to merge with - Identify duplicates
  3. Merge Ticket - Consolidate the duplicates
     **Result:** Single ticket with all customer communications preserved
</Accordion>

<Accordion title="Email Reply Consolidation">
  **When:** Customer replies to old closed tickets
  **Setup:**

  1. Trigger on ticket updates
  2. Find Ticket to merge with - Find related active tickets
  3. Merge Ticket - Combine old and new tickets
     **Result:** Current ticket includes all historical context
</Accordion>

<Accordion title="Multi-Channel Issue Consolidation">
  **When:** Same issue reported via phone, email, and portal
  **Setup:**

  1. Trigger on new tickets
  2. Find Ticket to merge with - Identify related issues
  3. Merge Ticket - Consolidate all channels
     **Result:** Single ticket with complete communication history
</Accordion>

## Example workflows

<Accordion title="Smart Duplicate Prevention">
  1. **Trigger:** New ticket created
  2. **Find Ticket to merge with** - Check for existing similar tickets
  3. **Merge Ticket** - Consolidate if duplicates found
  4. **Add Ticket Note** - Document the merge for team reference
  5. **Result:** Automatic duplicate prevention with documentation
</Accordion>

<Accordion title="Customer Communication Cleanup">
  1. **Trigger:** Customer reply to any ticket
  2. **Find Ticket to merge with** - Look for active related tickets
  3. **Merge Ticket** - Consolidate communications
  4. **Notify Ticket's Contact** - Inform customer of consolidation
  5. **Result:** Clean communication flow with customer notification
</Accordion>

## PSA-specific behavior

### ConnectWise

* Uses ConnectWise's native merge functionality
* Preserves all ticket history and relationships
* Maintains ConnectWise's audit trail
* Handles time entries and notes automatically

### Autotask

* Manually copies notes, attachments, and details
* Provides more control over what gets merged
* Allows queue changes during merge process
* Maintains Autotask's activity history

<Warning>
  Always test merging behavior in a development environment first. Different PSA systems handle merges differently, and you want to ensure the results match your expectations.
</Warning>