Phase 222
The gate that decides whether a future assigned public lead may be contacted, through which channel, with what script, and under which consent.
Design decision
This phase keeps FAEDA disciplined: an assigned lead can only move toward contact when consent, channel, script, timing, masking, and reviewer authority are all clean.
Phase boundary
Phase 222 designs the lead contact permission gate only. It does not call, message, email, notify, visit, assign CRM tasks, create accounts, verify identity, approve onboarding, activate listings, create orders, create payments, create wallets, create commissions, or sync data to partners.
Channels
6
Sends
0
CRM
0
Permission outcome
Assignment is approved, consent matches the channel, message purpose is narrow, and no privacy hold exists.
Prepare a future contact draft with channel, purpose, script, expiry, and reviewer evidence.
No send, call, WhatsApp, SMS, email, push, visit, or CRM task in this phase.
Permission outcome
Consent is missing, expired, vague, channel-mismatched, or captured under older wording.
Mark the packet as needing a future consent refresh path.
No follow-up contact until the refresh method is approved later.
Permission outcome
The visitor approved one channel but not another, such as email but not phone.
Restrict any future contact draft to the approved channel only.
No channel switching, fallback calling, or field visit workaround.
Permission outcome
The proposed contact time violates quiet hours, prayer-sensitive timing, local norms, or visitor preference.
Hold contact until a safe time window is available.
No urgent-looking message unless a real emergency workflow exists later.
Permission outcome
Sensitive, legal, financial, health, identity, child, harassment, or safety content is involved.
Escalate to privacy, compliance, or supervisor review before contact may be drafted.
No raw content to FAEDA Team, sales, partner, or founder observer surfaces.
Permission outcome
The contact purpose is sales pressure, spam, unsafe, out of scope, or not tied to the original lead intent.
Reject the contact proposal with a safe reason and keep the lead packet protected.
No blacklist, punitive scoring, or public accusation.
Channel rules
Only if phone contact consent exists, identity-safe script exists, and call window is approved.
No cold call, repeated call, recorded call claim, OTP request, or pressure script.
Only short consent-safe notice with no sensitive details and clear opt-out wording.
No marketing blast, deep link with private token, payment request, or fake urgency.
Only if WhatsApp consent is present and message is plain, minimal, and role-scoped.
No group add, image/doc request, voice note pressure, catalog spam, or payment link.
Only if email consent exists and the body avoids private internal details.
No attachments, exports, invoices, credentials, account links, or hidden tracking claim.
Only after a future account/session exists and backend confirms customer scope.
No notification to anonymous lead, no fake account, no cross-customer exposure.
Only as a future approved field-support workflow with masked context and area scope.
No unapproved visit, no exact-address exposure, no random freelancer handoff.
Consent states
CONSENT_VALID_CHANNEL_MATCH
Consent exists for the exact channel and purpose.
CONSENT_MISSING
No operational contact consent exists.
CONSENT_EXPIRED
Consent exists but is too old for safe contact.
CONSENT_REVOKED
The visitor opted out or withdrew consent.
CONSENT_CHANNEL_MISMATCH
Consent exists for a different channel only.
CONSENT_PURPOSE_MISMATCH
Consent exists but not for this role, message, or follow-up purpose.
CONSENT_SENSITIVE_HOLD
Sensitive data requires privacy review before any contact draft.
CONSENT_ACCOUNT_REQUIRED
The channel requires a future authenticated account/session first.
Contact matrix
Approved assignment plus valid phone consent
Permission: Permit phone contact draft
Lock: No call placed yet
Approved assignment plus WhatsApp-only consent
Permission: Limit to WhatsApp draft
Lock: No phone fallback
Consent missing
Permission: Require consent refresh
Lock: No message
Consent revoked
Permission: Reject contact request
Lock: No recontact
Sensitive data in lead packet
Permission: Escalate contact risk
Lock: No raw context exposure
Quiet hours active
Permission: Hold for quiet hours
Lock: No urgent wording
Purpose changed from original intent
Permission: Require consent refresh
Lock: No sales expansion
Multiple role lanes
Permission: Separate contact drafts
Lock: No shared private script
Partner/compliance claim
Permission: Compliance review first
Lock: No legal/financial promise
Clean low-risk support query
Permission: Permit contact draft
Lock: Expiry and opt-out required
Message policy
Permission bands
Assignment approver
Can request contact permission review after Phase 221 approval.
Contact reviewer
Can approve or reject a channel-specific contact draft policy.
Privacy reviewer
Can mask sensitive context or block contact if privacy risk remains.
Compliance reviewer
Can approve regulated, partner, legal, bank, government, or medical contact language.
FAEDA Team lane owner
Can receive only approved future contact task context, never raw private data.
Founder observer
Can see contact health and risk counts, not raw message bodies or contact details.
No one in this phase
Can send, call, visit, verify, onboard, create CRM work, create accounts, or collect documents.
Contact packet fields
Frequency and timing rules
Revoked consent, sensitive hold, blocked data, legal risk, abuse risk, or unsafe message purpose.
Reject contact request or escalate.
Partner, government, financial, medical, legal, employment, or high-value business source contact.
Compliance or supervisor checker before draft permission.
Valid consent but current time is quiet, culturally sensitive, too late, or outside visitor preference.
Hold until allowed contact window.
Clean assignment, exact-channel consent, safe purpose, safe script, and opt-out wording.
Permit future contact draft with expiry.
Blocked automation
Review stops
Acceptance checklist
Next phase
Next we design how future contact outcomes can be reviewed safely without creating sales pressure, fake conversion, or account/onboarding truth.
Open Phase 223