For AI service providers · Guide
How to manage AI agents for multiple clients
Manage client agents with a separate workspace, named owner and acceptance routine for each client. Keep a portfolio register of expected work, then review records inside the relevant workspace. Start with a tested deliverable and expand only after access, approvals, output and cost checks pass.
By Agentic Workers Team · Published · Updated
Responsibilities and evidence
Agree on the owner and retain a safe evidence reference for each responsibility.
- Service scope
- Provider drafts; client accepts. Evidence: agreed output and stop conditions.
- Account ownership
- Client and provider confirm owners. Evidence: account inventory without secret values.
- Configuration
- Provider sets up the intended workspace and agent. Evidence: reviewed settings.
- Action review
- Named reviewer checks supported actions. Evidence: request and decision.
- Acceptance
- Client or delegated reviewer checks the result. Evidence: accepted artifact.
- Exit
- Account owner and provider remove access. Evidence: handoff and denied-access check.
1. Define each client’s operating record
Record the workspace, agent, source accounts, delivery channel, review owner and expected cadence. Put credentials in the approved account system, not in the register. Use fictional data to verify boundaries before connecting production records.
2. Run and review one client at a time
Select the Team workspace, confirm the agent and inspect its latest run. Check the artifact against the acceptance checklist and confirm delivery. Record exceptions in the portfolio register; do not infer healthy client work from a running agent alone.
3. Expand only after a repeatable result
Repeat the test after instruction or tool changes. When adding a client, reuse the procedure but connect fresh accounts and replace context. Rehearse removal of access before a service ends.
Example provider workflow. Adapt it to the client’s agreed scope.
- 01
Step 1: Define each client’s operating record
- 02
Step 2: Run and review one client at a time
- 03
Step 3: Expand only after a repeatable result
Fit and limitations
- Good fit
- Providers applying this process to an agreed client service.
- Poor fit
- Treating this checklist as an automatic product feature or a substitute for a client agreement.
- Known limits
- These are operating recommendations. Test each supported product path in the target workspace and plan. Examples are not performance, pricing or security benchmarks.
Sources and evidence
Documentation establishes the scope of a claim. It does not replace an acceptance test in your client’s environment.
| Source | What it supports | Checked |
|---|---|---|
| Team workspace setupProduct documentation | Teams organize agents and connected tools by workspace. Verify membership and the active workspace before setup. | |
| Read an agent run recordProduct documentation | Inspect available tool calls and execution details within the relevant workspace. A completed run is not proof of an accepted result. | |
| Customer portal operating notesProduct documentation | Upload and app-connection invitations are scoped to a selected agent. Revoking an invitation is separate from disconnecting an account. |
Questions providers ask
Who is responsible for the result?
The provider names an operator; the client names the person who can accept the deliverable. The platform does not replace those responsibilities.
What evidence should we retain?
Keep the source date, workspace and agent, expected output, review decision and artifact reference. Exclude credentials and unnecessary personal data.
When should we stop and review?
Stop when the account, recipient, output or permissions differ from the agreed scope, then resolve the exception before continuing.
Set up one client service
Set up the client workspace, connect its tools and review the first deliverable. Use a tested delivery path, such as Telegram, so the client can receive work in chat. Track operating costs and review effort before pricing a recurring service.
Sign up now