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 run days, which are Monday to Friday by default, so a step never lands on a weekend unless you choose to run then: if Day 1 is a Monday, Day 5 is Friday and Day 6 is the next Monday. With the default five-day week, Day 30 of an onboarding track is the member’s 30th run day, about six calendar weeks in. You can change which days a track runs on - see Run days below. 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.

​
📆 Run days

Every track has a set of run days: the days of the week it is allowed to deliver steps on. New and existing tracks default to Monday to Friday, so nothing changes unless you pick different days. Day N always counts forward through the run days, in each member’s timezone, skipping any day the track does not run on. Set run days in the track’s trigger settings, next to catch-up, by toggling the days of the week. You can pick any combination, for example:
  • A six-day week (add Saturday) so each Day N comes around in fewer calendar days.
  • A week that starts on Sunday (for example Sunday to Thursday) for teams whose working week does not begin on Monday.
  • Weekends included, if a step should be able to land on a Saturday or Sunday.
You must select at least one day - a track with no run days could never deliver, so the builder blocks it. A sparse set (say Monday, Wednesday, Friday) shows the resulting cadence so a slow schedule is never a surprise.
Run days are the track’s default. When you manually add people, you can tick Run every day for that group to deliver on any day, including weekends - handy for testing a track over a weekend or an urgent enrollment.

​
🕘 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 timezone 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).

​
🙋 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, added mid-afternoon when Day 1 has a 9:00 AM step. Nothing is ever skipped either way:
  • On (default): the passed steps deliver right away, in order, and the rest of the track continues on schedule.
  • Off: the whole track shifts so Day 1 starts clean on the track’s next run 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