Skip to main content
Vida supports two different embed experiences. Choose based on what the person should be able to do.

​
Embed one Agent

Use the Agent embed when a public website needs a call or chat button.
  • data-target is the published Agent username.
  • data-type is call or chat.
  • data-number can 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 Vida application

Eligible resellers can place the Vida application inside their product. Your trusted backend maps the signed-in user to the correct Vida 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 Vida domain. Never place a long-lived Vida API token in browser code, storage, or an iframe URL. See Embed the Vida 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.