Philippines staffing guide
Build an Inbox Label Taxonomy an Assistant Can Actually Apply
Labels should describe the next decision, not the sender's mood, so an assistant can sort a shared inbox without guessing.
Published · 7 minute read
On this page
Most shared inboxes collapse under labels that describe topics instead of actions. A message tagged billing still leaves the reader unsure whether to answer, forward, or wait. An assistant sorting forty overnight emails needs categories that point to the next step and a rule for the messages that fit none of them. The taxonomy is a routing document, not a filing system.
Start from the decisions the inbox produces
Write down the six or seven outcomes that actually happen after someone reads an email: reply with a standard answer, request a missing detail, route to a specialist, hold for a named date, escalate for approval, or archive as informational. Those outcomes become the top-level labels. Topic labels can live underneath as a second dimension, but they never replace the action. When a new topic appears, ask which existing outcome it feeds before inventing a new branch.
Give each label a positive test
A usable label has a test that two people can apply to the same message and reach the same answer. For example, an approval request contains a specific amount or commitment and names no approver in the thread. Write the test as a sentence, then add one real example and one near miss. Near misses matter more than clean examples because they show where the category stops. Review the tests quarterly against the messages that were re-sorted.
Route by owner, not by department name
Departments are stable; individuals are not. Still, a label that points to finance leaves the assistant with no name when finance has three queues. Attach each routing label to a role and a backup, and keep the current holder in a small table the assistant can read. When the holder changes, only the table changes. Avoid labels that encode a person's name, because those age badly and make the taxonomy feel like insider knowledge.
Handle the ambiguous message explicitly
Create a hold label for messages that need a fact nobody can supply yet, and a review label for messages that could create a commitment, a refund, a legal position, or a security action. The assistant applies the label and writes one line about the missing fact. Neither label is a dumping ground. If the review pile grows for two weeks, the problem is usually an unclear approval path or a sales process that promises exceptions before the desk sees them.
Protect sensitive threads from the sorting lane
Identity documents, payroll details, medical notes, and credentials should not sit in a general inbox label where any assistant can browse them. Define a protected route that moves the thread to an approved location and leaves only a reference in the inbox. The sorting role can recognize and redirect these messages without reading the attachment. This is the practical version of data minimisation: collect less, expose less, and keep the audit trail at the routing level.
Measure the taxonomy with rework
Count messages that were re-labeled, returned by the receiving owner, or answered twice. Sample ten of each per month and ask which test was unclear. A high rework rate on one label is cheaper to fix by rewriting its definition than by retraining the whole team. Retire labels that have not been used in a quarter, and merge duplicates before adding anything new.