What this FAQ covers
This page answers recurring questions about agency workflow for agencies and client-service teams. The answers define practical boundaries, identify the evidence that matters, and explain when a question requires account-specific, technical, contractual, or legal review.
- Can reports use agency branding?
- Can I use audits for lead generation?
- How are clients separated?
- Can findings become estimates?
Use the answers responsibly
Apply each answer to the actual website, scope, agreement, and evidence. Avoid publishing scores without explaining what was tested or what the score means. When the decision could affect production availability, security, accessibility, billing, privacy, or contractual commitments, document the responsible reviewer and verification plan.
Questions and answers
01Can reports use agency branding?
Agency OS is designed to support branded and white-label reporting subject to the selected plan and configuration.
02Can I use audits for lead generation?
Yes, when the audit is authorized or limited to appropriate public observations and the marketing does not misrepresent risk, certainty, or affiliation.
03How are clients separated?
Organizations, websites, users, findings, reports, notes, exports, and permissions should remain tenant- and role-scoped.
04Can findings become estimates?
The workflow can connect findings to scoped repair paths, assumptions, dependencies, estimates, approvals, and implementation records.
05Can clients see progress?
Client portals can present approved summaries, priorities, reports, status, decisions, and evidence according to role.
06How does recurring care work?
Schedule baseline reviews, maintenance checks, content reviews, technical audits, and monitoring feeds against the same client record.
Turn agency workflow into an accountable record.
A clear, supportable answer set for agency workflow linked to the relevant workflow or policy.