Carrier contact release
Review the release, not the message.
This gate decides whether controlled contact may proceed to execution evidence. It still does not send a message, place a call, or assign a carrier.
1
COA
6/6
Checks
0
Released
Current status
Select an approved offer-request packet and decide whether controlled contact release may proceed to execution evidence.
1. Approved queue
Start only from COA packets.
2. Movement snapshot
What may be shared later.
COA-DEMO-CUSTOMER-ORDER
Customer daily order
Ali Sabzi Wala / local shop to Mohallah family doorstep
12 kg
Payload
Bike
Carrier fit
Verified Mohallah Rider
FAEDA app masked request · Selected carrier only · Use LBG cost target as planning ceiling only
3. Release mode
How contact may be released later.
Can share later
movement title · lane · payload band · pickup window · delivery window · proof needed
Blocked from sharing
customer identity · exact address · final payout · wallet/payment data
4. Decision
Approve, hold, or reject release path.
5. Release checks
Confirm before release packet.
Runtime locks
Release review still does not contact anyone.
Carrier contact release gate is not contact execution.
Approved packets only move to the execution-evidence gate; they do not send a message, place a call, or create a dispatch by themselves.
No exact phone, address, customer identity, wallet, payable, or settlement data is exposed from this gate.
No carrier is assigned, no dispatch task is created, and no movement starts from release review.
No pickup, route tracking, GRN, inventory, invoice, payment, ledger, payout, or settlement is created.
Held and rejected release packets must stay blocked from offer-request execution evidence.
Recent release packets
Local release evidence.
Next locked step
Carrier Offer Request Execution Evidence.
The next gate records the actual app send, WhatsApp send, or ops call attempt with evidence. Only there does the contact attempt become real.
Continue to execution evidence