Onboarding

Build a shared inbox label scheme a virtual assistant can maintain

A small label scheme tied to the work queue, with clear rename rules, an owner, and a monthly audit so the inbox stays usable after the first week.

By OnboardingEmployees editorial team | | 5 min read

Build a shared inbox label scheme a virtual assistant can maintain
On this page
  1. Start from the work queue
  2. Limit the label set
  3. Define when a label changes
  4. Name the owner of the scheme
  5. Handle ambiguous messages
  6. Audit the scheme monthly
  7. Related reading

A shared inbox label scheme is a small set of categories that tells a virtual assistant where a message belongs and what happens next. It should follow the work queue rather than the org chart, because the assistant needs to act on the message, not describe the company. A good scheme has fewer labels than the team expects and a clear rule for each one. It should also survive a week when the assistant is away.

Start from the work queue

List the actions that actually happen to a message after it arrives. A message may need a reply, a review, a document, a callback, or no action at all. Those actions are the raw material for the label scheme. A label that does not lead to an action is probably a folder for someone else's reporting.

Group the actions into a small number of stages, such as new, waiting on us, waiting on them, and done. The names should describe the state of the work rather than the mood of the sender. A stage label helps the assistant decide what to open next. It also shows the queue to a manager without a separate report.

Keep a separate small set of topic labels only if the team truly searches by topic. A dozen topic labels will drift within a month because two people will classify the same message differently. If topics are needed, limit them to the ones used in a weekly review. The rest can live in the subject line or the message body.

Limit the label set

Choose a maximum number of labels before the scheme is created, and treat the limit as a design constraint. A small set forces the team to decide what matters and makes the inbox faster to scan. The limit also makes an unused label visible. A scheme that grows without a limit becomes a second filing system.

Name each label with one or two words that a new assistant can understand without training. Avoid internal project codes and abbreviations that only one team uses. If a code is necessary, write the plain meaning beside it in the label guide. A label that needs a glossary will be applied inconsistently.

Record the one action that each label requires and the time frame for it. A waiting-on-us label may require a reply within the same day, while a waiting-on-them label may require a check after three days. The action and the time frame turn the label into a queue. Without them, the label is only a color.

Define when a label changes

Write the trigger for moving a message from one stage to the next. A message moves to waiting on them when a question has been sent, not when the assistant intends to send it. A message moves to done when the requested action is complete and recorded. The trigger should be observable in the thread.

Record who may move a message backward, such as reopening a done item after a new reply. A reopened message should keep its history rather than start a new thread. The scheme should say whether the assistant or the owner decides. A clear rule prevents two people from working the same item.

Define what happens to a message that fits no label. It should go to a review label with a note about the ambiguity, not into a catch-all that hides the problem. The review label should be checked weekly. A growing review pile is a signal that the scheme is missing a stage or a topic.

Name the owner of the scheme

Name one person who approves a new label, a rename, or a removal. A scheme with several owners will accumulate synonyms and exceptions. The owner should also keep the label guide current. The role can be shared, but the approval should be one name at a time.

Record how a label change is communicated to the team and when it takes effect. A rename applied without notice can make old instructions wrong. The guide should show the old name beside the new one for one review cycle. The change should be dated so a later reader can follow the history.

Review the label guide when the role changes, not only when the inbox feels messy. A new task type or a new client may need a stage that did not exist before. The review should ask which label is unused and which is overloaded. The owner should remove at least one label before adding another.

Handle ambiguous messages

Write a short triage note for messages that contain more than one request. The assistant should split the message into separate tasks only when each has a different owner or deadline. Otherwise, one task with a clear summary is easier to track. The note should say which request comes first.

Record how to label a message that is informational but still important, such as a client notice of a holiday closure. A read-and-file label may be enough, but the team should decide whether the notice changes a schedule. The assistant should not create a task for every newsletter. The scheme should distinguish a notice from a request.

Ask the assistant to record the reason when a message is moved to review. The reason should be one of a short list, such as unknown sender, unclear request, or missing owner. The list makes the weekly review faster. It also shows whether the scheme needs a new stage.

Audit the scheme monthly

Count the messages in each label and the time they spent in each stage. A label with a large count and a long wait may be a bottleneck, while a label with two messages may be unnecessary. Report the counts beside the label guide. The comparison is more useful than an opinion about the colors.

Sample ten messages from the review label and check whether they were classified correctly. A misclassification is a chance to clarify a label name or an example. Record the correction in the guide rather than in a chat. The next assistant should be able to learn from it.

Ask the assistant which label saved the most time and which one caused the most doubt. Keep the first and rewrite the second. A scheme that is maintained by the person who uses it is more likely to stay honest. The monthly review should take less than half an hour.

Continue building the workflow

Related support: onboarding operations support, contact us. The U.S. Small Business Administration - Hire and manage employees guidance on setting expectations and managing a new working relationship.