Scheduled posts and the weekly digest
The only two times SAM speaks first, and how to make it stop.
SAM speaks first in exactly two situations: the weekly digest you switched on, and a scheduled prompt somebody asked for. Both carry a one-click Stop these button, because a message nobody asked for needs an off switch that isn't "remove this app".
The weekly digest
Run /surface digest in the channel you want it in. It posts Monday morning
in your timezone, covering the last 7 days against the 7 before: lead volume, which
forms and sources drove it, what shipped in content, and AI visibility if it's
enabled.
SAMApp09:00
Lead volume held, but Demo Request is doing the work.
• 312 leads, up 18% week over week
• Demo Request 141 (+31), pricing form 92 (+9)
• Paid search down 12%, the only channel that fell
• 3 posts shipped, the pricing teardown took 41% of content pageviews
Worth a look: the pricing form's second question loses 34% of starts.
The shape is deliberate: one bold line naming the single thing worth knowing, 4-6 short bullets with the numbers behind it, one line on what to look at next, under 180 words. If a number didn't move, it says so. A digest that finds something dramatic every week gets muted by week three.
Run /surface digest again to turn it off. If the bot isn't in the channel yet,
it tells you to invite it before it saves anything, rather than failing
silently every Monday.
Scheduled prompts
Anything else on a timer. Ask in plain English:
Every weekday at 8:30, post who has a draft scheduled today.
DM me every morning at 9 with yesterday's submissions.
Every Monday at 9, post the week-over-week lead numbers.
| Option | Values |
|---|---|
| Cadence | daily, weekdays (Mon-Fri), weekly (pick the day) |
| Time | Any hour, rounded to the nearest quarter hour. 8:30 really is 8:30 |
| Timezone | Yours, from your Slack profile. Half-hour zones such as IST resolve exactly |
| Where | The current channel, or a DM to you |
| Cap | 10 schedules per workspace, digest included |
"Weekdays" follows your working week, not UTC's. Someone in Auckland gets Monday to Friday local, which is Sunday to Thursday in UTC.
Writing a scheduled prompt that holds up
A scheduled run happens with nobody there to answer a follow-up question, so the prompt has to stand on its own.
| Weak | Strong |
|---|---|
| post the numbers | Post yesterday's form submissions as a table: form name, submissions, change vs the same day last week. One line at the top if anything dropped more than 20%. |
| remind me about drafts | List every CMS entry still in draft, oldest first, with who last edited it. If there are none, say so in one line. |
SAM wraps your prompt with an instruction to do the whole thing rather than ask. If something's missing it says what, and carries on with the rest.
Managing them
- See everything: the Home tab, or ask "what do you have scheduled?". Home renders each one in your timezone, not the timezone of whoever set it up.
- Cancel one: the Stop these button on the post itself, or ask it to cancel by name.
Worth knowing
- A scheduled run is a normal turn with a question nobody typed: same tools, same module permissions, same daily cap.
- Scheduled runs cannot create more schedules or start background jobs. A cron that can schedule is a cron that can breed.
- Scheduled posts count against the workspace's daily question limit.
- If a run can't finish, it says so and tries again next time it's due, rather than posting half an answer.