So you want to know when a new company visits your website—without living in your inbox or logging into yet another dashboard. That’s what Slack alerts are for. If you use Visitor Queue to track which companies are poking around your site, hooking it up to Slack can help you (and your sales team) move faster, without extra noise.
This guide is for anyone who wants clear, direct steps—no fluff, no hype. If you’ve ever tried to set up an integration and ended up cursing at your screen, you’re in the right place.
Why bother with Slack alerts?
Getting notified in Slack when a new company visits your site is handy—if you set it up right. You’ll see fresh leads in real time, and it’s easier to loop in your team. But too many alerts, or alerts sent to the wrong channels, and it just becomes background noise.
Before you start, ask yourself:
- Who actually needs to see these alerts? (Sales, marketing, or just you?)
- How often do you want notifications? (Every visit, or just once per company?)
- Do you want all companies, or only those that fit certain criteria?
Get clear on this now. It’ll save you from notification overload later.
What you’ll need
- A Visitor Queue account (with admin or integration permissions)
- A Slack workspace (where you can add apps and create channels)
- Zapier or a similar automation tool (unless you’re on Visitor Queue’s Pro plan, which has a direct Slack integration—more on this below)
If you’re hoping for a native, one-click integration in every version of Visitor Queue, you’re out of luck (for now). Most folks use Zapier or something similar.
Step 1: Set up your Slack channel
Decide where you want the alerts to go. This could be:
- A new private channel (e.g.
#website-leads) - An existing sales/marketing channel
- A direct message to yourself (if you don’t want to annoy anyone else)
Pro tip:
Don’t dump alerts into a general channel—people will just mute them. Start with a dedicated channel.
How to make a channel:
- In Slack, click the “+” next to “Channels.”
- Name your channel (e.g.
#visitor-queue-alerts). - Set it to private unless you want the whole company to see these.
Step 2: Connect Visitor Queue to Slack
Option 1: Use Visitor Queue’s built-in Slack integration (Pro plans only)
If you’re on Visitor Queue’s Pro plan:
- Log in to Visitor Queue.
- Go to Integrations (usually in your dashboard sidebar).
- Find the Slack integration and click “Connect.”
- Authorize Slack and pick the channel you created.
- Set the alert criteria—like new company visits, location, company size, etc.
Honest take:
The built-in integration is the easiest if you have access. But it’s not super flexible—you get the alerts Visitor Queue gives you, and not much customization.
Option 2: Use Zapier (works with any paid Visitor Queue account)
If you’re not on Pro, or want more control:
- Sign up for a Zapier account if you don’t have one.
- In Zapier, click “Create Zap.”
- For the Trigger, search for “Visitor Queue” and pick the “New Company Visit” event.
- If Visitor Queue doesn't show up, use the “Webhook” trigger (see Advanced section below).
- Connect your Visitor Queue account using the API key from Visitor Queue’s settings.
- For the Action, search for “Slack” and select “Send Channel Message.”
- Connect your Slack account and pick your alert channel.
- Customize the message. You can include:
- Company name
- Website
- Location
- Visit date/time
- Any other data Visitor Queue provides
Pro tip:
Keep the message short and actionable. Example:
:bell: New company on your site! Company: {{Company Name}} Website: {{Company Website}} Visited at: {{Visit Time}}
- Test the Zap. If all looks good, turn it on.
Honest take:
Zapier works well, and you have a lot more control over what goes into the alert. Downside: it’s another tool to manage, and you’ll hit Zapier’s limits if you get tons of visits.
Step 3: Filter your alerts (or risk drowning in noise)
This is where most people mess up. If you set it to alert on every single visit, you’ll get sick of Slack in a week.
How to filter:
- In Visitor Queue, set filters for things like company size, location, or industry.
- In Zapier, use the “Filter” step to only continue if certain fields match (e.g. only companies with more than 50 employees, or only US-based visits).
- You can also set up deduplication, so you don’t get pinged each time the same company visits.
What to ignore:
Don’t bother alerting on every visit from small companies, ISPs, or locations you don’t sell to. You’ll just annoy your team.
Pro tip:
Start with stricter filters. You can always loosen them up if you’re missing leads, but it’s harder to recover if you annoy everyone first.
Step 4: Test your setup (and fix what’s broken)
Don’t just assume it works—test it.
- Visit your site from a different network or ask a colleague to do it.
- Watch for the Slack alert.
- Check the message for missing or weird info.
- Make sure only the right people see the alert.
If something isn’t coming through, double-check:
- Your Visitor Queue filters and integration settings
- Zapier’s history (for errors or throttling)
- Slack permissions (sometimes messages get blocked by Slack admins)
Step 5: Roll it out to your team (if you’re not the only user)
- Let people know what to expect and how to mute or manage alerts.
- Get feedback after a week—is it helpful, or just noise?
- Adjust filters, channel, or frequency based on real-world use.
Honest reality:
No matter how much you plan, you’ll probably need to tweak things. That’s normal.
Advanced: Using webhooks or other automation tools
If you’re technical or want more flexibility, Visitor Queue can send data to a webhook. This means you can:
- Use Make (formerly Integromat), n8n, or your own scripts
- Format messages exactly how you want
- Do things like enrich company data, assign leads, or trigger other workflows
But—this is only worth it if you have the time and skills. For most folks, Zapier does the job.
What actually works (and what doesn’t)
Works well:
- Notifying a focused team channel when a qualified company visits
- Filtering out junk (small companies, ISPs)
- Using clear, concise Slack messages
Doesn’t work:
- Alerting on every single visit (burnout guaranteed)
- Sending alerts to general-purpose channels
- Forgetting to test or get feedback
Keep it simple (and tweak as you go)
Don’t overthink it. Set up the basics, start with tight filters, and see what actually helps your team. If you’re not sure whether you should alert on something, leave it out—you can always add it later.
The best Slack alerts are the ones people actually read. So err on the side of less noise, more action. That’s how you get value out of Visitor Queue—and keep your team from muting yet another channel.