Today, when manually snoozing a conversation, the agent can choose the duration — “until the next reply”, “1 hour”, “tomorrow”, “next week” or a custom date.

When the same snooze is configured as an action within a macro, the time option does not appear in the constructor: the action is selectable, but there is no field to define how long the conversation will be delayed.

Request: equate the behavior of the macro to manual snooze, exposing a duration selector (next answer/1h/tomorrow/next week/custom date) in the configuration of the action within the macro.

Motivation: macros are used to standardize repetitive service flows. Without the duration, macro snooze is tied to the standard behavior and forces the agent to snooze manually afterwards - which negates the macro's productivity gain.