Define what arrives in the inbox
A shared inbox triage rule starts with a written definition of what counts as a request. Include client questions, internal handoffs, vendor notices, and automated alerts, because each type follows a different path. Name the channels that feed the inbox so the assistant knows where work can appear. A rule that covers only email will miss the requests that arrive through chat and the client portal.
Separate a request from a notification before assigning an owner. A newsletter or a system alert may need filing rather than a reply, while a client question needs a named responder. Write one example of each type beside the rule. The example gives the assistant a test it can apply without asking a manager.
Set the first-pass buckets
The first pass should sort every message into one of a small number of buckets. Use labels such as reply today, schedule, waiting on client, and file only, and define each bucket in a sentence. Keep the number small enough that the assistant can hold it in mind. A taxonomy with twenty labels is a filing hobby rather than a triage rule.
Set the decision order so the assistant handles the riskiest message first. A complaint, a payment issue, or a legal notice should outrank a routine scheduling request. Put those triggers at the top of the rule and route them to a person immediately. The order protects the client from a delayed response on the item that matters most.
Name owners and queues
Every bucket needs a named owner and a queue that the team can see. The owner is a person, not a department, and the queue is the system where the work waits. Write the response time for each bucket beside the owner. A message that is labeled but unassigned is still unanswered.
Define what the assistant may resolve without escalation. A password reset or a document resend may be within scope, while a contract change is not. Record the limit and the evidence the assistant must attach. The rule should let the assistant act confidently at the low end and stop cleanly at the high end.
Handle ambiguous messages
Ambiguous messages need a default path rather than a guess. Route them to the owner of the closest matching bucket and mark them as needing clarification. The assistant should send one short question with a specific choice, not a broad request for more detail. A clear question gets a faster answer than a paragraph of uncertainty.
Do not let the assistant invent a client commitment to close a thread. If the answer depends on price, timing, or policy, the message waits for the owner. Record the wait in the queue so the delay is visible. A rule that rewards speed over accuracy will produce confident mistakes.
Protect sensitive threads
Some messages must bypass normal triage and go straight to a restricted queue. Include legal threats, safety concerns, payroll disputes, and messages containing identity documents. Name the person who receives them and the channel used for the handoff. The assistant should acknowledge receipt without discussing the substance.
Keep sensitive attachments out of shared folders that the whole team can browse. The rule should say where the file goes and who may open it. Add the step to the triage checklist so it is not left to memory. A fast route for sensitive work protects both the client and the assistant.
Review the rule against real messages
Review a sample of triaged messages each week and compare the label with the outcome. Count the messages that were rerouted, the ones that waited too long, and the ones the assistant escalated unnecessarily. Those three counts show whether the rule is clear. A rule that is never sampled drifts as the client changes.
Ask the assistant which message was hardest to classify and why. The answer usually points to a missing definition or an owner who does not respond. Change one line of the rule and test it for a week. A small, documented revision is easier to adopt than a full rewrite.
Sources
Open the original publisher and confirm the current version, definition, and scope before using a source for a business decision.
Turn the reading into a role brief
Bring the recurring tasks, tools, schedule, access limits, and owner-only decisions. Start with one work sample and one clear review path.
Plan a Philippines-based role