A routine is recurring work described in plain language and done unattended, the weekly digest, the competitor watch, the content refresh nobody has time for.
Where a journey is a precise flowchart for contacts, a routine is a brief for an agent: what to do, which tools it may use, and where the output goes. Routines handle everything that doesn't message a contact directly, reports, research, data pulls, publishing to your tools.
Each run starts by reading what previous runs covered, then picks up from there, last week's report doesn't get rewritten, the competitor scan starts from the last article it saw. Every run records an outcome and the artifacts it produced.
A routine starts as a draft and can't be activated until it has instructions, no accidentally-live agents. Once on, it follows its schedule, and a Run now button kicks off an immediate run when you can't wait.
Every Monday 08:00 · emails you a summary of last week's sends
Daily · scans competitor blogs and drafts a briefing of what changed
Weekly · runs an AEO check and files the trend report
On demand · pushes approved posts into your Sanity dataset
Anything that doesn't message a contact directly: compile reports, research topics, refresh content, pull data, and publish to your connected tools. If it needs to reach contacts, that belongs in a journey.
Each routine runs with an explicit tool allow-list you set, and it's ops-only by design, customer sends always flow through journeys and their guardrails.
No. Cross-run memory means each run reads what previous runs covered and continues from there, so nothing gets rewritten.
We're onboarding B2B marketing teams during Public Preview. Tell us a little about your team and we'll be in touch.
Prefer to talk first? Book a demo or get pricing from the top of any page.
Placeholder, the Request early access form is generated in Thoughtfuly and embedded here via embed.js. Submissions post to the platform and write straight to your CRM.
