You have enough work for a virtual assistant: unanswered enquiries, untidy records, appointment changes and follow-ups that depend on you remembering them. The difficult part is turning that workload into a role someone can understand and own.
A list of everything you dislike doing rarely explains which work comes first, what good looks like or when the assistant needs a decision. Start with one connected workflow and describe the results you expect from it.
The following role-design method is a practical proposal for a business engaging its first Philippines-based VA. Assess the individual's skills and experience; nationality does not establish capability or suitable responsibilities.
Choose a workflow with a clear purpose
For a hypothetical service business, consider an enquiry and appointment coordinator. The workflow starts when an in-scope enquiry arrives and continues through information gathering, appointment coordination and handover to the consultant.
Those activities share records, customers and a finish point. Graphic design, overdue-account disputes and the director's travel bookings require different priorities and skills. Adding them all to the first brief makes the intended role harder to explain.
Review a sample of recent enquiries before deciding the workload. Record how many needed straightforward processing, how many required clarification and how long cases waited for your own decisions. Include quiet and busy periods.
Australian government recruitment guidance recommends defining responsibilities, reporting relationships and required skills in a position description. Use that planning principle to describe your actual work rather than borrowing a generic VA advertisement. Business.gov.au: creating a position description.
Write a role brief the assistant can use
Here is an original example to adapt. It describes the operating role; fill in your own systems, coverage arrangements and contacts before using it.
| Brief element | Example for an enquiry and appointment coordinator |
|---|---|
| Purpose | Keep enquiries moving through the agreed process and prepare reliable appointment handovers |
| Starting inputs | Assigned enquiry queue, approved service information, booking rules and current consultant availability |
| Work owned | Record enquiries, request agreed information, offer permitted appointments and maintain follow-up actions |
| Accepted outputs | Accurate enquiry record; confirmed appointment with required details; or a clearly assigned unresolved item |
| Decision limits | Use approved information; escalate pricing, technical questions, complaints and requests outside booking rules |
| Support provided | One supervisor, a backup contact, worked examples, approved templates and scheduled coaching |
Add the working hours, expected contact channels and priority order. If appointments can only be confirmed during agreed coverage, write that explicitly. An inbox receiving messages overnight does not mean the assistant is expected to monitor it continuously.
Keep a separate backlog for possible future duties. Review new requests against the role's purpose before adding them, including what existing work would need to move.
Define what an accepted result looks like
An appointment is ready for handover when the customer has confirmed the agreed date and time, the relevant location or meeting link is recorded, required preparation is available and the consultant can find it. Adapt these checks to your service.
An unanswered enquiry is different. It remains open with its last contact, next permitted follow-up and owner visible. The VA should not be judged as unsuccessful simply because a customer has not replied.
Separate controllable work from business outcomes influenced by others. The coordinator can maintain accurate records and complete agreed follow-ups. Revenue, consultant availability and whether a customer buys are shared or external dependencies.
Choose a few review measures: handovers accepted without correction, enquiries missing a next action and overdue follow-ups within the coordinator's control. Check the quality behind the counts. Closing a record without a valid reason should not improve the score.
Select skills using realistic examples
Derive the selection criteria from the brief. This coordinator needs clear written communication, careful record handling, practical scheduling skills and judgement about when to seek clarification. Knowledge of your CRM may be useful, but distinguish skills needed immediately from product knowledge you will teach.
Use a short, paid simulation with fictional enquiries and a simple booking guide. Include one straightforward request, one incomplete message and one customer asking for an exception. Ask the candidate to prepare a reply, update a sample record and explain their next action.
Assess the work against the same criteria for each person. Did they use the supplied facts, recognise the missing detail and respect the booking limits? A candidate who asks a relevant question may be showing the judgement the role needs.
Explain the actual communication demands and discuss availability. Avoid relying on vague labels such as “excellent English” when you can assess the specific writing or conversation required.
Pair responsibility with authority and access
Give the coordinator enough authority to complete routine work. For example, they may offer available appointment slots within published rules, while a request for an unlisted service goes to the supervisor. Document who decides and how urgent questions reach them.
Imagine a customer asks for a weekend appointment outside the approved schedule. The coordinator can acknowledge the request and seek a decision. They should not promise availability or wait silently while the enquiry disappears in the queue.
Set up access around those duties. ACSC's small-business guidance recommends individual accounts where possible, multi-factor authentication and access limited to what each person needs. ACSC: small business cyber security guide.
Identify approved tools, storage and information-handling instructions before sharing live records. Give the assistant a clear contact for access problems. Our hybrid-team responsibility guide explains how to assign decision owners and backups.
Make coaching part of the role design
Reserve the supervisor's time before the first assignment. Review early examples together, then choose regular samples that include exceptions. Explain corrections using the agreed output standard so the assistant can apply the lesson to the next case.
Ask which instructions caused uncertainty and which decisions arrived too late. Sometimes the fix is clearer training; sometimes the business needs to resolve a conflicting rule or provide a faster approval route.
Keep a brief revision record when responsibilities change. Expand the role after reviewing quality, workload and the support required, rather than adding duties whenever another team member becomes busy. For solar businesses, our onboarding guide offers a staged training structure.
Talk to Nexus about your first VA role with one workflow, a few recent examples and the results you need the role to produce.
