When should duplicate community discussions be merged?

Merge when the task, conditions and required answer are sufficiently alike, and the combined thread remains clear. Review useful contributions, answer status and original links first. If important differences remain or the chronology becomes confusing, connect the threads with an explanation instead.

Is linking discussions better than merging them?

Linking is often better when discussions are related but address different versions, configurations or purposes. It preserves context while helping readers move between relevant material. Merging can be useful for true duplicates, provided the tools retain meaning, access and a clear route for existing readers.

Should an accepted answer survive a merge?

Only if its status remains accurate for the combined discussion. Check who confirmed it and under which conditions. An answer accepted by one customer may not resolve another customer's issue. Preserve qualifications and identify unresolved work rather than inheriting a misleading solved status.

How should you tell a customer their post was merged?

Explain the reason, identify the new location and tell them how to continue if their circumstances differ. Keep the message respectful and practical. Avoid implying that they wasted the team's time; repeated questions can reveal problems with search, titles or the completeness of existing guidance.

Why do customers keep creating duplicate discussions?

They may not find the existing answer, may use different terminology or may have a condition the answer does not cover. Review the customer task and discovery route before assuming inattention. Improve relevant guidance and navigation, while preserving space for genuinely different questions.

Merge Duplicate Discussions Without Losing Context

Decide when to merge, link or preserve similar discussions while keeping customer context, answer status and participation intact.

Published: 14 October 2026
Topics: Community knowledge, Customer experience, Content operations

Merge duplicate community discussions only when they address the same customer problem under compatible conditions and the combined thread remains understandable. Compare context before acting, preserve useful contributions and explain the change. Link discussions instead when merging would confuse the timeline, erase meaningful differences or attach an answer to the wrong situation.

Two customers ask why a report is missing. One lacks a permission; the other is using a different configuration. Their titles look identical, but merging the threads could make a correct answer appear to solve both problems when it addresses only one.

Check whether the customer problem is really the same

Read beyond the title. Compare the intended task, observed behaviour, conditions and unresolved question. Similar wording can describe different problems, while different wording can describe the same one. The moderator's first job is to establish that relationship rather than tidy the list of discussions.

This is a preview. The full piece is free for members (3 reads a day) and unlimited with Premium.

Read the full piece on Led by Community (free account, 3 reads a day)