​
Definition

Calendar is an organization-scoped time view of work that already has a date or window. Events can come from Automation schedules, Issue dates, Agent Run windows, or configured calendar sources. A navigable event keeps a link to its source object. Calendar answers when something was scheduled or happened. The source Issue, Automation, or Run still owns its status, result, and next action.

​
One illustrative case

The operations digest is scheduled for 18:00. Calendar shows the scheduled event and, after execution, the run window. The owner opens the event, follows it to the Automation, and checks the linked Chat result. If the run failed, the failure is handled on the source run and Automation record, not by editing a separate Calendar status. Calendar work history

​
When it is useful

Use Calendar to see timing, overlap, missed windows, and human checkpoints across a period. Day, week, and month views change how the same source events are arranged. They do not change the underlying records. For current ownership or a decision that needs attention, return to the source Issue, Messenger thread, Automation, or Agent Run.

​
Operating boundaries

Calendar is not an assignment queue and does not infer that time spent means work succeeded. It must preserve organization scope and source identity. The highest-risk boundary is duplicate state. A Calendar event must never become a second status record for an Issue or Automation. If a source changes, Calendar reflects that source rather than maintaining an independent truth. For repeated schedules, read Automations. For attention recovery, read Chat and Messenger.