Warmly uses Slack to notify you when visitors are on your website. By utilizing Warmly’s segments, you’re able to apply guardrails to your Warmly Slack channels and only be notified when certain events are occurring (visitors hitting your website, visitors requesting to chat via Inbound Chat, etc.) or when certain companies or individuals are doing the events (for example, only companies greater than 50 employees or only visitors based in the United States).
Warmly’s Slack integration is set up in just a few clicks.
Create a Slack channel (and name is something like warmly-notifications)
Within the Slack section of the Settings tab in Warmly, select ‘Get Started’
Select the Slack channel that you created on the next page and accept permissions
In many instances, we would recommend that your team have multiple Slack channels set up to receive Warmly’s notifications. This will help your team take action on these notifications by implementing prioritization strategies.
Warmly’s Slack integration is vital to your success with Warmly. Be sure to check out our playbook on making Slack channels for success.
See below for a screenshot of how Warmly organizes its Slack channels for success.
Specific Slack channel for Max's accounts / contacts
Specific Slack channel for Keegan's accounts / contacts
Identified visitors (visitors from outbound email sequences with Warmly's UTM parameter for individual-level identification) hitting key high intent pages (pricing, demo)
Unidentified visitors hitting key high intent pages (pricing, demo)
Inbound chat / AI chat responders
Slack channel for our marketing team to illuminate the effectiveness of marketing campaigns
Broader channel for all identified visitors within Warmly's ICP (not specific to high intent pages being hit)
Broader channel for all identified companies within Warmly's ICP (not specific to high intent pages being hit)
Notifications that a prospect is in the process of filling out a form on Warmly's website (helps your reps get ahead of form abandonment!)
This video and article was made by Ryan Beyer, Head of Customer Success. Feel free to reach out at [email protected] with any questions.