Scheduled Chats

​

What a scheduled chat is

A scheduled chat is an Agent Chat ask set to run on its own cadence. Instead of opening the chat and retyping the same question every Monday, you save the question once, pick how often it should run, and the agent runs it, compares the new answer to the last one, and tells you what changed. You reach it from the Scheduled tab in the chat sidebar. Scheduled runs are always read-only: unlike an interactive chat, where the agent can create, update, and delete on your say-so, an unattended scheduled run gets no write tools, so it only analyzes and reports. Chat, and with it the Scheduled tab, is not available on white-label organizations.

​

How to create a scheduled chat

There are two ways in.

​

From the Scheduled tab

1. Open Scheduled in the chat sidebar. The composer sits at the top of the list.
2. Type the ask in the box (for example, “Which prompts did we lose visibility on this week, and why?”).
3. Click the schedule button and pick a cadence: a preset like Every morning 8:00 or Weekly Monday 9:00, or Custom… for full control.
4. Click the arrow to create the schedule. A confirmation strip appears: the schedule is saved, with a Run it once now button so the first scheduled run has something to compare against.

​

From an existing chat

If you already have a chat you want to repeat, open its options menu and choose Schedule this agent. That prefills the composer with the chat’s first message, model, and tool settings, so you only set the cadence. The quickest starting point is the Suggestions list under the composer. Each suggestion pairs a ready-made ask with a sensible cadence: 7-day GEO briefing, Diagnose visibility, Competitor opportunities, and Content gap sprint. Clicking one fills in the prompt, the cadence, and the tools that ask needs.

​

Setting the cadence

Presets cover the common rhythms. Custom… opens the cadence picker, where you set:

• Frequency: Hourly, Daily, Weekly, or Monthly.
• Every: the interval, so “every 2 weeks” or “every 3 days.” Hourly runs have a floor of every 6 hours.
• Time of day (Starting at for Hourly): the hour the run starts.
• Day of week: which weekday a weekly schedule runs (Weekly only).
• Day of month: which day a monthly schedule runs, from 1 to 28 (Monthly only).
• Timezone: the run fires in the timezone you choose, adjusting for daylight saving on its own.

If you set a cadence that runs more often than your monitors refresh, the picker warns you, because running ahead of your data mostly re-reads the same responses. Match the schedule to how often the underlying numbers actually move.

​

Getting told only what changed

By default a schedule stays quiet when nothing is new. In a schedule’s Edit dialog, the switch Only notify me when the answer changed controls this. When it is on, each run loads the previous run’s answer, the agent leads with what changed since then, and a comparison decides whether the change is material. A run with a real change is delivered; a quiet run delivers nothing and simply records itself in the run history. Turn the switch off to be notified on every run. This is what makes a daily schedule bearable: most mornings you get silence, and the mornings you get a notification are the ones worth reading.

​

Reading run history

Open a schedule to see its runs, newest first. The header shows the cadence and the next run time; each row shows how the run ended and a one-line summary:

• A completed run shows the headline of what changed, or Nothing material changed for a quiet run.
• A skipped run shows why it did not execute (see below).
• A failed run shows the error, or Run failed.
• Running now and Queued mark runs still in flight.

A completed run links to the full chat behind it, so you can read the agent’s full reasoning, not just the headline. A schedule that fails three runs in a row is paused automatically so it stops burning credits on a broken ask. Runs are skipped, rather than failed, for reasons like a paused schedule, a project that is no longer available, no active subscription, a previous run still in progress, the organization running out of Agent Chat credits for the period, or the schedule using up its own share of those credits.

​

Delivering to Slack

A schedule can post its result to Slack in addition to the in-app bell notification. Slack is connected once for the whole organization, then pointed at projects.

1. An organization owner opens Settings → Slack and clicks Add to Slack to connect the workspace. Only organization owners can connect and configure Slack, and it is not available on white-label organizations.
2. Under Channel project mappings, pick a Slack channel and the Promptwatch project it should serve, then Add mapping. Delivery needs this explicit mapping per project: the Default project only decides which project the agent answers for when you chat from an unmapped channel, it does not deliver schedules.
3. Back in a schedule’s Edit dialog, a switch to also post to the mapped channel appears once its project has a channel. Turn it on.

From then on, a run with a material change posts its headline and answer to that channel. The in-app bell notification still fires for the person who created the schedule, whether or not Slack delivery is on. See notifications for the bell behavior, and Slack for the full integration setup.

​

What plan you need

Every paid plan can create up to 10 schedules; the Explore plan can see the tab but not create one. How often a schedule may run depends on the plan too: daily is the floor on Essential, Professional, and Agency Kick-off, and Business, Enterprise, Agency Growth, and Agency Scale unlock the 6-hour hourly cadence. Schedules also draw from a capped share of your organization’s monthly Agent Chat credits, so a busy schedule cannot spend the whole budget on its own.

​

After you schedule it

Use Run now from the schedule’s menu so the next run has a baseline to compare against, then leave it. The schedule will sit quiet until something in your AI visibility actually shifts, and surface the change where your team already works. When a recurring question stops earning its notification, open its menu and delete it; the chats from past runs stay available.