For AI service providers · Guide
How to offboard an AI service client
Offboard a client by stopping recurring work, handing over agreed artifacts and removing access in separate, verified steps. Revoke customer portal invitations, disconnect authorized app accounts and review workspace membership. Revoking a link alone does not delete uploaded files, cancel existing provider consent or transfer ownership.
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. Agree on the final deliverable
Confirm the client’s account owners, retained files, final output and remaining support. Stop or pause scheduled work before changing access. Record unfinished work and obtain agreement on who will handle it.
2. Remove the access paths
Revoke active upload and app invitations, disconnect app accounts and remove provider membership as appropriate. Check outstanding authorizations with the source provider. An active invitation can reconnect an app, so invitation revocation and account disconnection both matter.
3. Verify and document the handoff
Test that removed access fails and that the client can use its own source accounts. Confirm receipt of the agreed artifacts. Handle retention and deletion under the actual agreement and platform behavior; do not promise automatic certified erasure.
Example provider workflow. Adapt it to the client’s agreed scope.
- 01
Step 1: Agree on the final deliverable
- 02
Step 2: Remove the access paths
- 03
Step 3: Verify and document the handoff
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 |
|---|---|---|
| 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. | |
| Team workspace setupProduct documentation | Teams organize agents and connected tools by workspace. Verify membership and the active workspace before setup. | |
| Schedule a recurring jobProduct documentation | Configure and test the schedule, time zone, agent and supported result destination. |
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