Skip to main content
White-Label Client Portal

White-Label Checklist Before You Invite Clients

Run through this checklist before your first client signs in, so they see your brand, the right data and nothing else.

Written By voiceaiwrapper

Last updated 26 days ago

Your client's first login sets the tone. Before you invite anyone, run through this checklist so the portal shows your domain and brand, the emails come from you, the client sees only what you intend, and billing is ready.

Each item links to the full article with the detailed steps. Work through them in order: several later items depend on earlier ones.

The checklist at a glance

#CheckWhere
1Custom domain shows LiveClient Portal β†’ Portal Configuration β†’ Domain Settings
2Brand name, logo, page titles and theme savedPortal Configuration β†’ Branding
3Branded emails workingClient Portal β†’ Client Emails
4Workspace has a campaign and an agentClient Accounts β†’ client β†’ Overview
5Permissions reviewedClient Accounts β†’ client β†’ Workspaces
6No engine or provider names showingPreview as the client
7Billing method chosen and plan assignedClient Accounts β†’ client β†’ Billing
8Portal previewed as the clientPrimary login or Login as User

1. Your custom domain is live

Open Client Portal β†’ Portal Configuration β†’ Domain Settings and check that the badge next to your subdomain says Live.

A live domain matters for more than the address. Branding and languages can only be set once a domain is connected, Stripe billing for a client needs a verified custom domain, and checkout redirects only work on it.

See Connect Your Custom Domain.

2. Your branding is in place

On the Branding tab, fill in and save:

  • Brand Name, shown throughout the portal.
  • Logo: square, PNG or JPG, at least 256Γ—256.
  • Meta Title and Meta Description, used in the browser tab and by search engines.
  • Portal Theme: Light, Dark or System. Clients can still switch.

Click Save branding. If you skip this, clients see a generic portal title instead of your name.

Optional at this stage: pick extra portal languages on the Localization tab, and add your own help chat on the Client Support tab.

See Brand Your Portal: Name, Logo, Meta and Theme, Offer the Portal in Multiple Languages and Add Your Own Support Widget.

3. Branded emails are working

Open Client Portal β†’ Client Emails:

  1. On Email Configuration, connect SendGrid with an API key (your sender email must be verified in SendGrid first), then click Send test.
  2. On Email Templates, turn on the emails you want clients to get, including the set up password email, and edit the wording so it sounds like you.

Without this, you can't turn on Send set-password email when you add client users. Its tooltip says "Cannot send a set-password email yet: SendGrid is not connected, or the set up password email template is off." You can still set a password for the user yourself and send it to them.

See Send Branded Emails to Clients With SendGrid.

4. The client's workspace has something in it

Open Client Accounts, then the client. The Overview tab shows a Client readiness checklist covering Workspaces, Users, Billing and Security.

Clients only see data in workspaces that have at least one campaign and one agent. If you invite users before that, they sign in to an empty portal. Every user in a client account can open all of that client's workspaces.

See Create a Workspace and Assign Assets.

5. Permissions match what you want the client to do

Edit the workspace and go through the Access Control step area by area. For each one, choose No Access, View Only or View & Edit. Start with less access: it's easier to open things up later than to explain why something disappeared.

Pay special attention to:

  • VAW Native workspaces: the What ran tab in call logs shows clients the models and providers behind the agent. It's off by default on a white-labelled portal. Leave it off unless you want clients to see which models and providers you use.
  • Vapi, Retell AI and ElevenLabs workspaces: Show prompt to client and Allow client to make test calls. Test calls aren't billed to the client, because only calls and chats inside a campaign are charged. They still run on your provider account, so you pay for them there.

See Set Client Permissions on VAW Native Workspaces and Set Client Permissions on Vapi, Retell and ElevenLabs Workspaces.

6. No engine or provider names are showing

Clients shouldn't need to know which voice engine powers their agents. When you preview the portal (item 8), look for any names you'd rather keep private, and turn off the access that shows them.

Places to check:

  • Call details, if you turned on the What ran tab.
  • Agent prompts, if you turned on Show prompt to client. Your prompt may mention tools or services by name.
  • On VAW Native workspaces, the AI model picker groups models under OpenAI, Anthropic and Google, if you let the client change the AI model.
  • Phone number, call transfer and text message screens mention Twilio, if the client can open them.
  • On Vapi workspaces, the agents page is called Assistants, which matches Vapi's own wording.

The portal itself avoids product and provider names: it says "the system" where your webapp says VAW, calls the AI agent builder Agent Builder, and removes provider names from call error messages and end reasons.

7. Billing is set up for the client

Open the client's Billing tab and choose how you'll bill them:

  • Stripe billing: charges the client automatically. Needs your Stripe account connected and a verified custom domain.
  • External billing: you collect payment yourself and the webapp tracks usage.

The billing method is permanent. Once you confirm Stripe billing or External billing for a client, you can't change it for that client.

Then click Assign a Billing Plan. A call is only charged if it happens after the client's subscription is active and the campaign is assigned to that client. Calls before then aren't billed, so assign the plan before the client starts making calls.

If you bill through Stripe, you can also choose where clients land after checkout. See Redirect Clients After Checkout.

See Ways to Bill Your Clients: Stripe or External Billing and Assign a Plan and Manage a Client's Subscription.

8. You've previewed the portal as the client

Sign in as the client and click through every page they can see:

  • From Client Accounts, click Primary login on the client's row. This needs a primary user, set on the client's Users tab.
  • Or, on the client's Users tab, open a user's actions and click Login as User.

Check the logo, brand name and browser tab title, the sidebar pages, the data in each workspace, and anything from item 6.

See Log In as a Client to Preview Their Portal.

Optional extras

None of these block a launch, but they're easier to set up before clients start using the portal:

  • Custom pages in the portal sidebar, such as a welcome page or a link to your booking calendar. See Add Custom Pages and Links to the Portal.
  • Client forms to collect onboarding details. See Build Client Forms.
  • IP access control on the client's Security tab. It's optional and doesn't affect client readiness.

Ready to invite

Add the client's users on the Users tab. To share the sign-in address, copy it from Client portal β†’ Copy link on the client's Overview tab. It's the same link for every client account.

See Add and Manage Client Users.