echo dot, amazon, language assistant, alexa, sound off, tired, micro-phone, alexa, alexa, alexa, alexa, alexa. How four onboarding measures reveal where a virtual assistant agency stalls
Photo by HeikoAL on Pixabay

Guides

How four onboarding measures reveal where a virtual assistant agency stalls

Improve virtual assistant agency client onboarding by measuring four things across your last five accounts, then fixing the one stage that repeats.

What to take away

  • You cannot improve onboarding you have not measured. Four numbers per account, taken from your last five, will point at the stage that is actually costing you.
  • The usual culprit is access, and the usual cause is that the client's part of it was never made explicit or dated.
  • Improvement means removing rediscovery, not working faster. Every question asked twice is a document that does not exist.
  • Fix one stage per account. Changing the whole process at once means you learn nothing from the next one.

This page is an audit method. It contains no timelines, prices or benchmarks; the comparison is between your own accounts.

The four measures

Use the same definitions for each of your last five clients, from kickoff through the end of the first full cycle. Record these four measures for each account:

  1. Client wait (calendar days):Add the elapsed calendar days from each dated request for required client access or input until usable access or input arrives.
  2. Agency own time (hours):Add the hours agency staff actively spend on onboarding work. Exclude time when work is waiting on the client; that belongs in client wait.
  3. Repeat questions (count):Count each time anyone working on the account asks the same underlying question again after an answer has already been provided.
  4. Second-person handoff (yes/no):Record whether a trained second person completes a real account task while the usual assistant stays silent; enter 1 for yes and 0 for no. Log questions during the test, but treat that log as diagnostic detail, not a fifth measure.

Use these same definitions across accounts. The audit compares your accounts; it does not set a universal threshold for a long wait or a high amount of agency time.

Four onboarding measures to record

  • Days from signature to first useful work
  • Days lost waiting on the client
  • Questions asked more than once
  • Days until a second person did real work

Four numbers, five accounts, one hour of work. The pattern is usually obvious as soon as they sit next to each other.

Reading the pattern

What the numbers showWhat it meansWhere to fix it
Long wait on the client, short own timeYour requests are unclear or undatedRewrite the access request as a dated list
Long own time, short client waitYou are rediscovering the same setup each timeBuild a reusable account template
High repeat questionsDocumentation is written after the fact, from memoryDocument during the first cycle, not after
Second person never involvedEvery account is a single point of failureAdd a mandatory handover step
Everything fine, client unhappyYou are not telling them what is happeningAdd a scheduled progress note

The table's five rows are diagnostic patterns, not five measures. Its “everything fine, client unhappy” pattern is a reason to investigate expectations or communication, not an extra number to record. Read “long” and “short” relative to the other accounts in your set; there is no universal cutoff in this audit.

Two rows can be true at once. Fix the one with the largest number first, and only that one.

Fixing the access stage

This is the stage that stalls in most agencies, and the fix is mechanical.

Fixing the access stage

  1. Send one list, not a series of messages
  2. Give each item an owner and a date
  3. State what happens if an item is late
  4. Test each grant on arrival
  5. Record the removal route with the grant

Keep the controls at a level you can genuinely maintain. An elaborate access policy nobody follows protects nothing, while a short one that is applied every time protects a great deal.

Fixing the repeat-question stage

Repeat questions are the clearest signal in the whole audit, because they are countable and they point at exactly what is missing.

Fixing repeat questions

  1. Question asked a second time
  2. Do not answer it
  3. Write answer into working standard
  4. Send them the link

The rule is simple and hard to keep: when somebody asks you a question about an account for the second time, do not answer it. Write the answer into the working standard, then send them the link.

Within two accounts this changes the shape of your onboarding, because the document starts absorbing knowledge that previously lived in one person's memory.

Fixing the handover stage

If no second person has ever worked on an account, onboarding is not finished, whatever the client thinks.

Fixing the handover stage

  1. Different trained person performs a real task
  2. Usual assistant stays available and silent
  3. Log every question they have to ask
  4. Treat each question as a gap

Add one step: a different trained person performs a real task while the usual assistant stays available and silent. Log every question they have to ask. Each one is a gap.

This costs a couple of hours per account and it is the difference between a client relationship and an agency asset. Having that second trained person is also where most retention comes from, which is why it sits at the center of the renewal and reporting playbook rather than being treated as a staffing detail.

Fixing the silence

A client who hears nothing for a week assumes nothing is happening, even when the work is on schedule.

Two short notes fix it. One at the end of week one: what is done, what is waiting on them, what happens next. One at the end of the first full cycle: what was delivered, what surprised you, and what you propose to change.

The second note is the more valuable. It shows you are running the account rather than reacting to it, and it is the moment most clients decide the relationship is going to work. That impression is worth more than any acquisition activity, which is why the marketing and growth guide treats delivery as the strongest channel a small agency has.

The obligations that should be raised, not discovered

Where the retainer includes anything customer-facing, name the obligations that belong to the client early, so nobody is surprised later.

Accessibility is the common one where the work touches a client's website or public scheduling. The Department of Justice's ADA guide for small businesses is a reasonable orientation, and the right move is to raise it and let the client take advice rather than making judgments for them.

Where the tasks include contacting customers for reviews or testimonials, the FTC's guidance on soliciting and paying for online reviews governs how it may be done, including the rules against incentives conditioned on favorable reviews and undisclosed material connections.

And settle who directs the assistant day to day. It matters for scope, and it matters for worker status, which the Labor Department's page on misclassification myths explains is decided by the economic reality of the relationship rather than by the agreement's wording.

Reinvesting what you save

A shorter onboarding is margin recovered on every future client, not just this one. The first month costs far more to deliver than the tenth, and that cost sits in your price whether or not you named it.

So when the audit produces a saving, decide deliberately what happens to it: a lower entry price, a faster start date offered to buyers, or margin kept. The reasoning that connects the three is in the pricing and profit guide, and the phase structure the audit is measuring against is set out in the onboarding workflow for new clients.

Common questions

How often should I run this audit?

Every five accounts, or twice a year, whichever comes first. More often and you are measuring noise.

What if I only have two clients?

Run it on two. The absolute numbers mean little at that volume, but the repeat-question count is useful immediately.

Should I ask the client how onboarding went?

Yes, once, at the end of the first cycle, with one question: what took longer than you expected. Broad satisfaction questions produce polite answers.

Is a faster onboarding always better?

No. Compressing the observation phase produces documentation of an assumption, and you pay for it in exceptions later.

More in Guides

Latest from Review Desk