> ## Documentation Index > Fetch the complete documentation index at: https://docs.itellico.ai/llms.txt > Use this file to discover all available pages before exploring further. # Client Service Models > Choose between parent-billed subaccounts, agency access, billing transfer, and hybrid client models Use this page if you serve multiple customers or clients and need to choose who owns billing, who owns the account relationship, and how your team manages ongoing work. There are two main models: * **Parent/subaccount model** - your company owns the parent account relationship with itellicoAI, keeps centralized billing, and may package, resell, or rebill your own customers separately. * **Agency access model** - the client owns and uses their own itellicoAI account, while your team gets elevated access to set up, manage, or maintain it. Hybrid setups are possible. An agency can use parent-billed subaccounts for some customers and agency access for others. ## Choose the Right Model | Model | Best when | Billing relationship | | --------------------------- | ------------------------------------------------------------------------------------------------------------ | ----------------------------------------------------------------------------------- | | **Parent/subaccount** | You resell, rebill, integrate by API, or want one isolated subaccount per customer under your parent account | itellicoAI bills your parent account; you handle any downstream customer billing | | **Agency access** | You set up, manage, or maintain client-owned accounts | The client is billed directly by itellicoAI | | **Direct billing transfer** | A customer starts under your parent account but later wants direct platform ownership | Billing moves from the parent account to an independent customer account | | **Hybrid** | Different customer types need different commercial or operational models | Some customers stay parent-billed; others become independent direct-billed accounts | ## Parent/Subaccount Workflow Start with [Accounts and Subaccounts](/accounts/overview) to decide whether each customer needs its own subaccount under your parent account. Use [Creating Accounts](/accounts/creating-accounts) and [Subaccounts](/accounts/subaccounts) to create isolated customer accounts with separate agents, contacts, conversations, and members. Leave subaccounts on parent billing when your company should receive one itellicoAI invoice and manage its own customer billing outside itellicoAI. Use account-scoped API keys, integrations, and the account switcher to manage each customer account in the right context. ## Agency Access Workflow Use agency access when the client owns the itellicoAI account and should keep direct billing. Use [Team Management](/accounts/team-management) and [Agency Settings](/accounts/agency-settings) to grant elevated access without changing account ownership. Build agents, configure integrations, review operations, and support the client while their account remains independent. ## Billing Decisions **Parent Billing** is the default for new subaccounts — your company receives one consolidated itellicoAI invoice and manages its own customer billing. To move billing responsibility to a customer, use the billing transfer flow in [Subaccounts](/accounts/subaccounts). After transfer, the customer account is independent and no longer a subaccount. ### When to Keep Parent Billing * You resell, rebill, or bundle itellicoAI into your own service * You want one invoice across multiple customers * Your API integration or support process expects parent-level oversight * Your team manages customer setup and commercial terms ### When to Hand Off Billing * The customer is ready to pay itellicoAI directly * The customer needs independent plan management * You want to keep service access without staying financially responsible for usage Use the billing transfer flow in [Subaccounts](/accounts/subaccounts) when a customer needs its own subscription but you still want to preserve agency access after the transfer. ## Access and Governance Use these pages together: | Need | Where to go | | ------------------------------------------------------------------- | --------------------------------------------- | | Control what non-agency members can access in client-owned accounts | [Agency Settings](/accounts/agency-settings) | | Invite and manage members | [Team Management](/accounts/team-management) | | Review data retention, data requests, or public trust settings | [Trust Center](/manage/trust-center/overview) | | Lock down authentication and sessions | [Security](/accounts/security) | ## Suggested Reading by Role Focus on subaccounts, parent billing, API keys, and customer isolation first. Focus on Manage after launch. Focus on agency access when clients own their own itellicoAI accounts. Focus on integrations, API keys, webhooks, and custom actions. Focus on retention, data requests, and public trust settings. ## Next Steps Review the hierarchy model and access rules Set the default access baseline for agency-managed client accounts Manage permissions, limits, and billing transfer Understand plans, usage, and ownership of charges