HELP / INTEGRATIONS / SLACK

Connect Slack for notifications and channel signals

Admin4 min read

Last verified 2026-09-17

Install the ValueRamp Slack bot across your workspace, approve channel scopes, invite the bot to customer-shared Slack Connect channels, and stream communication signals.

Before you start

  • ValueRamp Admin role
  • Slack workspace administrator permissions or app installation approval rights

Connecting Slack enables ValueRamp to capture real-time conversational signals from customer-facing channels, extracting feature requests, renewal sentiment, blocker risks, and action items directly into post-sales account timelines.

The Slack integration is configured at the workspace level from Settings → Workspace Integrations (/integrations). Connecting and disconnecting Slack requires the Admin role.

Connecting Slack for your Workspace

Unlike individual meeting or calendar connections, Slack is installed once for your entire organization:

  1. Navigate to Workspace Integrations (/integrations).
  2. Locate the Slack card in the integrations grid.
  3. Click Connect Slack (or Reconnect if restoring a previously disconnected workspace).
  4. You will be redirected to Slack's OAuth authorization screen. Select the target Slack workspace and click Allow.
  5. Once returned to ValueRamp, the card displays your connection status:
    • Connected: The bot is active and listening to customer channels.
    • Needs a shared channel: The bot is installed in the workspace, but has not yet been invited into any Slack Connect channels.
    • Disconnected: The bot token is inactive. No new messages are analyzed, but past account signals are preserved.

Requested Slack Permissions

ValueRamp requests only the OAuth scopes needed to read shared channels and match participants:

  • channels:history and channels:read: Reading public channels where the bot has been invited.
  • groups:history and groups:read: Reading private channels and Slack Connect channels where the bot has been invited.
  • users:read and users:read.email: Mapping message authors to customer account stakeholders by verified email address.
  • team:read: Identifying the host Slack workspace organization.

Inviting the Bot to Customer Channels

ValueRamp relies on Slack Connect to cleanly separate customer communications from internal chatter:

  1. Open any Slack Connect channel that your team shares with an external customer organization (e.g. #ext-acme-valueramp).
  2. In the message box, type:
    /invite @ValueRamp
    
  3. Press Enter. Slack invites the ValueRamp bot into the channel.
  4. As new messages are posted in that channel, ValueRamp ingests them, evaluates sentiment, and attaches milestones or action items to the matching customer account.

Privacy and Data Safeguards

ValueRamp enforces rigorous data minimization principles enforced in software logic:

  • Shared channels only: ValueRamp analyses channels Slack marks as shared. On Enterprise Grid this can also include channels shared internally across your own organisation. Ordinary internal company channels are strictly ignored, even if an employee invites the bot to them.
  • No historical backfill: The bot only processes messages sent after it has been invited to the channel. Historical channel archives are never retrieved.
  • No private communications: ValueRamp cannot read direct messages (DMs), group DMs, or internal private channels.
  • Domain validation: If an incoming message cannot be verified against a customer domain in your active Accounts roster, the payload is immediately dropped and discarded.
The Slack integration card showing disconnected status pill and Reconnect button

1 / 4Review Slack workspace bot status and reconnection controls

Steps

  1. Review Slack workspace bot status and reconnection controls

    The Slack integration card showing disconnected status pill and Reconnect button
  2. Install the ValueRamp bot and approve requested channel scopes

    The bot installation guidance detailing required workspace scopes including channels, groups, and user read
  3. Invite the bot to customer-shared Slack Connect channels

    The /invite @ValueRamp command instructions for external customer-shared channels
  4. Verify privacy guarantees that exclude private DMs and internal chats

    The privacy safeguards block stating that direct messages, private group DMs, and internal channels are never read

Common questions

Is Slack installed per user or for the whole workspace?

The Slack integration is installed once by an Admin at the workspace level. A single bot installation covers your entire organization. Individual CSMs and team members do not need to install their own bots.

What types of Slack channels does ValueRamp monitor?

ValueRamp only monitors Slack Connect channels shared with external customer organizations where an Admin or teammate has explicitly run `/invite @ValueRamp`. ValueRamp automatically ignores internal-only channels, even if the bot is invited into them.

Does ValueRamp read private direct messages or pre-existing message history?

No. ValueRamp never reads direct messages (DMs), private group chats, or message history sent before the bot was invited into the channel. These restrictions are enforced directly in the backend code and API queries.

What happens if a message sent in a Slack Connect channel does not match a customer domain?

If a message originates from a domain that does not correspond to any known account in your ValueRamp workspace, the message is dropped and its text is discarded immediately without retention.

What happens when an Admin disconnects Slack?

Disconnecting Slack revokes the stored bot token and halts message analysis immediately. Any signals, sentiment indicators, and action items already extracted and filed to account timelines remain preserved.

Was this helpful? Tell us what was missing