{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":33262,"path":"it-service-management/on-call-scheduling/slack-setup-oncall.md","title":"Setting up Slack as a contact method","bundle":null,"doc_type":null,"release":"australia","body":"\n# Setting up Slack as a contact method\n\nYou 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.\n\n## Configuring Slack for On-Call Scheduling\n\nThe Slack spoke automates On-Call Scheduling notifications and responds to them. The following configurations support On-Call Scheduling notifications:\n\n## Outbound Configurations\n\n-   **Slack > Outbound Configurations > On-Call: Assign by Acknowledgement**\n\n    Generates a general escalation message. Modify the record to customize the message template.\n\n    \\[Omitted image \"slack-outbound-assign-by-ack-oncall.png\"\\] Alt text: Outbound Assign by Acknowledgement subflow\n\n-   **Slack > Outbound Configurations > On-Call: Assign by Acknowledgement Catch All**\n\n    Generates a catch-all escalation message. Modify this record to customize the message template.\n\n\n\\[Omitted image \"slack-outbound-catch-all-oncall.png\"\\] Alt text: Outbound Assign by Acknowledgement Catch All subflow\n\n## Inbound Decisions\n\n-   **Slack > Inbound Decisions > On-Call: Assign by Acknowledgement Decision**\n\n    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.\n\n    \\[Omitted image \"slack-decision-oncall.png\"\\] Alt text: Inbound Assign by Acknowledgement Decision subflow\n\n-   **Slack > Inbound Decisions > On-Call: Assign by Acknowledgement Catch All Decision**\n\n    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.\n\n    \\[Omitted image \"slack-catch-all-decision-oncall.png\"\\] Alt text: Assign by Acknowledgement Catch All Decision subflow\n\n\n## Subflows\n\n\\[Omitted image \"slack-subflows-tab.png\"\\] Alt text: Subflow designer\n\n-   **On-Call Assign by Acknowledgement**\n\n    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.\n\n-   **Insert Slack Response**\n\n    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**.\n\n-   **On-Call Response Controller**\n\n    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.\n\n\n**Parent Topic:**[Configuring On-Call Scheduling](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-service-management/on-call-scheduling/configuration.md)\n\n"}}