Slack Notifications and Alerts
Getting Connected
To set up the Slack integration, go to Settings, Integrations, Slack and click Connect Slack. You'll authorize Conference Hero through Slack's OAuth flow, and notifications start flowing immediately. The integration is available on Starter tier and above.
After connecting, choose which channels receive notifications. You can designate a primary channel for general event updates (e.g., #conferences) and separate channels for specific events or teams. Conference Hero can also map your workspace members to their Slack accounts using email matching, with manual overrides for team members who use different email addresses. Once mapped, task assignments and lead alerts can mention the right person directly.
Task and Event Notifications
When tasks are created, assigned, or completed in Conference Hero, a formatted notification posts to the configured Slack channel. Each notification includes the task title, assignee, due date, and a direct link back to Conference Hero. Your team can stay on top of conference prep without leaving Slack, and completed tasks update everyone in real time.
Channel assignments are configurable per conference. Your trade show team sees booth logistics in their channel while marketing gets lead capture alerts in a separate one. This keeps noise down and relevance up during busy event weeks.
Lead Alerts and Score Thresholds
Conference Hero notifies your team the moment a high-value lead is captured at an event. Instead of waiting until the conference ends to review lead lists, your sales reps see hot leads pop up in Slack in real time. Each alert includes the lead's name, company, score, and the event where they were captured.
Set score thresholds to control which leads trigger alerts. You might configure alerts only for leads scoring 80+ out of 100. You can also set up tiered notifications: leads scoring 60-79 post to a general channel, while leads scoring 80+ trigger a DM to the assigned rep. Beyond scores, configure triggers for target account matches, demo requests, or ideal customer profile criteria. A common setup is a dedicated channel per event (e.g., #saastr-2026-leads) so leadership can monitor capture velocity in real time.