Scheduling : a conversation that starts by itself

The /planification page

A scheduled task is a conversation that starts by itself at the appointed hour. You write an instruction and a frequency, and you only come back to read what came out of it.

Writing the instruction

Exactly what you would have typed in Chat: "List the supplier invoices more than thirty days overdue and make me a table of them." No script, no formula, no special language. A sentence.

The frequency

Every day at a set time, or one day a week at a set time. Farida set hers for Monday at 8 a.m.: she finds the overdue-payments table waiting when she gets to the office.

Filing the output

By default the answer stays in its thread. You can ask for it to become a corpus document, in the space of your choosing: Monday's weekly summary then becomes material the AI will read on Tuesday.

Getting the report by email

A report you have to go and fetch is not a report. Tick send me the result and every successful run reaches you by email; you can add up to five other addresses. The joinery's accountant has no account here, and yet receives the monthly summary they are sent.

Pause rather than delete

A task you have to delete in order to stop it is a task you will rewrite from memory to resume it, and from memory, you write it badly. The pause button exists: the task stays in the list, switched off, ready to start again.