B2B agencies, independent operators, and client owners
Give a client and operator a clear handoff
Agree who owns the relationship, approvals, replies, and evidence before an agency or BDR starts work.
Guide dated September 30, 2026. Your actual report has its own evidence time and scope.
The work to complete
Agree one client's scope
Keep each client company's work in its agreed Workspace. Define the deliverables, channels, approval owner, response capacity, and stop rules. Separate software access from a service commitment.
Keep this artifact
A dated responsibility sheet accepted by the client owner and delivery owner.
Map identity and access
The Sending Seat owner controls their authorized sender accounts. A VA/BDR operator works through a scoped service identity: it is not a paid Sending Seat and cannot independently own provider Konnections. Confirm assigned access before opening or changing client work.
Keep this artifact
A scope list showing who can view, draft, approve, or act. No shared credentials.
Review the first draft together
Walk through targeting, permitted records, exclusions, copy, delay logic, and reply guidance. The client checks commercial truth and qualification rules; the operator checks execution details. Sending begins only after required payment, consent, Konnections, and launch checks.
Keep this artifact
A reviewed Kampaign draft and explicit approval from the responsible owner.
Prepare the reply handoff
Define what the operator can answer, what must go to the client, and how interest is qualified. A resource request, a referral, and a meeting request need different responses. Record the next owner and use only the approved channel.
Keep this artifact
A reply decision sheet with escalation, decline, absence, and scheduling rules.
Make the first update useful
Report the same authorized scope and dates every week. Explain completed setup, recorded outcomes, expected waits, actual failures, and the decision needed next. Client portal access remains limited to the client's permitted read-only view.
Keep this artifact
A progress note with evidence time, unknowns, owner, and next review date. Avoid promises of lead volume or revenue.
Inspectable walkthrough
How we use Klosent: the workflow
Fictional example: a specialized recruitment agency works with one client company. The client approves the target roles; an assigned BDR reviews replies; the sender owns the paid Sending Seat and its Konnections.
An example to adapt, with no customer result or live execution. Access and actions depend on authorized scope and your Workspace's actual availability.
01
Workspace and Sending Seat scope
- Start with
- The agreed client, named sender, assigned operator, and approved responsibilities.
- Reviewable output
- A checked access and responsibility sheet for that client's work.
- Human decision
- Verify the actual role and Seat scope. An operator assignment does not grant independent provider ownership or access to other clients.
02
Kampaigns → Konvos
- Start with
- The approved draft and reply decision sheet, with all launch requirements satisfied.
- Reviewable output
- A permitted conversation reviewed by the BDR and handed to the client when the question needs their expertise.
- Human decision
- Confirm the buyer's expressed need. The human owner approves the response and any scheduling action.
03
Outkomes → client review
- Start with
- The client's authorized reporting window and current recorded evidence.
- Reviewable output
- A progress update with counts, freshness, waiting reason, and next owner.
- Human decision
- Check the read-only client view and explain missing receipts. A booked meeting remains a booking until attendance and qualification are recorded.
Your working checklist
Checkboxes are for your reading and are not saved. Download the worksheet for your review. Keep client data in its authorized space.