Slack on Devotel Orbit: What the Integration Actually Is (and When to Use It)

Search "orbit slack" and the honest answer deserves to be the first thing you find: on Devotel Orbit, Slack is a workspace integration your team installs, not an outbound channel you message customers on. A "Slack setup" in Orbit means your own Slack workspace receives the operational events Orbit already knows about — an SLA clock breaching, a queue stalling, a campaign finishing — posted by a Slack App you connect once from the dashboard.

That distinction matters because it decides whether Slack belongs in your architecture at all, and where.

The honest framing: a tenant app, not an ops webhook

There are exactly two things people mean when they say "Orbit posts to Slack," and they are not interchangeable:

• The tenant-facing Slack App. You connect your workspace from Channels → Slack in the dashboard, and Orbit posts tenant-side events — new conversations, completed campaigns, SLA breaches, voice-queue warnings — into the channel you pick. This is what this guide covers, and what the Slack channel reference documents.
• An internal alerting webhook. Devotel's own platform operations route their internal alerts to a Devotel-internal channel over a deployment-level webhook. That is plumbing for the people running Orbit, not a customer feature, and it has no effect on your workspace.

If someone on your team "set up Slack," verify which one they mean before you build on it. Everything below is about the first one — the app your tenant installs.

When Slack is the right surface

Slack fits when the audience is your own staff and the trigger is an event Orbit's Inbox or queues already measure:

• SLA breach alerts. Inbox SLA timers hang first-response, next-response, and resolution clocks on every conversation. When a clock breaches, the workspace policy can alert supervisors, post to Slack, fire a signed webhook, or reassign the thread.
• Queue escalation. Per-digital-queue escalation policies watch the queue as a whole — how many conversations have breached, how long the oldest one has waited. When the conditions trip, the policy raises the alert, pages your webhook, or runs an escalation ladder whose later steps can post to Slack when nobody acted.
• Team coordination. If your agents coordinate in Slack while working the inbox, a breach landing in the channel they already watch beats an email nobody reads. If your team lives in Orbit's own workspace, the internal team chat keeps that coordination next to the softphone with no second app at all.

The common thread: these are internal notifications about customer work. The customer is never on the other end of a Slack post.

When a channel is the right surface instead

If the audience is the customer, Slack is the wrong tool and always will be. Pick the surface the customer actually answers:

• [WhatsApp](/docs/channels/whatsapp), [RCS](/docs/channels/rcs), or the OTT apps (Viber, Telegram, LINE, KakaoTalk, Zalo, WeChat) for rich, region-appropriate messaging.
• [SMS](/docs/channels/sms) and [MMS](/docs/channels/mms) for universal reach, with sender registration handled per destination.
• [Voice](/docs/channels/voice) when the moment needs a conversation, not a notification.
• [Email](/docs/channels/email) for long-form, attachment-bearing threads.

The omnichannel channel-selection matrix walks the decision in full. Slack enters that matrix only as the internal half of the loop: the alert goes to your team, the follow-up goes to the customer on a real channel.

How the integration shapes up

The install is a standard OAuth v2 round trip, documented endpoint-by-endpoint in the Slack channel reference:

1. From the dashboard, open Channels → Slack and choose Connect Workspace. Orbit mints a signed state token and hands your browser a Slack authorize URL.
2. You approve the requested bot scopes in Slack.
3. Slack redirects back to Orbit's public callback, which verifies the signed state, redeems the temporary code, and stores the workspace credentials in your tenant. The callback is intentionally public — browsers do not reliably carry the session cookie across Slack's cross-site redirect, so trust anchors on the signed state round-trip, with a ten-minute TTL and replay protection.

Once connected, inbound Slack traffic — Events API callbacks, slash commands, interactivity payloads — posts to Orbit's inbound endpoint, and every request is verified against the App's signing secret before anything is dispatched. The receiver fails closed: a request it cannot authenticate is rejected, and a workspace with no credentials configured drops notifications silently rather than blocking whatever triggered them. Notification delivery is fail-open by design — a Slack misconfiguration must never hold up a campaign send or an SLA escalation.

Two operational notes worth reading before you connect:

• Pick a notifications channel at connect time. Orbit resolves each post's destination from the channel on the notification, then the channel chosen at connection. There is no fallback channel; nothing configured means the notification is quietly dropped.
• The bot needs posting rights. It must be a member of the target channel, or hold the public-posting scope the default scope set includes, or Slack refuses the post.

None of this is configuration most buyers need to touch — but it is the shape you are installing, and it is inspectable end to end.

Related reading

• Slack channel reference — the operator guide this post summarizes.
• Team chat inside UCaaS — when internal coordination belongs inside Orbit instead of a second app.
• Omnichannel shared inbox — the SLA timers and escalation policies that Slack alerts come from.
• Commerce hub consoles — the same install-once, operate-from-the-dashboard vocabulary applied to the commerce surface.

Frequently asked questions

Can I message customers through Slack on Orbit?

No. The Slack integration is an installable App that posts internal events — SLA breaches, queue escalations, campaign completions — to your own Slack workspace. Customer-facing messaging runs on the omnichannel surfaces: SMS, WhatsApp, RCS, email, voice, and the OTT apps.

What is the difference between the Slack App and an alerting webhook?

The Slack App is a tenant feature you connect from the dashboard under Channels → Slack; it delivers your tenant's events to a channel you choose. A deployment-level alerting webhook is separate internal plumbing for platform operations — it is not a customer feature and has no effect on your workspace's notifications.

What inbound payloads does the integration accept?

Events API callbacks, slash commands, and interactivity payloads, posted to one inbound endpoint. Every request is verified against the Slack App's signing secret with a five-minute timestamp window before dispatch — unverifiable requests are rejected, and the channel stays disabled until the signing secret is configured.