Slack

SupportedServer-side credentialsNotifications

Queue health, SLA risk, reconciliation holds, and batch reviews post to Slack automatically. Every message names the work and the location, never the contact.

01What the splice does

Told in Slack what matters. Never told who.

Automated alerts

Policy-driven posts into the Slack channels your team already watches.

Content-minimal

A location, a time, and a work type; identity stays inside the workspace, behind scope.

Recovery inbox

Anything unacknowledged in Slack still waits in the in-app recovery inbox.

Per-location policy

Which alerts go to which channel is a versioned configuration revision.

Supported today. Credentials live server-side; scope is enforced on every request.

Notification policy · NorthgateRevision 14 · Content-minimal

AlertPushSMSEmailTeams / SlackRecovery

Callback due in 10 minutesOnOn——Until ack

SLA-risk deferral needs approvalOn—OnOnUntil ack

Overnight batch ready for review——OnOn—

Reconciliation hold openedOn——OnUntil ack

Workspace locked · inactivityOn————

Recovery inbox2 unacknowledged

Callback due · Northgate · 4:00 PM12 min ago · push, SMSAcknowledge

Deferral awaiting approval · Riverside34 min ago · email, TeamsAcknowledge

What an alert saysNo identity

DialSplicenowCallback due · Northgate · 4:00 PMOpen the work item to see who.

No name, no number, no message body. The same rule applies on SMS, email, Teams, and Slack.

02How it connects

Reads, writes, and never returns.

We read

The channel directory, to choose destinations
Delivery acknowledgements

We write

Content-minimal alert messages
Daily and shift digests
Links back into the workspace for acknowledgement

We never return

Contact identity
Message bodies
Recordings or transcripts

Credentials never reach the browser

Provider tokens live server-side; the agent's browser only ever sees a work item.

Scope on every request

Organization and location travel with each call to the connector; an unknown scope fails closed.

Idempotent, journaled, reconciled

Every effect is journaled once; an ambiguous outcome enters reconciliation instead of a retry.

03Common stacks

What Slack is usually spliced with.

One connector per category. These are the systems we most often see beside Slack; any of them can be swapped for the one you run.

RCSupportedRingCentralTelephony providerOpen HLSupportedHighLevelCRMOpen ZSupportedZenotiEHR / system of recordOpen FConnectingMicrosoft Fabric / OneLakeData platformOpen SBOn requestSendBlueMessaging channelOpen

04Also in this category

Other Notifications connectors.

TSupportedMicrosoft TeamsNotification channelOpen

All integrations What a splice is

05Questions

Slack and DialSplice.

Who it is for, and what to ask before the demo.

Medical groups Financial teams Outsourced call centers Agencies

Does DialSplice replace Slack?

No. Slack stays the channel your team already works in. DialSplice adds the queue, the contactability preflight, and the audit ledger on top, and hands work back to Slack where it belongs.

What does DialSplice store from Slack?

Work items, scope, timestamps, dispositions, event hashes, and operational telemetry. Identity is read from Slack under your scopes and is not copied into the ledger.

Is the Slack connector available today?

Yes. It is supported today and included in the platform fee.

Where do the Slack credentials live?

Server-side, always. The agent's browser only receives a work item; provider tokens never reach it, and every request carries organization and location scope.

06Book a demo

See Slack spliced in.

Bring the rest of your stack; we will show you the workspace with every system named.

Book a Demo Request a Connector