Step 4 · Delivered · Operations
Requests
Changes and fixes from any channel.
Every workflow is custom built for you.
Requests
5 this week · 3 open
AIPA agent
3 requests opened from WhatsApp this week2 urgent, both fixed
| No. | Request | Project | Type | Status | Via | Due |
|---|---|---|---|---|---|---|
| R-552 | Add export button to invoices page | P-115 | Change | In progress | 3 Oct | |
| R-551 | Login fails on one phone | P-117 | Urgent | Fixed | 2 Oct | |
| R-550 | New article topic list for November | P-114 | Change | Queued | 9 Oct | |
| R-549 | Wrong currency on one receipt | P-115 | Urgent | Fixed | 1 Oct | |
| R-548 | Add Bahasa to contact page | P-116 | Change | In review | Meeting | 7 Oct |
How it works ↓
The screen
What it does
What your team and the agents do on this screen.
- 01From any messageWhatsApp, email or a meeting note becomes a request.
- 02Owner and dateEvery request has both.
- 03Urgent firstUrgent fixes jump the queue.
- 04Closed loopThe client is told when it is done.
Analytics
What it measures
Reported on the screen and in the morning brief.
- 01Requests opened and closed per week
- 02Time to close, urgent vs change
- 03Requests per project
Accurate data
How we keep it right
Every number traces back to where it came from.
- 01One request per messageDuplicates are merged, not counted twice.
- 02Source keptEvery request links to the message it came from.