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

Description and use

Agencies using Retell AI choose an account structure: most clients are served in a single agency account with strict naming and metadata, while separate accounts are created for clients requiring ownership, regulation, or high volume. Rules include agreements on number ownership, recording retention, and secure key management.

Problem

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

Outcome

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.

Workflow

• 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.

Evidence

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?

Source

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

Source

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

Source

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

Source

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

Source