Skip to main content

Slack Notifications in Knock2

Written by Knocky
Updated over 2 weeks ago

Slack Notifications in Knock2

Slack notifications bring Knock2 insights directly into your team's workflow, so you can review, discuss, and take action on accounts and contacts without living in the dashboard.

They are designed to surface important signals, provide shared visibility across your team, and let you make fast qualification decisions in real time.


What Slack notifications are used for

Slack notifications act as a real-time review layer for inbound activity processed by Knock2. Teams commonly use them to:

  • Monitor high-intent accounts and contacts

  • Share visibility between Sales, Marketing, and RevOps

  • Quickly decide which leads are worth follow-up

  • Create lightweight conversation around inbound signals

  • Capture qualification decisions without extra tools or steps

Rather than flooding your CRM or inbox, Slack becomes the place where decisions happen.


Account and contact notifications

Slack notifications can be enabled separately for:

  • Account notifications — company-level activity and identification

  • Contact notifications — person-level identification and enrichment

Each notification is sent after the lead has been processed by Knock2, ensuring the information you see is enriched and ready for review.


Note: If Knock2 identifies a contact for a given account, only the contact notification will be sent — no separate account notification will fire for the same visit. This prevents duplicate alerts. You can still view the associated account record in the dashboard.


What information is included in a Slack notification

Depending on what data is available, a Slack notification may include:

  • Account or contact details

  • CRM company owner

  • CRM deal owner

  • Current CRM deal stage

  • A direct link to open the record in the Knock2 dashboard

  • Actions to qualify or disqualify the account or contact

This gives your team enough context to decide what matters without leaving Slack.


Configuring Slack notifications

Slack notifications are configured directly from the Knock2 dashboard.

From Settings → Slack, you can:

  • Connect your Slack workspace

  • Choose the channel where notifications are sent

  • Enable notifications for accounts, contacts, or both

  • Apply filters so only relevant leads trigger notifications (e.g., Lead Score ≥ 50)

This lets you control both volume and relevance, keeping Slack useful instead of noisy. Leads that don't meet your filter criteria will still appear in the dashboard — they just won't generate a Slack notification.


Qualifying and disqualifying leads from Slack

Each Knock2 Slack notification includes two action buttons:

  • 👍 Qualify

  • 👎 Disqualify

These actions allow your team to give immediate feedback on an account or contact directly from Slack. The decision is saved on the record in Knock2 and is visible to your entire team.


Understanding the qualification button states

The appearance of the Qualify and Disqualify buttons changes depending on whether a decision has already been made for that lead:

  • No decision made yet — Both buttons appear in their default (unselected) state.

  • A decision has been made — The selected button will appear highlighted. If the lead was qualified, the Qualify button is highlighted; if disqualified, the Disqualify button is highlighted. This lets anyone on your team immediately see that the lead has already been reviewed.


Additionally, when a qualification decision is made:

  • First time — Slack will add a 👍 or 👎 emoji reaction to the notification message and thread a confirmation message showing who made the decision (e.g., "Qualified by @david").

  • Subsequent decisions — If the same lead is reviewed again (e.g., they return to your site), the button will reflect the prior decision in color: green for qualified, red for disqualified.


Note: Contacts and accounts are qualified or disqualified independently. If you disqualify a contact, the associated account is not automatically disqualified — this is intentional, since the account may still be a good fit even if that specific person isn't the right contact.


Why qualification status matters

Qualification and disqualification are not just visual signals in Slack. That status is stored on the account or contact record in Knock2, which means it can be used for:

  • Filters and views in the dashboard

  • Workflow logic and automation

  • Suppression or prioritization rules

  • Preventing duplicate review across your team

Slack provides the action. Knock2 stores the decision and makes it usable everywhere else.

Did this answer your question?