01
Run the matching how-to workflow
Most incidents are setup or role-plan mismatches, not backend outages.
Clubster Status
Operational snapshot and escalation rules.
Use this page before opening support tickets. It helps teams separate platform incidents from setup issues and keep support traffic focused on true blockers.
Target: 99% support solved via website
Technical support: support@nuvexonix.com
Club/partner topics: partner@nuvexonix.com
Service Snapshot
Current platform signal.
| Component | Status | What to verify if blocked |
|---|---|---|
| Clubster app core flows | Operational | App version, network state, and account role permissions |
| Business plan and quota checks | Operational | Active plan, quota balance, and role ownership in account setup |
| Promotion and boost workflows | Operational | Cooldown windows, campaign slot timing, and correct deeplink target |
| Notifications and push delivery | Operational | Follower state, opt-in permissions, and message relevance/timing |
Escalation Sequence
Follow this sequence before support email.
02
Cross-check FAQ constraints
Use FAQ for known behavior around quotas, cooldowns, and account actions.
03
Check latest release updates
Recent releases can change expected behavior in promotion and visibility modules.
04
Escalate with full context
Provide role, app version, timestamp, club/event identifiers, and exact steps to reproduce.
Clear process keeps support fast and accurate.
Support ticket template
What to include in one message.
- Role: user, owner, or event manager.
- App + version + device/OS.
- Exact timestamp and timezone.
- Club ID/event ID or deeplink if available.
- Expected behavior vs actual behavior.