Required decisions
- the reseller and customer identity
- whether the organization is a customer or internal organization
- the approved product plan
- the Agent template or custom configuration
- required members, channels, integrations, and Computer capabilities
- approval for resources that affect billing
1. Verify reseller state
- Read the reseller account.
- Confirm its enabled features, billing provider, domains, templates, and available plans.
- Search existing organizations by the customer’s stable external ID and name.
2. Create the customer organization
Use the organization creation operation with the reseller as the authorized parent. Supply a stableexternalAccountId when another system owns
the customer identity.
Save the returned organization ID and read it back. Confirm its reseller parent, organization type,
plan, active state, and external identifiers before continuing.
3. Create or configure Agents
Choose one path:- create Agent accounts and follow the Agent launch cookbook, or
- apply an approved reseller Agent template and supply its declared onboarding values
4. Configure customer access
Invite the required members with minimum access. Use restricted child-account access when a member should see only selected Agents. Verify the customer’s actual account view. For an embedded Vida experience, generate one-time user authentication tokens only from a trusted backend after confirming the user-to-customer mapping.5. Connect customer capabilities
Configure only what the approved plan and workflow require:- phone numbers, SMS, and SIP
- apps, functions, email, and webhooks
- Computer Agent lifecycle, skills, credentials, channels, and Tasks
- reporting fields and metrics
6. Verify billing and product access
Confirm the customer plan, subscription status, enabled features, included usage, and billing-system mapping. When checkout or subscription creation is part of onboarding, complete one approved test through the actual customer flow. Do not configure internal feature entitlements or payout behavior through undocumented routes.7. Run acceptance tests
Verify:- organization and Agent ownership
- customer member access
- prepared and live Agent configuration
- every required channel and integration
- one representative customer workflow
- logs, conversations, reporting fields, and usage visibility
- billing and support handoff