Helpful by design.
Bounded by your rules.
An assistant needs more than instructions. It needs defined access, review points, and a way to stop. Those decisions belong in the setup—not in the fine print.
A visible review boundary
A draft is not
permission to send.
Customer reply prepared
“We can offer Tuesday afternoon. Please confirm the site address before we finalize the visit.”
Reviewer checks availability, scope, recipient, and wording.
Human checkpoint
A named reviewer can approve the real message for sending, return it for revision, or stop the workflow. This page does not pretend to perform those actions.
Illustrative boundary only. Nothing is sent or scheduled.
Understand the boundaries
Clear answers.
Before access is granted.
What can the assistant access?
Only the systems and permissions agreed for the workflow. Start with the minimum necessary access, separate accounts where appropriate, and a named owner who can revoke access. Actual permissions must be checked against each tool’s capabilities.
Where does it run, and where does data go?
Deployment may use client-controlled infrastructure, hosted services, or a combination, subject to technical fit. Hosting location alone does not determine where data is processed. Model providers, integrations, retention, backups, and data flows must be reviewed and documented before launch.
Who owns the accounts, data, and configuration?
Your business retains its business data and control of its accounts. Ownership and licensing of custom configuration, third-party software, export formats, and offboarding support need to be stated in the agreement. We do not assume every vendor makes everything portable.
What happens when something is uncertain or wrong?
The workflow should route missing information and exceptions to a person instead of guessing. Agree on activity records, a pause procedure, responsible reviewers, and recovery steps. AI outputs still need checking; a review gate is not a guarantee of correctness.
Does this replace legal, clinical, or compliance review?
No. These examples cover administrative preparation. Professional judgment stays with qualified people. Regulated or contract-restricted information requires a separate suitability review; this prototype makes no certification or compliance claim.
A practical next step
Set the boundary with the task.
Your first workflow summary includes who reviews the work and which actions should stay on hold.