Two kinds of requests
Questions. “What did we decide about the pricing page last week?” “Which customers are past due?” Henry answers with sources: the thread, the record, or the document it drew from. Work. “Draft replies to the three unanswered support emails.” “Create a Linear ticket for each bug in this thread.” “Build a sheet of every active Stripe subscription with its renewal date.” Henry does the work, asks for confirmation before anything that changes your tools, and reports back in the same thread.Writing a good ask
- Name the destination. “Put it in the Q3 planning sheet” beats “make a spreadsheet”.
- Say what done looks like. “One row per customer, sorted by renewal date, flag anything renewing in 30 days.”
- Give Henry the thread. Mention Henry inside the discussion the work is about. It reads the thread for context.
- Ask for sources when it matters. Henry cites what it read. If you need a link, ask.
Henry keeps working
A confirmation is never the end of the job. When you click Confirm, Henry carries on with the rest of the work and tells you when it is finished. On big jobs, Henry may finish part of the work in the background and post the result a few minutes later in the same thread. See Long-running work.Fast replies
In Slack, add!fast anywhere in a message to get a quicker, cheaper answer for that one message. Good for lookups where depth does not matter.