The proposed workflow helps Sales prepare a request, checks for required facts, and lets Operations approve the packet before an office record is created. In this example, a missing site access window stops the handoff.
Illustrative sample — not a client engagement or measured result
Today and a proposed first trial
Current sequence to investigate
Customer sends a request by email or phone.
Sales reads it and asks follow-up questions from experience.
Sales passes a free-form note to Operations.
Operations may discover a missing site fact while planning work.
Office staff create or correct the work-order record.
This is a hypothesis for the invented company, not an observed baseline.
Proposed sequence
Capture the inquiry in a review queue.
AI extracts stated facts and drafts a customer question and work packet.
A deterministic checklist blocks the packet when the site access window is absent.
Sales confirms the missing fact with the customer; Operations reviews the complete packet.
Office staff receive the approved record for work-order entry.
No automatic customer message, dispatch, scheduling, or system write is assumed.
CaptureInquiry and source record
PrepareAI draft with source references
CheckRequired facts and exception owner
ApproveOperations review before office handoff
Trace the same request through the stop
These invented artifacts let a reviewer see what the system should do when the access window is missing. The names and details below are synthetic.
1. Customer input
Illustrative sample — not a client engagement or measured result
From
Morgan Lee, Cedar Works Property Team (invented)
Request
“The rooftop unit at our West Annex is cycling off. Can someone look at it this week? Use the loading-door entrance.”
Stated facts
Site: West Annex; issue: rooftop unit cycling off; entrance: loading door; timing request: this week.
Missing fact
Site access window: no date or time when the team may enter.
2. AI-prepared draft for Sales
Illustrative sample — not a client engagement or measured result
Extracted summary
West Annex rooftop unit cycles off; customer requests a visit this week; loading-door entrance mentioned. Every fact must link back to the inquiry text.
Draft question
“What date and time window can our team access the West Annex rooftop unit?”
Review state
Unsent draft. Sales checks the wording and asks the customer.
Not inferred
No access time, urgency class, service commitment, price, technician, or cause is invented.
3. Stopped exception
Illustrative sample — not a client engagement or measured result
Rule result
STOP: site access window is required and absent. The draft work packet cannot advance.
Owner
Sales representative. Ask the customer, record their answer with its source, and resubmit for review.
Operations state
No packet to approve yet. Once the access window is supplied, Operations verifies the scope and access details before approving an office handoff.
Office state
No work-order record until Operations approves. The eventual approved record retains source, reviewer, and exception history.
4. Customer answer and reviewed packet
Illustrative continuation — all people and records are invented
The original packet remains stopped in its history. This continuation shows the extra evidence and decision needed to release a revised version.
Customer answer · source S2
Morgan replies: “The facilities lead can meet your team at the loading door on September 25, 2026, from 10 a.m. to noon Central time. They can escort the technician to the roof.” This is an access window, not a confirmed appointment.
Sales revision · packet v2
Site: West Annex. Equipment symptom: rooftop unit cycling off (original inquiry S1). Entry: loading door (S1 and S2). Access: September 25, 10 a.m.–noon Central, with facilities escort (S2). Requested timing: this week (S1). Price, diagnosis, assigned technician, and appointment remain unset.
Rule check
Required access window now present and linked to S2. Packet v2 may enter Operations review; it cannot advance to the office on this check alone.
Operations decision · R1
Jamie Ortiz, fictional Operations reviewer: approved for office intake. The stated symptom and customer access conditions are sufficient to create a planning record. Staff must still confirm technician availability and safe site access before committing to a visit.
Office handoff · H1
Create a pending work-order record from packet v2 with S1, S2, reviewer R1, and the original stopped version attached. Status: planning required. No dispatch, customer commitment, diagnosis, or charge is authorized by this example.
Who does what
Responsibilities and permitted actions in the proposed trial
Actor
Permitted action
Boundary
AI preparation
Extract stated facts, cite source spans, draft a question and packet.
Cannot supply an unstated access window, contact the customer, approve, dispatch, or write a work order.
Deterministic rule
Check that a site access window is recorded before moving the packet to Operations.
Pass/fail on a required field; it does not judge feasibility or service priority.
Sales
Check the draft against the inquiry, ask the customer for the access window, record the answer and source.
Owns missing customer information; does not self-approve Operations readiness.
Operations
Review the complete packet for scope, access, and safe planning; approve or return it.
Approval is a human decision. A rule pass alone cannot release the packet.
IT and system owner
Define data access, retention, queue permissions, logging, and any later integration test.
No production connection or autonomous system write is implied by this sample.
Office
Receive the approved packet and create or update the work-order record through the agreed process.
Receives no unapproved draft as a final instruction.
Trial conditions and measurement
Evaluation cases
Complete request: all required facts present, source links correct, Operations can approve or return.
Missing access window: rule stops; Sales receives the exception; office sees no approved record.
Contradictory access times: Sales resolves the conflict with the customer before resubmission.
Ambiguous equipment or site: no invented value; Sales asks for clarification.
Operations rejection: packet returns with a reason and retains its review history.
Human decision
Handoff criteria
Sales confirms source facts and records the customer-provided site access window.
The required-field check passes and points to the recorded answer.
Operations approves the scope and access details in a named review step.
Only then may the office receive the packet for work-order entry.
Failure at any criterion keeps the packet in the review queue with a named owner.
Definitions to establish a baseline and compare a trial
Measure
Definition
Source and caution
First complete packet time
Elapsed working time from logged inquiry to first packet that meets required fields and receives Operations review.
Use timestamped queue and review records; separate customer waiting from internal handling.
Return rate
Packets returned by Operations for missing or incorrect information divided by packets reviewed.
Count reasons consistently; a higher early rate may reflect safer detection.
Review and rework effort
Sales, Operations, and office minutes spent checking, correcting, and entering each request.
Use a sample or time study; do not equate AI draft speed with total time saved.
Adoption
Eligible inquiries processed through the reviewed queue divided by eligible inquiries in the agreed period.
Track bypasses and why people chose them.
Quality exceptions
Incorrect facts, unsupported inferences, missing access details, and inappropriate approvals per reviewed case.
Review examples, not only totals; serious errors trigger a stop.
A trial needs a client-specific baseline, case mix, and review period before any value claim. Released staff capacity may improve responsiveness without reducing cash expense.
Use this to make a decision
The companion brief compares process-only, existing-tool, and bounded AI options against this same missing-access-window problem. It names prerequisites and reasons to defer.
