Skip to content

WhatsApp Knowledge Base submissions

Knowledge Base, Kiriman WhatsApp contains the contributor allowlist, incoming proposals, admin review, and before/after history. Administrators can add, read, edit numbers and names, enable or disable, and delete contributor numbers. Deleting permission preserves earlier submissions and audit events. The allowlist starts empty.

Contributors forward text privately to the helpdesk, send /pengetahuan followed by a title and source text, or send /adendum ID followed by additional information for an existing source passage. Plain forwarded text is detected from the WAHA forwarding flag. Unmarked messages require the explicit command. Direct group ingestion remains excluded by the existing private-message webhook validation. Sender phone numbers determine authorization.

Incoming proposals are sanitized, deduplicated by WhatsApp message ID, and held for admin approval. The original sender, phone, submission time, forwarding flag, parent passage ID, and parent fingerprint are recorded. The submission is committed before its helpdesk acknowledgement is queued.

Reviewers edit the proposed title and answer, remove private details, record a reason, and approve or reject. Approved new items become published articles. Approved addenda create a combined replacement passage and a source authority relation. The original passage and its other PDF sections remain traceable through the before/after audit history. A changed, missing, expired, or superseded target cannot be overwritten through a stale proposal. The contributor must submit an addendum against the current source.

This intake handles text. The existing PDF upload workflow handles source files. Source permissions do not grant dashboard access or administration privileges.

For sender names, WEBJS notifyName and pushName fields populate placeholder profiles. User-provided /nama Name, nama saya Name, and panggil saya Name set an explicit preferred name. Forwarded message bodies cannot change the sender’s name. Explicit preferred names and admin-maintained profiles take precedence over later WhatsApp profile updates. Names are display data and do not affect authorization. Chat details identify the name source.

Verification uses tests/test_knowledge_intake.py and scripts/check_knowledge_intake_browser.py. Browser checks use mock recipients and perform no live publication or WhatsApp sends.