Choose a cadence and where results land

Two settings decide whether a Routine is useful: when it fires, and where the result shows up. Both live in the Routine form, and both read back in plain language so you can check them before you save.

The four cadences

Under When, pick one:

• Once runs a single time. You choose a date, a time, and a time zone: Once on 14 Oct at 9:00 AM.
• Hourly runs every hour at a minute you choose: Every hour at :15.
• Daily runs once a day: Every day at 8:00 AM.
• Weekly runs on the days you select: Every Mon, Wed & Fri at 9:00 AM.

There is no cron field, and cron text is rejected on purpose. If you need a shape the four cadences cannot express, run two Routines.

Time zone

Every recurring Routine stores an explicit time zone, pre-filled from your browser. It is part of the schedule sentence, so check it when you travel or when you are scheduling for a team in another region. A 09:00 Monday briefing set in one zone does not follow you to another.

Start and end dates

For anything other than Once, you can set an optional Starts and Ends date. Use Starts to arm something ahead of a launch, and Ends to close a commitment that has a natural finish, like a campaign or a quarter.

Where the result lands

Result delivery is where the complete result is sent. Tick as many as you want:

• TalentOS puts it in your Talent home in the web console.
• Slack sends it to you as a direct message, or to a channel you pick from the list.
• Telegram sends it to your connected Telegram chat.
• iMessage sends it to the number you paired.

A channel only appears once you have connected it, so if Telegram is missing from the list, connect Telegram first and reopen the form.

Asking for a schedule in chat

When you set a Routine up by talking to your Talent, an incomplete time is treated as a question, not an error:

• "Every Monday" with no time resolves to a default time. It recurs, so a wrong guess corrects itself next week and the schedule is read back to you either way.
• "Tomorrow morning" resolves inside that window. The exact minute is a correction, not a guess.
• "Monday" for a one-off run asks you which time you meant, and offers candidates. It fires once, so guessing wrong would be the whole outcome.
• "Tomorrow" asked between midnight and 04:00 always asks which date you meant, and offers both.

Genuinely unparseable text such as "sometime soonish", an unknown time zone, and a time already in the past are refused outright.

A worked example

Your five person marketing team needs a campaign pulse every weekday at 4:30 PM in the team's local time. Create one Weekly Routine, select Monday through Friday, confirm the time zone, and choose the team Slack channel plus TalentOS for delivery. Set an end date for the day after the campaign closes. The schedule sentence and delivery list are your final preflight check.

What to check

• The schedule sentence matches what you meant. It is what gets stored, not the words in your instructions.
• The time zone is the one the audience lives in.
• At least one delivery target is ticked.
• If a Slack channel you picked earlier has vanished from the list, use Refresh next to the channel picker. The available channel list expires and is re-fetched.

Related