43 lines
1.7 KiB
Markdown
43 lines
1.7 KiB
Markdown
---
|
|
id: TASK-7
|
|
title: 'Add lead qualification, deduplication, and blacklist handling'
|
|
status: To Do
|
|
assignee: []
|
|
created_date: '2026-06-03 19:13'
|
|
labels:
|
|
- mvp
|
|
- leads
|
|
- quality
|
|
dependencies:
|
|
- TASK-6
|
|
references:
|
|
- PRD.md
|
|
priority: high
|
|
ordinal: 7000
|
|
---
|
|
|
|
## Description
|
|
|
|
<!-- SECTION:DESCRIPTION:BEGIN -->
|
|
Implement the rules that turn raw business discoveries into usable lead states. Leads should be classified by contact availability, website potential, duplicate risk, existing contact history, and manual blacklist matches before any audit or outreach work starts.
|
|
<!-- SECTION:DESCRIPTION:END -->
|
|
|
|
## Acceptance Criteria
|
|
<!-- AC:BEGIN -->
|
|
- [ ] #1 Leads with no usable email are placed in Kontakt fehlt while preserving phone and source data
|
|
- [ ] #2 Generic business emails are preferred and named emails are accepted only when explicitly found as business contact addresses
|
|
- [ ] #3 Hard duplicates are detected by domain, Google Place ID, or email; probable duplicates are flagged by name plus address or phone
|
|
- [ ] #4 Manual blacklist entries for domain, email, phone, company name, and Place ID are enforced during discovery and review
|
|
- [ ] #5 Priority values Hoch, Mittel, Niedrig, Zurückstellen, and Gesperrt are assigned or editable with clear reasons
|
|
<!-- AC:END -->
|
|
|
|
## Implementation Plan
|
|
|
|
<!-- SECTION:PLAN:BEGIN -->
|
|
1. Add blacklist CRUD in Convex and dashboard UI.
|
|
2. Implement email/contact extraction result fields and Kontakt fehlt transitions.
|
|
3. Add hard and probable duplicate matching rules.
|
|
4. Add priority assignment rules based on website/contact signals.
|
|
5. Surface reasons and source data in lead detail and run logs.
|
|
<!-- SECTION:PLAN:END -->
|