White-label GetVoiceBot

Present GetVoiceBot under your brand with eligible reseller domains, application settings, communications, and embedded access.

Eligible resellers can present GetVoiceBot as part of their own customer experience. White-label options
depend on the reseller's agreement and enabled product capabilities; an ordinary organization does
not need a reseller account to create and operate its own Agents.

Customer application domains

Use a domain you control for the customer-facing GetVoiceBot application. GetVoiceBot must be able to serve the
domain over HTTPS before customers use it.

Reseller administrators can manage registered application domains from GetVoiceBot. API integrations can
use the White-label domains and embedded access guide.

Embedded application

Resellers can place the complete GetVoiceBot application inside their own product. Your backend verifies
the customer and user, generates a one-time authentication token, and your frontend loads
/app/embed on the GetVoiceBot domain.

See Embed the GetVoiceBot app for the complete security and onboarding flow.

Branding and customer defaults

Available reseller settings can control customer-facing identity, navigation, onboarding defaults,
and enabled product experiences. Configure only the options available in your reseller account and
verify the result from a downstream customer account—not only from the reseller administrator view.

Agent behavior still belongs to each Agent's staging and publish lifecycle. Do not use account
branding settings as a substitute for Agent instructions, functions, voices, or reporting fields.

Communications and billing

Depending on your agreement, GetVoiceBot can support reseller-specific phone, SIP, email, and billing
arrangements. These can affect routing, compliance, and customer charges. Confirm the intended
ownership model with GetVoiceBot before moving a production number, domain, SIP route, or billing account.

Launch checklist

Open the app All docs