Virtual assistance

What a virtual assistant is and what the day actually looks like

A virtual assistant is a person who takes on a business's repeating work remotely: the inbox and customer messages, the calendar and appointments, order follow-ups, gathering information, and light bookkeeping. If what you are after is software that does those things by itself, that is a different thing called an AI assistant, and this page separates the two.

  • Lesson 1 of 6
  • Beginner
  • Free, no signup

The five groups of work that orbit the assistant role

No assistant carries all five at once. The scope is closed in the contract, not in the job ad.

Virtual assistant the job: closing open loops
  • Inbox and calendar
  • Customer messages and support
  • Follow-up and coordination
  • Gathering information
  • Light money work

This ring is not the full scope, it is the common shape of it. Specialist work such as formal accounting or legal matters does not belong here, and handing it to an assistant moves the problem rather than solving it.

Last checked: Facts and tool names in this lesson are re-checked against their sources on this date.

What does a virtual assistant actually do in one working day?

The work starts with a queue, not with a plan. When the assistant sits down in the morning, what is in front of them is the pile from last night: a few repeated questions about price, a customer who got no answer last week, an email that belongs to somebody else, and two that are not work at all. The first job is sorting that queue: what needs an answer right now, what needs one today, and what needs none.

After that the work tends to fall into a few groups. Answering customer messages in a voice that belongs to the business rather than to the assistant. Holding the calendar and the appointments, and reminding people of the thing that was supposed to happen. Following up: chasing the supplier who never replied, checking the order that was never delivered. Gathering information, such as producing a list of ten suppliers with prices and phone numbers. And light money work, such as recording invoices and matching payments.

That is still a description of tasks, not of the job. The difference between the two sits in a sentence no job ad writes: the work of a virtual assistant is not to do the tasks, it is to leave nothing half finished. Every small business carries a few open loops, things that were started and nobody remembers where they stopped. The person who is genuinely worth the money is the one who counts those loops and closes them.

One thing catches newcomers off guard: a large part of this job is making small decisions. Can this discount be given? Should this angry customer go straight to the owner? Someone who asks their client about every small decision has increased that person's workload rather than reduced it. That is why the boundary of authority is a first-week conversation, not something that becomes clear later on its own.

An envelope, a clock, a parcel and a spreadsheet orbiting a white headset in red, green, blue and white

Is a virtual assistant a person or software?

Both meanings are in circulation, and that is exactly what creates the confusion. In the Iranian job market, "virtual assistant" means a person working remotely. In software marketing the same phrase means a program: Google publishes its Gemini page under that very heading, your new personal AI assistant. If you are hiring or looking for work, you want the first meaning. If you are looking for a tool, the second.

The practical border between them is where responsibility starts. Today's software drafts well, summarises long text, sorts a message queue and pulls a table out of a file. What it does not do is stand behind a decision. When a customer is promised delivery on Saturday, a person has to have made that promise and to chase it on Saturday; and if Saturday passes with nothing, a person has to answer for it.

Our position is that the right question is not which one replaces the other. An assistant who has genuinely learned these tools and one who has not are doing two different jobs; the first can carry several clients at a quality the second struggles to reach for one. Lesson four of this path is about exactly that. And if you do not yet know what AI itself is and what it can actually do, the lesson on what AI is is a better starting point, and which tool is currently better for which task is kept up to date in the AI reference.

What the software does and what the person does

The border between them is where responsibility starts, not where the work gets hard.

The AI tool

  • Drafts a reply and summarises long text
  • Sorts the message queue and pulls a table out of a file
  • Starts from nothing each time unless you supply the context
  • Stands behind no promise

The human assistant

  • Makes the small decisions inside an agreed authority
  • Makes a promise and chases it on the day
  • Knows what should not be answered at all
  • Carries the responsibility when it goes wrong

The two columns are not rivals and in practice they overlap. An assistant who knows the tools carries the same work faster; but not one line from the human column can be handed to a tool.

How is this different from a secretary, a freelancer or a remote employee?

These four titles get mixed together in job ads, and the difference matters, because it decides who sets the priorities and how the money is counted.

RolePlace and hoursPaymentWho sets the order of work
On-site secretaryOn the premises, fixed hoursMonthly salaryThe manager, moment to moment
Virtual assistantRemote, agreed hoursHourly or a fixed packageThe client gives priorities, the assistant sequences them
Project freelancerRemote, own schedulePer defined deliverableThemselves, inside the project scope
Remote employeeRemote, fixed hoursMonthly salaryThe manager, inside the company structure

