Retell AI for Agencies: One Account or One Per Client? How to Structure Accounts, Keys and Phone Numbers

Описание и применение

Агентства, использующие Retell AI, выбирают структуру аккаунтов: большинство клиентов обслуживаются в одном агентском аккаунте с строгой номенклатурой и метаданными, а отдельные аккаунты создаются для клиентов, требующих владения, регулирования или высокого объёма. Правила включают соглашения о владении номерами, хранении записей и безопасном управлении ключами.

Задача

Agencies building Retell AI agents for multiple clients face a tenancy decision that impacts cost attribution, data isolation, ownership disputes, and blast radius.

Результат

Agencies can maintain clear cost attribution, data isolation, and secure offboarding by defaulting to a single agency account with strict naming and metadata, while reserving client‑owned accounts for cases of ownership, regulation, or high volume. Phone number and recording policies, along with server‑side API key management, further mitigate risks.

Рабочий процесс

• Choose default structure (agency account for retainers, client account by exception).
• Document reason for client‑owned account in contract.
• Prefix every agent with client code (e.g., ACME-receptionist-v3).
• Pass client identifier in call metadata for usage tracking.
• Track monthly usage per client even with flat pricing.
• Agree on phone number ownership and exit rules before purchase.
• Define recording retention, export, and deletion terms.
• Keep API keys server‑side, limit access, rotate keys proactively.
• Monitor all clients in the account.
• Provide a scoped client view that filters data by tenant.

Доказательства

If you build Retell AI agents for more than one business, you hit a design question long before you hit a scaling problem: does every client live in one Retell account, or does each client get their own?

Источник

That setup creates four real problems as you grow: Cost attribution, Access and data isolation, Ownership disputes, Blast radius.

Источник

One place to build, test and update every agent, which matters when you roll the same fix across ten clients.

Источник

I prefix every agent with the client code, for example ACME-receptionist-v3, so nothing is ambiguous in logs, webhooks or reports.

Источник

Phone numbers cause more offboarding fights than anything else, so I treat them separately from the account question.

Источник