Work · Official example
Pick up a dropped thread
Instinct presents following up on unfinished conversations as a use case, and one person on X says it found four people they had dropped the ball on and drafted follow-ups. A second user, who praises it for tracking replies, also calls its memory pretty bad, so read every dropped thread draft before it goes out.
What you can get
Stays in the chat Nothing leaves the conversation.
-
It does
- Nothing is sent — this task ends at a draft
-
It stops and asks
- Before it reads anything: confirm which threads are in scope and which mailboxes are off limits.
- Before you send: check the recipient list, especially on threads with people copied in.
- Before you act on the summary: confirm each unresolved item against the thread itself.
-
You approve
- Read access to the threads in scope
- Approval before anything is sent — this task produces drafts only
Derived from this task's own brief and steps, not from the source.
- Bound the conversation setStops for your approval
Name people, topic, channel, and date range to review.
- Locate the last concrete action
Find the latest question, promise, or decision and nearby closure evidence.
- Classify the thread
Mark it open, waiting, closed, or unclear with a message reference.
- Review a draftStops for your approval
Check recipient, tone, commitment, and missing context before sending anything.
Editorial, not from the source
Works when
- The conversation exists somewhere you can hand over.
- You want the unanswered points listed before deciding whether to reply at all.
- You are going to read the draft before it goes anywhere.
Does not work when
- The conversation happened somewhere it cannot read — a call, a meeting, a channel it has no access to.
- The reply is sensitive enough that the wording needs to be yours from the first line.
- You want it sent automatically. This task stops at a draft.
Pick up a dropped thread: review template
| Thread | Open point evidence | Draft decision |
|---|---|---|
| [Conversation and channel] | [Last meaningful message reference] | [Open / waiting / closed] |
| [Unresolved request] | [Question, promise, or decision] | [Draft or clarify] |
| [Recipient set] | [Role and relationship context] | [Review before sending] |
The source case
Instinct's homepage, as archived on 2026-09-15, listed "following up on threads you've dropped" as something it handles; the current homepage no longer names it. On X, @ItsAlexStarr reports that Instinct proactively found four people they had dropped the ball on and put recommended follow-up drafts in their email, and @aliceisplaying lists keeping tabs on replies, deadlines and reminders; in a later post @aliceisplaying adds that its memory is "pretty bad" and that it is "prone to mix things up sometimes". None of the posts names the threads or says whether the drafts were sent as written; they were checked on 2026-09-24 and are individual reports. A further X post from @snehabytes says Instinct has managed back-and-forth email threads with their immigration lawyer and healthcare insurer, the kind they usually lose track of between replies. The post does not say what was in those emails or whether any reply was sent without their review first.
Published by the product maker. Not independently tested here.
From the source
Source excerpt
Proactively found 4 people I had dropped the ball on with follow-ups and threw the recommended draft in my email.
Source excerpt
kept tabs on replies & deadlines & reminders
Source excerpt
its achilles heel is that whatever memory system it runs on is like, pretty bad and it's also prone to mix things up sometimes
Source excerpt
it has managed back-and-forth emails with my immigration lawyers and healthcare insurance - the kind of threads where I usually lose track between replies.
Quoted from the original posts. Not written by this guide, and not a result produced here.
Suggested prompt
Bring Relevant messages. Acts Nothing is sent — this task ends at a draft. Source official example, checked 2026-10-10.
Written by this guide as a starting point, not quoted from the source. Your edits stay in this browser.
Other ways to ask
Editorial rewrites of the brief above, for a different emphasis. Copy them separately.
What you need
Editorial, not from the source
You supply
- Relevant messages
Connected
- The mailbox or message threads you want reviewed, either connected or pasted in
How to try it
Editorial, not from the source
- Identify the email or message threads to review.
- Ask for a list of unanswered questions and draft follow-ups.
- Check recipients and context before authorizing any message.
Find the decision point in a thread
Scope the search to named people, approximate dates, channels, and the topic rather than sweeping a whole mailbox. Read enough surrounding messages to identify the last concrete request, promise, decision, or unanswered question. A thread may look dormant because it concluded elsewhere, was superseded, or deliberately needs no reply. Build a compact thread note with participants, latest meaningful date, open point, evidence link or message reference, and confidence. Do not infer urgency merely from age; a two-day-old scheduling question may matter more than an old informational exchange. Keep private threads outside scope unless they are explicitly included. Keep a date boundary in the search record so a follow-up is not based on a later message that was excluded accidentally.
Separate a reply owed from a reply optional
Classify each candidate before drafting: needs a response, needs an internal decision first, waiting on someone else, closed, or unclear. This avoids the common error of sending a polite nudge that contradicts later context. For a promised follow-up, recover the promised deliverable and deadline; for a question, restate the question plainly. Where several recipients appear, identify who can answer and who only needs visibility. The output should explain why the thread was selected and what evidence supports the unresolved item, not just provide a long list of messages that happen to lack a final reply. For commitments involving files or approvals, identify the missing artifact rather than drafting a vague “just checking in” message.
Draft with the conversation’s tone and stakes
Draft a message that addresses the actual open point and uses the established relationship and channel. Offer alternatives when the sender needs a choice, but do not manufacture commitments, deadlines, or apologies absent from the record. Preserve names, dates, attachments, and prior decisions exactly; mark missing context for the user to fill. A strong draft ends with a concrete next step, while a sensitive or consequential thread may need only a summary and no draft at all. This task stops at review: check recipient selection and tone before anything is sent. Where a thread contains several topics, split the record so one resolved issue does not obscure another still-open request. Preserve the last message timestamp and channel so a draft does not merge context from a different conversation accidentally.
Open Instinct to try it. That is the product's own site; this guide is not part of it.
Limits and confirmation points
- Only connected or supplied conversations can be reviewed.
- An unanswered message does not always need a reply.
- One regular user reports that the assistant's memory is weak and that it sometimes mixes things up. A list of dropped threads is a starting point to check, not a complete record.
Editorial, not from the source
- Before it reads anything: confirm which threads are in scope and which mailboxes are off limits.
- Before you send: check the recipient list, especially on threads with people copied in.
- Before you act on the summary: confirm each unresolved item against the thread itself.
Editorial, not from the source
- It summarises a thread you cannot find
- Ask for the date, sender and subject line. A summary you cannot trace back to a message is not usable.
- Something you already answered is reported as unresolved
- Ask it to re-read the thread in date order. Replies buried further down a long thread are the usual miss.
- The draft answers a question nobody asked
- Give it the specific message to reply to instead of the topic. A topic search can land on the wrong thread.
- Details from two conversations get mixed together
- Ask for each open item with the sender, the date and the line that is still unanswered, and check the draft against that message before it goes anywhere. One regular user describes the assistant as prone to mixing things up.
Common questions
How do I tell an unresolved thread from an old one?
Look for the most recent concrete question, promise, decision, or requested action, then check nearby messages for closure. Message age is only a cue; classify threads as open, waiting, closed, or unclear using the conversation evidence.
What should a thread review record contain?
Include participants, last meaningful date, topic, the specific open point, message reference, proposed next step, and confidence. This lets you inspect the basis for a follow-up instead of trusting a bare label.
Why can an unanswered message need no reply?
A later conversation, an external decision, or an intentionally informational note can close the matter. Treating every unanswered message as a debt produces unnecessary nudges and can reopen work that is already settled.
How are recipients chosen for a follow-up draft?
Use the thread to distinguish the person who can answer from people copied only for awareness. If authority or ownership is unclear, flag it for review rather than guessing or expanding the recipient list.
Will this task send my follow-up?
No. It identifies unresolved points and produces drafts for your review. You should check the recipient list, tone, attachments, and any commitment before deciding whether to send a message. Keep uncertainty explicit when the ownership of the next action is unclear.
Next
More in Work
Similar tasks
Get recurring task recommendations — ask your own agent to check for relevant updates.