Skip to main content
M
MoonTech
Communication

Notifications & Push

Notification campaigns, audience filters and direct send

6
Sections
3
Panels
Admin ConsoleClub PanelUser Portal
Service Overview

Notifications keep members, staff, and operators informed — push to mobile, in-app inbox on portal, and optional SMS/email depending on club configuration. Platform admins broadcast ecosystem messages; club managers target segments; members read and manage preferences from the portal Notifications tab.

Effective notification strategy balances engagement with fatigue — use categories, respect opt-out where required, and test on a staging member before mass send.

1
Section 1 of 6

Core concepts

ConceptMeaning
**Notification**Message with title, body, optional deep link action.
**Channel**Push, in-app, SMS, email — availability varies by club setup.
**Segment**All members, level, group, or custom filter.
**Scheduled send**Future datetime for campaigns.
**Read / unread**Member inbox state on portal and app.
**Device token**Mobile registration for push — managed automatically by app.
Previous sectionNext section
2
Admin ConsoleSection 2 of 6

Platform notifications

**Menu:** Platform Admin → Operations → Notifications

System-wide broadcasts and monitoring — maintenance windows, security alerts, new feature announcements to club managers.

Prerequisites

  1. Platform notification permission.
  2. FCM or push infrastructure configured on server (operator concern).

Page layout

  • Compose form: title, body, target audience (all admins, all clubs, specific club).
  • Optional action: open URL or internal admin page name.
  • History table: sent time, audience size, delivery stats if available.

Step-by-step

  1. Open Operations → Notifications.
  2. New notification — write concise title (≤50 chars for push).
  3. Select audience — avoid "all members" from admin unless true emergency.
  4. Preview on test device if test club configured.
  5. Send or Schedule for off-peak hours.
  6. Archive copy in internal runbook for maintenance tickets.

Tips

  • Platform pushes to wrong audience create high ticket volume — double-check club filter.
  • Link to status page rather than long body text.
Previous sectionNext section
3
Club PanelSection 3 of 6

Club notifications

**Menu:** Club Panel → Community → Notifications

Club campaigns: events, new acceptors, wallet promos, level upgrades.

Prerequisites

  1. Notifications option on subscription.
  2. Club linked to wallet app with push enabled for mobile delivery.
  3. Send permission on staff role.

Page layout

  • Compose tab: title, body, image optional, action link (portal page name or service).
  • Segments: all members, membership level, member group, customers with tag.
  • Schedule datetime picker.
  • History: past sends with open/read rates if analytics enabled.

Step-by-step — send campaign

  1. Open Community → Notifications.
  2. New notification.
  3. Write body — first line visible on lock screen.
  4. Choose segment — narrow beats blast for promos.
  5. Set action — e.g. open Events, Shop, or dynamic page summer-sale.
  6. Send test to your own member account mobile.
  7. Send now or schedule.
  8. Monitor support tickets for confusion within 24h.

Step-by-step — transactional use

  1. Triggered automatically by modules (order shipped, ticket reply) — usually no manual send.
  2. Customize templates in module settings where available.
  3. Do not duplicate auto messages with manual blast same day.

Segment guide

SegmentExample use
All membersMajor club announcement
Gold levelVIP early access
Group "Employees"HR benefit notice
Active wallet usersCashback campaign

Tips and common issues

IssueCauseFix
Push not receivedApp not installed or notifications off OS-sideMember enables OS permission
In-app onlyNo device tokenNormal for portal-only users
Wrong languageSingle templateProvide bilingual title/body
Duplicate messagesScheduled + manualCheck history before resend
Previous sectionNext section
4
User PortalSection 4 of 6

Member inbox

**Menu:** User Portal → Bottom tabs → Notifications (or bell icon)**

Personal inbox — system, club, and transactional messages.

Page layout

  • List grouped by date with unread dot.
  • Tap row for full body and action button.
  • Mark all read and settings link.

Step-by-step

  1. Open Notifications tab or bell.
  2. Tap unread item to execute action (open order, event, etc.).
  3. Pull to refresh after expected message not shown.
  4. Open Settings → Notifications to toggle categories if club allows preferences.

Tips for members

  • Disable OS notifications only if willing to miss time-sensitive alerts.
  • Wallet and OTP messages may still use SMS separately per club policy.
  • Old notifications may auto-archive after retention period.
Previous sectionNext section
5
Section 5 of 6

Compliance checklist (club managers)

  1. Marketing messages include opt-out path if law requires.
  2. No sensitive data (full card, password) in push body.
  3. Segment test on internal account before 10k+ send.
  4. Document recurring campaigns in content calendar.
Previous sectionNext section
6
Section 6 of 6

Summary for support

  • Admin = platform audience; club = member segments; portal = member read state.
  • Push needs app + token; portal inbox works web-only.
  • Action links should name member-facing destination ("Open Shop") not internal paths.
Previous sectionNext section