A customer fills out your moving quote form, then calls to check that it arrived. Later, their partner sends an email with the preferred date. The owner starts answering the call while someone in the office prepares a separate estimate from the email.
In this fictional example of a small moving business in Orlando, several messages concern one possible move. Treating every message as a new opportunity can produce conflicting replies and an inflated list of open requests. The first improvement is a shared way to recognize the request before anyone starts another estimate.
Look for an existing request before creating one
Choose one place where the team checks open inquiries. That may be the customer system you already use or a small shared list. Give each request a stable reference, such as "Request 412," and record its responsible person and next action.
When a message arrives, search that list using the contact details provided, then compare the work described. For a move, the proposed date and the pickup and destination details can help distinguish it from another inquiry. Use information already supplied; don't collect identity documents to solve an office filing problem.
A matching email address or phone number is a clue, not a decision. One customer may arrange two different moves. Two people may discuss the same move from different accounts. A familiar name alone isn't enough to join their records.
If the connection is unclear, mark it for review and ask a neutral question, such as whether the new message relates to the move they already requested. Don't disclose another person's addresses or quote details just because a caller says they are involved.
Keep the messages, give the work one owner
Once you've confirmed that the messages concern the same request, attach or reference them from the existing record. Keep the date and channel of each contact so someone can reconstruct what changed. A call note should say what the customer added and what was promised, rather than simply "called."
In the example, the partner's email may contain a new preferred date. Linking it to Request 412 should make that change visible to the person preparing the estimate. It shouldn't silently overwrite a previously confirmed detail. Clarify conflicting information with the customer before using it.
Name the person who will send the next reply. If the owner hands the request to the office, the office should acknowledge that handoff before the owner stops following it. A small team can do this manually in its existing work record. Two people privately deciding that the other has it is how a request gets missed.
If two records already exist, identify which one will carry the ongoing work and mark the other as linked to it. Preserve its messages and notes. Check for a reply or promised action on either record before stopping duplicate follow-up. This is a review step, not an instruction to erase the extra row.
Use familiar tools to help you review
For a team already using a supported desktop version of Excel, Microsoft's duplicate-value guidance describes highlighting repeated values with conditional formatting. Applied to a contact column, that can bring repeated entries to your attention. It won't establish that they concern the same job. Different phone formatting or another household member's email may also keep a related request from standing out.
The same guide warns that Remove Duplicates deletes data and recommends preserving a copy first. For intake review, start with highlighting and manual comparison. Keep an untouched copy when trying a cleanup on an exported list, and don't let the cleaned export replace your live records without checking what was lost.
In new Outlook or Outlook on the web, categories can label and group messages. A category such as "Check existing request" can help you return to an email. Microsoft notes that other people don't see the categories you assign, so a personal label should not be the team's only record of who is handling the request. Phone notes and form submissions still need to be connected to the shared record.
Count requests separately from contacts
Keep both numbers understandable. In the opening example, a form submission, call and email are separate contacts associated with one request once that relationship is confirmed. If you report new inquiries each week, count the request once according to its original received date. Keep later contacts in its history rather than presenting them as new demand.
Leave uncertain matches visible. A small "needs review" list is more honest than a precise total built on guesses. Restrict access to the contact details and moving information to staff who need them; avoid circulating a full export when a job reference will do.
Start with a few fictional examples: a repeated form submission, one customer requesting two jobs, and two people discussing one job. Ask a colleague to work through them using the agreed rules. This trial needs no new subscription. If your current customer system already supports linked records and ownership, use that before adding a separate spreadsheet. Consider automation only after you know which matches require a person and how a mistaken link would be undone.
The request and quote tracking example shows how a shared record can support follow-up. If your team sometimes answers the same inquiry twice, we can discuss where incoming messages should meet before the next reply goes out.