The portfolio view: clients, branding, billing, and who on your team can operate.
The operating layer for agency AI.
One workspace for the agency. A workspace per client. Website Chat, WhatsApp, Instagram, and AI Forms sit on that client — with knowledge, capture, and the portal beside them.
What sits in the workspace.
Client work stays attached to the client.
The unit of work. Plan, status, and which deployments are live stay on that account.
Website Chat, WhatsApp, Instagram, and AI Forms attach to the client — not a pile of unrelated bots.
Website and files for knowledge. Shopify, WooCommerce, or Magento for live catalogue answers.
Contact Requests, webhooks, and Cal.com keep the client’s existing stack involved. Calendly is coming soon.
A monthly story for the agency, plus a branded portal the client can open.
Launch the client, then the next one.
The same sequence, without a new stack.
- Add the client
Name, plan, and a workspace. This is what you invoice — not a generic bot project.
- Connect sources
Website and files for knowledge. Catalogue tools only if that client needs live products.
- Deploy what they need
Start with Website Chat. Open WhatsApp, Instagram, or AI Forms when the job needs them.
- Prove and expand
Contact Requests, Insights, and the portal give the retainer something specific to talk about.
Four jobs, one product.
Sales through operations.
Sales
Demos and Website Chat on the client site — not a vendor login the prospect has to learn.
Implementation
Knowledge, appearance, embed, and go-live happen in the same workspace you just showed.
Client success
Contact Requests, Insights, and portal access the client can open without operating Kuga.
Operations
Plan limits, account separation, and a repeatable path across the portfolio.