Client agent
It turns meetings and delivery notes into decisions, actions, updates, health checks, and proof requests inside one client workspace. Client-facing work still waits for review.
Inside the Operations Agent The Client Agent is one of two jobs inside the Operations Agent.
See the Operations AgentSummary
Runs
Client onboarding, meeting capture, delivery drafts, project updates, reports, health checks, proof requests, and case-study drafts
Reads
One client workspace, meetings, goals, reports, decisions, offers, and approved templates
Writes
Briefs, meeting logs, decisions, actions, checklists, reports, risk lists, testimonial requests, and draft case studies
Guardrail
One client at a time. No sibling client reads. No client contact without a person
Three agents
Direct answer
A Client Agent organizes service work inside one active client workspace: onboarding, meeting capture, decisions, actions, updates, reports, health checks, proof requests, and case-study drafts. Client-facing work waits for review.
Where it helps
It helps most when calls, promises, and follow-ups are spread across notes and nobody has the full picture before the next meeting.
What it can run
Each card lists the Conversion Skills the build can use for that job, so you can see what the agent draws on.
The client skill can onboard a client, create the workspace, pull a strategist brief, log a meeting, draft a deliverable, build a report, run a health check, or archive a client.
It can turn transcripts or notes into a filed meeting record, route decisions, extract actions, append metric rows when numbers are mentioned, and log the work to the daily note.
It can build a dated onboarding checklist with milestones, owners, due dates, and a first-value success measure.
It can refresh a project brief, log progress, append ledger rows for moved metrics, surface blockers, and hand off published work as a status update.
It can scan accounts or client goals for stale metrics, silence, missed milestones, open escalations, renewal risk, and recommended save plays.
It can draft testimonial requests, store received testimonials with consent status, and draft a case study only when a ledger row supports the result.
How it works
Step 01
The agent works only inside the active client workspace. If the client is ambiguous, it asks or files the note for a person instead of guessing.
Step 02
Meetings, decisions, actions, metrics, deliverables, reports, and proof each go to their correct home so the next run can find them.
Step 03
The result says what changed, what is waiting, who owns the next move, and what a person should review before anything client-facing leaves the business.
Human gates
The agent can prepare every update, recap, and report. Sending them, and anything that touches money or scope, stays with a person.
Outputs
Drafts you can read in a minute, with the decisions and owners already pulled out of the notes.
Firewalled client workspaces and one-screen briefs
Meeting records with routed decisions, metrics, and actions
Onboarding plans with owners, dates, and success measures
Project updates with blockers and next steps
Weekly or monthly client reports
Client health checks, proof requests, and draft case studies
Quick answers
What service teams usually ask before handing client notes to an agent.
Related agents
Pair it with the Report Agent and the numbers in each client update have a source behind them.
Public standard
The client workflows here come from Conversion Skills, the toolkit the operations build runs on. Access is free by request if you want to read how each one works.
