Active Requests
Tickets currently in progress
| No | Code | Group | Title | Age |
|---|
QC Pending per Group
Finished tickets not yet checked per group
| Group | Not checked |
|---|
Requests
Every incoming chat lands here — CHECK (AI answers), PROBLEM (issue), and CHANGE (developer handles, then Finish/Cancel).
| Code | Group | Title | Action | Status | Type | Closed |
|---|
WhatsApp Messages
Incoming messages processed by the agent
| ID | Time | Group | User | Message | Decision | Request | ✓ |
|---|
Outgoing messages
Customer messages after the bot rewrites them. SKIPPED = dropped acknowledgement (the batch already had the real answer).
| ID | Time | Group | Request | Status | Message |
|---|
Users
WhatsApp sender names. Salutation = how the bot addresses them (pak, bu, ci, koh, kak, mas, mba); empty means none. Mark Developer so the bot stays quiet when they reply, unless mentioned.
| Number | Salutation | Name | Developer | Updated |
|---|
Bot trigger words
The bot only answers when addressed to us: mentioned, one of these words appears, or a Developer is tagged. Separate words with commas.
Groups
Each group links to one ERP. Check 24 hours to serve all day, otherwise active 07:00–23:00 WIB. Changes save automatically.
| Group / JID | Silent | 24 hours | Active | ERP access key |
|---|
System Health
Real-time service status
Prompts
Edit the markdown prompt files the agent uses (ack-variants, clarification questions, session messages, wrap-up, maia). Changes apply on the next message — no restart needed.
Word circulated (short style)
Outgoing words are randomly shortened to one of the variants (±70%) or kept as-is (±30%) for a casual look. Doc numbers, @tags, URLs, and code are never touched. Empty = off.
Activity Logs
Agent activity trail
| Time | Action | Source | Metadata |
|---|
Edit Markdown
Word circulated (short style)
| Word | Alternatives (comma separated) |
|---|