Settlement exception
CriticalFinance question tied to SET-MAY-004.
Merchant support
Resolve onboarding, wallet, campaign, and settlement questions.
Support tickets route through the existing backend API and are ready for status updates, admin review, and audit logs.
TodayDemo data
QR training
TrainingStore operator needs redemption guidance.
Wallet setup
OnboardingMerchant owner needs address confirmation.
Support SLA96%
Demo tickets inside target
Open tickets9
Merchant support items awaiting action
Critical tickets1
Settlement-related escalation
Average response4h
Sample support response time
Workspace records
Support queue
Support records are shaped for backend persistence and admin review.
| Record | Owner | Status | Value | Next action |
|---|---|---|---|---|
| SUP-104 | Main Street Store | Pending | Settlement | Finance response |
| SUP-108 | Canal Walk Kiosk | Active | QR training | Schedule call |
| SUP-111 | Somerset Outlet | Completed | Campaign setup | Archive |
| SUP-113 | Online Store | Required | Wallet | Verify address |
Performance shape
Operating signals
Demo indicators show the decision model before production analytics are connected.
Open24%
Demo tickets
In progress42%
Demo tickets
Resolved34%
Demo tickets
Secure intake
Create support ticket
This form posts to `/api/support` and safely validates even when the database is not configured.
Production focus
What this page helps merchants control
Each workspace area is designed around repeat-purchase growth, operational clarity, and safe approval flows.
Escalation paths
Separate onboarding, wallet, campaign, and finance support requests.
Operator context
Tickets should include merchant, store, wallet, and campaign references where relevant.
Audit readiness
Production support status changes should be linked to user roles.