Integration / Slack

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.

How it works

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.

# Sample routes
> new_member -> #membership-ops
> payment_received -> @treasurer (DM)
> dues_lapsed -> #at-risk-members
> event_registered -> #events
> ai_flagged_at_risk -> #engagement-team
FAQ

Common questions.

Can different staff members get different notifications?
Yes. Notifications can route to channels (everyone on the channel sees them) or to direct messages (just one staff). Per-event-type routing means the treasurer gets payment notifications and the membership chair gets new-member notifications.
Can we mute notifications during evenings or weekends?
Notification scheduling is on the roadmap. At launch, route to channels with custom Slack notification preferences (Slack's own do-not-disturb). For staff DMs, Slack's existing DND rules apply.
What about notification rate limits?
Sembr batches sub-second notifications into a single Slack post to avoid noise. For high-volume events (e.g., a 200-person renewal day), the digest format collapses into "12 renewals received in the last hour" with a link to the dashboard.

The dashboard is for action. Slack is for notice.

Stop checking the dashboard for routine updates.