Nudge without noise
Notifications help people act at the right moment without adding clutter. Overlays prompt participation, the Inbox tracks status, and email/Slack can backstop important items.
Who gets what
- Members: light overlays to participate; inbox updates after they submit; notifications when outcomes are approved
- Reviewers: alerts when items need a decision; approve/request changes; points apply on approval
- Admins/Finance: notifications for perk claims (if manual approval required), high-value outcomes, export reminders
How the notification system works
Teamwins uses an event-driven notification system:
1. Action occurs (contribution submitted, approval requested, outcome approved, perk claimed) 2. Event record created in event queue table 3. Notification rules evaluated (which events trigger which notifications?) 4. Notification dispatched via configured channel (in-app, email, Slack)
See the full explanation in Notification architecture guide.
Notification types
Instant notifications (sent immediately):
- Approval requests to reviewers
- Outcome approved confirmations to contributors
- Perk claim requests to admins/finance
- High-value outcome alerts
Batched notifications (sent once per period):
- Weekly digest of new Assists published
- Monthly leaderboard update
- Quarterly ROI summary
Approvals and perk auto‑approve
- Assist outcomes require a Reviewer decision; there is no auto‑approve for Assists
- Perks can be configured as auto‑approved (per-perk setting) or require manual approval
When a perk is auto‑approved, points are finalized and the delivery is issued immediately—no notification to reviewer. Use manual approval for expense/receipt perks and high-value items.
Channels and controls
- In‑app overlays and Inbox for day‑to‑day flow
- Email: Real-time emails for urgent reviewer queues; digests for non-urgent updates
- Slack (optional): Channel posts for wins and approvals
- Snooze/mute: Temporarily silence specific Assists; set reviewer fallback
Best practices
- Keep messages short and contextual to the action required
- Set a light SLA for reviewers (24–48h) and celebrate wins weekly
- Use email digests for quieter users who prefer fewer interruptions
- Configure Slack for high-visibility outcomes (hires, big deals, milestone wins)
