Overview
Scheduled Chats let you set up recurring Ender Chat reports that run automatically on a schedule. Instead of manually creating a new chat each time, you define the question, filters, frequency, and audience once, and the system generates a new result chat on each scheduled run.
There are two report types:
General purpose -- sends the same report to a list of recipient users.
For agent -- generates a separate report for each target team or agent.
Each schedule tracks its run history, and you can open the latest result directly from the schedule list.
How It Works
Accessing Scheduled Chats
Open EnderGPT from the main navigation sidebar. If you have access to both regular chats and scheduled chats, the chat sidebar on the left shows two top tabs:
Chats -- regular chat history.
Schedule -- opens the Scheduled Chats list in the main area.
Click Schedule to open the list. To return to your regular chats, click Chats.
If your role only has scheduled chat permissions (without regular chat permissions), the EnderGPT workspace opens directly to the Scheduled Chats list and the tab strip is not shown.
Viewing the Schedule List
The Scheduled Chats page displays all schedules, including inactive ones. Each schedule card shows:
Name and prompt -- the schedule title and the question that runs on each execution.
Report type -- either "General purpose" or "For agent."
Status -- "Active" or "Inactive."
Latest run status -- "Queued," "Running," "Completed," "Failed," or "No runs yet."
Frequency -- Daily, Weekly, Monthly, or Quarterly.
Next run -- the date and time of the next scheduled execution.
Last run -- the date and time of the most recent execution.
Recipients / targets -- for general-purpose reports, the recipient user names; for agent reports, the number of target teams and agents.
Last result -- a summary of the most recent run result. When a completed result is available and you have access to it, an Open result button appears.
Creating a Scheduled Chat
Click New Schedule in the Scheduled Chats list header. (When the list is empty, the same action is also offered from the empty-state card.)
Fill in the form:
Name -- a title for this schedule (up to 255 characters).
Prompt -- the question the AI should answer on each run (up to 20,000 characters).
Report Type -- choose General purpose or For agent.
Filters -- optionally add filters to narrow the data scope. Date filters are never allowed in scheduled chats. Agent reports also block agent filters in the filter set.
Frequency -- choose Daily, Weekly, Monthly, or Quarterly.
Run time -- the time of day the schedule should run.
Timezone -- the timezone for the run time. Defaults to your browser's timezone.
Defer next run -- leave unchecked to let the system use the schedule's next valid run based on the frequency and run time. Check it to pick a specific Next run date instead.
Add the audience:
For General purpose reports: add at least one recipient user by searching for users in the recipients field.
For For agent reports: add at least one target team or target agent using the targets picker. Open the picker, select teams and/or individual agents, then click Apply.
Click Save.
Editing a Scheduled Chat
From the schedule list, click Edit on the schedule card. The edit form opens pre-filled with the current settings. Make your changes and click Save.
How your edits affect the Next run timing:
Changing frequency, run time, or timezone automatically recomputes the next run to the next valid slot for the updated schedule. For example, moving a weekly schedule from 09:00 to 18:00 shifts the next run to the next 18:00 slot instead of leaving the previous 09:00 time in place.
Checking Defer next run and picking a Next run date overrides the automatic calculation and uses the date you selected, using the current run time and timezone.
Other edits -- such as name, prompt, filters, recipients, targets, or activating/deactivating the schedule -- do not change the next run time.
Deactivating and Reactivating
To stop a schedule from running, click Deactivate on the schedule card and confirm in the dialog. The schedule becomes inactive and will not generate new runs until reactivated.
To resume a deactivated schedule, click Reactivate on the schedule card.
Viewing a Scheduled Result
When a schedule completes a run, you can click Open result on the schedule card to open the generated result chat. The result chat opens in the regular chat view with a Scheduled label.
Scheduled result chats have restricted actions compared to regular chats:
Action | Schedule owner | Other viewers |
Read the full chat result | Yes | Yes |
Send follow-up questions | Yes | No |
Copy message text | Yes | Yes |
Copy chat link | No | No |
Like or dislike responses | No | No |
Regenerate responses | No | No |
Switch between response versions | No | No |
Rename | No | No |
Delete | No | No |
Manage sharing | No | No |
Move between projects | No | No |
Viewers who are not the chat owner see a read-only indicator at the bottom of the chat.
When No Conversations Match the Filter
If a scheduled run executes and its filter matches no conversations for the reporting period, the system does not generate a result chat. The run is recorded as completed in the schedule's run history, but the Last result column shows no chat to open.
Instead of a result chat, each recipient receives a Scheduled chat skipped notification:
In-app card. Appears in the notifications list with a "No conversations matched" headline and the name of the scheduled chat. This card is always delivered in-app and cannot be turned off.
Email. Sent when the recipient has the email channel enabled for the Scheduled chat skipped event in their Profile notification settings. The email shows the reporting period, the filter summary, and up to two action buttons:
Review filter -- opens the Conversations view with the schedule's filter pre-applied, so the recipient can confirm there really is nothing in the period. This button is included only when the recipient also has permission to view conversations.
Edit schedule -- opens the schedule edit form. This button is included only when the recipient has permission to manage scheduled chats.
A skipped run does not count as a failure. The schedule stays active and will run again on its next scheduled tick. A quiet schedule -- one that only notifies when something matches -- can be a deliberate setup, so the notification suggests reviewing the filter rather than deactivating the schedule.
When a Run Fails
If a scheduled run cannot produce a result -- for example, the target agent is no longer available, the LLM provider is temporarily unable to respond, or the report cannot be generated for the reporting period -- the schedule's Last result column shows a short failure reason in your interface language. Possible reasons (shown here in English) are:
The LLM provider quota was exceeded (429). -- The underlying AI service refused the request because of a rate or usage limit. This is typically the most actionable one: raise the quota with the provider or move the schedule to a less busy run time.
Could not queue the scheduled result. -- The run could not be picked up for execution.
Research could not gather enough evidence. -- The AI could not find enough matching material to produce a report for the reporting period.
The scheduled chat is no longer available. -- The schedule was removed before the run finished.
The schedule owner is no longer active. -- The user who created the schedule has been deactivated.
The target agent is no longer available. -- An "For agent" report cannot resolve one of its target agents (missing, or no active linked user).
The generated result is no longer available. -- The result chat produced by the run disappeared before it could be published.
Failed -- A generic label shown when the failure does not match any of the reasons above, or when the run predates the current failure reporting behavior.
Failure reasons are always drawn from this fixed set. Raw error text, stack traces, connection strings, and other internal diagnostics never appear in the schedule's failure reason -- if the underlying error does not map to a specific reason above, the run is shown as Failed with no additional text.
A failed run does not deactivate the schedule; the next scheduled tick will run as usual.
Access and Permissions
Who Can Access Scheduled Chats
Action | Required access |
See the EnderGPT navigation item | Any chat permission (regular chat, scheduled chat, or scheduled result) |
Open the Scheduled Chats list | Scheduled chat view or scheduled chat manage permission |
Create, edit, deactivate, or reactivate a schedule | Scheduled chat manage permission |
Open a scheduled result chat | Scheduled result view permission, or ownership of the result, or direct-target access to the result |
Either scheduled chat view or scheduled chat manage permission is enough to open the Scheduled Chats list and to see the Schedule sidebar tab when the user also has regular chat history access. Manage permission alone (without view) is sufficient -- a separate view grant is not required.
Default Landing
Users with regular chat permissions land on the chat home screen by default.
Users who have scheduled chat view permission but no regular chat permissions land on the Scheduled Chats list.
Users who only have scheduled result permissions can open result chats through links sent to them (for example, from notifications) but do not see the Schedule sidebar tab.
Open Result Visibility
The Open result button on the schedule list appears only when you have confirmed access to the resulting chat. If your access cannot be verified (for example, due to a temporary error), the button is hidden and the result status shows as available without a direct link.
Form Validation Rules
The scheduled chat form enforces these rules before saving:
Name is required.
Prompt is required.
Run time is required.
Timezone is required.
Next run date is required when the "Defer next run" option is checked.
General-purpose reports require at least one recipient user.
Agent reports require at least one target team or target agent.
Date filters (date range, datetime range) are never allowed.
Agent filters are not allowed in the filter set when the report type is "For agent."
Frequency Options
Frequency | Description |
Daily | Runs once per day at the configured time |
Weekly | Runs once per week at the configured time |
Monthly | Runs once per month at the configured time |
Quarterly | Runs once per quarter at the configured time |