Weekday Resets Container explained

The plain Reset Times field resets a list at the same clock times every single day. That is fine until your week is not uniform. Maybe you dial hard Monday through Friday but barely on weekends. The Weekday Resets Container is how you give each day of the week its own reset schedule, so a Lead gets recalled on a rhythm that matches your real staffing.

It builds on the same reset idea covered in the lists and leads guide, just with finer per-day control.

What a settings container is

A Settings container is a small reusable block of configuration you define once and point many things at. For weekday resets, you create one of type LIST_WEEKDAY_RESETS, fill in the per-day times, then set the list's Weekday Resets Container field to that container. The default for the field is DISABLED, so nothing happens until you assign one.

Inside the container, each weekday gets its own dash-separated reset times in 24-hour format. A working example looks like this:

• monday => 0830-1230-1800
• wednesday => 0930-1200-1730-1900
• saturday => 0930-1100

To leave a day with no resets, either skip the line entirely or list the day with no times after the arrow. Sunday can simply be left out. The format inside the container is the same 24-hour, dash-separated style you already use in the plain Reset Times field, so there is nothing new to learn beyond the per-day arrow syntax.

Because the container is a reusable settings block, you can point several lists at the same one. If three campaigns share the same weekly rhythm, define one LIST_WEEKDAY_RESETS container and assign it to all three lists. Change the schedule in one place later and every list that references it picks up the new times. That saves a lot of tedious editing and keeps your reset policy consistent across the floor.

How it layers with Reset Times

flowchart TD
  A[Reset reaches its time] --> B{Reset Times field set?}
  B -->|Yes| C[Run those resets every day]
  A --> D{Weekday container set?}
  D -->|Yes| E[Run today's weekday resets too]
  C --> F[List becomes callable]
  E --> F

Here is the key behavior: the container does not replace the daily Reset Times field. Any times you set there still run every day. The weekday container adds extra, day-specific resets on top. So a list can have a baseline 1200 reset every day from Reset Times plus heavier Monday resets from the container, all feeding the Hopper together.

Per-weekday resets are handy when staffing or compliance windows shift across the week, for example lighter Saturdays and no Sundays. Match the container to when your Campaign actually has agents on the floor. To review what a list holds before you schedule it, see what is a VICIdial list.

One common mistake is to assume the container overrides the daily field. It does not. If you already have 1200 in Reset Times and then add monday => 1200 in the container, that Monday gets two resets at noon stacked on top of each other, which is wasted effort at best and over-dialing at worst. Decide whether a list should be driven by the daily field, the container, or a deliberate combination of both, and write your times with that choice in mind.

Want settings containers and per-weekday resets ready on a tuned dialer instead of building them yourself? See our pricing and have a managed VICIdial server running in under 40 seconds.