Skip to main content

    Operations

    Separate spam from real generator requests

    Use evidence to separate spam from real requests. Keep unknown leads open for review and record why a record was excluded.

    By SwiftSocial3 min read

    Keep spam, staff tests, repeats, real poor-fit requests and unknowns separate. Use evidence before you exclude a generator request. No answer, a low budget or an outside-area home is not proof of spam.

    Save the reason, reviewer and date. A label should help fix the right issue, not make the lead count look better.

    On this page

    Name the issue you can see

    A clear sales pitch to your office is not a homeowner quote request. A staff test is not a new customer. A second form from the same buyer is a repeat, not two new leads.

    Some records are less clear. A typo, a short name or a call with no answer may still come from a real person. Mark these for a check rather than a quick purge.

    Use separate review labels

    Keep spam, repeat, test and outside-area requests apart. Each one points to a different fix. A real buyer outside your area may need clearer ads. A staff test may need a cleaner test process.

    Do not make the lead source look better by using one broad bad-lead label.

    • Clear spam or sales pitch.
    • Known staff test.
    • Repeat request from a known lead.
    • Real request we cannot serve.
    • Unknown and needs a check.

    Keep the reason with the row

    Save the received date and the original source. Add a short reason, the check date and the reviewer. Use only the private detail needed for that check.

    Keep a way to reverse a wrong label. If the buyer later replies, the next person should be able to see what happened.

    Show what the count leaves unknown

    This made-up batch shows why one “bad lead” label can hide useful facts. It is a count exercise, not a client result.

    Keep the raw ten submissions beside the business count. If an unknown later proves real, update its label with the new evidence. Do not erase the earlier review.

    Check the pattern before a fix

    Look at the source and date of confirmed bad records. One bad request does not prove an ad is broken.

    Share a small, clear pattern with the site or ad owner. Keep raw records and the corrected business count distinct. This review does not call for sending, changing or replaying platform events.

    Sources and further reading

    Sources checked .

    Back to the blog

    Use honest lead counts

    Bring the lead labels and the unknowns your team needs to resolve. Ask how SwiftSocial’s ads, pages, follow-up and sales training work. See if the offer fits your firm.