Skip to main content
A schedule has an AI employee prepare a piece of work at a set time, every day or every week, with nobody pressing a button. What it prepares waits for a person: a schedule never changes anything in another system by itself. The daily summary is one short email to your owners and administrators about what your employees did.
AI employees are in beta. Schedules and the daily summary need a second switch on your deployment, off by default, so you will not see them unless your deployment has turned them on. See AI employees.

Add a schedule

An Owner or Administrator opens an employee’s page, finds On a schedule and chooses Add a schedule.
  1. Say what to do, with any details, as you would when handing the work over by hand.
  2. Choose Every day or Every week, the day if it is weekly, and a time. Times are in UTC.
  3. Choose Save schedule. It first runs at the time you chose, not straight away.
To stop one for a while choose Pause, and Resume to start it again. Choose Remove to stop it for good. What it already proposed stays in Approvals.

What a scheduled run may do

It reads through the employee’s tools and asks your knowledge at once, as it does for work you hand over. Every answer counts against your monthly allowance. Anything it would change in another system waits for a person, whatever your approval policy says. A policy can let an action run without approval because the person who handed the work over answers for it. On a schedule, nobody did.

When a schedule does not run

The page says what happened under each schedule. Nothing runs while your organisation is suspended, after its trial ends, or if AI employees are turned off for it. It starts again when that changes, and nothing is listed for the time in between. An organisation can keep 20 schedules.

The daily summary

An Owner or Administrator switches on Send the daily summary on the AI employees overview. It is off until then. Once a day it goes to each Owner and Administrator, and lists:
  • Done: what the employees did, by kind of work, with how many of each.
  • Waiting for approval: everything still waiting for a person.
  • Did not work: actions that failed, and scheduled runs that did not run.
It lists counts and titles. It never quotes what a ticket or a message said, what a tool answered or who asked. No email goes out on a day when nothing happened and nothing is waiting. While anything is waiting for a person, however old, the email goes out once a day until someone deals with it. It stops if the person who last switched it leaves or stops being an Owner or Administrator. To start it again, switch it off and on yourself.

Approvals

Where everything a schedule proposes waits for you.

Approval policy

What waits for a person when someone hands work over by hand.
Last modified on November 3, 2026