Add Network Enforcement to a Voice or Messaging Service Policy

Depending on your integration, network enforcement in a voice or messaging service policy or service eCommerce policy is ensured by adding a Bucket ID.

If a voice or messaging service policy does not reference a Bucket ID (it says None next to the Bucket ID label) and if the network feature containing the policy or the service eCommerce policy is in Draft or Testing mode, you can add a bucket ID to the policy. Network enforcement may or may not be required in a policy depending on your tenant settings.

Find the voice or messaging service policy in Draft or Testing mode that you want to add a Bucket ID to.
- For a service policy in a network feature, Go to Policy > Features.
- For a service eCommerce policy, go to Policy > eCommerce Policies.
Click the corresponding View button in the right column. (The buttons in the right column appear when you hover the mouse pointer over the row.)
Click the Lock button (to unlock and enable editing).
Make sure that the voice or messaging service policy that you want to add the Bucket ID to has at least one component, and that at least one component has at least one filter. Otherwise, add a component, and then add a filter.
Click None > From Library next to Bucket ID in the upper-right corner of the policy.
Click the radio button next to the Bucket ID you want to use.
Click Add.

The new association is saved automatically.

The goal of network enforcement is to enforce policies on non-embedded-client devices in parallel with the policy filters and policy events that control enforcement on embedded-client devices. If you do not make the filter and policy event in the service policy where you added network enforcement match the bucket ID, non-embedded-client devices and embedded-client devices may behave differently on your network and your intercept notifications may not work properly for notifications or plans that use the service policy.