One difference does not fit in the table: a virtual assistant usually sits inside several businesses at once, which is both the advantage and the risk. The advantage is that you see the same trade's work several times over and learn faster than a new employee would. The risk is that one busy week at one client flattens the others. Capping your capacity is the managerial skill of this job, and lesson six ties it to the contract itself.

Which businesses actually hire a virtual assistant?

The pattern is simple and comes from the work itself rather than from a statistic: a business run by one person, where that same person both sells and answers. The Instagram shop whose direct messages have got away from its owner. The clinic or training centre that books appointments by phone. The small company where one person raises invoices, chases customers and keeps the site up to date. The RGB virtual assistant service puts exactly those into six groups: calls and messages, social page management, sales calls, customer records and follow-up, day-to-day site work, and the inbox and support tickets.

And the part that gets said less often, where this does not work. If the thing wearing you down is specialist by nature, such as closing the tax books or drafting a legal contract, a virtual assistant is not the answer and you need that specialist. If the real problem is that there is no process and every order is handled in a new way, adding a person multiplies the mess. Build a repeatable route first, then hand it over. And if you cannot spare even one week for explaining, delegating during that week costs more than the work itself.

When it is time, and when the problem is somewhere else

Before hiring an assistantFor the owner

You genuinely need an assistant

  • Messages sit unanswered for days and you know which ones
  • The task you want to hand over looked exactly the same last week
  • You can say in one sentence what a correct result looks like
  • The access needed can be given narrowly and taken back later

The problem is somewhere else

  • Every order is handled a new way with no fixed route
  • What wears you down is specialist by nature, not repetitive
  • You expect the new person to work out what to do by themselves
  • You cannot spare even one week for explaining

None of these signs decides on its own. The line that matters most is the explaining one: the first week with a new assistant costs you time rather than freeing it.

How do I know whether this work suits me?

Three signs that this work suits you, and not one of them is a skill. First, you enjoy closing things that were left half done; if a list of finished items at the end of the day means something to you, this job pays you back. Second, constant interruption does not bother you, because the work is interrupted by nature. Third, you can start without anybody standing over you. The freedom of this job is as sweet as it sounds and, for some people, paralysing, and it is better to know which one you are before the first contract.

And where it does not suit you. If you want work that rewards long, deep concentration, this job breaks that concentration all day. If you expect clear, predefined tasks to arrive, you will be disappointed; a large part of this work is defining the work. And if saying no and drawing a line is hard for you, the first client will take your whole week, and you will have allowed it yourself.

The next step that genuinely helps is not learning a tool. It is spending one full week looking at a business you know through an assistant's eyes and writing down which of its tasks could have been carried remotely. If that list runs past ten lines, you have seen the market for this work with your own eyes. The recipe further down this page turns exactly that list into a delegation plan.

The fast path, with AI

The usual way is to sit and think about what to delegate, and what comes to mind is always whatever annoyed you this week. The faster way is to log one week raw and let the model do the sorting, under one constraint that makes all the difference: it may not name a task that is absent from your input. Without that constraint the output is the task list of an imaginary assistant rather than your own work.

  1. For one week, write every task you do on one line with a rough duration. Write it in the moment, not from memory at the end of the week; memory drops the short repetitive ones, and those are exactly the ones worth delegating.
  2. Strip names, phone numbers, amounts and addresses out of the list. This cannot be undone after you send it, and the customer data is not yours to spend.
  3. Give the list to a model with the recipe below. A fast cheap model of the Flash class is enough here because the pass is mechanical; keep a frontier model for the places that need judgement. Our current pick stays up to date in the RGB AI reference.
  4. Correct the output yourself. The model does not know which task is tied to your reputation, or which access cannot actually be narrowed.

Copy-ready recipe

This is a raw log of one week of my work. I am a {role} in a {type of business}.

{one line each: what I did / rough duration}

Rule: use only these lines. Do not add any task that is not in the list, even if it is common.

1) Put every line into one of these four buckets and give a half-line reason:
   a) can be delegated right now
   b) can be delegated after one round of training
   c) can be delegated only with sensitive access
   d) cannot be delegated
2) Total the time per bucket and tell me how many hours a week are freed if I delegate bucket a only.
3) For bucket b, write for each task what "one round of training" concretely means: what has to be written down or recorded.
4) For bucket c, say which access is needed and how that same access can be given narrowly and revocably.
5) Write no number and no task that did not come from my list.

