To carry conversation details into a support ticket, choose the workflow that matches the situation: convert an active conversation into a new ticket, merge a duplicate into an existing ticket, or create a follow-up to a closed ticket. These actions preserve different information. Review the resulting ticket before saving or closing anything, especially its comments, fields, ownership, and visibility.
Choose the right way to carry the conversation forward
| Situation | Workflow | What carries over | Important limitation |
|---|---|---|---|
| A conversation needs a new work item | Intercom conversation-to-ticket conversion or linked back-office ticket | A pre-filled title, summary-based description, and matching ticket attributes | The AI-generated title or summary and the populated fields should be checked against the conversation. |
| Two tickets describe the same unresolved issue | Merge the duplicate into the intended primary ticket | Depends on the help desk. Zendesk adds the latest public comment from the ticket being closed; Freshdesk moves eligible conversations from secondary tickets in chronological order. | Merging can omit fields or messages, has visibility implications, and may be permanent. |
| A customer replies after a ticket is closed | Zendesk follow-up ticket | A new ticket references the closed ticket and inherits its tags. | Many comments and operational fields are not copied by default. |
These workflows are not interchangeable. A conversion creates a ticket from an active conversation; a merge consolidates duplicate records; a follow-up creates a new record related to a closed one.
Before transferring context
- Identify the customer’s current issue and whether the existing conversation is active, duplicated, or closed.
- Choose the ticket that should remain the authoritative record. For a merge, this is the primary or destination ticket.
- Decide which information the next agent needs: the original request, relevant replies, troubleshooting already tried, current status, next action, and any commitments made to the customer.
- Check whether comments or notes will be visible to the customer or other participants. A private internal note and a public reply are not equivalent.
- After the transfer, inspect the destination record rather than assuming the source’s fields and complete history were copied.
Intercom: create a ticket from an active conversation
Intercom’s product update shared July 27, 2026, says that converting a conversation into a ticket—or creating a linked back-office ticket—opens a form pre-filled with conversation details rather than a blank form. The feature is intended for turning a conversation into a work item without starting the ticket description from scratch.
What the pre-filled form uses
- Title: the conversation subject or its AI-generated title.
- Description: the AI conversation summary.
- Matching ticket attributes: attributes matched by name and type. Dropdown attributes match using the option label.
Review before saving
- Open the active conversation and choose the workflow to convert it into a ticket or create a linked back-office ticket.
- Review the pre-filled title and description against the actual conversation. Correct omissions, mistaken summaries, or details that are no longer current.
- Check each populated ticket attribute, including dropdown selections, and correct any mismatch.
- Save only after confirming that the ticket represents the work to be done. Intercom says the agent’s edits take precedence when saving.
The product update establishes the pre-filled form behavior, but not a universal set of fields for every workspace. Available attributes and exact workflow labels may depend on configuration.
Do these 3 things before closing this tab:
1Repair Windows errors before they cause bigger problems2Fix the driver behind crashes, sound loss and screen glitches3Clear out junk files and repair common Windows errors#1 Best Overall
Zendesk: merge duplicate tickets without assuming a full copy
A merge is appropriate when two tickets concern the same issue and one should become the continuing record. Zendesk’s merge guidance, edited September 8, 2026, describes important limits: only the latest public comment from the ticket being closed with the merge appears in the destination by default. Older comments remain available for review in the closed ticket, but are not thereby copied into the destination.
What does and does not carry over
- The latest public comment from the ticket being merged into another appears in the destination by default.
- Earlier comments remain reviewable in the closed ticket.
- Tags, type, priority, and status from the ticket being closed are not carried over.
- The merge is permanent.
Safe merge workflow
- Open the tickets and compare their request, conversation history, and current status. Select the record that should remain as the primary destination.
- Before merging, review the source ticket for useful earlier messages, troubleshooting, commitments, and field values. Do not treat the latest public comment as a complete history.
- Prepare a concise handoff note for relevant context that will not move automatically. Keep customer-visible content separate from internal-only information.
- Choose whether the merge comment should be a public reply or an internal note. Confirm its audience before submitting; a public reply is customer-visible.
- Complete the merge only after confirming that the selected destination and the limited transferred comment are correct. Because the merge is permanent, do not rely on undoing it to recover a mistaken choice.
- Review the destination ticket and, when needed, consult the closed source ticket for older comments or fields that were not transferred.
Zendesk’s guidance also describes status and requester/CC restrictions. Eligibility can therefore depend on the records’ state and participants, as well as workspace permissions.
Zendesk: handle a reply to a closed ticket
When a customer replies after a Zendesk ticket has closed, Zendesk can create a follow-up ticket that references the original. The follow-up article, edited September 9, 2026, makes clear that a reference is not the same as a full copy of the old ticket’s context.
Follow-up ticket carry-over
- Inherited: tags.
- Not copied by default: comments, priority, type, group or assignee, organization, skills, and external ID.
- Admin option: an administrator can enable copying the original group and assignee.
What to check on the new ticket
- Open the follow-up and use its reference to inspect the closed ticket’s relevant history.
- Confirm the new ticket has the correct owner or group, priority, type, organization, and any other operational details needed to handle the request.
- Bring forward the necessary issue history and next action in an appropriate note or the new ticket’s conversation. Do not assume the old comments have been copied.
- Check routing and reporting behavior for the follow-up in your workspace, particularly if ownership or organization affects how the ticket is handled.
Whether group and assignee are copied depends on the administrator setting; other listed omissions should not be treated as inherited just because the new ticket references the closed one.
Quick wins for a faster PC:
Scan for outdated or missing drivers - takes under a minuteDriver Scan →Repair Windows errors before they cause bigger problemsFix Now →Freshdesk: merge eligible tickets with their conversation history
Freshdesk documents a different merge behavior. Its ticket-processing article, modified October 1, 2026, says that for eligible tickets, conversations from secondary tickets move into the primary ticket in chronological order. Private notes link the secondary tickets to the primary, and the secondary tickets close.
Channel restrictions and visibility
- Web chat, WhatsApp, Facebook, and Instagram tickets cannot be merged under the cited Freshdesk documentation.
- The merge note defaults to private. Making it public may notify requesters, so check the audience before changing its visibility.
Freshdesk merge workflow
- Identify the primary ticket that should retain the issue and the eligible secondary tickets that should be consolidated.
- Check the source channels against Freshdesk’s exclusions. Do not attempt to use this documented merge workflow for web chat, WhatsApp, Facebook, or Instagram tickets.
- Review the conversations and select the correct primary record before proceeding.
- Keep the merge note private unless a customer-visible message is intended. If making it public, account for the possibility that requesters may be notified.
- After merging, verify that the secondary conversations appear in chronological order in the primary ticket, and that the secondary tickets are closed and linked by the private notes.
Freshdesk’s documented message movement is broader than Zendesk’s default latest-public-comment behavior, but it applies only to eligible tickets and channels.
Rank #3
![Free Fling File Transfer Software for Windows [PC Download]](https://m.media-amazon.com/images/I/41Vq6ZqHfjL._SL160_.jpg)
- Intuitive interface of a conventional FTP client
- Easy and Reliable FTP Site Maintenance.
- FTP Automation and Synchronization
Write a useful handoff when automation leaves gaps
When a platform does not carry all relevant context, add a short, factual note rather than copying an entire conversation without review. This makes the next agent’s starting point clear while reducing the risk of exposing internal material to the customer.
- Issue: what the customer is trying to resolve.
- History: the key prior steps or troubleshooting already completed.
- Current state: what is known now, including any unresolved question.
- Next action: what the receiving agent should do next.
- Commitments: any promised update, timing, or outcome that remains relevant.
Use an internal note for agent-only context and a public reply for information meant for the customer. Before saving, check names, sensitive details, and any content that should not be shared with every ticket participant.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREERepair Windows errors before they cause bigger problemsFix Now →How to choose between conversion, merge, and follow-up
- Choose conversion when an active conversation needs to become a trackable ticket. Review the generated summary and mapped attributes before saving.
- Choose a merge when separate records are duplicates of the same issue and one record should remain. Confirm what the product transfers, what remains in the source, and whether the merge can be reversed.
- Use a follow-up when a customer response creates new work after closure. Treat it as a related new ticket, then restore any necessary context and routing details that are not inherited.
Plan, channel, role permissions, and workspace configuration can affect the available workflow. The product-specific behaviors described above are documented for the cited Intercom update and Zendesk and Freshdesk help guidance; they should not be assumed to apply identically across all configurations.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
How do I link a new ticket to an existing conversation?
In Intercom, the documented route is to convert the conversation into a ticket or create a linked back-office ticket. The form opens with conversation-derived details; review its title, summary, and attributes before saving.
Can I recover a Zendesk ticket after merging it by mistake?
Zendesk describes a merge as permanent. The safe course is to verify the primary ticket and source before confirming the merge, rather than expecting a reversal.
Does a follow-up ticket include the original Zendesk conversation?
It references the closed ticket, but comments are not copied by default. Open the original through the reference when you need to review its conversation history.
Will merging tickets send a message to the customer?
It depends on visibility settings and the platform workflow. Zendesk allows a merge comment to be a public reply or internal note, while Freshdesk defaults its merge note to private and warns that making it public may notify requesters.
Why can’t I merge a Freshdesk ticket from WhatsApp or social messaging?
Freshdesk’s cited ticket-processing documentation excludes web chat, WhatsApp, Facebook, and Instagram tickets from the described merge workflow.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
