How to Use Muse to Follow Up on Email

Muse, Meta's personal AI agent, was practically built for this task, because Meta says the agent works asynchronously — it keeps working after you close the app — and comes back when something changes or when it needs approval. In practice that means you can ask it to watch specific threads for replies, keep a status list of who has and hasn't responded, and prepare a follow-up draft when someone goes quiet past your chosen deadline. The send itself stays gated: emailing people is a sensitive action Muse checks with you on first, so the realistic pattern is draft-in-waiting rather than autonomous nagging. The honest limit is reliability — Reuters reported that an internal flight-monitoring test stopped refreshing, and Meta's Vishal Shah has said Muse will sometimes fail to finish things — so for genuinely high-stakes chases, keep a manual fallback.

• Async monitoring is new and Reuters reported a monitoring test that stopped refreshing; confirm your watcher is still active after a day or two.
• Muse prepares follow-ups but sending is a sensitive action — someone who never checks the app will find drafts, not sent mail.
• Caps matter: without an explicit limit, a watcher could reasonably draft multiple reminders for one silent recipient.

1. 1

   Name the threads precisely

   Give senders, subject lines, or dates: 'the venue quotes I sent on the 3rd to the five places on my shortlist.' Vague watches produce vague results.

2. 2

   Set the follow-up trigger

   Define when silence becomes action: 'if no reply after three business days.' Business days beat calendar days for anything professional.

3. 3

   Cap the persistence

   Say 'one reminder maximum per person.' You want to be the person who follows up once politely, not the one who pings four times.

4. 4

   Choose what happens on a reply

   Options: wake me up with a notification, summarize what they said and suggest a response, or draft the reply for review. Pick per thread if the stakes differ.

5. 5

   Confirm the watcher exists

   Because async tasks can stall, ask Muse to confirm what it's watching and check in after a day. The audit trail shows what it has actually been doing.

An independent contractor chasing two overdue invoices and a contract that's been unsigned for over a week.

I'm waiting on three things: a signed contract from Harborview Dental (agreement sent 9 days ago) and payment on invoices #204 and #207 from Ridge Consulting, both past due since the 20th. Check my inbox for any replies from either company. If nothing has arrived, draft one short, friendly-but-firm nudge per item — the invoice wording gets firmer than the contract one, and mention the late-payment terms on the invoices. Hold both drafts for my approval and keep watching these threads each weekday morning. Tell me the moment anything lands from either company, and if you ever can't check, say so instead of going quiet.

• The exact threads to watch

  Sender plus date or subject line keeps the watcher scoped to the right conversations.

• Your follow-up etiquette

  How long to wait, how many nudges, how firm — Muse will otherwise default to its own (possibly pushier) rhythm.

• Your voice for reminder drafts

  Follow-ups are tone-sensitive; a note like 'polite, assumes good intent, no guilt-tripping' prevents robotic nagging.

• What a reply should trigger

  A notification, a summary, or a drafted response — deciding now avoids missed momentum when the reply finally lands.

• An escalation threshold

  Knowing when to stop reminding and try a phone call is human judgment; tell Muse where that line is.

For this task, it is smart to make Muse check with you before it takes certain actions. Decide your rules up front and include them in the prompt.

• Sending each follow-up — Emailing on your behalf is a sensitive action Muse checks first — approve every reminder before it leaves, individually.

• Second reminders beyond your cap — Persistence past one nudge changes how you look to the recipient; that call should always be yours.

• Replying to something the sender wrote — A reply commits you to terms, dates, or promises — read the incoming message yourself before approving what goes back.

• ✓Batch your watchers: one instruction covering all open chases is easier to audit than five separate monitoring tasks.
• ✓Ask Muse to timestamp its last check per thread — it's the quickest way to spot a stalled watcher without reading everything.
• ✓For payment chases, have Muse quote the invoice number and due date in the draft; specificity reads as organized, not aggressive.
• ✓Let silence-triggered drafts accumulate for a morning review rather than approving each the moment it's written — you'll keep a consistent tone across recipients.
• ✓If a watcher goes quiet, don't assume it's working: ask for the status list and check the audit trail.