The Same Person Enquires Twice: One Lead, a Timeline Line and a Fresh Call

Why does a second enquiry matter?

Someone who fills in a form twice has told you something. Either the first call never came, or they are still deciding and came back to you. In both cases they are more interested than a lead who filled in one form and went quiet. Treated badly, the same event does damage: two cards on the board, two reps phoning the same person, or a closed lead that stays closed while the person waits for an answer. We have not measured how often it happens, so we will not give you a figure. We built the rule because the mistake is easy to make.

How does MAJ Leads know it is the same person?

Every source goes through one intake step. The phone number is cleaned to the UAE format first, so 0501234567, +971 50 123 4567 and 971501234567 are one number (our guide to UAE numbers in forms covers the formats). The database then keeps one lead per workspace and phone number, and the check happens inside the database, so two submissions arriving in the same second cannot both create a lead.

A lead can arrive with an email and no usable phone, for example when a form's phone box was optional. That lead is kept, in a "needs phone" stage, and merged on the email address. If the same person comes back later with a phone number, the number is filled in on the lead they already are.

What happens when the repeat arrives?

For a lead that enquires again through a live enquiry source (a website form, Meta, Google, a chat, a hand-typed entry, a forwarded email or a paste-in link), the database function that handles it does these things, in order:

1. Checks the exits. A deleted lead, a lead marked do-not-call, a lead who replied STOP, and a number on the workspace's don't-call list are never reopened.
2. Skips a second task. If the lead already has a call due or in progress, no new one is made. The repeat is still recorded.
3. Makes one fresh call due, scheduled by the workspace's working hours. In a team workspace it goes to the person who held the lead last, if they are still on the team, and to the normal pick if not (the sticky owner rule).
4. Reopens a closed lead. A lead sitting at not reached, not interested, lost or nurture moves back to contacting when the fresh call is made.
5. Keeps the new question. The lead's "ask" becomes the new message, and the timeline event keeps the previous one and the stage before.

The rep sees a small tag, "Came in again 2 hours ago", on the call card, in the call list and on the leads list. Nothing else changes on screen: it is the same lead with the same history, so the rep opens one timeline and sees the first enquiry, every attempt and the second message together.

When does it stay quiet?

The first row is worth a link out. Google's own webhook page says a lead is "not guaranteed to be delivered exactly once" and tells you to use its lead ID to dedupe (Google Ads webhook guide). Our guide to a Meta lead that never arrived covers the same idea from the other side: platforms send again, so an intake step must treat a repeat delivery as safe. A repeat delivery and a person who comes back are two different events, and only the second should put a call on a rep's list.

What if the number came from an import and sits on the national do-not-call register?

A number brought in by spreadsheet import that appears on the national register gets no follow-up from MAJ Leads, because nobody asked to be contacted. If that person then enquires on their own through a live source, the lead is stamped as having reached out themselves, and the import hold on follow-up is lifted. That is a product rule, not a legal opinion, and whether a given call is a marketing call is a question for your lawyer. Our guide to your don't-call list and the DNCR goes into it.

What should you do with the tag?

• Read the new message before you dial. It is the most recent statement of what the person wants.
• Call first and say you saw their second message. Nobody minds hearing that.
• If the number belongs to someone who keeps resubmitting, log the result as normal. Do not delete the earlier lead to tidy up, because the timeline is the record.
• Do not send an apology for "duplicates". There is nothing to apologise for: they asked twice and got one reply.

Where does this leave your team?

One person, one lead, one history, and a repeat enquiry that puts a call on the list instead of a duplicate on the board. See how it works and pricing.