Before you trust the output: The output of this recipe is a starting list, not a decision. The model does not know which task in your business is tied to your reputation, or which access cannot really be narrowed. Read bucket a yourself once and pull out anything that touches money or a password until trust has been built. And if you wrote the week from memory, the output is that memory rather than your actual week.

AI in this kind of work

In this lesson the job of AI is sorting, not deciding. Wherever you hold raw input and have no patience to order it, a model genuinely helps: that week log, a crowded inbox, ten pages of meeting notes. Wherever the question is which task to delegate or whom to trust, the model gives you something shaped like an answer with nothing behind it.

Tools that actually help

  • Claude It holds a constraint well, and in this recipe the constraint is everything: a task absent from the list must not be invented. Iran is on neither of Anthropic two supported country lists; we read that on Anthropic own page rather than measuring it.
  • Gemini It understands Persian itself, so a Persian week log needs no translation first. Google own page says the Gemini web app runs in over 230 countries and territories, and Iran is not on that list.
  • NotebookLM It earns its place when the input is several files, because it builds the summary from those files with references back to them. It belongs to the Gemini apps family and its access status is the same: Iran is not on Google supported country list.
  • ChatGPT It works for this same sorting pass and most people are already comfortable with it. We make no claim about access from Iran: the OpenAI supported countries page returns 403 to this server, and we do not write a claim with nothing behind it.

Where it backfires

The specific risk in this lesson is the list itself. A week of a business owner tasks carries customer names, amounts and phone numbers, and most people paste it into a chat without thinking. Whether your conversation is used to train a model depends on the plan and the settings; on its own privacy page Anthropic writes that in its consumer products it uses chats to improve models when you have chosen to allow it, when a conversation is flagged for safety review, or when you have explicitly opted in. So the answer is that it depends, and it depends on a setting you have never looked at. The practical rule is simple: strip names, numbers and amounts before pasting, and if the data belongs to a client, do not put it anywhere without their permission. The second risk is naming: a service that calls itself an AI assistant may well have people behind it too, and if client data is going to pass through it you have to ask who and what can reach that data rather than guessing from the name.

Sources: Anthropic: supported countries and regions Anthropic privacy: is my data used for model training Google: where you can use the Gemini web app Google: Gemini Notebook help, frequently asked questions

Where this advice stops

This lesson defines the work, not the job market. Three things are deliberately absent and all three are later lessons of this path: finding clients, pricing and contracts, and the tools. We gave no income figure either, because no citable statistic has been published for Iran and inventing one is precisely what we criticise elsewhere. There is another boundary that gets stated less often: everything here is about working with Iranian clients. Assisting a foreign client is effectively a different job; the language, the time difference and, above both, getting the money into Iran are problems this page does not solve. And none of this is legal advice: the form of the working relationship, insurance and tax should be checked with somebody whose job that is.

From our own work

We learned one thing from our own code that changed how we define this job. On this site freelance platform, the project attachment path used to discard an oversized or disallowed file silently: the project was saved, the client saw a success message, and the attachment had never been stored. No error was recorded anywhere either, so until somebody went looking for the file there appeared to be no problem at all. Every upload path now runs through one shared layer and the error goes back to the user; the explanation still sits at the top of that file, in rgb-freelance/includes/uploads.php. The lesson it carries for a virtual assistant is one sentence: a success message is not evidence. Someone whose job is closing loops counts a task as finished where they have seen the result, not where the system said it was done.

Real follow-up questions

Are a virtual assistant and a virtual receptionist the same thing?

In everyday speech they are used almost interchangeably, but the scope differs. A virtual receptionist usually means the calls and messages part: answering, booking, taking messages. Virtual assistant is the wider title and also covers admin work, follow-ups and gathering information. What matters in the contract is not the title but the list of tasks.

What do I actually need to start?

A device, an internet connection that does not drop, and a fixed way to be reachable during working hours. That is it. What actually blocks people is not skill, it is an unstable connection: a client who gets no answer at ten in the morning does not come back to you next time. If your home connection goes down on some days, put a second route in place before the first contract.

Will AI take this job?

It changes the shape of the work rather than removing it. The part that is only typing and summarising shrinks, and is shrinking already; the part tied to responsibility, decisions and dealing with people does not. The practical result is that an assistant who knows these tools carries several clients at once, while one who does not is still struggling with the single client they have.