YTF Chat Receipts
Viber / LINE → safe owner action → ledger → signoff
Loading chat receipt workflow…
No raw messages, no sends, no database extraction. This page creates one context-only receipt from a human export, screenshot packet, or prepared visible-window review.
Default packet now
Start here for daily YTF knowledge flow. Copy the safe Viber request, get one six-bullet owner packet or “Not reported,” then draft one receipt below.
Loading default packet request…
Packet → receipt helper
Choose the exact Viber/LINE lane, then paste only the already-safe six-bullet owner packet or “Not reported.” This is browser-only: it fills the receipt form without uploading the packet or using LLM/computer-use.
Paste a safe packet to fill the receipt form locally.
Four-step chat SOP
Low-cost chat ingestion
Default path: human export, daily summary, or screenshot packet first. Computer-use is only an exception when one exact chat lane is visible and the composer is empty.
Loading low-cost chat ingestion contract…
Ask lane owner
Copy one short request to the lane owner. The owner sends a summary, redacted screenshot/export packet, or “Not reported”; then `/chat` turns it into a safe receipt.
Loading lane-owner packet request…
YTF Managers daily packet
Default Viber lane. Ask for six short business bullets max, not raw chat. “Not reported” is valid when proof is missing.
Loading YTF Managers daily packet…
Cheap computer-use preflight
Use this before asking any agent to look at Viber or LINE. If the lane is not exact and the composer is not empty, stop and do not use computer-use.
Draft safe chat receipt
Use this after you or an agent reviewed a human export, screenshot packet, or prepared visible window. Do not paste message text here; write the business meaning only.
Choose one chat lane and draft a safe receipt.
Exact chat lanes
Allowed vs blocked
Chat receipts are context only. Use /sources for all source lanes, /ledger for acknowledgement continuity, /signoff for authority, and /brief for manager-safe sharing.