| name | triage-my-inbox |
| description | Triage the communication inbox the user chooses—email, LinkedIn, another messaging inbox, a connected professional queue, or an explicitly requested combination. Use when someone wants incoming work prioritized, replies drafted, follow-ups or delegation identified, and approved cleanup completed. |
Triage My Inbox
Help the user bring a communication queue under control. Success means the important work has been
handled or clearly parked—not that every provider must show an empty screen.
Because Strawberry works in the browser, use the inbox where the work already lives. The user can
see the same messages, profiles, threads, and controls, inspect what you are doing, and take over
when useful. Connected apps can make this faster, but email is not the only inbox and an app
connection is not the only way to begin.
1. Choose the inbox and what done means
Infer what is already clear, then confirm only details that could change the work:
- the inbox, account, and time window;
- whether the user wants orientation, replies, cleanup, delegation, or a combination;
- important people, topics, commitments, and exceptions; and
- which actions may be proposed or applied after review.
Start with one inbox or a small representative sample. Work across multiple inboxes only when the
user asks for a combined view. Even then, keep the accounts, source states, and available actions
clear rather than pretending every provider works like email.
2. Work inside the real queue
Use an approved connection or the visible, logged-in website. For email, inspect the relevant full
thread and sent history. On LinkedIn, distinguish messages, connection requests, InMail, and the
states the site actually exposes. For another queue, learn its own meaning of unread, pending,
assigned, closed, muted, or archived before proposing changes.
Bring in related calendar, meeting, project, file, CRM, Slack, or other context only when it helps
understand a sender, promise, decision, or response. Suggest a connection when it would materially
improve the result; otherwise continue from the browser, uploads, or details the user provides.
If the selected queue is primarily customer support and the work depends on SLAs, refunds,
escalations, help-center policy, or specialist support judgment, use the appropriate Customer
Support workflow instead.
3. Find what really needs attention
Adapt the sorting to the source and the user's work. Look for:
- important incoming work and messages that need a reply;
- decisions, approvals, introductions, or promised follow-ups;
- work that can be delegated or routed to someone else;
- recurring noise and low-value items the user may want to reduce; and
- ambiguous, private, sensitive, or consequential items that need the user's judgment.
Do not treat unread as important, an unanswered message as an obligation, or a connection request
as something to accept by default. Check whether a thread was resolved elsewhere before flagging
it. When a commitment reaches beyond this inbox into meetings, tasks, projects, or other systems,
use strawberry/operations/close-open-loops for the wider audit.
4. Give the user a useful control view
Lead with the messages that could change what the user does next. A useful first result may include:
- a short priority view with the reason each item matters;
- replies drafted in the right channel and the user's established voice;
- clear delegation or follow-up suggestions; and
- a reviewable cleanup group for archive, label, mute, unsubscribe, accept, decline, delete, or
another action the selected service actually supports.
Keep the visible result compact. Separate the current provider state, your recommendation, and the
action that would be taken. For a large inbox, calibrate on a varied sample before expanding.
5. Apply only the approved actions
Show the account, people or records, channel, action, and scope before making consequential changes.
One approval may cover a clearly defined batch; ask again when the scope or expected effect changes.
Use the controls and concepts of the selected service rather than translating email labels into
LinkedIn or another provider. If an action is unavailable, say what can be done instead. After
applying an approved batch, verify the result and report anything that stayed unresolved.
Drafting, creating an external draft, sending, accepting or declining a connection, archiving,
muting, unsubscribing, and deleting are distinct actions. Do not treat approval of the priority view
or reply wording as approval of all later steps.
6. Make the next pass faster
Use feedback from a real batch to remember useful priorities, exceptions, voice, delegation rules,
and what counts as done for this inbox. Do not turn one unusual day into a permanent rule. When the
method should help others, offer to save the accepted approach as a team skill or use
strawberry/operations/set-up-shared-team-workflow for shared ownership.
When the queue has a useful cadence, a Routine may check the agreed inbox and time window, prepare a
short priority view and reply suggestions, and surface proposed cleanup or delegation. Keep sends
and provider changes reviewable unless the user explicitly approves a narrower recurring action.
Stop when the account or inbox is unclear, a person or thread cannot be matched reliably, private
context could cross a boundary, or the next action needs the user's judgment. Skip the Routine when
on-request help is enough.
