Routines: the work you never ask for
The jobs your assistant does without being asked — the two that are always on, the ones you write yourself, and how to read what each run did.
Everything in the last article started with you typing. A routine is the other half: a job your assistant does on its own, either when something happens or at a time you picked. Routines in the sidebar is where they all live.
The two that are always on
These start the moment your mailbox is connected, and you cannot switch them off:
- Inbox Triage — an email arrives, your assistant reads it, files it against the right company, contact and deal, and moves the deal on if the thread moved it. Anything worth your attention shows up on Where you stand.
- Meeting Debrief — a recording finishes transcribing, your assistant reads the conversation, files it, updates the record and writes the summary onto the recording.
The reason they are not optional is the reason they are safe to leave running: on this path your assistant has no way to write to anyone. It reads, files and tells you. Replying is not a thing it can do here — the ability is not in its hands on this route, so a connected mailbox never means a surprise email.
Routines you write
Everything else is yours. A routine you add is a time plus an instruction in plain language — the same thing you would type into the box on Home, except it runs on a schedule. Daily, weekdays, or one day a week, at a time you set. You can keep twenty.
Four templates give you a starting point, and each is only an instruction you can rewrite: Daily briefing, Meeting prep, Weekly review, Pipeline pulse.
When one runs, it opens as a conversation under Recents, exactly as though you had asked. That matters more than it sounds: the result is not a report you read and close. You can reply to it, push back, ask for the version that leaves out the deals you already know about.
Reading what happened
Open any routine for its Logs — every run, what triggered it, and what came of it. A scheduled run links to its conversation; a run that fired on an email or a recording keeps a read-only replay you can open.
Each routine also carries its own model, which you can change, including on the two built-in ones. If your workspace runs out of credits, runs do not fail silently — the work queues and replays once you top up.
A routine that has produced nothing useful twice running is telling you the instruction needs sharpening.
Next: what it is all writing to
Triage files things; debriefs update records. Companies, contacts and deals is the three tables underneath all of it.
Up next
Companies, contacts and deals
The three tables your CRM is made of, the typed fields on them, the memory behind every record, and how the shape changes when you need it to.