A Duplicate Enquiry Check: Decide Whether Two Messages From One Customer Are One Job or Two

A customer fills in your form, then sends an email the next morning, then calls. Three messages arrive in three places. If each is handled alone, the customer gets three different replies, or none. This article proposes a short check you can run before replying, so the team decides whether it is one job or two. Treat it as an option to adapt.

The inputs you need

For each new message, note five things:

Contact details given, such as name, email and phone.
The channel it arrived through.
The time it arrived.
The thing being asked for, in a few words.
Any reference the customer quotes, such as an earlier reply or a date.

Then look for earlier messages sharing at least one contact detail within a window you choose, for example the last two weeks.

The branching decision

Compare the new message with the earlier one and pick a path.

Same contact, same thing asked: merge. Keep one record, add the new message as a note, and send one reply that covers both. Tell the customer you have combined them.

Same contact, related but different thing: link. Keep two records, add a note in each pointing to the other, and assign them to the same person so the customer hears one voice.

Same contact, clearly unrelated thing: keep separate. Do not merge only because the name matches.

Different contact, similar wording: do not merge. It may be a colleague, a family member or a coincidence. If you suspect a link, ask the customer rather than assume.

Unclear: ask one short question, such as "Is this about the same job as your message on Tuesday, or a new one?" Hold both records unchanged until the answer arrives.

A hypothetical worked example

Imagine a small garden maintenance business. On Monday a customer submits a form asking for a spring tidy of a front garden. On Tuesday an email arrives from the same address asking whether hedge trimming can be included. The team compares: same contact, related request, same property. They choose link, not merge, because hedge trimming may need a separate estimate. One person takes both and replies once: "I have your tidy request and your hedge question together. Here is what I need to confirm each." On Wednesday a phone call arrives from a different number about a neighbour's garden. No shared contact detail, so it stays separate, and the team asks the caller whether the neighbour's request is connected to the first.

Stop conditions

Pause and ask a person instead of deciding by rule when the messages mention money already agreed, a dispute, or a complaint. Also pause if merging would delete any original text. Never discard the earlier message; the merge should only add context.

Small acceptance checks

After each decision, confirm:

The customer receives one reply, not one per message.
Every original message is still readable.
Each record says why it was merged, linked or kept apart.
One named person owns the thread.
The reply never states that two different jobs are the same unless the customer has said so.

Review a handful of past cases after a few weeks. If merges were later undone often, tighten the rule so that only same contact and same request qualify. If customers still complain about repeated questions, widen the linking window. Keep the rule short enough that anyone covering the inbox can apply it without asking.