An interactive example of a connected operational workflow. Compare routine and urgent requests, inspect the sample evidence and decide what happens next.
Not another answer.
A next step your team can review.
Please service the ventilation unit at our Carlton office next week. Asset V-204. Our maintenance summary is attached.
Fictional attachment: asset V-204 · Carlton office · last service 12 months ago. No safety inspection or diagnosis recorded.
Try “Urgent fault” to see why the same system must choose a different next step.
One request, with the information your team normally has to piece together.
ATT-01 / Maintenance summary
Fictional attachment: asset V-204 · Carlton office · last service 12 months ago. No safety inspection or diagnosis recorded.
POL-01 / Service policy
Fictional rule: routine service may be proposed in the next available window. Urgent faults require dispatcher review. Do not promise same-day attendance without an available slot.
CAL-01 / Team schedule
Fictional availability: today—no slots; next Tuesday—10:00–12:00. Static sample, not a connected calendar.
The log reflects actions in this demo. Restarting or changing the request clears the run.
A working interaction model, not a live AI agent or a customer-results case study. Predefined requests and local rules; no model calls, document parsing, external integrations or real actions. A client pilot replaces these sample steps with agreed sources and tools.