Introduction to routines
Recurring jobs your assistant runs on a trigger or a schedule — the morning brief, inbox triage, meeting debriefs, and any job you write yourself.
A routine is a job your assistant does without being asked — either when something happens, or at a time you pick. Routines in the sidebar is where they live.
This is what makes the engine proactive rather than responsive. You do not have to remember to ask for the brief; the brief is already there.
The two that are built in
These run from the moment your mailbox is connected:
- Inbox Triage — when an email arrives, your assistant reads it and keeps your CRM current, capturing real opportunities and filing them against the right deal. It works silently; the moves worth making surface on Your desk.
- Meeting Debrief — when a recording finishes transcribing, your assistant reads the conversation, files it against the right deal, updates the record, and writes the summary onto the recording.
Neither needs setting up. They are marked Built-in.
Routines you add
Everything else is yours to define. A routine is a trigger plus an instruction written in plain language — the same way you would ask in chat, except it runs on its own.
Triggers available:
| Trigger | Fires |
|---|---|
| When an email arrives | On each inbound message |
| When a meeting recording is ready | After transcription finishes |
| Every day at a time | Daily |
| Weekdays at a time | Monday to Friday |
| Every weekday at a time | Weekly |
Four templates are offered as starting points, and each is just an instruction you can edit:
- Daily briefing — what needs your attention today across calendar, inbox and deals.
- Meeting prep — a morning brief on today's meetings: attendees, context, open threads.
- Weekly review — a Friday summary of what moved, who went quiet, what to line up next.
- Pipeline pulse — a Monday snapshot of deals by stage and what has stalled.
Reading the results
Each routine card shows when it last ran and when it runs next. Open a routine to read what it produced on any past run — a routine that has produced nothing useful twice in a row is telling you the instruction needs sharpening, not that the feature is broken.
A routine can be paused at any time without deleting it.
Up next
Dopia's data model
The three tables your CRM is made of, the fields that drive your pipeline, and the memory that sits behind every record.