James Plaschke
Builds/Build 08

The 5 Bots That Run My Week

Five bots took the busywork out of my week. Here's each one, and the two I switched off.

BotRunsStatus
Morning briefingEvery morningRunning
Comms coachDaily, ~5pmRunning
Time trackingOn demandRunning
Call runbookBefore each callRunning
Customer health4x a day + MondaysPosts paused
Support digest2x a weekdayRetired
What each bot does and when it runs.
The problem

Starting the day meant opening six apps to work out what mattered. Timesheets are universally hated, so people under-report. Feedback on how I write came once a quarter.

How it works
  1. Support digest: looks up who is on call, then posts their open and unassigned tickets to Slack. Built and ran twice a weekday.
  2. Customer health: scores accounts on usage, engagement and expansion, alerts on a 10-point drop, and sends a Monday action list. Built and ran; posts are paused.
  3. Morning briefing: today's calendar, email, Slack highlights and open tasks in one post, then a 3-5 item must-do plan.
  4. Comms coach: reads the day's messages and transcripts and DMs me wins, verbatim fixes and multi-week patterns.
  5. Time tracking: classifies calendar events, posts a review table to Slack, takes plain-English corrections, then files the entries.
  6. Before a call: a runbook skill builds a second-screen HTML run sheet with timed beats, from the real transcripts.
The numbers
89accounts scored, up to 4x a day
23teammates registered for time tracking
7,689impressions on my LinkedIn post about the comms coach
The value
  • My day starts with one post instead of six apps, which saves about 20 to 30 minutes each morning (my estimate).
  • Teammates file their time by confirming a table instead of filling in a timesheet. 23 have signed up.
  • Before every call I have a run sheet built from what the customer actually said.
  • Together, the bots save me about 30 minutes to an hour a day (my estimate).