Controlling the on-call communication channel with Notify
Configure On-Call Scheduling with Notify to always use a user's preferred communication channel.
If Force communication channel is specified in the Escalation settings for rosters, the preferred user device is used: SMS, voice, or email.
For example, if the preferred device is SMS and the on-call member does not have an SMS device defined, the user is not contacted even if the user has an email address. When forcing a communication channel on an escalation level does not succeed, no further communication attempts are made. The fact that the user could not be reached is logged.
- On-Call Assign by Acknowledgement workflow
The On-Call: Assign by Acknowledgement workflow is provided with Notify.
Parent Topic:Using Notify with On-Call Scheduling
Related topics
Set up Notify with On-Call Scheduling
Call a user from the WebRTC UI
Key differences between on-call scheduling with NotifyNow and with Notify
[bundle-platadm.c_SubscriptionBasedNotifications]
--- title: Controlling the on-call communication channel with Notify description: Configure On-Call Scheduling with Notify to always use a user's preferred communication channel. locale: en-US canonical_url: https://www.servicenow.com/docs/r/servicenow-platform/notify/c\_OnCallNotifyForceCommChannel.html release: brazil product: Notify classification: notify topic_type: concept last_updated: "2026-09-10" reading_time_minutes: 1 breadcrumb: [Using Notify with On-Call Scheduling, Using Notify, Notify, Manage service capabilities, Extend ServiceNow AI Platform capabilities] --- # Controlling the on-call communication channel with Notify Configure On-Call Scheduling with Notify to always use a user's preferred communication channel. If **Force communication channel** is specified in the **Escalation settings** for rosters, the preferred user device is used: SMS, voice, or email. For example, if the preferred device is SMS and the on-call member does not have an SMS device defined, the user is not contacted even if the user has an email address. When forcing a communication channel on an escalation level does not succeed, no further communication attempts are made. The fact that the user could not be reached is logged. - **[On-Call Assign by Acknowledgement workflow](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/servicenow-platform/notify/c_OnCallAssignByAckWorkflow.md)** The **On-Call: Assign by Acknowledgement** workflow is provided with Notify. **Parent Topic:**[Using Notify with On-Call Scheduling](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/brazil/markdown/servicenow-platform/notify/c_NotifyWithOnCall.md) **Related topics** [Set up Notify with On-Call Scheduling]() [Call a user from the WebRTC UI]() [Key differences between on-call scheduling with NotifyNow and with Notify]() [bundle-platadm.c_SubscriptionBasedNotifications]
| title | Controlling the on-call communication channel with Notify |
| description | Configure On-Call Scheduling with Notify to always use a user's preferred communication channel. |
| locale | en-US |
| canonical_url | https://www.servicenow.com/docs/r/servicenow-platform/notify/c\_OnCallNotifyForceCommChannel.html |
| release | brazil |
| product | Notify |
| classification | notify |
| topic_type | concept |
| last_updated | 2026-09-10 |
| reading_time_minutes | 1 |
| breadcrumb | Using Notify with On-Call SchedulingUsing NotifyNotifyManage service capabilitiesExtend ServiceNow AI Platform capabilities |