A: Hi, Thanks for the detailed questions. Yes, Release0 can work well for an agency/service model where you manage the agents yourself and deploy them on your clients’ websites, without giving each client access to the Release0 dashboard.

For your specific questions:

1. 30–40 clients in one workspace: You can manage multiple client-facing agents within the same workspace, subject to your Tier 5 limits. If your average is 300 completed chats × 40 clients, that would equal 12,000 submission chats/month.
2. Tracking usage per client/agent: The monthly submission allowance is calculated at the workspace level. There isn’t currently a native system for assigning a separate submission quota to each agent, such as exactly 300 chats per client.
3. Setting a 300-chat monthly limit: There is no native per-agent monthly submission limit. If strict client-level limits and separation become important, using separate workspaces for clients is an option, but each workspace has its own plan and limits.
4. Going over the monthly allowance: Your agents don’t simply stop immediately when you reach the submission limit. Please contact us if you need additional submissions and we can arrange additional capacity without changing your lifetime plan.
5. Cost for 5,000 additional chats: Please contact us at [email protected] for pricing based on the additional volume you need.
6. Scaling to 50–100+ clients: If you continue managing everything yourself, you can organize multiple agents within a workspace. As you scale, separate workspaces can also be useful when you need stronger separation of client limits, statistics, access and credentials. Keep in mind that each workspace has its own plan.

And regarding your main question: yes, you can provide the chat solutions you build with Release0 to your own clients and charge them setup and recurring service fees. Your clients don’t need dashboard access if you’re managing the agents for them. The public-facing agents can also be deployed without Release0 branding and using your custom domains, according to your plan’s limits.

One useful detail for an agency model is that multiple agents can share the same custom domain using different slugs, so you don’t necessarily need one custom domain for every agent/client.