Your customers are not the test environment.
We replay normal, incomplete, unusual and failed cases before the workflow depends on live customers.
Visual State implementation standards
Clear before cleverKnow exactly what your AI can do before it touches a customer.
Before we switch anything on, you approve the rules, access, decisions, fallback and proof. If the system cannot be explained clearly, it is not ready for your business.
Before anything goes live
Six answers must be clear to you.
- 01PurposeOne clear job✓
- 02AccessOnly what it needs✓
- 03Owner decisionsClearly named✓
- 04Messy casesProperly tested✓
- 05Manual pathReady to use✓
- 06MeasuresAgreed with you✓
Your price and promises remain yours.
The decisions that change scope, cost, capacity or risk wait for the person you approve.
Your business still has a manual path.
If a connection fails or a request falls outside the rules, the next human step is already clear.
Six non negotiables
The questions we answer before you depend on anything.
You should not need technical knowledge to understand who is responsible, where the boundary sits and what happens next.
01Who owns the rules?
One person owns the next step.
You know who can approve the rules, who handles exceptions and who can accept a change before it reaches customers.
Owner, approver and exception path recorded
02What can it see and do?
It only gets the access the job needs.
You approve the systems, information and actions required for the agreed workflow. Extra access is not treated as convenient access.
Sources, actions and permissions listed
03What still comes to me?
Real decisions stop with you.
Pricing, scope, capacity, contracts, complaints, sensitive information and unusual requests follow the human path you choose.
Owner only decisions named before launch
04What has been tested?
We test the clean, messy and broken cases.
A workflow is not ready because the easiest example worked once. Missing details, duplicate events, urgent wording and connection failures are tested too.
Accepted cases and results kept together
05What actually changed?
The report says what happened.
A handled enquiry is a system event, not automatically a sale. Won work, saved time and revenue are only reported when the evidence supports them.
Activity and business outcomes kept separate
06Can I take over?
You can see it, pause it and use the manual path.
Key events, exceptions and failures stay visible enough for the responsible person to stop affected actions and return to the agreed process.
Monitoring, support and fallback agreed
A messy request on a real Tuesday
The standard has to hold when the easy path stops.
Your system should move normal work without pretending every request is normal. Here is the difference between useful automation and confident guessing.
- 01A customer asks for a standard service
Approved reply sent and useful details collected
Moves within your rules - 02The request fits your normal area and service
Normal path confirmed and record prepared
Rules passed - 03The customer asks for unusual access and timing
Request held with the full context attached
Waits for you - 04The calendar connection does not respond
No booking promise is made to the customer
Manual path starts
Your sign off
You approve the operating rules, not a vague AI promise.
We turn the workflow into a clear acceptance record. You can see what is included, what still needs a person and what happens when the normal path fails.
See how we build and test- 01The exact job✓
What the workflow carries and what outcome it is meant to improve.
- 02The access✓
Which systems, information and actions are required for that job.
- 03The business rules✓
Approved wording, normal conditions, limits and anything the system must not invent.
- 04The owner decisions✓
Every price, promise, exception or sensitive issue that still needs a person.
- 05The failure path✓
What pauses, who is told and how your team continues manually.
- 06The proof✓
The cases we tested, the result you accepted and the measures used after launch.
Clear responsibility
You do not hand over your business judgement.
01The system carries
The repeatable work
- ✓Approved routine responses
- ✓Information collection
- ✓Prepared drafts
- ✓Approved reminders
- ✓Record updates
02You decide
The business judgement
- ↗Final price and scope
- ↗Capacity and commitments
- ↗Sensitive customer issues
- ↗Unusual exceptions
- ↗Professional judgement
03Visual State maintains
The implementation
- ✓Workflow build
- ✓Acceptance testing
- ✓Visible failure handling
- ✓Agreed monitoring
- ✓Documented changes
The boundaryVisual State owns the implementation work. You or your approved person owns the business decision.
Honest evidence
We report the result without turning every click into revenue.
You deserve to know what the system actually changed. Activity, owner time and business outcomes stay separate until the evidence connects them.
- ✓Enquiries handled
- ✓Replies and exceptions
- ✓Owner review time
- ✓Quotes or requests progressed
- ✓Recorded customer outcomes
- ×Every message into won revenue
- ×An assisted result into sole cause
- ×An estimate into a measured saving
- ×Website or creative work into an AI case study
- ×An unknown outcome into a success
When the evidence stopsIf we do not know, the report says unknown.
When something breaks
Your business still needs a next step.
- 01
Pause affected actions
Stop the part that cannot be trusted while the rest of the business keeps its manual path.
- 02
Use the fallback
The approved person receives the context and continues the work without guessing what happened.
- 03
Inspect the record
We trace the event, inputs, rule and connection that produced the problem.
- 04
Correct and retest
The change is replayed against the normal, messy and failed cases before it returns.
- 05
You approve the return
The affected path resumes only after the responsible owner accepts the correction.
What these standards do not promise
Clear controls are not a legal guarantee.
These are Visual State operating standards. They are not legal advice, a compliance certification, a cybersecurity certification or a guarantee of error free output. Privacy, consumer, employment, recording, industry and contractual obligations depend on your workflow and business context.
Questions you should ask before launch
Do not accept an answer you cannot use.
01Can the system send customer messages without me approving every one?+
A routine path can use wording and conditions you approve before launch. Pricing, commitments, sensitive requests and anything outside those rules can be held for you or the person you nominate.
02Who can access my customer information?+
Access is defined for each workflow. You approve which systems and information are required, who can operate the workflow and what actions it may take. We do not promise a connection until the real access and controls have been verified.
03What happens if the system gets something wrong?+
The affected action follows the agreed failure path. That may mean pausing, handing the full context to a person, correcting the rule or connection, replaying the test cases and asking the responsible owner to accept the return to live use.
04Can I turn the system off and go back to doing it manually?+
The manual fallback is defined before launch for the important path. The exact pause and takeover controls depend on the tools involved, so we confirm what is genuinely available instead of promising a universal switch.
05How will I know whether the system is actually helping?+
We agree on the baseline and useful measures before launch. System activity, owner time, exceptions and real business outcomes stay separate so you can see what moved without turning every automated action into an invented return.
06Do these standards guarantee legal or industry compliance?+
No. These are Visual State operating standards, not legal advice, a compliance certification or a guarantee of error free output. Privacy, consumer, employment, recording, industry and contractual obligations depend on your workflow and business context.
Bring one real workflow
See the control points before you agree to the build.
Show us one enquiry, quote, follow up or finished job. We will map what can move, what must stay with you and what has to happen if the normal path fails.