Sembr & Slack.
Membership activity in the same place your team already lives. New members, payments, lapses, event registrations. Routed to channels or DMs, your call.
Pipe what matters, mute what doesn't.
Per-event-type routing
Pick which event types to surface. Route each type to its own channel or DM. Treasurer gets payments; chair gets new members.
Channel or DM
Notifications go to a channel (everyone sees) or a DM (one staff member sees). Slack's own DND rules apply.
Smart batching
Sembr batches sub-second notifications into a single Slack post to avoid noise on high-volume days.
Status: Phase 2.
Sembr's native notification system ships first (G5, polling-based). Slack is a destination layered on top. One-way push from Sembr to Slack. Two-way (Slack commands that update Sembr records) is not currently scoped; use Zapier for that today.
Common questions.
Can different staff members get different notifications?
Can we mute notifications during evenings or weekends?
What about notification rate limits?
The dashboard is for action. Slack is for notice.
Stop checking the dashboard for routine updates.