Choose How to Embed GetVoiceBot
Embed one Agent interaction on a website or place the complete GetVoiceBot customer application inside your product.
GetVoiceBot supports two different embed experiences. Choose based on what the person should be able to do.
| Experience | Use it for |
|---|---|
| Agent embed | Let a website visitor call or chat with one published Agent. |
| GetVoiceBot app embed | Give an authenticated reseller customer access to the complete GetVoiceBot application inside your product. |
Embed one Agent
Use the Agent embed when a public website needs a call or chat button.
<button class="support-button" data-gvb-button data-target="AGENT_USERNAME" data-type="call">
Call us
</button>
<button class="support-button" data-gvb-button data-target="AGENT_USERNAME" data-type="chat">
Chat now
</button>
<script src="https://www.getvoicebot.com/embed/button/v1/script.js" defer></script>
data-targetis the published Agent username.data-typeiscallorchat.data-numbercan optionally direct a mobile call through the phone dialer.
Test microphone permission, browser compatibility, mobile behavior, and the Agent's live
configuration before adding the embed to production traffic. See Embed your Agent
for the full implementation.
Embed the complete GetVoiceBot application
Eligible resellers can place the GetVoiceBot application inside their product. Your trusted backend maps
the signed-in user to the correct GetVoiceBot customer organization, creates a one-time authentication
token, and returns the short-lived token to the frontend. The frontend loads /app/embed on the
reseller's GetVoiceBot domain.
Never place a long-lived GetVoiceBot API token in browser code, storage, or an iframe URL. See
Embed the GetVoiceBot app for the authentication and onboarding flow.
Brand and verify the experience
Use the intended white-label domain and review:
- logo, color, labels, links, and support destinations
- login, logout, and account switching
- microphone and camera permissions where used
- mobile and desktop layout
- customer access boundaries
- billing, onboarding, and deep links
The Agent embed and full application embed solve different problems. Do not give an unauthenticated
website visitor a customer application session when one public Agent interaction is sufficient.
