Skip to main content
Troubleshooting and FAQs

White-Label and Clients FAQ

Short answers about your white-label client portal: brand and provider names, your own domain, clients building agents, how clients pay you, data separation, embedding and languages.

Written By voiceaiwrapper

Last updated 12 days ago

Quick answers to what agencies ask about the white-label client portal: what clients see, where they log in, what they can do and how they pay you. Each answer links to the full setup article.

Branding and domain

Mostly no, once you've set up your domain and branding. Clients log in on your domain and see your logo and brand name. They never see your Pod connections, API keys, your VoiceAIWrapper plan, your AI credits or your costs: campaign analytics in the portal never show the cost section.

A few places can still show a product or provider name:

  • The AI agent builder is called VAW Assistant, for example Create with VAW Assistant. Only clients you allow to build agents see it.

  • Campaign webhook settings can name the engine, such as Vapi or VAW Native, if the client can edit campaign settings.

  • Before you connect your domain, the portal runs on a shared VoiceAIWrapper address without your branding.

  • On VAW Native workspaces, the What ran tab in call logs lists the models and providers used. It's off by default; leave it off for a fully white-label portal.

Log in as the client before you invite them, and click through every page they can see. See Log In as a Client to Preview Their Portal and White-Label Checklist Before You Invite Clients.

Yes. Connect a subdomain such as portal.yourbrand.com under Client Portal β†’ Portal Configuration β†’ Domain Settings. Once it shows Live, clients log in there. You need a plan that includes Custom domain.

A connected domain also unlocks the Branding tab (logo, brand name, page titles and theme) and the Localization tab. See Connect Your Custom Domain and Brand Your Portal: Name, Logo, Meta and Theme.

Yes. Connect your own SendGrid account under Client Portal β†’ Client Emails, with a sender email you've verified in SendGrid. Invitations, password resets and call summary emails then go out under your name. You need a plan that includes White-labeled emails. Without SendGrid connected, clients don't see a Forgot password? link on the portal's login page. See Send Branded Emails to Clients with SendGrid.

Twelve: English, Spanish, Portuguese, German, Italian, French, Austrian (Austrian German), Dutch, Polish, Russian, Hungarian and Danish. You choose which ones clients can pick under Client Portal β†’ Portal Configuration β†’ Localization. English is always included.

Multilingual client portals and agency admin portals are included on Pay-as-you-go, Growth and Scale. A connected custom domain is needed to configure the languages offered on your branded client portal. The setting translates the portal itself, not your agents, prompts or custom pages. If you need an additional language, contact support. See Offer the Portal in Multiple Languages.

Yes. Open Client Accounts, click the client, open the Users tab, and choose Generate Embed URL in a user's menu. Register the domain where the portal will appear, then copy the link or the iframe code. The embed only loads on the domains you register. You need a plan that includes Embed the client portal on your own site.

Anyone who can open the page where you embed the portal sees that client user's portal without logging in. Only embed it on pages that are private to that client.

See Embed the Client Portal in Another Site.

What clients can do

Yes, if you allow it in the client's workspace:

  • VAW Native workspaces: turn on Create agents, and set Maximum agents to cap how many they can make. You can also decide whether they can change the voice, language or AI model, and whether they can delete agents. See Set Client Permissions on VAW Native Workspaces.

  • Vapi, Retell AI and ElevenLabs workspaces: turn on Can create agents with VAW Assistant. Clients then build agents with the guided builder. The agents are created in your provider account, and the builder uses your own OpenAI key. Your plan must include VAW Assistant. Clients can't delete agents on these workspaces. See Set Client Permissions on Vapi, Retell and ElevenLabs Workspaces.

Any calls your clients' agents make are paid by you: from your AI credits on VAW Native, or by your provider account on other Pods.

No. You create every client user from the client's Users tab. All users of a client account see the same workspaces and have the same access. If two people at a business need different access, give them separate client accounts. See Add and Manage Client Users.

Yes. Add your own support chat widget (for example from your help desk tool) under Client Portal β†’ Portal Configuration β†’ Client Support. It appears in every client's portal. You need a plan that includes Support widget in client portal. See Add Your Own Support Widget.

Billing and data

You choose one of two methods for each client, on the client's Billing tab:

Method

How it works

Stripe billing

The client pays by card in their portal. Subscriptions, usage packs and one-time charges are collected automatically through your own Stripe account. Needs Stripe connected and a verified custom domain.

External billing

You bill the client yourself, outside the platform. The platform tracks usage, plans and payment requests. When the client pays you, you record it with Update status on the payment request.

The choice is permanent: "This is permanent, you cannot change the billing method for this client later." With either method, a call is only charged if it's made after the client's product subscription is active and the campaign is assigned to that client.

Stripe billing needs a plan that includes Bill your clients with Stripe; external billing needs Bill clients outside the platform. See Ways to Bill Your Clients: Stripe or External Billing.

No. Each client account is separate. A client's users only see the workspaces you create for that client, and each workspace only shows the agents, campaigns, numbers and other items you assign to it. Several clients can share one Pod, each with their own workspace.

Two rules keep assignments clean:

  • A campaign belongs to one client. Calls are billed to that client. To serve two clients, clone the campaign and assign one copy to each. See Assign a Campaign to a Client.

  • On VAW Native, an agent belongs to one client. Assigning it to a second client's workspace fails with "… already belongs to …. Remove it there first, then add it here."

See How Client Accounts and Workspaces Work.

Yes, one per Pod. For example, a client can have a workspace on your VAW Native Pod and another on your Vapi Pod. They switch between them with Select Workspace at the top of the portal. See Create a Workspace and Assign Assets.

Related articles