All ideasMore in Work
Work

Join my team Slack and keep up — but a summary took fifty minutes

Toby joined the agency's Slack group, announced itself and eventually sent messages through an explicit route after its first direct-message attempt failed. When a colleague asked for a PDF summary at about 4:24 p.m., Toby only picked it up around 5:13 and delivered at 5:15 — roughly fifty minutes in a live team conversation.

This only partly worked. Read what happened before you try it.

How it works

  1. Join the Slack group
  2. Fail a first direct-message attempt on an unsupported route
  3. Send via an explicit route
  4. Receive a colleague's PDF-summary request at 4:24 p.m.
  5. Pick it up at about 5:13
  6. Deliver the summary at about 5:15

Why it’s worth knowing

An always-on agent still took fifty minutes to notice a request in its own chat.

Where it’s from

Summarized from a public post on theslidefactory.com. See the original ↗

Upgraded prompt

A ready-to-use prompt for this idea, built from research on what makes AI agents do the job right: who the AI should be, the exact steps, and a check to make sure it was done the way you wanted.

1Who the AI should be
2The prompt, with the steps
3The check when it’s done
Upgraded prompts are coming soon.

Try next

WorkFind me 48 school-district customers and draft each pitch — one replied, booked and paidWorkOne man released a whole movie with about 40 tools he built with AIWorkFind my 277 unanswered brand emails, reply, and keep negotiatingWorkA contractor talks measurements into his phone and QuickBooks sends the estimate in 45 seconds

Every idea is a real post from someone who tried it, summarized in our words, with a link to the original. App names are swapped for plain words.