Small business outsourcing workflow guide

Build a customer onboarding checklist for a virtual assistant

A customer onboarding checklist that carries the welcome, the access, the first deliverable, and the owner review without gaps.

Build a customer onboarding checklist for a virtual assistant

Open with the promise and the first date

A customer onboarding checklist should begin with what the customer bought, what happens first, and the date they should expect it. The assistant can turn the sales handoff into a short welcome message that names the service, the contact, and the next step. Do not promise a date before the delivery owner has confirmed capacity. Record the promised date in the customer record and in the task that will deliver it. A welcome that arrives without a real date creates a follow-up question before the work even starts.

Separate the welcome from the request for information so the customer is not hit with a form in the first message. The first note should confirm the purchase and introduce the person who will do the work. The second note can ask for the details the business needs to begin. This small gap gives the customer a chance to reply and makes the request feel less like a gate. Keep both messages in the approved template library.

Collect only the details the first deliverable needs

List the fields required for the first deliverable, such as the account name, the preferred contact, and the files the assistant needs to start. Do not collect every possible detail at onboarding just because a form has room for it. Each extra field adds a reason for the customer to delay or abandon the setup. The assistant should mark which fields are required and which can wait until later. A short first form gets completed, while a long one gets a partial answer and a follow-up call.

When a required field is missing, send one specific question rather than a general reminder. Name the field, explain why it matters, and give an example of a complete answer. Record the date of the request and the date the customer replied. If the customer does not reply after two attempts, escalate to the owner with the evidence. The owner can then decide whether to pause, call, or proceed with a stated assumption.

Collect only the personal data the first deliverable needs, and do not copy an identity document into a shared folder because a template asks for it. The assistant should check whether the field is required for the service or only convenient for a future sale. If the data is not needed now, leave it out and explain why. A shorter data request is easier to complete and safer to store.

Set up access without sharing a personal login

Create a named account for the assistant and grant only the access the first deliverable requires. Do not ask the customer to share a password, even for a short task. If the customer must grant access, send a short guide that names the exact role and the person who should approve it. Record who granted the access and when it was tested. Test the login before the kickoff call, because an access failure during the call wastes the customer's time.

Keep customer data in the approved workspace and remove any downloaded copy at the end of the task. The assistant should know which files may be stored locally and which must stay in the system. If a customer sends personal data that is not needed, do not copy it into the working folder. Record the receipt and ask for a redacted version when possible. A clean data path at onboarding prevents a much harder cleanup later.

Name the first deliverable and its acceptance check

The first deliverable should be small enough to review in one sitting and specific enough to show the customer what good looks like. Write the acceptance check beside it, including the format, the reviewer, and the date. The assistant can draft the deliverable, but the owner or a named reviewer accepts it. Send the customer a short note that says what was delivered and what happens next. A first deliverable that is vague turns into an open-ended project with no clear win.

If the customer asks for a change, record whether it is a correction, a new request, or a scope change. A correction belongs in the current deliverable, while a new request may need a new date or a new agreement. The assistant should not accept a scope change on the owner's behalf. Route the request to the owner with the original promise and the new ask in one place. This record prevents the team from quietly absorbing work it never priced.

Show the customer one example of a good first deliverable so the acceptance check is concrete. The example can be a redacted sample, a short outline, or a description of the format. The assistant should ask whether the example matches what the customer expected before the work starts. A five-minute check here prevents a week of rework.

Close onboarding with a review and a next step

At the end of the first week, ask the customer whether the welcome, the access, and the first deliverable met the promise. Record the answer in the customer record and share it with the delivery owner. Ask the assistant which step took the most messages or the most waiting. Choose one onboarding change and test it with the next customer. A checklist that never changes is either perfect or unread.

Keep the completed checklist with the customer record so the next request starts from context rather than a blank page. Note the preferred channel, the review contact, and any sensitivity about data or timing. The assistant should be able to look at the record and answer a basic customer question without asking the owner. If the record cannot support that, add the missing field before the next customer. Onboarding is finished when the relationship can run on a documented path.

Sources and next steps

Compare this workflow with the small-business outsourcing service guides and bring a redacted source record to the scoping call.

Related guides

Free role planning call

Build a clearer work lane.

Share the role, tools, schedule, and approval needs. We will use those details to prepare a practical Philippines staffing conversation.

Contact Us