Connected once for the whole instance, then every notification is personal.
An Outreach contract, an Outreach admin, and permission to add apps to Slack
Messages, Activities, events only.
Lighter than the other Slack pairs here, and personal rather than broadcast. One admin connects the instance over Slack OAuth, Outreach maps users to their Slack accounts automatically, and from then on each person chooses which alerts reach Slack instead of the in-app feed, email or the browser. The channel story is thin on purpose: only the Kaia meeting summary is documented at account level, one channel per account, and turning that on makes account notifications visible to everyone in the channel. Read it as a better inbox for reps, not as a team alerting system.
Object by object, with the direction each one moves in. This is the table to read before the feature list, because a capability that only moves one way is a different product from the one you think you are buying.
| What | Direction | What that means in practice |
|---|---|---|
| Personal notifications | One way, in | Email-reply mismatches, meeting updates, new voicemails, bounce limits, CRM plug-in errors, mentions and overdue tasks, to the user who owns them. |
| Kaia meeting summaries | One way, in | Sent automatically when ready, and the one notification documented at account level, with a single Slack channel per account. |
| Deal Agent suggestions | One way, in | AI-detected opportunity updates from a call recording, which a user can accept, reject or edit from Slack. |
| Accepting a suggestion | One way, out | The decision travels back to Outreach and updates the opportunity field, which is the only thing moving in this direction. |
| Prospects, sequences and activity | Event only | Nothing. This is a notification surface. The records stay in Outreach and in whichever CRM it syncs with. |
Nothing in that table moves in both directions. Whichever system you treat as the source of record, the other one is downstream of it, and a correction made in the wrong place does not travel.
Nothing syncs. There are two separate notification systems here, a personal one and an account one, and they overlap in exactly one place. Knowing which events belong to which is the whole configuration.
| In Slack | In Outreach | What to know about the match |
|---|---|---|
| Somebody other than the recipient replying | Personal, available in Slack | A prospect replies from a different address, belonging either to another prospect or to somebody Outreach does not know. The notification exists because the reply would otherwise be invisible. |
| Meeting updates | Personal, available in Slack | Booked via your public calendar link, reassigned to another prospect, rescheduled, or scheduled on your behalf by another Outreach user. |
| New voicemails | Personal, available in Slack | One trigger, one notification. The simplest thing on the list. |
| Bounce limits | Personal, available in Slack | Three thresholds: 50% of the bounce rate, 80%, and a final warning when you cannot send for the next 24 hours. The one notification on this page that stops work if ignored. |
| Plug-in and sync errors | Personal, available in Slack | Issues with the connected CRM, and a disconnected mailbox or calendar that has stopped synchronising. Worth routing somewhere a person actually reads. |
| Mentions and urgent tasks | Personal, available in Slack | Being mentioned in the Kaia chat, and an urgent task going past its due date. |
| Kaia meeting summary | Personal and account-level | The only event that exists in both systems, and the only one an account channel can deliver. |
| An account to a channel | One channel per account, public only | Selected from an autocomplete on the account details page. The Outreach app does not need to be invited to the channel, which is unusual and worth knowing. |
Worth knowing before you write a report against it, because the wording below is what you will be filtering and searching on rather than anything you choose.
| The action | How it reads on the record |
|---|---|
| A prospect opens an email | Browser notification only, with OS-level permission required |
| A prospect clicks a link | Browser notification only |
| A prospect replies to an email | Browser notification only |
| An incoming call | Browser notification only |
| An overdue urgent task | Browser, and also available as a Slack notification |
| A Kaia meeting summary | Slack, personally or into a channel attached to the account |
Three things are worth knowing before you plan around this mapping, because each one is a decision somebody has to own rather than a setting to find.
Every row above travels as a file: eight field mappings, six action rows and three documented exclusions, each one's note, and the three vendor documents behind them. The CSV opens in a spreadsheet, the JSON is the shape an agent wants, and the Markdown is the table to paste into a ticket.
The second table is the one that resets expectations, because the three events a sales team most wants in a channel are the three that do not go there. Anybody planning a deal-channel strategy around reply alerts is planning around a browser notification on one person's laptop.
Nothing here is gated by a plan on either side: the app is free and Outreach includes the notifications with the contract. What varies is the delivery channel, and Outreach states outright that not all notifications support all channels. Pick one on each side and the grid marks the answer.
Pick one on each side.
| What you want to be told about | Slack | A browser notification |
|---|---|---|
| A reply from an unexpected address | Delivered | Not available |
| Meeting updates and voicemails | Delivered | Not available |
| Bounce limit warnings | Delivered | Not available |
| A prospect opening, clicking or replying | Not available | Delivered |
| An incoming call | Not available | Delivered |
Counted off that grid, of ten pairings: five give you delivered, five give you not available. Three rows go one way and two go the other, with no overlap, which is the cleanest possible statement of the thing teams get wrong. Slack carries the exceptions and the warnings, the ones that mean something has gone sideways; the browser carries the engagement, the ones that mean somebody is interested right now.
Every step below is from the two vendors' own setup documentation, in the order they document it. Two of them cost you an afternoon if taken late, so the order is the useful part rather than the clicks.
Slack: app management
Outreach lists it as a prerequisite before anything else. The connection is made from Outreach, but it installs an app in Slack, and a locked-down workspace will stop the admin halfway through.
Outreach: Administration, Organization, Org info, General
Scroll to Slack notifications and follow the prompts. This is Slack OAuth once for the whole org rather than per user, and once it is done Outreach tries to map Outreach users to their Slack users automatically.
Outreach: the same screen
Allow users to connect Slack channels to Outreach accounts is a separate switch, and Outreach warns what it means: account-related notifications sent to those channels may be visible to all channel members. That is a disclosure decision rather than a feature toggle.
Outreach: Personal Settings, General, Notifications
The admin connection enables nothing by itself. Each user toggles their own Slack notifications, and a user who does not see Slack as an option has not been mapped yet rather than hit a bug.
The browser, after clicking Enable browser notifications
Three of the most-wanted events are browser-only: a prospect opening an email, clicking a link or replying. Outreach notes these need OS-level permission, so a blocked popup setting silently disables them.
Outreach: the account details page
The notifications for Slack panel sits under the account name in the top right. Pick a public channel from the autocomplete, and note that the Outreach app does not need to be invited to it, unlike most Slack integrations.
The same panel
One notification type is supported today: the Kaia meeting summary, triggered after a call associated with that account once Kaia has processed the recording. Outreach says more may be added; today that is the list.
The same panel
Each account links to a single Slack channel, changed by returning to the account page. Outreach recommends this for teams running dedicated deal channels, which is exactly the shape it fits.
The admin step takes ten minutes and enables nothing visible, which is why this pair is so often reported as not working on the day it is connected. Everything a person actually sees is switched on by that person or by whoever owns the account, and that distribution is what the collaboration layer demands of every tool that writes into a channel.
The same sequence, the sync table, the documented limits and the error list ship as one agent skill. Point Claude Code, Cursor or anything that reads a file at this pair as a skill and it has the whole pair without reading two sets of vendor docs first.
curl -o .claude/skills/slack-outreach/SKILL.md https://www.reversecontact.com/integrations-hub/skills/slack-outreach.md
Every limit below is documented by one of the two vendors. They are here because they change decisions, not because they are flaws.
Each of those is documented behaviour rather than a fault, so none of them is going to be fixed by a support ticket. The ones that produce a symptom you would misread are below.
Each one below is a symptom somebody reports, the documented reason behind it, and the fix. Most are configuration rather than faults, which is why they survive a support ticket.
WhyOutreach answers this one directly: Slack must be enabled by an Outreach admin and mapped to the user's account.
Confirm the instance-level connection exists, then check the user mapping. Outreach maps users automatically after connecting, so an unmapped person usually joined afterwards.
WhyCorrect behaviour. The admin connection enables the channel and switches nothing on; each user toggles their own notifications.
Send people to Personal Settings, General, Notifications. This is the single most common reason the integration is reported as broken on day one.
WhyThey are browser notifications rather than Slack ones. Outreach states that not all notifications support all channels.
Enable browser notifications and grant the OS-level permission. There is no configuration that routes engagement events into Slack.
WhyPopups are blocked, or the OS permission was never granted. Outreach says the browser asks after you press Enable browser notifications.
Check both the browser and the operating system settings. Outreach answers this in its own FAQ, which is a sign of how often it happens.
WhyEither Slack is not connected to the Outreach org, or the account-channel feature has not been enabled by an admin.
An admin connects the integration and enables the feature in Org info. You also need edit permission on the account you are configuring.
WhyThat is the full list. Outreach supports only the Kaia meeting summary at account level today.
Use personal notifications for everything else. Outreach notes additional types may come in future releases, which is not something to plan around.
WhyIt is triggered post-call and sent after Kaia has processed the recording. Outreach documents a short delay.
Wait rather than reconfiguring. If it never arrives, check the call was actually associated with that account.
WhyOutreach warns about this when the feature is enabled: account-related notifications sent to a channel may be visible to all channel members, and only public channels can be selected.
Treat channel membership as the access control, because it is. This is a decision to take before enabling the feature across the org.
If none of those is it, the next thing to check is the thing most pairs fail on: whether the plan you are on carries the feature at all, which the grid above answers. The same symptom on another pair is often the same cause, so the directory indexes all of them by the message rather than by the integration.
The right-hand column is the one worth being honest about, because every item in it is a reason to spend the budget somewhere else in the stack rather than a reason to configure harder.
Searched for the problem this pair solves rather than for the pair itself, because the pair by name returns almost nothing. 14 threads from 2023 to 2026 were read in full on 11 October 2026, and the 5 below are the ones that carry a point. Each is one person's experience rather than a measurement, and the vendors' own documentation is what the rest of this page rests on.
i've tried a bunch of setups, but what works best for me is just one main slack channel per client keeps things simple and less noisy i use threads for updates, feedback, random questions, so stuff doesn't get lost
r/agency·July 2025·1 points
Arrived at independently, and it is exactly the shape Outreach built: each account links to a single Slack channel, and Outreach recommends it specifically for teams running dedicated deal channels. The agreement between a practitioner and the product is worth more than either on its own.
Unless you're a Tier 1 you're not getting a dedicated Slack channel
r/CustomerSuccess·August 2025·10 points
About customer-facing channels rather than internal ones, and it raises the question this feature makes urgent. Outreach warns that account notifications may be visible to all channel members and only public channels can be chosen, so a shared channel and a deal channel are very different places to send a call summary.
That 10-15 integration range is the sweet spot. Going past that usually just add
r/Slack·April 2026·1 points
Cut where the cached comment is, and offered as a rule of thumb rather than a measurement. It is the right frame for a pair whose personal notifications are nine separate toggles: every one you enable competes with everything else already in that person's Slack.
you should have a saved search that will always show at any given time what orders are approved and ready for fulfillment. NetSuite is your source of truth. The saved search is what tells you at any given time how many orders are approved and ready for fulfillment. The slack notification is just a
r/Netsuite·June 2026·1 points
A different product entirely and the clearest statement of the principle. Outreach holds the sequence, the account and the Kaia recording; the Slack message exists to make somebody look, which is why the bounce-limit warnings matter more here than the engagement events do.
The inability to disable threaded messages, or at least a toggle that forces them to post to the channel by default instead of requiring a user to check a box each time. Too many people miss too many threaded (hidden) messages.
r/Slack·May 2025·5 points
Relevant to every pair that ends in a channel message. A Kaia summary posted into a busy deal channel competes with the platform's own defaults, which is an argument for the quiet dedicated channel that both this comment and the first one point at.
Nobody discusses this pair by name, so the search was for the job: putting sales activity into the channel where a team already works. What comes back is almost entirely about structure and restraint, from people running client and deal channels at scale. The advice is consistent and it maps onto the one account-level feature Outreach supports: one channel per thing, organised around the account rather than the tool.
A job search returns structural advice rather than bug reports, which is the honest outcome for a pair nobody names. All five agree with the documented design, and the one place they add something is the warning about who can read an account channel, which Outreach raises and most teams decide in a hurry.
Every other Slack pairing on this hub is about broadcasting an event to a team. This one is mostly about moving one person's notifications from a place they do not look to a place they do, which is a smaller idea and a more reliable one. The failure mode that ruins channel alerting, somebody enables every event type and the channel gets muted, barely applies when the notifications are personal and each user picked their own. That makes it one of the few Slack integrations here that is hard to configure into uselessness.
The piece worth deciding deliberately is the account-channel setting, because it is the only part with a disclosure consequence. Letting users attach a Slack channel to an Outreach account means account notifications can be seen by everyone in that channel, which Outreach says in the admin documentation. In an internal deal room that is the point. In a channel shared with a customer or a partner it is a problem, and the control is an admin toggle rather than something the person connecting the channel will think about.
The Deal Agent path is the most interesting thing here and the newest, so treat the documentation as moving. An AI suggestion drawn from a call recording arrives in Slack and a human accepts, rejects or edits it, which writes back to the opportunity. That is a genuinely different pattern from a notification: the channel becomes a place where CRM hygiene happens rather than a place where it is announced. Whether that survives contact with a sales team is a question worth asking in a pilot rather than at rollout.
Reverse Contact resolves an email, a domain or a profile URL into a verified people and company record, through one API with a consistent schema. It sits under Slack, Outreach and everything else in this directory, and it returns null with a confidence score rather than a guess.
Free trial, no card required, and 500 credits to start.
An Outreach admin, once, for the whole instance. It runs on Slack OAuth from Administration, Organization, Org info, General, and the admin needs permission to add apps to the Slack workspace. After connecting, Outreach tries to map Outreach users to their Slack accounts automatically, and where that works users can switch notifications on themselves.
Mostly personal alerts rather than channel ones. Outreach lists Slack as one of several notification channels alongside the in-app feed, email and browser notifications, and users choose which they want under Personal Settings, General, Notifications. Documented examples include email-reply mismatches, meeting updates, new voicemails, bounce limits, CRM plug-in errors, mentions in the Kaia chat and tasks that pass their due date.
Only narrowly, and only if an admin allows it. There is a setting that lets users associate Slack channels with Outreach accounts, and Outreach warns that account-related notifications sent to those channels may be visible to everybody in the channel. On the account-level documentation only the Kaia meeting summary is supported, with one Slack channel per account.
Because the Outreach application for Slack has been under review by Slack, which Outreach notes in its own admin documentation. It is a Slack marketplace status rather than a security finding, and it is the kind of thing worth telling a security team in advance rather than explaining after somebody escalates it.
Tier requirements, sync behaviour and limits read from each vendor's own documentation in September, October and November 2026. Vendors change these without notice.
Reverse Contact appears in this directory as a data provider and publishes it. Every other tool is here on merit and nobody pays for placement.