Custom end-user notifications are available to Manage plan subscribers. If you are interested in this feature, contact us at

Custom end-user notifications provide three new options when enabled: Do Not Notify Users, Notify Before Patching and Rebooting, and Notify Before Rebooting. Each can be used to tailor the end-user notification experience.

  • Do Not Notify Users: No end-user notifications are sent for any patching event.
  • Notify Before Patching and Rebooting: End-user notifications are sent out for all patches, including those that do not require a reboot. Custom messages can be set for each patch type in place of Automox's default message.
  • Notify Before Rebooting: End-user notifications are only sent out for patches that require a reboot, with an option for a custom message in place of Automox's default message.

NOTE: The policy must be scheduled for the notifications to take effect. If a policy is triggered manually, these custom notifications are not sent.

Custom Messaging

When you enable one of the user notification types, you can set custom messages for both patch and reboot operations, depending on the selected notification. This allows more flexibility in informing end users of what is being patched, the severity of the patch, or your expectations for regular patching.

The default Automox patch message is automatically sent, unless a custom message is provided. Leave the field blank to have the default message sent.

To set a custom message for patching and/or reboot, fill in the text box with messaging of your choice. Message length varies depending on your operating system. Messages for Windows can be up to 125 characters, and for Mac they can be up to 70 characters. They can contain Unicode characters, and appear in Windows and Mac default notification windows.

Remediation time for the patching window can also be optionally provided to the end user by using the {{remediationTime}} tag. This tag will automatically fill in the patch window for the policy, giving the end user more context around when to expect patch or reboot operations.

Custom Deferral Times

You can set three or fewer deferral times for notifications, allowing end users to delay a patching operation for a number of hours. By default, users are able to defer for 1, 4, or 8 hours. You can override these settings to provide different time intervals based on your needs.

To set custom deferral times, fill in the three boxes for the first, second, and third deferral options, as needed. All numbers are represented in hours, only integers are accepted, and the maximum single deferral time is 24 hours.

Custom Number of Deferrals

You can also set a custom number of deferrals for notifications. When set, the end user is able to defer patching up to the provided number of deferrals. On the last possible deferral, the patch is applied as guided by the policy.

If a user misses the patch notification, their system is automatically patched and/or rebooted 15 minutes after the missed notification.

To set the number of deferrals, fill in a number in the “Number of Deferrals Allowed” field. The default number of deferrals available is 3. You can set as few as 1 deferral or as many as 10.

Did this answer your question?