Phase 220
The policy layer that tells future reviewers when to reject, correct, hold, route, escalate, or mark a public lead packet review-ready.
Design decision
The queue can have clear decisions before FAEDA builds any live lead runtime. This prevents random sales follow-up, unsafe onboarding, and fake verification claims.
Phase boundary
Phase 220 designs the public lead triage decision policy only. It does not update lead records, contact visitors, assign agents, create CRM tasks, create accounts, verify identity, approve onboarding, activate listings, create orders, create payments, create wallets, or sync data to partners.
Outcomes
6
Runtime
0
Auto ops
0
Decision outcome
Spam, fake, abusive, out of scope, or impossible to handle without unsafe data.
Mark future packet as rejected with a safe reason code and no public accusation.
No blacklist, no punitive scoring, no external reporting, no user contact.
Decision outcome
The packet is useful but missing consent, role clarity, safe message, or area scope.
Prepare a future correction request packet with simple instructions.
No SMS, WhatsApp, email, push, or agent task in this phase.
Decision outcome
Operational follow-up consent is missing, unclear, expired, or revoked.
Place the future packet in consent hold.
No follow-up, marketing, or sales activity.
Decision outcome
The lead has clear intent for customer, shop, supplier, manufacturer, rider, partner, or unsure.
Tag the future packet for the correct role review lane.
No role account, no listing, no onboarding approval.
Decision outcome
High risk, legal concern, sensitive data, duplicate conflict, safety issue, or unclear role ownership.
Flag for supervisor review with risk reason and masked detail.
No direct founder alert, public claim, or emergency action.
Decision outcome
Clean packet, clear role, valid consent label, no sensitive data, no duplicate conflict.
Move the future packet to review-ready for a later approved workflow.
Still no contact, assignment, onboarding, account, or external sync.
Decision matrix
No operational consent
Decision: Hold for consent
Lock: No contact allowed
Sensitive data found
Decision: Reject safely or request correction
Lock: Raw sensitive content stays hidden
Duplicate high risk
Decision: Escalate to supervisor
Lock: No auto-merge
Role unclear
Decision: Request correction or route to unsure
Lock: No account creation
Business claim too strong
Decision: Request correction
Lock: No verification claim
Clean customer interest
Decision: Mark review-ready
Lock: No order or payment
Clean shop interest
Decision: Route to shop lane
Lock: No shop activation
Clean supplier interest
Decision: Route to supplier lane
Lock: No supplier approval
Clean manufacturer interest
Decision: Route to manufacturer lane
Lock: No Business Pro activation
Clean rider interest
Decision: Route to rider lane
Lock: No rider registration
Reason codes
CONSENT_MISSING
Operational follow-up consent is not present.
SENSITIVE_DATA
Public packet contains blocked private or financial data.
ROLE_UNCLEAR
The requested FAEDA role is unclear or mixed.
DUPLICATE_RISK
Similar lead pattern needs human duplicate review.
OUT_OF_SCOPE
The request is outside public lead capture scope.
UNSAFE_MESSAGE
The message includes abuse, threat, or unsafe instruction.
NEEDS_SUPERVISOR
Reviewer cannot safely decide alone.
REVIEW_READY
Packet is clean enough for a later approved review workflow.
Priority policy
CNIC, bank, password, OTP, medical, payroll, invoice, exact address, or file upload reference appears.
Block or correction gate
Legal, safety, abuse, duplicate conflict, fraud risk, or public claim risk.
Escalate to supervisor
Valid consent but role, area, or message needs interpretation.
Route, correct, or hold
Clean, clear, consented, and role-scoped packet.
Mark review-ready
Audit fields
Blocked automation
Reviewer duties
Intake reviewer
Can apply obvious hold, correction, route, or safe rejection draft.
Safety reviewer
Owns sensitive-data and unsafe-message decisions.
Duplicate checker
Owns duplicate risk and possible future merge review.
Role router
Maps lead to customer, shop, supplier, manufacturer, rider, partner, or unsure lane.
Supervisor
Approves high-risk decisions and review-ready policy exceptions.
Founder observer
Sees aggregate triage health, not raw private lead content.
Escalation rules
Acceptance checklist
Next phase
Next we design the approval gate before any future lead can be assigned to a role lane, FAEDA Team owner, reviewer, or support path.
Open Phase 221