- 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.
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
Design the account structure
Start with Accounts and Subaccounts to decide whether each customer needs its own subaccount under your parent account.
Create customer subaccounts
Use Creating Accounts and Subaccounts to create isolated customer accounts with separate agents, contacts, conversations, and members.
Keep billing centralized
Leave subaccounts on parent billing when your company should receive one itellicoAI invoice and manage its own customer billing outside itellicoAI.
Agency Access Workflow
Confirm account ownership
Use agency access when the client owns the itellicoAI account and should keep direct billing.
Invite agency users
Use Team Management and Agency Settings to grant elevated access without changing account ownership.
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. 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
Access and Governance
Use these pages together:| Need | Where to go |
|---|---|
| Control what non-agency members can access in client-owned accounts | Agency Settings |
| Invite and manage members | Team Management |
| Review data retention, data requests, or public trust settings | Trust Center |
| Lock down authentication and sessions | Security |
Suggested Reading by Role
Reseller or Platform Operator
Focus on subaccounts, parent billing, API keys, and customer isolation first.
Client Success or Operations Lead
Focus on Manage after launch.
Agency Owner or Admin
Focus on agency access when clients own their own itellicoAI accounts.
Technical Implementer
Focus on integrations, API keys, webhooks, and custom actions.
Compliance or Governance Lead
Focus on retention, data requests, and public trust settings.
Next Steps
Accounts and Subaccounts
Review the hierarchy model and access rules
Agency Settings
Set the default access baseline for agency-managed client accounts
Subaccounts
Manage permissions, limits, and billing transfer
Billing Overview
Understand plans, usage, and ownership of charges