An alert that arrives by email competes with dozens of other emails. When the notification lands in the Slack channel where your team already talks, someone replies right away. This article shows how to connect a WiseData NPS alert to a channel — for example, the "NPS critical" alert from the post-support survey going to #support.
Before you start
You need permission to create an app in your Slack workspace. If your company restricts that, ask your Slack administrator — they can do step 1 and hand you the URL. In WiseData NPS, alerts are set up by the account administrator, and the feature is part of the Pro and Business plans and of the trial.
Step 1 — Generate the URL in Slack
- Go to api.slack.com/apps and click Create New App.
- Choose From scratch, give it a name (for example, "WiseData NPS") and select your workspace.
- In the side menu, open Incoming Webhooks and turn on Activate Incoming Webhooks.
- Click Add New Webhook to Workspace and pick the channel that will receive the notifications.
- Copy the generated URL. It starts with
https://hooks.slack.com/services/— any other address is rejected by the form.
Step 2 — Paste it into WiseData NPS
- Go to Alerts and click New Alert (or edit an existing one).
- Fill in Alert Name, Condition and Survey, just like any other alert.
- Under Notification Methods, turn on Slack.
- Paste the URL into the Incoming Webhook URL field and click Create Alert.
What the notification looks like
The message arrives with the alert name as its heading, a sentence with the condition that fired (in the example, "NPS dropped below 30 in the last 30 days."), the survey and the current numbers — current NPS, configured threshold, window analyzed and responses. At the end, a View in system button, which opens the Results of the survey that fired the alert (for an alert applied to all surveys, it opens the Alerts page). The text comes in the account owner's language.
The pace is the same as any alert: checked every 30 minutes and, after firing, 6 hours without repeating. See the Alerts article for what that means for each condition.
The channel is fixed per URL
This is the most common question. The Incoming Webhook URL is tied to the channel you picked in step 1 — the channel cannot be changed from WiseData NPS. If you want new comments in one channel and NPS drops in another, generate two URLs in Slack (one per channel) and create two alerts, each with its own.
Combining with email and webhook
The methods are not exclusive: the same alert can go to Slack, to up to 3 emails and to a webhook at the same time. It is common to use Slack for the team's quick reaction and email for people who follow up less often. Turning Slack off while editing removes the URL from the alert.
If notifications stop arriving
When someone removes the app from Slack or revokes the webhook, messages stop arriving. The system tries to deliver up to 3 times; if every attempt fails, the alert card shows Last delivery failed. Hover over the warning to see the destination and the reason — for example, "Slack: HTTP 404". In that case, generate a new URL through step 1 and update the alert. The warning clears on its own at the next successful Slack delivery; a successful webhook delivery does not clear the Slack failure, and vice versa.
Security
Treat the Incoming Webhook URL like a password: anyone who has it can post messages in that channel. It is stored encrypted and only shown to the account administrator.
Where to go next
- Alerts — the conditions and how often each one warns.
- Sending alerts to a webhook — the same warning in your own system.
In short: generate a Slack Incoming Webhook for the channel you want, paste the URL into the alert with Slack turned on, and use one URL per channel.