---
title: Setting up Slack as a contact method
description: You configure Slack to enable users to receive Slack notifications for escalations. To offer Slack as a contact method for shift members, you install the IntegrationHub spoke for Slack.
locale: en-US
canonical_url: https://www.servicenow.com/docs/r/australia/it-service-management/on-call-scheduling/slack-setup-oncall.html
release: australia
product: On-Call Scheduling
classification: on-call-scheduling
topic_type: reference
last_updated: "2026-03-12"
reading_time_minutes: 2
breadcrumb: [Configuring On-Call Scheduling, On-Call Scheduling, IT Service Management]
---

# Setting up Slack as a contact method

You configure Slack to enable users to receive Slack notifications for escalations. To offer Slack as a contact method for shift members, you install the IntegrationHub spoke for Slack.

## Configuring Slack for On-Call Scheduling

The Slack spoke automates On-Call Scheduling notifications and responds to them. The following configurations support On-Call Scheduling notifications:

## Outbound Configurations

-   **Slack > Outbound Configurations > On-Call: Assign by Acknowledgement**

    Generates a general escalation message. Modify the record to customize the message template.

    \[Omitted image "slack-outbound-assign-by-ack-oncall.png"\] Alt text: Outbound Assign by Acknowledgement subflow

-   **Slack > Outbound Configurations > On-Call: Assign by Acknowledgement Catch All**

    Generates a catch-all escalation message. Modify this record to customize the message template.


\[Omitted image "slack-outbound-catch-all-oncall.png"\] Alt text: Outbound Assign by Acknowledgement Catch All subflow

## Inbound Decisions

-   **Slack > Inbound Decisions > On-Call: Assign by Acknowledgement Decision**

    Defines inbound configuration for general response handling for Accept or Reject escalation messages. Use **action\_id** as the key to map outbound configuration and inbound decisions for general escalations. The answer points to the subflow that is executed when the user clicks **Accept** or **Reject**. Modify the record to change the response handling behavior.

    \[Omitted image "slack-decision-oncall.png"\] Alt text: Inbound Assign by Acknowledgement Decision subflow

-   **Slack > Inbound Decisions > On-Call: Assign by Acknowledgement Catch All Decision**

    Inbound configuration for catch-all response handling for escalation for Accept or Reject messages. Use **action\_id** as the key to map outbound configuration and inbound decisions for catch-all situations. The answer points to the subflow that is executed when the user clicks **Accept** or **Reject**. Modify the record to change response handling behavior.

    \[Omitted image "slack-catch-all-decision-oncall.png"\] Alt text: Assign by Acknowledgement Catch All Decision subflow


## Subflows

\[Omitted image "slack-subflows-tab.png"\] Alt text: Subflow designer

-   **On-Call Assign by Acknowledgement**

    This subflow handles incoming responses from Slack and then acts. For example, assign a task to a user and return an acknowledgement message. In case of rejection, the subflow logs the response and moves the escalation to the next escalatee.

-   **Insert Slack Response**

    This action creates a record in the \[sn\_slack\_ah\_v2\_inbound\] table for incoming Slack responses. You can reference the response by workflow based on **context\_id**.

-   **On-Call Response Controller**

    This action performs appropriate operations when the user clicks **Accept** or **Reject** from Slack. It invokes the utility methods to perform actions from the OnCallSlackUtils script include.


**Parent Topic:**[Configuring On-Call Scheduling](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/on-call-scheduling/configuration.md)