Skip to main content

    Operations

    Handle repeat generator lead requests

    Join repeat requests without losing the first source or date. Keep separate jobs apart and give the buyer one clear owner.

    By SwiftSocial3 min read

    Match the person and the job before you join repeat generator requests. For the same job, keep one lead. Save each call or form with its own date.

    Keep the first known source and latest promise. The goal is a clear job history, not a tidy screen that loses useful facts.

    On this page

    Check the person and the job

    Look for a matching number or email, then read the job notes. A shared surname alone is not enough. Two people in one home may use different names for the same project.

    The same customer may also have a second home or a new job. Keep those projects distinct. A contact and a job are not always the same thing.

    Keep the first record intact

    Preserve the first known request date and source. Add later calls or forms as new touches. If a buyer gives a different account of how they found you, keep that note too.

    Do not overwrite a known ad source with direct just because they called today. Do not invent an ad source when all you have is their memory.

    Choose who owns the next reply

    Before staff act, check the last promise and owner. Stop two people from sending different answers about the same visit.

    If the records cannot be safely joined in your system, cross-link them with a note. Ask the system owner to review the match. Keep a record of what was joined and why.

    • Same person checked.
    • Same job checked.
    • First date and source kept.
    • Later touches kept.
    • One next owner named.

    Know when the records must stay apart

    The same phone or email may serve more than one job. Check the site and request before you join records.

    Before a join, check open tasks and contact choices too. Ask the system owner to prevent two replies to one request. Keep any stop note in view. If the match is unclear, link the two records with a note. Leave the merge for review.

    Check the count after the merge

    A repeat form should not create a second sold job or payment. Read the open stage after a merge and check that nothing was lost.

    Review a few matches with the office. If staff often guess, add a clearer job reference. Do not delete raw history or rewrite tracking events as part of this desk check.

    Sources and further reading

    Sources checked .

    Back to the blog

    Keep one clear job history

    Bring the repeat-request gap without private customer details. Ask how SwiftSocial’s ads, pages, follow-up and sales training work. See if the offer fits your firm.