If every request starts sounding urgent, your service menu is probably doing too little work.
When a business owner asks what a virtual assistant can handle, they are usually asking three things at once: What can I hand off safely? What should stay out of scope? How do I keep the work from drifting? Michael Porter put the strategy problem bluntly: The essence of strategy is choosing what not to do.
That is why guides like Harvard Business Review’s discussion of great delegators and Asana’s scope creep guide are useful companions here. Both point to the same practical truth: work gets easier when the boundaries are visible before the work starts.
In this article, I will walk through a simple way to build a virtual assistant service menu that feels calm to use, easy to price, and clear enough to protect both sides. You will see how to choose the right admin tasks, how to describe what is included, what to leave out, how to package the work, and how to answer the inevitable Can you also do this?
question without overpromising.
For the broader site context, you can always start at the home page, use Support when you want help shaping a request, or browse more service-focused articles on the blog.
Terminology that keeps the conversation honest
Before I get into the menu itself, I like to define a few terms. It saves a lot of circular conversation later, especially when a client is moving fast and a VA is trying to stay accurate.
- Service menu: a written list of tasks the VA can perform, usually with notes about what is included and what is not.
- Scope creep: when a task quietly grows beyond the original agreement, often one small favor at a time.
- Turnaround time: the time between receiving a complete request and delivering the finished task.
- Access requirement: the level of login, file, or system access needed to complete the work.
- Approval loop: the step where the client reviews, confirms, or corrects work before it moves forward.
These terms are not there to sound formal. They are there to stop the work from becoming fuzzy. When people know the words, they also know the edges.
Why a menu beats vague requests
A vague request usually sounds simple at first. Can you help with admin?
Can you take some things off my plate?
Can you just keep me organized?
The problem is that each of those questions can hide ten different jobs. Without a menu, every new task becomes a small negotiation.
A service menu gives both sides a shared reference point. It reduces the back-and-forth, but more importantly, it reduces the emotional drag that comes from guessing. The VA does not have to keep translating a half-formed idea, and the client does not have to wonder whether the request is too small, too large, or too expensive.
The goal is not to make the menu rigid. The goal is to make it legible. A good menu leaves room for exceptions, but it makes exceptions visible.
- It helps the VA answer faster because the answer starts with a known category.
- It helps the client compare options instead of describing the same problem five different ways.
- It lowers the risk of a task being accepted before the inputs, timing, or approvals are ready.
If you are building a service page or a support page, this is the same logic in different clothing. People relax when they know what will happen next.
How to choose tasks: frequency, complexity, and access
I usually sort tasks by three questions:
- How often does it happen? Repeated tasks are easier to menu because they can be standardized.
- How much judgment does it require? Tasks with low judgment are safer for a service menu than tasks that need deep strategic calls.
- What access does it require? If a task needs sensitive systems, financial permissions, or multiple approvals, it needs clearer boundaries.
That is the practical filter. The right menu is usually built from work that is frequent, repeatable, and easy to verify. You do not need to sell every possible kind of support. In fact, trying to do that often weakens the menu.
My rule of thumb: if a task can be explained in one sentence, repeated with a checklist, and checked before delivery, it is usually a good candidate. If it requires a one-off strategy decision, professional judgment beyond your lane, or access you would hesitate to grant quickly, it belongs in a separate conversation.
12 admin task categories you can offer
The table below turns common VA work into a practical menu. I am keeping the language plain on purpose, because a client should be able to read it quickly and know exactly what kind of help they are buying.
| Task category | Inputs needed | Typical turnaround | What is out of scope |
|---|---|---|---|
| Inbox triage | Email access, priority rules, canned replies, escalation contacts | Same day or next business morning | Negotiating complaints, making promises, or answering legal or financial questions |
| Calendar updates | Calendar access, working hours, blackout dates, scheduling priorities | Same day for simple changes | Strategic planning, overbooking, and rescheduling without approval |
| Meeting prep and follow-up | Agenda, attendee list, notes, documents, desired next step | Before the meeting and within 24 hours after | Running the meeting or making executive decisions |
| Document preparation | Source notes, template, brand style, deadline, approval path | One to two business days | Final legal, accounting, or compliance review |
| Social media scheduling | Approved captions, images, posting window, platform list | Two to three business days | Content strategy, paid ads, community management, or DMs |
| Data entry and CRM updates | Source file, field map, naming rules, access to the database | Depends on volume and cleanup needs | Data verification beyond the source or system redesign |
| File and folder organization | Folder structure, naming rules, retention preferences | One to two business days | Records policy creation or legal retention advice |
| Light research and list building | Criteria, preferred sources, target audience, output format | One to three business days | Due diligence, expert analysis, or purchasing decisions |
| Customer support inbox responses | FAQ, brand voice, approved scripts, escalation rules | Same day during business hours | Refund decisions, complaints that need management, or technical troubleshooting |
| Travel or event coordination | Dates, budget, preferences, traveler details, confirmation rules | Two to five business days | Visas, emergency rebooking, or event production management |
| Basic bookkeeping support | Accounting access, receipt rules, chart of accounts, filing cadence | Weekly or monthly cadence | Tax filing, reconciliations, or financial advice |
| Invoice and payment follow-up | Invoice list, due dates, reminder script, escalation contact | Weekly or per the billing cycle | Collections disputes, legal escalation, or hardship negotiation |
The pattern is simple: the more repetitive and verifiable the task, the easier it is to menu. The more a task touches money, reputation, or specialist judgment, the more carefully it needs to be bounded.
Inbox triage
Inbox triage is usually the easiest place to start because the work is visible and the value is immediate. The VA sorts incoming messages, flags urgent items, drafts replies for routine questions, and leaves anything sensitive for the owner. I like to define this task by response level: delete, delegate, draft, or escalate.
Good boundaries matter here. A VA should know which messages can be answered directly, which ones need approval, and which ones should never be answered without the business owner. That keeps the inbox useful instead of merely cleared.
Calendar updates
Calendar work looks simple until it starts colliding with priorities. A clear menu for calendar support should explain who gets scheduled first, what counts as a blackout date, and how far ahead appointments can be moved. That keeps the schedule from becoming a second inbox.
If the client wants support with recurring meetings, blocks for deep work, or travel-related changes, those items should be named separately. Small distinctions here save surprisingly large amounts of stress later.
Meeting prep and follow-up
Meeting prep is best treated as a package: gather documents, confirm attendees, check the agenda, and prepare the follow-up notes. The client should not have to rediscover the context every time a meeting appears on the calendar.
What stays out of scope? Running the conversation, steering decisions, or speaking for the business owner unless that role was explicitly agreed in advance. A VA can support the meeting without owning the meeting.
Document preparation
This category includes things like polishing client-facing notes, formatting handouts, preparing checklists, and turning rough material into a clean draft. It is a good fit when the content already exists and just needs to be organized, formatted, or made easier to use.
One practical boundary is simple: the VA can prepare the document, but the owner reviews the final message. That keeps the voice consistent and the risk manageable.
Social media scheduling
Scheduling is not the same thing as strategy. A service menu should separate publishing support from content creation so nobody accidentally expects a full marketing plan from a task that was only meant to move posts into the queue.
Good inputs include approved copy, images, hashtags, platform rules, and timing preferences. Out-of-scope work usually includes replies to comments, creating graphics from scratch, or rewriting the message every week because the owner changed direction at the last minute.
Data entry and CRM updates
Data entry becomes far easier to manage when the field list is clear. If the source document says one thing and the database expects another, the mismatch has to be resolved before anyone begins. Otherwise the VA spends the day guessing, and guessing is expensive.
Use this task for transfer, not interpretation. The best version of data entry support is a clean handoff from one system to another with minimal judgment in the middle.
File and folder organization
Folder cleanup may not look glamorous, but it often changes the daily feel of a business. A well-named structure makes it easier to find the right file, share the right document, and stop recreating work that already exists.
This is also a perfect place to define naming conventions. If every file is saved differently, the menu becomes a scavenger hunt. If every file follows the same pattern, the work becomes lighter almost immediately.
Light research and list building
Research support works well when the question is narrow. Find five vendors, compare three article ideas, build a contact list, or gather examples of a particular service page. That kind of work is repeatable and easy to verify.
What should stay out of scope? Any research that requires deep analysis, careful due diligence, or a purchasing decision. The VA can gather the pieces, but the owner should decide what matters most.
Customer support inbox responses
This task overlaps with inbox triage but is worth naming separately when the business handles a steady flow of customer questions. A support menu should say which topics can be answered from a script, which ones need approval, and which ones must be escalated immediately.
The reason is simple: customers relax when the replies are consistent, but consistency only works when the VA knows where the line is.
Travel or event coordination
Travel and event coordination can save a surprising amount of owner time, especially when the task is mostly logistics. That can include comparing options, gathering confirmations, watching deadlines, and keeping the details in one place.
Still, the menu should exclude high-risk situations like visa decisions, emergency rebooking, or event production management unless those responsibilities are specifically agreed. There is a difference between planning logistics and owning the whole event.
Basic bookkeeping support
This category needs the clearest boundaries of the entire menu. The VA might help with receipt sorting, categorization, invoice tracking, and file organization, but the client should understand what is administrative and what requires a financial professional.
The IRS recordkeeping guidance is a useful reminder that clean records matter long before tax season. Good bookkeeping support depends on neat inputs, not wishful thinking.
Invoice and payment follow-up
Following up on invoices is one of those tasks that seems small until a business owner is spending an hour each week doing it by hand. A VA can send reminders, confirm receipt, and keep the billing cycle moving so the owner does not have to chase every payment personally.
What should stay out of scope is the harder human work around disputes, hardship situations, or legal escalation. Those conversations need a different lane.
Boundaries that protect quality
A service menu is only helpful if the boundaries are strong enough to hold under pressure. I would rather see a smaller menu that works well than a larger one that quietly collapses under exceptions.
- Approval boundaries: spell out which tasks can be completed independently and which ones need sign-off first.
- Voice boundaries: define whether the VA writes in a brand voice, a neutral service voice, or a template-only style.
- Access boundaries: decide what systems, logins, and documents are appropriate to share.
- Escalation boundaries: name the moments when the VA stops and alerts the owner instead of guessing.
- Time boundaries: explain what counts as same-day, next-day, or rush work.
I also recommend a simple rule: if the task changes money, legal exposure, public reputation, or a customer promise, pause and escalate. That one habit prevents a lot of accidental overreach.
Another small but important boundary is secure access. A VA should not have to fish for passwords in email threads. Use proper access tools, invite-based permissions, or a password manager so the handoff stays tidy and safer.
Pricing and packaging options: hourly, retainer, or task-based
Once the menu is clear, pricing becomes easier to explain. The wrong price model usually creates tension because the client thinks in outcomes, while the VA gets paid for time, bandwidth, or a specific deliverable. A better model aligns those expectations up front.
| Pricing model | Best when | Strength | Watch out for |
|---|---|---|---|
| Hourly | The menu is still evolving or the workload changes often | Flexible and easy to start | Can feel open-ended unless tracking is very clear |
| Retainer | The client needs steady weekly support with repeat tasks | Predictable for both sides | Scope drift if the retainer does not have a task cap or review point |
| Task-based | The deliverable is obvious, repeatable, and easy to describe | Very clear for one-off work | Can undersell complex tasks if the brief is too vague |
In practice, many VAs use a hybrid. A retainer covers the recurring work, and a task-based quote handles anything new, bigger, or unusually urgent. That combination often feels fair to both sides because the routine work stays stable while the unusual work gets priced separately.
If the service menu starts to feel like a small internal system with repeat requests, a web app generator can be a practical way to prototype a simple intake portal or task tracker before a custom build is necessary. The point is not to overengineer it. The point is to make the request flow easier to use.
For more service and process articles like this, you can also keep an eye on the blog.
A simple client intake form section for VA work
A good intake form saves everyone from re-asking the same questions later. I would keep it short enough to finish, but detailed enough to prevent the first week from becoming a scavenger hunt.
| Field | Why it matters |
|---|---|
| Business name and primary contact | So the VA knows who owns approvals and where to send updates |
| Service categories requested | So the menu item is clear before the work begins |
| Desired turnaround time | So rush work is named early instead of discovered late |
| Approved tools and logins | So the VA knows where the task actually lives |
| Brand voice or response notes | So the client does not have to correct tone after every draft |
| Escalation contact | So sensitive situations do not stall in the inbox |
| Billing and approval rules | So the scope, rate, and sign-off process are visible |
If you want one extra field, make it this: What would make this request a success? That single question often surfaces the real expectation faster than a long questionnaire.
I also recommend one small security rule in the intake form itself: do not ask people to share passwords in plain text. Use secure access methods instead. It is a simple line, but it keeps the relationship more professional from day one.
Quality checks before work is considered complete
The end of the task is not I sent something.
The end of the task is I sent the right thing in the right format to the right place.
That may sound picky, but that is exactly the kind of quiet discipline that makes a VA service feel reliable.
- Check that the task matches the original brief.
- Confirm that all required inputs were used.
- Make sure dates, names, links, and file names are correct.
- Review spelling, formatting, and tone.
- Confirm that anything sensitive was handled the way the client requested.
- Send a short completion note that explains what changed and what still needs approval, if anything.
Good quality control is not dramatic. It is repetitive, boring, and very effective. Most clients do not need a grand promise. They need work that arrives cleanly and consistently.
FAQ: Can you do X?
Clients will always ask for the edges of the menu. That is normal. The goal is not to sound defensive. The goal is to answer clearly enough that the next step is obvious.
Can you do this even if it is not on the menu?
Yes, if the task is small enough to quote separately and the inputs are clear. If it needs a bigger scope, it should be added as a new item instead of squeezed into the wrong one.
Can you also decide what should happen?
Only if the menu explicitly gives that authority. Otherwise, the VA can prepare, organize, and draft, but the owner keeps the final decision.
Can you turn this around today?
Maybe, if the request is simple and the inputs are ready. If it is urgent, say so early. Rushed work can be done, but it should be priced and scheduled honestly.
Can you just handle everything in the inbox?
Usually not. I would break the inbox into categories first: routine replies, drafts for approval, and escalations. That one distinction keeps the answer practical instead of vague.
Can you do all of this for one flat price?
Sometimes, but only if the menu is stable and the volume is predictable. If the requests vary a lot, an hourly or hybrid structure is often kinder to both sides.
If you want a phrase that stays firm without sounding cold, try this: I can help with that if it fits the menu and the inputs are ready. If it needs a different scope, I can quote it separately.
Conclusion
A good virtual assistant service menu is not a buzzword exercise. It is a way to reduce stress for the client, protect the VA’s time, and make the work easier to understand before anyone commits. The best menus are simple, specific, and honest about what stays out of scope.
If I had to reduce the whole approach to one sentence, it would be this: name the task, name the inputs, name the turnaround, and name the boundary. That is enough to make most admin work feel far less chaotic.
If you are refining your own services, start with the work you can repeat, define it cleanly, and build from there. Then point people to the Support page when they need help shaping a request and the Contact page when they are ready to talk through next steps.
- A service menu works best when it is narrow enough to be clear and broad enough to be useful.
- Frequency, complexity, and access are the fastest way to decide what belongs on it.
- Boundaries protect quality, especially when tasks touch money, reputation, or sensitive systems.
- Hourly, retainer, and task-based pricing each work in different situations.
- A short intake form and a simple quality check keep the work calm from start to finish.