Dispatch October 26, 2026

The One Text at 6 PM That Tells You How the Day Went

It's a little after nine. Dinner's cleared, the kids are finally down, and you've got both feet up for the first time all day. So why is the phone back in your hand?

Because you still don't really know how today went. You've got a feel for it, sure, but the honest picture is scattered across your scheduling app, your payment app, a couple of text threads, and a voicemail you never played. So you open one, then another, then a third, rebuilding the day at the exact hour you're supposed to be putting it down.

You don't need all that every night. You need the four or five facts that tell you whether today was fine or whether something actually wants you. One text, around six, with the day boiled down to what matters. The relay gathers the facts; you spend fifteen seconds deciding if you care.

What a good recap actually says

A recap earns its keep by being glanceable. If you have to study it, it's just another dashboard with the words moved around. Four buckets cover almost any trade.

  • Jobs done. How many you closed out, and which ones are still open. "6 completed, 1 left open (Harmon, waiting on a part)."
  • Money in. What actually hit the account or the card reader today, not what you invoiced. "$2,140 collected across 4 payments."
  • No-shows and late cancels. Who didn't turn up and who bailed at the last minute. Names matter here, because a name is a decision waiting for you.
  • First thing tomorrow. One line: the earliest job, the address, and anything odd about it. "7:30 at 14 Oak, gate code's in the notes."

That's the whole thing. Four lines, maybe five, with a name or a dollar figure doing the heavy lifting. You should be able to read it standing at the fridge with the door open.

What to leave out so it stays glanceable

Most recaps die from doing too much. Someone figures that since the data's sitting right there, it may as well all go in, and by line twelve you've quit reading. Keep these out of the nightly text:

  • Vanity counts. Texts sent, website clicks, how many people opened an email. Maybe interesting once a month, useless at six.
  • Anything you can't act on tonight. If it keeps till morning and isn't tomorrow's first job, it isn't recap material.
  • Full line-item breakdowns. You don't need every charge. You need the total and the one thing that looks off.
  • Good news that needs no decision. Six clean jobs and nothing on fire can be one word: "Quiet day, all clear."

Ask one thing of every line: would it change what you do tonight or first thing tomorrow? If not, it can live in the app for the day you go looking. The recap is a summary, not an audit.

The one or two numbers that should make you look up

A glanceable recap still needs teeth. The point isn't only to inform you, it's to flag the two or three spots where a quick look right now saves a mess later. Pick your triggers and let the robot put them in bold.

  • Money well below a normal day. You know your floor. If collections land under it, that's a look-now, not a shrug.
  • A second no-show from the same name. Once is life. Twice is a pattern, and probably a card-on-file conversation.
  • A job still open past its own day. Usually fine, sometimes a customer waiting on you and getting quietly annoyed.
  • Tomorrow's first job missing something. No address, no gate code, no confirmation. Better to know tonight than from the curb at 7:25.

Keep the trigger list short. If everything's flagged, nothing is. Two or three real tripwires beat a text full of red.

Where the facts come from, and where you still come in

Honest moment. A robot can pull these numbers because they already live in systems that count well: the scheduler knows what got marked done, the payment tool knows what cleared, the calendar knows what's first tomorrow. Wiring those into one message is the easy part.

What a machine can't do is weigh them. It can tell you the Pilcher job's still open; it can't tell you Mrs. Pilcher is the referral queen who gets a call, not a text. It can count two no-shows; it can't decide whether that customer's worth keeping. That judgment is yours, and it should stay yours. The recap just makes sure you're deciding with the facts in front of you instead of a vague worry at midnight.

Which is the real win, honestly. Not the saved minutes, though figure fifteen or twenty a night. It's that you stop carrying the whole day around in your head, half-sure you forgot something.

Worth doing this week

This one roughs out in an evening. Start simple, add later.

  1. Write down the four lines you'd actually want at six: jobs, money, no-shows, tomorrow's first. Borrow the list above if it fits.
  2. Pick your one or two tripwires, the numbers that mean "look now" instead of "look someday."
  3. Find where each fact already lives. If it's only in your head, that's the part to fix first.
  4. Send yourself a recap by hand for three nights. See whether fifteen seconds of reading tells you enough.
  5. Once the shape feels right, have it sent for you. This is the kind of quiet relay we build at TellRobots: set the four lines once, and the text just shows up before dinner.

The goal was never a prettier dashboard. It's closing the laptop at nine knowing the day's accounted for, and trusting that if something needed you, the text would've said so.

More dispatches →