Dashboard accounts and received cases
Scope: helpdesk dashboard accounts only. No App Hub identity/password changes or SSO integration.
Administrator workflow
Section titled “Administrator workflow”Open Anggota & akses → Kelola to edit a name, email, WhatsApp number, role and access. Save the profile first. Email is an administrator-maintained contact address; it is not a verified email login or automatic proof of identity.
Choose Kelola login dashboard to create/edit a username and enable/disable dashboard login. Only active administrators can have enabled logins; granting the member role alone does not create credentials. Newly created logins have an unknown random initial password. Save, then choose Buat tautan reset kata sandi so the account owner can choose a password.
Reset links are single-use, last 30 minutes and are invalidated by issuing another link, changing the email/phone/username, disabling the account, changing its password, or removing administrator access. Up to five links per target per hour. Password reset revokes existing target sessions. Username edits and login disabling revoke sessions too. An administrator cannot disable their own login or remove their own active admin role. Password hashes and API credentials are never returned to the management UI.
Copy/share controls open the administrator’s WhatsApp or email client with a draft addressed to the profile contact. The administrator reviews and sends it there. This does not automatically dispatch email/WhatsApp or configure SMTP. Always verify the recipient before sharing. The password itself is entered only on the reset page, never chosen or displayed by the admin.
The raw reset token exists only in the response/browser and chosen sharing application; PostgreSQL stores its SHA-256 hash. The link uses /reset#TOKEN, so the token is not in the HTTP request path/query; the page removes it from the address bar on load. It sends the token in an origin-checked POST body. No third-party scripts/analytics are used. Reset endpoint access does not grant a login session. Logs and audits exclude reset tokens/passwords. Common reset URL and credential patterns are sanitized if pasted into a helpdesk conversation.
Received conversations
Section titled “Received conversations”Percakapan & kasus lists received cases, sender name/contact data, message count and last activity. Open one for its transcript, current user profile, response-processing state and related tickets. Ticket detail links back to the case. Older messages load in pages of 100. Search matches subjects, received message text, names, phone numbers, emails or case number.
A bot-managed case automatically closes after 24 hours without a new message. Cases assigned to human support remain open until a staff member closes them or returns them to the bot, subject to archive retention. The worker checks idle sessions about once a minute, and the next incoming message independently checks the timeout before starting a fresh case. Model context is scoped to the case. Existing conversations remain archived under the 30-day retention policy. This is conversation grouping, not automatic semantic separation of simultaneous issues. Staff can close/reopen cases. Ticket creation from a received message associates it with that case; unrelated historical/manual tickets are not attached by guesswork.
Accepted requests are archived in the enqueue transaction, before AI processing. Completed replies are saved with the job transaction. Failed jobs retain received text with a failed-processing state. sent means WAHA accepted the outbound request, not proof of delivery/read receipt; not_sent means that send was not accepted or outbound was disabled. No automatic send retry was added.
Each archived message expires after 30 days. Empty case metadata expires 30 days after the last received message; cleanup runs hourly. Expired data is excluded from dashboard reads before cleanup. Ticket records remain and their case association is cleared if the case expires. Backup retention follows the existing backup policy. Short-term AI memory remains separate: 15 exchanges, 24-hour expiry, 75,000-character prompt budget. Full archives and profile contact data are not automatically sent to Google. Raw screenshot bytes/media URLs are not archived; only a screenshot marker and sanitized textual explanation remain.
Capture starts with new requests after deployment; previously cleared message bodies cannot be restored. Case reads and changes, profile changes, account updates and reset-link issuance are audited without transcript or secret contents. All management data/endpoints require a current admin session; mutation endpoints enforce origin and CSRF checks. The public reset page exposes no user/case list.
Validation and rollback
Section titled “Validation and rollback”The isolated PostgreSQL suite covers reset single use/rotation/expiry, hashed-only tokens, session revocation, disabled roles/accounts, self-disable prevention, origin/CSRF, profile emails, case acceptance before processing, member isolation, ticket association, redaction, inactivity grouping, closure, expiration, deduplication and pagination. Browser fixtures use a separate temporary database and exercise profile edits, account creation, reset-page completion/login, sharing controls without sending, case viewing/closure and mobile widths.
Only dashboard, API and worker require recreation. WAHA, PostgreSQL and the shared reverse proxy stay running. Before rollout, database backup and source copy are taken. Rollback: restore code-backups/before-management/app on the server, rebuild and recreate only these three app services. Keep additive schema and data. Rolling back to old code also rolls back enforcement of the new dashboard enabled flag; block affected member identities before an emergency rollback if that enforcement is needed.
Administrator account list/create/edit/delete is now also available under Akun administrator. See pdf-knowledge.md for lifecycle and deletion semantics.
Balasan petugas
Section titled “Balasan petugas”A WhatsApp user can type bicara dengan petugas. The case enters Percakapan & kasus → Handoff petugas and the bot acknowledges the request once. An administrator can also claim an open WhatsApp case from its detail screen.
Open a conversation in Percakapan & kasus. On a desktop the list stays beside the thread. On a phone, use Kembali ke daftar to switch chats. Use Ambil kasus, review the messages, then write a reply and select Kirim balasan beneath the thread. Linked tickets and profile actions are under Rincian kasus. The case shows whether WAHA accepted the reply. Lepas kasus returns ownership to the queue. Aktifkan kembali bot lets the bot answer new messages. Messages received while staff were handling the case remain in the transcript for staff.
The first reply target is two working hours, Monday through Friday, 09.00 to 17.00 WIB. This provisional calendar has no holiday exceptions. The clock starts with the request or a manual takeover and stops at the first staff message accepted by WAHA. The elapsed wait shown in the case includes time outside staffed hours. The due date accounts for staffed hours.
A failed or uncertain delivery leaves the clock running. Review the transcript before sending a replacement. The worker records its delivery claim before contacting WAHA, so a worker restart cannot automatically resend a message whose delivery is uncertain.
Balasan dari aplikasi WhatsApp
Section titled “Balasan dari aplikasi WhatsApp”WAHA uses the signed message.any webhook for the linked session. A message sent by a person from that account pauses the active case, records the reply, and completes the first-reply clock. The app ignores WAHA API echoes and remembers IDs returned by its own sends. The bot also checks recent WhatsApp history before it sends. If the check fails, the bot holds the reply and the case shows that it was not sent.
Claim the case in the dashboard before replying when both staff and the bot are active in the chat. The dashboard coordinates ownership with the bot’s final send. A phone send and a bot send already in flight can cross before WAHA reports the phone message. Use Aktifkan kembali bot after the handoff to allow replies to new messages.