What shipped
Admin dashboard v5.5 consolidates every operator-facing queue into one inbox view. Before this release, dashboard staff moved between separate pages for refunds, approvals, scheme remediation requests and reconciliation exceptions. The inbox replaces those four pages with a single priority-sorted, keyboard-driven view.
Time-to-action on a typical merchant request drops from two minutes (across pages) to under fifteen seconds. The change came from instrumenting the previous workflow and finding that operator decision time was being spent on navigation, not judgement.
Why it matters
Most payment platforms treat the admin dashboard as an afterthought, optimised for a large operator workforce working sequentially through whatever the database returns. That works at the scale of a fifty-person ops team with segmented queues per person. It does not work at the scale of a focused operator group where the next ten things to do can land in any queue.
Fluxa runs the admin dashboard as the operating console, not as a back-office tool. The inbox treats every operator-facing decision as a unit of work with explicit state (open, in-progress, snoozed, resolved), explicit priority, explicit owner and explicit deadline. That is how high-throughput operations are run on every other domain (engineering ticketing, customer support, even the inbox in the merchant’s own email client); it is what the dashboard now does for payment operations.
The detail
Specifically, what v5.5 ships:
- One inbox, four queue types
- Refunds, approvals, scheme remediation and reconciliation exceptions, all priority-sorted, with quick filters per type. The default view is everything across all queues; a quick filter narrows to one type without leaving the page.
- Keyboard navigation
- j and k to move between items, e to resolve, s to snooze, a to assign, / to search, ? to show the full keymap. Mouse interactions work the same way and are documented in the dashboard help.
- Inline context
- Merchant name, transaction reference, relevant ledger entries, related items, all visible without leaving the inbox row. Drill-down opens in a side panel rather than a new page.
- Priority engine
- Priority is computed from item type, item age, merchant size, scheme-rule deadline (where applicable) and overall queue health. Operators can override the priority manually; overrides are audit-logged.
- State explicit on every item
- Every inbox row carries an explicit state with timestamps for state changes. The audit trail is queryable from the dashboard and exportable as CSV for reporting.
- Volume metrics
- v5.5 ships with 124 dashboard files, 204 API routes and 37 test suites, including 12 end-to-end Playwright suites that exercise the inbox flows from operator login through to item resolution.
What follows
SLA monitoring is the next release. Every queue type gets a target time-to-acknowledge, time-to-resolve and overall age; operators see the SLA breach indicator next to each item; reporting rolls up to operator and merchant level. The target is to publish public SLA metrics on the live page once the SLA targets are validated against live data.
Smart triage (suggesting the right operator and the right action based on case history) lands in v5.7. The data layer for it is being collected from v5.5 onwards, so the suggestion engine has real precedent data to train on by the time it ships.
Operator dashboard feedback: support@fluxapay.co.uk. Full operator documentation is in the developer docs under “Dashboard and operations”.