Notification & Support Roadmap
Comprehensive plan for proactive monitoring without disrupting current processes.
Phase 1 — Unified admin alerts
Completed- •Keep the existing notification bell and extend it with ticket sales, sponsorship receipts, crash reports, support tickets, and login issues.
- •Store important alerts as real records so they can be reviewed later, not just seen once in the dropdown.
- •Avoid replacing current flows; add alert creation as an extra step after each successful process.
Phase 2 — Automatic support ticket creation
Completed- •Create support tickets automatically for crashes and login problems that are not caused by bad passwords.
- •Deduplicate repeated login failures for the same person over a short time window so staff are not flooded.
- •Link notifications back to the support ticket page for quick follow-up.
Phase 3 — Login issue capture
Completed- •Capture artist, partner, member, and staff login failures that appear to be redirect/session/process issues.
- •Show the person a reassuring message that the issue was reported automatically and staff will follow up.
- •Include the affected email, account type, page, and redirect target in the support ticket context.
Phase 4 — Operations hardening
In Progress- •Expand alert creation to more backend functions over time, including payment exceptions and operational warnings.
- •Add ticket status workflow and assignment if needed later without changing the capture pipeline now.
- •Use the support ticket list as the central place for triage.