# Scheduled tasks

If you are copying the same request into a chat for the second time, it is no longer a request — it is a task.

## Creating one

Write it as a plain sentence in the chat:

<TryPrompt prompt="Create a task: every Monday at 10:00 send the sales and stock report for the marketplaces." />

The agent asks for anything missing and puts the task on a schedule. From then on it lives under **Tasks**, where you can see the run history, change the time, edit the wording, pause it or delete it.

## Scheduled task, manual run or skill

| When it should happen | What to use |
|---|---|
| By the calendar: every Monday, every morning, on the 1st | A scheduled task |
| It repeats, but you pick the moment: "once the month is closed", "once the export arrives" | A task run by hand: "Run the stock report" |
| The same method is needed by several tasks and chats | A skill, referenced from the task as "follow the Call review skill" |

The fastest route is not writing a brief from scratch but doing the job once with the agent and saying "do this every Monday at 10:00". Run the first task by hand, check the result, fix the wording — and only then hand it to the calendar.

## What a task brief consists of

The agent running the task sees only its text. The order of the lines is practical: where to take from → what to do → what to deliver.

1. **Source** — the service and the account by name: "Ozon, the Main account", "MoySklad".
2. **Period and breakdown** — "for the past week", "per product", "per warehouse". A relative period, not dates.
3. **What to do — as steps with thresholds**: "highlight products that dropped by more than 20%", "flag stock below 14 days of sales".
4. **Result format** — "a message up to 10 lines", "an Excel table, one row per product", and what to leave out: "no general recommendations".
5. **What to do when there is nothing or the service did not respond** — "if nothing changed, send nothing", "if the account did not respond, say so in one line and do not invent numbers".
6. **Where to deliver** — chat, email, Telegram, MAX or Pachca.

| Before | After |
|---|---|
| Every Monday send the sales report | Every Monday at 10:00 take Ozon, the Main account, for the past week: revenue and margin per product, comparison with the previous week and the 10 biggest drops. Deliver as a table, one row per product, plus five lines of conclusions. If the account did not respond, say so and do not invent numbers. Send to Telegram |

## Five rules

- **One account — one task.** Two Ozon accounts and one Wildberries make three tasks. Each has its own run history, and a failed one does not drag the others down. Name the account in the text.
- **Name the task the way you say it out loud.** "Monday sales", "Overdue invoices". That is the name you will use to run it by hand.
- **Thresholds instead of "if something is off".** "Below 14 days of stock", "a drop over 20%". Without a threshold the agent sends everything and hands the decision back to you.
- **A watcher may stay silent.** A task that watches prices or stock should write only when something changed. A daily "all fine" stops being read in the second week.
- **Access before the brief.** The connector is linked, the key has its permissions, the account is chosen. A task without access can only return the question to you.

## What people usually schedule

- a morning digest of money and incoming requests;
- weekly results: what was done, key numbers, next week's plan;
- overdue invoices and expected payments;
- new reviews and rating changes;
- emails and tickets left without an answer;
- stock levels, deliveries and warehouse reconciliation;
- an industry and competitor digest.

## Where results arrive

Wherever suits you: in the chat, by email or in a messenger — **Telegram** or **MAX**. The messenger has to be connected; the channel is chosen when the task is created and can be changed later.

**Phrase a task as carefully as a request**
Period, breakdown and format matter more here than in a one-off request: the task runs without you, and there is nobody to ask for clarification. "Send the sales report" is weak; "send revenue and margin per product for the week, as a file, with the 10 biggest drops" is what you want.

## If a task delivered the wrong thing

Open it under Tasks and fix the wording — the brief can be changed at any time and the run history is kept. You can also trigger a single run by hand instead of waiting for the schedule.

Do not rewrite the task from scratch — add the one missing line: a threshold, a breakdown, a format, a ban on inventing. That way you can see from which run it got better.

**If a task still needs you in its second month**
It is not the schedule that needs fixing but one line of the brief: the account is not named while two are connected, access is missing, there is no rule for an empty result, no threshold, no format.