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

Posted on Oct 20 • Originally published at voice-dash.com • Fully Autonomous

Disclosure: I'm Nabeel, founder of VoiceDash, a client portal for Retell agencies. This post is about account design, not the product.

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? It looks like a billing choice. It is really a tenancy choice, and it decides how you attribute cost, how far a leaked API key can reach, who owns the phone numbers, and how messy offboarding gets.

TL;DR: run one agency account for clients on a managed retainer, where you carry the usage and bill a flat fee, and use a client-owned account only when the client insists on owning the vendor relationship, works in a regulated industry that wants its own agreements, or is big enough to want its own billing. Whichever you pick, decide four things up front: who pays Retell, who owns the numbers, how agents are named and tagged per client, and what the client gets to see. I build production voice agents for US clients on Retell, n8n, GoHighLevel and Twilio. Here is how I structure it.

Nobody thinks about account structure on client one. You sign up for Retell, build an agent, buy a number, and ship. By client five you have a single account holding five businesses' agents, numbers, recordings and transcripts, all paid for on your card, all reachable with one API key.

That setup creates four real problems as you grow:

None of this means one account is wrong. It means one account needs rules.

This is what most agencies run, and what I recommend for the managed retainer model.

How it works. You own the Retell account and the payment method. Every client's agents live in it. You pay Retell for all minutes and charge each client a flat monthly retainer that covers usage up to an agreed level.

How it works. Each client has their own Retell account, usually with their own card on it. You get access to build and maintain the agent, and the client pays Retell directly for minutes. You charge a management fee on top.

The costs. Every client account means a separate setup, separate API keys to manage, separate webhook configuration and separate places to check when something breaks. Updates that take minutes across one account become a checklist across ten. You also lose the clean flat retainer, because the client now sees the raw per-minute bill and will compare it to your fee.

The rule that makes the hybrid work is writing the choice down at onboarding, in the same intake where you collect hours, services and escalation contacts.

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

Call data lives where the account lives. In a single agency account, every client's recordings and transcripts sit in your account, which is good for support and bad if you have not agreed retention and export rules.

What I put in writing for every client, whichever structure:

Offboarding cleanly is also a sales point. Telling a prospect exactly how they can leave makes them more comfortable signing.

A shared account is only as safe as its access rules.

Whichever structure you choose, the client should not be working inside Retell. Retell's dashboard is built for builders: agents, prompts, settings, and in a shared account, every other client's calls. Even in a client-owned account, the raw dashboard shows cost and configuration the owner does not need to see.

So the client-facing layer is a separate, tenant-scoped read model: calls synced from the API or webhooks, keyed by the client identifier you put in metadata or the agent prefix, and every query filtered by that tenant before anything renders. Whether you build that yourself or use an off-the-shelf portal, the account design above is what makes it possible. If agent names and call metadata are not consistent, no reporting layer can split the data cleanly afterwards.

Structure your Retell setup on purpose before client five forces it on you. One agency account is the right default for a managed voice AI agency because it keeps building fast and your margin private, as long as you name agents by client, split usage by client, agree ownership of numbers and data up front, and give every client their own scoped view instead of the raw account. Use client-owned accounts when ownership, regulation or volume genuinely call for it, and write that choice down.

Drafted with AI assistance and fact-checked against each vendor's docs.