Skip to content

Custom GPT Onboarding Builder: Generate a Client Onboarding Packet in One Session

For Virtual Assistants ·

Tools:ChatGPT
Time to build:1-2 hours
Difficulty:Advanced
Prerequisites:Comfortable using ChatGPT for everyday drafting. If you've already set up a persistent AI assistant before, such as the Claude Project described in this role's Level 3 guide "Set Up a Claude Project as a Persistent Per-Client Assistant," a Custom GPT will feel familiar; it's the same idea built on a different tool.
ChatGPT

What This Builds

Onboarding a new client usually means digging up your checklist, adapting a welcome email you sent someone else, and writing a starter SOP from scratch, roughly the same 30-day ramp-up each time. This builds a Custom GPT that already knows your onboarding process. Type in a new client's basics, a business name, a service type, a few quirks, and it drafts the onboarding packet, welcome email, and starter SOP set in one guided session instead of an afternoon of scattered documents.

Prerequisites

  • A Plus subscription ($20/month), since building a Custom GPT requires a paid plan
  • Your own onboarding checklist or SOP template written down somewhere, even a rough one
  • Comfortable writing clear prompts and reading AI output critically

Total ongoing cost for this build: $20/month, the only subscription this technique needs.

The Concept

A Custom GPT is like a new hire who read your operations manual before their first day. Instead of explaining your onboarding process to a blank AI chat every single time, you explain it once, upload your checklist, and every future conversation starts already knowing how you work. You still review everything it produces, but you stop re-explaining the basics.


Build It Step by Step

Part 1: Gather your onboarding materials

  1. Pull together whatever you already use to onboard a client: a checklist, a welcome email template, a starter SOP outline, and any notes on your own tone and formatting habits.
  2. Scrub out anything tied to a specific past client, names, account numbers, login details, or pricing you gave that one client, so what's left is a reusable template rather than one client's actual file.
  3. Save the scrubbed version as a single document (a Google Doc exported to PDF, or a plain text file works fine).

Part 2: Build the Custom GPT

  1. Go to chatgpt.com, click your profile in the corner, select My GPTs, then Create a GPT.
  2. Switch to the Configure tab for direct control over each field rather than the conversational setup.
  3. Name it something specific, like "Client Onboarding Builder," not "Assistant."
  4. In the instructions field, paste something close to this, adjusted to your own process:
Copy and paste this
You help a virtual assistant draft new-client onboarding materials.
When given a new client's business name, service type, and any notable
quirks, produce three things in this order:

1. A welcome email (under 200 words, warm and professional, confirming
   next steps and timeline)
2. An onboarding packet outline (sections: what to expect in week one,
   what you need from the client, how to reach you, communication
   norms)
3. A starter SOP list (5-8 numbered recurring tasks specific to this
   client's service type, formatted so they can be pasted directly
   into a project management tool)

Match the tone and structure of the uploaded reference document. If the
client's service type isn't covered by the reference material, ask one
clarifying question before drafting the SOP list.
  1. Under Knowledge, upload the scrubbed document from Part 1. Stick to one well-organized file rather than several; a Custom GPT searches uploaded files less accurately once there are more than a handful.
  2. Add two or three conversation starters, such as "New client: [business name], [service type]. Draft the onboarding set."

Part 3: Test and refine

  1. Run a test with a real (or realistic) new client scenario and read all three outputs closely against your actual process.
  2. If the SOP list is too generic, add one more example task to the uploaded reference document and test again.
  3. If the tone feels off, add an explicit tone instruction, such as "write like a helpful colleague, not a corporate template," directly into the instructions field.

Real Example: Onboarding a Two-Person Coaching Business

Setup: You built the Custom GPT above with your existing onboarding checklist as the knowledge file.

Input: You open the GPT and type: "New client: Bright Path Coaching, life coaching with two practitioners. They're disorganized with scheduling and want help getting a system in place fast."

Output: The GPT drafts a welcome email confirming a kickoff call and what to expect in week one, an onboarding packet outline covering communication norms and access needs, and a seven-item starter SOP list covering calendar management, intake form handling, and session note filing, formatted as a numbered list ready to paste into a task tool.

Time saved: What used to take an afternoon of adapting old documents becomes a single session, with the heaviest editing work now proofreading rather than drafting from a blank page.


What to Do When It Breaks

  • Output ignores the uploaded reference document → Too many files or too little structure in the one you uploaded. Cut it down to a single, clearly headed document and retest.
  • Drafts read generic, like they could apply to any VA → The instructions field is too vague. Add one real example sentence in your own voice directly into the instructions so the model has something concrete to match.
  • The SOP list misses a task you know matters → Treat every output as a first draft, not a finished packet. Compare it against your own mental checklist before sending anything to a client.
  • You're tempted to upload a real client's actual SOP as the knowledge file to save time → Don't. That file likely contains that client's specific account details, pricing, or process notes. Build the knowledge file from a scrubbed template instead, and check whether any client's contract restricts reusing their materials this way.

Variations

  • Simpler version: Skip the Custom GPT and save the same instructions as a reusable prompt you paste into a fresh ChatGPT conversation each time. No knowledge file, no setup, less consistency.
  • Extended version: Add a second knowledge file with a library of past starter SOPs by service type (coaching, e-commerce, real estate) so the GPT can pull a closer starting point for each new client's industry.

What to Do Next

  • This week: Write down your onboarding checklist if it only lives in your head, then scrub and save it as the knowledge file.
  • This month: Build the GPT, run it on your next two real onboardings, and note where the output still needs heavy editing.
  • Advanced: Turn the strongest starter SOP outputs into a small template library you reuse and refine across every new client, service type by service type.

Advanced guide for virtual assistant professionals. These techniques use more sophisticated AI features that may require paid subscriptions.