A CRM disqualification record should capture a specific reason, the decision date, the owner, and the evidence needed to interpret the decision. Preserve the original enquiry and campaign so marketing can trace patterns back to the form, targeting, or offer.
Suppose a campaign delivers 20 enquiries and sales closes 12 with the label “bad lead.” That label gives marketing little to investigate. A cluster of spam calls for a form review. A cluster of unsupported requests calls for clearer targeting or landing page copy. A cluster of people who never replied calls for a look at response timing and follow-up.
Use reasons that point to a next action
| Reason | When to use it | What to inspect |
|---|---|---|
| Spam or unsolicited pitch | The message was reviewed and confirmed as irrelevant promotion or abuse | Form controls and traffic sources |
| Service out of scope | The prospect needs a service the team cannot provide | Ad keywords and page copy |
| Region unsupported | The team cannot deliver in the stated location | Geographic targeting and service coverage |
| Budget mismatch | The prospect disclosed a budget outside the supported range | Pricing context and qualification questions |
| Timing deferred | A valid prospect postponed the project | Nurture or follow-up date, where appropriate |
| No response after follow-up | The documented follow-up window ended without a reply | Contact channel, timing and attempt history |
A duplicate delivery belongs in integration reporting. A second genuine request from the same person may still qualify. Keep that distinction so duplicate processing does not distort campaign quality.
Worked example with a campaign review
Assume 12 closed enquiries include five unsupported service requests, three confirmed spam submissions, and four that did not respond. The sales team also has eight enquiries still under review.
Marketing can sample the five unsupported requests and compare their wording with the ad and landing page. If all five sought a packaged subscription while the team offers custom implementation, the campaign copy can be clarified. The three spam submissions go to the form owner for review. The four unanswered enquiries remain visible as a follow-up outcome, with no conclusion about underlying fit.
Keep the eight pending records in the report. Closing the remaining cases may change the reason mix.
Make reasons consistent across representatives
Use a required primary reason when closing an enquiry as disqualified. Add a short note for context when necessary. Give the team examples of borderline cases, such as a buyer who postponed a project versus one who never responded.
Keep the reason definitions stable over a reporting period. If you change them, record the change date or taxonomy version. This keeps month-to-month comparisons interpretable. Limit who can see free-text notes, especially when they include contact details or sensitive project requirements.
What happens when the decision changes?
A prospect can reply after being marked unresponsive. Allow a representative to reopen the enquiry and keep the previous decision in its history. Reporting can then use current status for queue management and decision events for historical process analysis.
Review reasons by campaign, service and landing page at a regular cadence. Assign each recurring issue to the team that can change it and compare later enquiry cohorts after the change. That turns a sales status into feedback marketing can act on.
