Muse WorkflowPlaybooksPlan a workflow
← All playbooks
Personal operations / Vendor example

Triage your inbox without automatically replying

Separate messages needing a decision from reference material and low-priority mail.

MuseBeginnerOriginal editorial guide

What you’ll produce

A source-linked inbox review with action items, deadlines, and unsent reply drafts.

Inputs & connections

  • A limited date range or mailbox label
  • Your priority rules and examples of messages that matter

Begin with approved exports or pasted source material. Live access requires separately configured integrations and permissions; this guide does not install them.

Your starting prompt

Replace the bracketed fields. This is our suggested prompt, not a quote from the source.

Review [mailbox scope] using [priority rules]. Return messages requiring my decision, deadlines explicitly stated in the email, unanswered questions, and optional unsent reply drafts. Link to the original message and distinguish an explicit commitment from an inference. Do not send, archive, delete, unsubscribe, or change labels. Ask for clarification when the sender's intent is unclear.
Open Muse ↗

How to run it

  1. 01

    Connect only the mailbox access you intend Muse to use, or provide approved exports.

  2. 02

    Define the time range and examples of high-priority messages.

  3. 03

    Compare the first brief to the original messages, including excluded items.

  4. 04

    Adjust rules and use an approval step for any later actions.

KEEP A PERSON IN THE LOOP

Review before you act

Check deadlines, recipients, commitments, and any message the assistant may have missed.

Limitations & success checks

  • Mail access and available actions depend on your configured account.
  • A large inbox demonstration does not prove reliable triage for every mailbox.

Measure: Missed important messages, false priorities, and corrections to draft replies.

Sources & attribution

The sources below support the reported example or a tool capability. They do not validate our prompt or prove the outcome in your environment.

Vendor exampleMuse email demonstration ↗

September 8, 2026. Official demonstration of working with a large email history. Our priority rubric and draft-only prompt are editorial additions.

Creator / publisher: Muse, featuring Casey and Hal

Official documentationIntroducing Muse ↗

Official introduction of the personal agent. Connector access, account availability, and action permissions still need to be configured.

Creator / publisher: Meta

Editorial review: 2026-10-11. How we label evidence.

FROM A USE CASE TO A WORKING SYSTEM

Have a workflow worth building?

Ferociter plans and builds AI workflows for hospitality and commercial real estate teams.

Talk through your project ↗