Channel webhooks
Plain-text operational messages to Slack channels via Incoming Webhooks.
Workspace OAuth, channel webhooks, personal DMs, commands, and interactive approvals—while Orqit stays the system of record.
Slack connects to Orqit through the Integration hub for notifications and selected self-service actions. For the full Teams + Slack comparison and admin setup, see the Microsoft Teams & Slack page.
Use Slack for awareness and lightweight actions, then open Orqit for full ticket, asset, and device context.
Slack is Orqit’s deeper chat collaboration surface—configured next to Microsoft Teams in one Integration hub.
Plain-text operational messages to Slack channels via Incoming Webhooks.
Block Kit–oriented DMs for assignments, mentions, approvals, and SLA events.
Slash commands and Events API power the personal assistant.
Approve or reject from Slack interaction buttons when enabled.

Message the Orqit agent in Slack (for example show my tickets) to get structured ticket updates with status and priority—then open Orqit when you need full context.
For the complete Microsoft Teams & Slack Integration hub guide—including how Teams differs from Slack, ITSM event coverage, administration, and security—see:
Microsoft Teams & Slack integration
Slack-specific depth on that page covers workspace OAuth, personal DMs, Events API / slash commands, interactive approvals, and user mapping.
See the Microsoft Teams & Slack integration page for the shared Integration hub, capability comparison, and administrator configuration for both platforms.
No. Slack is a collaboration channel. Agents still use Orqit for full ticket and device context.
Launch a pilot workspace or book a walkthrough — with estimated seat savings versus legacy suites, plus 24/7 support.