Skip to content

Trusted WhatsApp publication

Active numbers in Knowledge Base > Kiriman WhatsApp default to direct publication. Existing trusted numbers receive this permission through an additive schema migration. This does not grant dashboard login or admin role. Admins can turn off Langsung terbit setelah judul diisi for a specific contributor to retain the reviewed-proposal workflow.

Flow: send a natural-language addition, a forwarded text message, or a legacy knowledge command; provide content if asked; for an addendum, select the intended current source; reply with a single-line title of 3–300 characters. The bot then publishes the entry without a separate administrator review. Acknowledgments and publication do not require a model call. Balas batal cancels the pending operation. Pending flows expire after 15 minutes or when the original case is closed. Existing pending proposals are not automatically published retroactively.

Permissions are rechecked at each message and locked during publication. Revoked/disabled senders cannot complete a pending flow. The original and final-title message IDs remain associated through audit records. Duplicate deliveries do not create duplicate entries. A title is mandatory even for forwarded/legacy input; a yes/no confirmation alone is not accepted as a title. Automatic publication retains the same source eligibility, version, expiry and overlap checks as reviewed publication. A source changed after selection/title prompt must be selected again. No text is silently truncated to fit: new content or the combined original-plus-addendum answer must fit the existing 3,000-character publication limit.

Addenda publish a replacement version preserving the original source text and linking a replaces relationship. The published answer retains the original content with the supplied addendum. The operation logs the verified sender, submitted content, chosen title, old/new source content and publication result. Admins can edit or withdraw published knowledge through existing controls. Automatic topic categorization follows the existing background quota policy.

Tests include title enforcement, invalid confirmation, idempotency, forwarded/legacy handling, revocation, source-change rejection, preservation/replacement of old sources and a signed-webhook/worker/dashboard/retrieval journey. The manual review tests explicitly opt into per-number review mode.