Setting Up Multiple Sub-Accounts on Your Own Telnyx Account
gohighlevel agency phone setup 3 min read
How agency-level install and per-sub-account phone setup work on Phone Clover: the Company token, adopting numbers per sub-account, and billing reality.
- Best for
- Agencies running several HighLevel sub-accounts who want their own Telnyx account behind calling and texting, and need to know what's per-sub-account vs. agency-wide.
- Not for
- Agencies expecting a single combined dashboard across sub-accounts, or one invoice covering everything. Neither exists today.
- The difference
- Phone Clover's install works at the agency level once, then each sub-account adopts its own numbers and registers its own texting, on the same connected Telnyx account.
Running phone and texting for one HighLevel sub-account is one setup. Running it for a dozen, on your own Telnyx account, is a different question: what’s shared at the agency level, and what has to be repeated per sub-account? This guide walks through both.
What happens at the agency level
If you install Phone Clover as an agency (a Company-level install in GoHighLevel), the app mints a Company token during OAuth. From that Company token, it fetches a per-location token for each sub-account on demand, re-minting automatically when a token expires. In plain terms: you install once at the agency level, and each sub-account under it gets its own access without a separate install step.
Your connected Telnyx account works the same way. One Telnyx account can sit behind every sub-account you manage; you don’t need a separate Telnyx account per client unless you want billing kept fully apart.
What’s per-sub-account, not agency-wide
This is where agencies most often assume more sharing than actually exists. Per sub-account, not shared across the agency:
- Number adoption. Tag a Telnyx number
ghl-<locationId>to route it to one specific sub-account, orghlfor a shared pool, then adopt it from that sub-account’s Settings, Numbers. See Number Management for how adoption and purchasing work. - A2P 10DLC registration. Each sub-account registers its own brand and campaign; there’s no bulk or agency-wide registration. Ten texting sub-accounts means ten registrations. See register for A2P 10DLC.
- Ring mode, business hours, forwarding. Configured independently per sub-account’s default number, even when every sub-account shares the same Telnyx account underneath.
- The Telnyx cost dashboard and daily spend limit, if you’ve connected your own Telnyx account. These are scoped to one sub-account’s usage at a time, not a combined agency total.
What’s honestly not built
Two real gaps agencies should plan around, not settings buried somewhere else:
- No multi-location agency dashboard. There’s no single screen showing call or text activity across every sub-account you manage. An admin’s dashboard view is scoped to one sub-account; reviewing ten sub-accounts means checking ten dashboards.
- No agency-wide Telnyx cost rollup. The cost dashboard and spend limit, when available, apply per sub-account, not as one combined number across the agency.
If centralized, cross-sub-account reporting is a hard requirement today, that’s a genuine limit to plan around, not a configuration you’re missing.
Billing: what “agency” actually means here
Agency tiers are manual contracts. That means billed together under one agreement, arranged directly, not automatic self-serve signup or one invoice auto-generated across every sub-account. Usage that Telnyx bills directly, numbers, call minutes, texts, runs through your own connected Telnyx account and its own billing, separate from whatever agreement covers Phone Clover itself.
A practical setup order
- Install at the agency (Company) level if you’re rolling this out to more than one sub-account.
- Connect your own Telnyx account once; it can serve every sub-account under the agency.
- For each sub-account, adopt or buy its numbers, set ring mode and business hours, and register A2P 10DLC if it’ll text.
- Repeat the per-sub-account steps for every client sub-account; there’s no bulk action across them.
See connect your Telnyx account for the connection step itself, and for agencies for the broader picture of running Phone Clover across clients.
Where this leaves you
Agency-level install and a shared Telnyx account save you from reinstalling and reconnecting per sub-account. Everything downstream of that, numbers, texting registration, ring mode, reporting, stays per sub-account, with no combined dashboard or single agency-wide invoice today. Plan the rollout with that in mind: one connection, many separate setups.
See Number Management and for agencies for the next steps, and pricing for how agency plans are structured.