CHAPTER 10 GUIDE
The Weekly Rhythm
In short
Up to now, you've been starting every job yourself. You finish an edit and send the transcript to the packaging bot.
Routines, in plain words
A routine is a job a bot does on a schedule, or when something happens. "Every Monday at 8 AM, check the business inbox and send me a summary." "When a new video is published, draft the X posts."
Two kinds of trigger
Some routines run on a clock. Every day, every Monday, the first of the month.
The upload-day chain
Here's how the work flows from that one action.
A sample week
Here's what a week at Patch and Mend looks like once the routines are running. This is an example, not a promise.
The weekly stats summary
One routine I'd add for every channel is a weekly summary of how things went. Keep it short.
The inbox sweep
Your deals bot can run every morning or a few times a week, sorting new email and drafting replies. Pick a schedule that suits how fast sponsors expect to hear back.
Usage limits
Every routine uses some of your Grok Bot allowance. My first book explains how usage limits work and how to check what you have left.
When a routine goes wrong
Sooner or later, a routine will do something odd. It might send you drafts for the wrong video, or skip a week, or write the X posts in a strange tone.
Reviewing the team
Once a month or so, take ten minutes to look at the whole team. Is every bot still useful?
Back to that week
Remember the week from Chapter 1? Here's the same week at Patch and Mend after the bots, as an example.
What went wrong: the routine that ran twice
One week, the owner saved the transcript, noticed a typo in the file name and saved it again with a corrected name. The routine ran twice, and two sets of drafts arrived.
A worked example: the quiet month
In one summer month, Patch and Mend's views dropped. The weekly summaries showed it clearly.