How to Organize Personal and Work Requests With One Assistant

Quick answer

Organize personal and work requests by labeling the context, choosing the authorized accounts, and stating which information may appear in each output. Keep separate priorities and review rules even if you use one assistant. Before allowing external action, confirm the sender identity, recipient, and relevant context so a personal request does not become a work communication by mistake.

Using one assistant can reduce the number of places you send requests. It can also create ambiguity if “my calendar,” “the account,” or “send the update” refers to different contexts. Clear names and boundaries make delegation easier without requiring a separate assistant for every area of life.

Name your contexts

Create simple labels such as work, personal, and household. Use names that match how you think about the requests, rather than elaborate categories. State which account and audience belong to each context.

For work, you might authorize a specific calendar and email account. For personal tasks, you might provide a different calendar and limit output to your private messaging channel. Account access should reflect the tasks actually assigned, not the convenience of connecting everything at once.

Record the distinctions that affect action:

• Which identity should send messages.
• Which calendar should hold the event.
• Which audience may see supporting information.
• Which budget or approval rule applies.
• Which priorities override a scheduling conflict.

An illustrative scheduling conflict

A founder asks for help coordinating a client meeting and a personal service appointment during the same week. The work calendar has a client call, while the personal calendar contains an unavailable period. The founder wants the assistant to consider both for scheduling but keep the personal details out of client communications.

The assistant's external availability message should describe suitable windows, not explain the private appointment. It should use the authorized work identity for the client and the separately approved contact path for the service provider.

If the client proposes a conflicting time, the assistant should return the trade-off or follow a precise scheduling rule already provided. It should not assume work always outranks personal commitments or move a private appointment without permission.

A context setup brief

Treat requests labeled work and personal as separate contexts. Use the assigned work accounts for client coordination and my private channel for personal reminders. When preparing work availability, consider authorized busy periods but do not disclose personal event details. Ask if a request does not identify the account or context needed for an external action. Do not transfer files or contacts between contexts without my authorization. Show the sender, recipient, calendar, and next action before a new communication workflow begins.

Confirm what the actual connections allow. Written instructions are important, but technical account scopes and provider settings also affect access. Do not assume a conversational label creates a technical isolation boundary by itself.

Keep priorities visible

Use separate task lists or sections in a shared briefing. A useful daily summary might have work decisions, personal reminders, and scheduling conflicts. It should not combine a client delivery deadline and a household errand into one opaque priority score.

State how to handle conflicts. Perhaps fixed family commitments stay protected, or urgent work decisions must return to you. The assistant should know the rule rather than infer your values from whichever message arrived last.

Review recurring workflows after life or work changes. A new role, shared account, or travel schedule may alter which identity is appropriate. Remove unnecessary access and close obsolete reminders rather than accumulating old permissions indefinitely.

For sensitive contexts, ask whether using separate accounts or assistants would provide a clearer boundary. The right choice depends on actual product controls and your needs; one conversational interface is a convenience, not a universal security guarantee.

Frequently asked questions

Does labeling a request restrict account access?

A label helps interpretation. Technical restrictions come from the connection and product controls. Review those separately and do not rely only on naming conventions.

Can the assistant use personal availability for work scheduling?

Define whether it may consider busy periods and what information may be shared. Availability and event details need not be treated as the same output.

What if I forget to specify the context?

Tell the assistant to ask before any ambiguous external action. For reversible internal preparation, it can state its assumption and provide a reviewable draft.

Righthand's multi-channel communication, calendar management, and integrations are relevant when setting up these boundaries.