Send high-intent website visits to Slack
Post repeat visits to pricing and other high-intent pages in Slack, with enough account context for the team to decide what to do next.
The conversation
Sample accounts and numbers, for illustrationYouShow me companies that viewed our pricing page at least twice in the past seven days, with the other pages they read, whether they fit our ICP, and who owns each account in our CRM.
Unify3 checks · Unify Intent, ICP and CRM
- Resolved pricing-page views from the past seven days to companies.
- Checked each company against the ICP in your company context.
- Matched each to a CRM account for owner, customer status and open opportunities.
Six companies viewed pricing twice or more this week. Two are customers. Of the other four, three fit the ICP.
| Company | Pricing views | Also read | Fit | Owner |
|---|---|---|---|---|
| Merridian Systems | 3 | Security, integrations | Fits | Ana |
| Northwind Labs | 2 | Customer stories | Fits | Priya |
| Fennimore Logistics | 2 | Integrations | Fits | No owner |
| Calderon Health IT | 2 | Careers | Outside the ICP | No owner |
Visits resolve to a company, not a person. Nothing here says who was browsing.
YouWhich of these should reach Slack, and what would the alert say?
UnifyThe three that fit. Calderon and the two customers stay out. This is the alert for Merridian.
- Why only three
- Fit and customer status are checked first. Two visits from a company outside the ICP are still not worth a ping.
- No owner
- Fennimore has nobody to tag, so its alert goes to the channel without an owner and someone claims it.
Alert preview · #pricing-alerts
Merridian Systems viewed pricing 3 times in 5 days. Recent visits: pricing, security, integrations. Owner: @Ana.
YouMake this run every day and post to #pricing-alerts.
UnifyAlerts run as a play, which you build in Plays with the same criteria. These are the settings to use.
- Trigger
- A company matches: two or more pricing-page views in seven days, fits the ICP, not a customer.
- Slack alert
- Posts to #pricing-alerts, tags the account owner and includes recent website visits.
- Cooldown
- The same company cannot alert again for 14 days, so one busy account does not fill the channel.
Plays check for new matches about every 15 minutes, so an alert lands shortly after the second visit, not on the click.
High-intent visits, with and without Unify
A pricing visit is only useful if someone sees it while it is still recent.
| Without Unify | With Unify |
|---|---|
| Pricing visits sit in an analytics dashboard nobody opens before a call | Repeat visits to the pages you choose post to a Slack channel |
| Every visit looks the same, including students, competitors and customers | Fit and customer status are checked before the alert is sent |
| Nobody knows whether the account already has an owner or an open deal | The alert tags the account owner and lists the recent visits |
| A company that visits five times produces five separate pings | A cooldown keeps one company from posting again for a set number of days |
Start from this prompt
Make it your own in Unify, then review the results.
Show me companies that viewed our pricing page at least twice in the past seven days, with the other pages they read, whether they fit our ICP, and who owns each account in our CRM.
What else you can ask for
The walkthrough is one path through this workflow. These are the turns people take most often.
How it changes by who you sell to
- Software
- Pricing, security and integrations pages carry the most intent. Ask for an alert on two pricing visits in a week, and leave out accounts that are already in a trial.
- Professional services
- Firms compare suppliers in a short window. Ask for the alert to fire on the second visit within seven days rather than the first, so the channel only hears about real shortlists.
- Manufacturing
- Visits cluster around budget cycles and often come from a plant rather than head office. Ask for the alert to tag the account owner, so the regional rep who covers that company picks it up.
- Retail and e-commerce
- Pricing traffic spikes before peak season. Ask for a tighter trigger from August to October, and a separate channel so peak-season alerts do not drown the rest.
Next in signals and intent
+4You connect 3 toolsResearch intentAct on category and comparison researchSomeone reading comparison pages has moved past whether to buy and on to which one.
All included with UnifyHiring audiencesBuild an audience from hiring signalsFind accounts investing in the team you sell to and keep the job evidence with the audience.
+5You connect 4 toolsDaily prioritizationBuild today's prospecting listOpen the day with ten accounts ranked on fit, this week's intent and your own history with them, each with a verified contact, instead of a judgment call about where to start.
Connect what this workflow uses
Each guide covers the connection, what Unify reads and writes, and what to check before the first run.
Connect SlackConnect Slack to Unify and design useful Play alerts: a public channel or a user DM, with prospect context and a clear next action.- Connect SalesforceAuthorize Salesforce in Unify, configure CRM field mappings, and choose when to enable writing.
- Connect HubSpotConnect HubSpot to Unify, map Company and Person fields, and plan CRM exclusions and supported write-back.
Questions about this workflow
Does the alert identify the person browsing?
No. Website identification resolves a visit to a company, not a person. The alert names the company and the pages it viewed.
Can I choose which pages trigger it?
Yes. The trigger is a page-view filter: a page, a count and a time window, such as two pricing views in seven days.
Where does the alert go?
To any public Slack channel, or as a direct message, chosen in the play's Slack alert action. It can tag the account owner.
How are repeat visits handled?
With the play's cooldown. A company that alerts today will not alert again until the cooldown you set has passed.
Is it set up in chat?
Chat shows you which companies would match and what the alert would say. The alert itself runs as a play, which you build in Plays.