Scheduling a job from chat
Worked examples: digests, monitors and reminders.
Jobs are created in plain language from Chat, or with the form on the Jobs page. These examples show what to ask for and what happens next.
A morning digest
every weekday at 9, check Help Scout for VIP conversations open for more than a day, look each customer up in HubSpot and the warehouse, and write a short digest with the ones that need attention first
Memtro creates a shared or personal job (it asks if unclear, or defaults to personal), confirms "At 09:00, Monday through Friday (Europe/London)", and says when the first run is. Each morning the report lands in a chat called Job: VIP ticket digest.
A monitor
every 15 minutes, check Stripe for failed payments in the last hour and, if there are any, list the customers and amounts; otherwise say nothing happened
Runs are cheap when nothing happened: the prompt tells the agent to say so in a line.
A weekly summary for the team
every Friday at 4pm, summarise this week's closed deals from HubSpot and merged pull requests from GitHub for the team, shared with the organisation
A shared job is visible to everyone on the Jobs page and editable by its owner and admins. It still runs as the person who created it.
Managing jobs from chat
- "list my jobs"
- "pause the VIP digest until next week" (then "resume it")
- "run the Stripe monitor now"
- "change the weekly summary to Thursdays at 5"
- "delete the Stripe monitor"
Writing a good prompt
The job's prompt is read by a future assistant with the same tools but no memory of your conversation, so include names, systems, filters and what the report should contain. Say what to do when there is nothing to report. Timezones are IANA names (Europe/London); the default is Europe/London.
Where results go
Every run is recorded with its status, tool calls and output under the job on Dashboard → Jobs. The report is also appended to the job's chat in Dashboard → Chat, where you can ask follow-up questions about it.