Understanding "End of Queue, Min. 1 Day" in VanillaSoft

In VanillaSoft, the result action "End of Queue, Min. 1 Day" behaves differently from other similar options, such as "Retry In 1 Day." Here's how it works:

Delay Timing

End of Queue, Min. 1 Day: This option delays the lead until the following day at some time, but not necessarily a full 24 hours from the current time. It simply postpones the lead until the next day, without specifying an exact time within that day.

Retry In 1 Day: In contrast, this option delays the lead for a full 24 hours from the current time.

Custom Time Settings

24-Hour Cycle: Other "End of Queue" intervals, such as "End of Queue, Min. 2 Days," use the 24-hour cycle. For example, "End of Queue, Min. 2 Days" would delay the lead for a minimum of 48 hours.

Custom Time: To ensure a lead waits a full 24 hours before re-routing. Users can specify a custom time and set it to 24 hours. Alternatively, using a custom time and setting it to "1 Day" achieves the same result, as "1 Day" in this context also means 24 hours.

Special Case

"1 Day" Exception: The "1 Day" option is unique in that it behaves differently with "End of Queue, Min. 1 Day," where it simply means moving the lead to the following day without specifying an exact 24-hour delay.

By understanding these distinctions, users can effectively manage lead routing and timing in VanillaSoft.