Skip to main content
A track is a sequence of days. Every step sits on a day (Day 1, Day 7) and has a send time, so the builder reads top to bottom as a timeline of exactly what arrives when.

​
📅 Days

Day 1 is the member’s first day on the track - the day it kicks off for them, which is the day they are enrolled. On a user-joined track, enrollment is the later of the member’s start date and the day they join Slack: if your HRIS provides a future start date, the track waits until then, so Day 1 is that start date; otherwise Day 1 is the day they join. Because Day 1 is always the enrollment day, the track never stacks days. Add a tenured employee, or a new hire who joins Slack a week late, and they simply begin at Day 1 when they enroll - no backlog of earlier days arrives at once. Days count only the Track’s working days. With the default Monday-to-Friday workspace policy, Day 1 on Monday makes Day 5 Friday and Day 6 the next Monday. A Track can override those days. With a five-day week, Day 30 falls about six calendar weeks after enrollment. See Working days and catch-up hours. In the builder, consecutive steps that share a day are grouped under a day divider (for example, “Day 3”). Edit the divider’s number to move every step in that group. Click the + on the connector between steps and choose Send on a day to start a new day.
The builder keeps steps in delivery order from top to bottom: days ascend, and within a day steps sort by send time. Changing a day or time moves the step to its slot, and dragging a step adjusts its time to fit its new position.

​
Working days and catch-up hours

Working days determine which days steps can run and how Day N advances in each member’s time zone. Doozy also checks overdue catch-up against the selected days and daily hours in that time zone. At least one working day is required. A sparse schedule such as Monday, Wednesday, and Friday can put up to three calendar days between consecutive steps. Start and end times apply only to overdue catch-up. They do not move a future step’s send time. If an overdue step is ready outside the recipient’s working day or hours, Doozy waits until the next opening. Overdue steps may run exactly at either time boundary. The workspace default is Monday to Friday, 09:00 to 17:00, with Europe/London as the default timezone. A workspace owner can change working hours and the separate default timezone under Workspace settings → Track settings. Doozy uses the default timezone only when a member has no time zone. New Tracks use the workspace policy unless you turn on Override workspace working days and hours in the Track’s trigger settings. Older Tracks keep their saved working days and use the workspace’s hours until you set their Working Hours. Changes apply only to new enrollments. People already enrolled keep the policy they started with.
These are daytime windows only. Choose times to the minute in HH:mm format. The start time must be earlier than the end time. Equal, reversed, or overnight windows are not valid.

​
🕘 Send times

Every step has a send time, shown next to the step title. Steps send at 9:00 AM in the member’s local time zone by default; click the time to change it. Put two steps on the same day with different times to pace them within a day (9:00 AM, then 11:00 AM). An authored future send time remains due at that time even if it falls outside working hours.

​
🙋 Catch-up: if someone reaches a step after its time

Catch-up is a single on/off setting for the track, on by default. It decides what happens when a member reaches the track after a step’s send time has already passed that day, for example, when someone is added mid-afternoon and Day 1 has a 9:00 AM step. Nothing is ever skipped either way:
  • On (default): overdue steps become eligible in order during working hours.
  • Off: Day 1 shifts to the next working day, and no step is sent before its time.
Find the setting in the track’s trigger settings.

​
🔄 Tracks built with waits

Tracks built before day-based timing could space steps with relative waits (“wait 2 days”). Those tracks keep running with their exact original timing. When you open one in the builder, it appears converted to days and times, with a notice that it was upgraded to day-based timing. Nothing changes until you save; saving adopts the days and times shown, and the first save asks you to confirm.

​
⭐ Best Practices

  1. Anchor milestones to days: Day 1, Day 5, Day 30 intervals work well
  2. Use times for same-day pacing: Two steps on one day, an hour or two apart
  3. Keep momentum: Avoid gaps longer than 2 weeks between touchpoints

​
🔗 Related Steps