How do I set up the Slack integration?

Create an incoming webhook in your Slack workspace, then paste its URL into Settings → Notifications in SuperLedger, turn on Enable Slack alerts, and pick which alerts to send. Action-required alerts — a dropped HighLevel connection, a misbehaving agent, a spam surge — then post straight to your channel. Gap analysis and per-call sentiment stay out by default, so the channel stays actionable.

Before you start: Admin or owner role in SuperLedger, and access to a Slack workspace where you can add an app (or an incoming-webhook URL someone already created for you).

Step 1 — Create a Slack incoming webhook

  1. Go to api.slack.com/apps and click Create New App → From scratch.
  2. Name it (e.g. SuperLedger Alerts) and pick the Slack workspace to install it in.
  3. In the left menu, open Incoming Webhooks and toggle Activate Incoming Webhooks on.
  4. Click Add New Webhook to Workspace, choose the channel the alerts should post to, and click Allow.
  5. Copy the Webhook URL. It looks like https://hooks.slack.com/services/T00000000/B00000000/XXXXXXXXXXXXXXXXXXXXXXXX.

Step 2 — Connect it in SuperLedger

  1. In SuperLedger, go to Settings → Notifications.
  2. Paste the webhook URL into the Slack incoming-webhook URL field. (It must start with https://hooks.slack.com/services/ or it won't save.)
  3. Turn on the Enable Slack alerts master switch.
  4. Choose which categories to send:
    • Connection lost & spam surges — your HighLevel connection dropped, an agent stopped receiving calls, or a spam-caller surge. On by default.
    • Agent outages & degradation — one-way audio, an agent stuck in a loop, early-hangup spikes. On by default.
    • Per-call negative sentiment — fires on individual angry / low-CSAT calls. Higher volume. Off by default.
  5. Click Save, then click Send test — a confirmation message should appear in your Slack channel within a few seconds.

What happens next

The moment an enabled alert fires, SuperLedger posts it to your channel with the location, the diagnosis, and what to do about it. Each alert is sent once per incident — no repeat-spam while the condition persists.

What does not go to Slack

By design, Slack only carries alerts you can act on:

  • Gap analysis never goes to Slack — it's review material, not a page.
  • Failing human-call (F-grade) alerts aren't routed here either. A transferred call your client's front-desk staff handled poorly isn't something you can fix from your side — you'll still see it in-app and in the client portal as evidence, but it won't ping your channel.
  • Platform / cron failures (sync stalls, pipeline issues) are SuperLedger's responsibility, not yours, so they never reach your channel.

How it works

The webhook URL is stored per agency. Categories map to toggles on your organization, and every alert is de-duplicated so one incident equals one Slack message. If you turn the master switch off, nothing is sent regardless of the category toggles. To stop a specific noisy alert, mute the location from its monitoring panel, or turn its category off here.

Troubleshooting

  • Test says "Slack rejected the webhook": the URL is wrong, revoked, or the Slack app was removed. Recreate the webhook (Step 1) and paste the new URL.
  • Saved but nothing arrives: confirm Enable Slack alerts is on and at least one category is enabled, then hit Send test again.
  • Wrong channel: a webhook is bound to one channel. Create a new webhook for the channel you want and replace the URL.
← Back to Help Center