Repeated customer conversations can scatter one service issue across several places. Bringing them together may help a client and an outsourcing provider see the work more clearly, provided they agree which issue is being combined and what still needs attention.
In a November 13 announcement, Intercom described merging up to 100 conversations in one step. The user chooses a primary conversation that stays open, and that conversation displays a card listing the merged conversations, grouped by what the customer asked about. This is the vendor’s feature description, rather than a test of a client’s workflow. The announcement alone does not settle every operational consequence of a merge.
Agree what counts as the same issue
The following is our original client–provider analysis, using an invented service situation. It is not a claim about how the platform handles any particular record.
Imagine a customer writing twice about a delayed delivery and once about changing the address for a separate order. All three messages come from the same person. That fact does not make them one piece of work.
Before combining conversations, the provider needs a clear basis for deciding which belong together. The client and provider could agree that the underlying request, order or unresolved question matters more than the identity match alone. The appropriate rule depends on the service and the records available.
Apply the rule to examples before relying on a broad instruction to “clean up duplicates.” That instruction can otherwise hide different judgments about whether two messages repeat a request or introduce an additional one.
Find the commitments inside the conversations
In our hypothetical case, one colleague promised to check the delivery position, while another said an update would follow that afternoon. The team needs to understand both commitments before deciding what to tell the customer next.
A combined view should support that understanding. The person taking over the work should be able to identify what has been promised, what has been done and what remains unresolved. Merely reducing the number of visible conversations would not establish that the customer has received the promised follow-up.
The client and provider can define a short handover note for cases that need it. Focus the note on the current request, the next action and its owner. Avoid adding a lengthy narrative that makes the important commitment harder to find.
Give the combined work an accountable owner
Choose who will take responsibility for the continuing interaction. In the invented example, the delivery enquiry may need one owner while the separate address request continues elsewhere. Everyone involved should understand which colleague is doing what.
If a supervisor performs the merge while another team serves the customer, agree how that team will learn about the change. A convenient administrative action should not leave the people handling the work uncertain about where to continue.
Also decide when a case should be reviewed before consolidation. A practical boundary might concern competing requests or an unclear customer identity. Those are examples of operating questions to resolve locally, not assertions that the product automatically detects or prevents them.
Explain the change in the service review
If the provider reports conversation volumes, keep an account of how consolidation is treated in that report. Ask the reporting owner what the figures represent and whether the client’s interpretation remains appropriate after the working process changes.
For example, a smaller visible workload after a clean-up should not automatically be described as fewer customer problems. In our hypothetical situation, it may reflect the team putting related work together. The actual reporting effect would need to be checked in the relevant system.
Combining conversations can be part of a clearer customer journey. The client–provider agreement should make that purpose concrete: identify related work, preserve the commitments people need to act on and assign responsibility for the next response. The service outcome is the work completed for the customer, not simply the tidiness of the inbox.
AI-generated conceptual editorial photograph of fictional service paperwork; not customer files or a demonstration of the software merge feature.