Skip to main content

Getting Started & Core Understanding

Vapify is a white-label management and billing layer for voice AI agencies. Vapi and Retell run the actual calls and host your assistants. Vapify sits on top of them and lets you package those assistants into a client-ready product with subaccounts, pricing, billing, and a branded client portal. Vapify does not replace Vapi or Retell, and assistant creation still happens in those provider dashboards.
Yes. Vapify does not create or host assistants. You must have a Vapi or Retell account with at least one assistant created in the provider. Vapify connects using provider API keys and syncs assistants from there.
The correct setup order is: create the subaccount, connect the provider API keys, sync assistants from the provider, assign the correct assistants, set per-minute pricing (and monthly fee if applicable), set the billing start date (go live), and then invite users. Skipping any of these is the most common cause of setup issues.
Going live is billing activation. When you set the billing start date, billing begins from that date forward, usage after that date becomes billable, the provider API keys become locked, and call logs begin syncing. You can still update assistant assignments after going live. Call logs are not synced until the subaccount is live.

Subaccounts & Client Structure

Subaccounts are strict client isolation boundaries. Each subaccount has its own assistants, pricing, users, billing and credits, and call logs. Using one subaccount for multiple clients breaks billing, reporting, and security.
No. An assistant can only belong to one subaccount at a time. Each subaccount represents one client, and assistants should never serve multiple clients. If you need similar assistants for multiple clients, create separate assistants in the provider and assign each to the appropriate subaccount.
If the subaccount is not live yet, you can remove assistants and assign different ones. Once the subaccount is live, you can still add and remove assistants as required, but you cannot edit the provider API keys.
Partially. Users can still log in and access the dashboard, but call logs are not synced until the subaccount is live. You must set the billing start date before call logs will appear.

Assistants & Provider Sync

Common causes are an incorrect API key, the key not being saved correctly, or the assistant list not being refreshed. Save a valid provider key in the subaccount and click “Refresh Assistant List” to re-sync.
Assistants are tied to the provider account connected to each subaccount. If assistants appear in one subaccount but not another, the subaccounts are using different API keys, the assistant list was not refreshed, or the assistants belong to a different provider account.
No. Assistants can still be synced even without phone numbers. This supports web calls made to the assistants.

Billing, Credits & Pricing

They serve different purposes. The monthly subscription is a fixed recurring fee (e.g., a platform or retainer charge) billed automatically through Stripe. Per-minute billing charges clients based on actual call duration — the more they use, the more they pay. Most agencies combine both: a monthly fee for predictable base revenue, plus per-minute charges for usage.
The monthly fee is a retainer or platform access fee by default. Usage is billed via per-minute pricing. If you want bundled minutes, that is a pricing strategy you implement as a package model and should verify how it is configured in your current plan and UI.
Credits and balance are different. Credits are assigned only by the agency and used for promotions or onboarding. Balance is funded by the client via Stripe top-ups and is used for per-minute charges after credits are exhausted. Agency clients can enable auto top-up so the balance replenishes automatically when it drops below a set threshold. Credits are always consumed first, then balance.

Call Logs & Usage

Common causes include billing not being live yet, incorrect provider API keys, delays in provider syncing, or calls made outside the subaccount context. Call logs sync automatically, but short delays can occur depending on provider status or rate limits.