Confirm a visit in one shared customer and staff record
Request an available time, confirm it as staff, and see the same visit in the customer view.
Recorded example · Read the desktop transcript · Read the mobile transcript
Ada needs an office-cleaning visit. Staff need her requested time and entrance note before confirming it. This example uses one shared visit record, so both views show the same request and confirmed status.
Fictional records. Actions stay in the simulation.
Open this demo pageTry the example
Change the records, prepare the work, and review it before saving. This uses the same local simulation as the demo page.
Actions stay in this demo.
Open full demoHow Do Both Views Share the Visit?
Select an available Tuesday time. Keep Ada’s note, “Please use the side entrance,” or change it. Request the visit to create sample record VISIT-204.
Open the staff view. It shows Ada, office cleaning, the requested time, and her entrance note. Staff can confirm the visit after examining those details. Confirmation reserves the selected slot in the example.
Return to the customer view. Ada sees the same confirmed visit and time. The result is one completed request across two views, with a shared status.
Try the unavailable Wednesday time after resetting. The request cannot proceed. A second request cannot duplicate the existing visit record. These rules keep the request and confirmation connected.
This application demonstrates a clear scheduling flow. It does not need AI to make the shared state useful. The example creates no real appointment and sends no notification. Staff make the confirmation decision.
What Potential ROI Could This Produce?
At 60% adoption, this example releases 20 hours per month. Assisted time includes human review.
Labor proxy: general administrative assistants. BLS May 2025 US wages are $23.73/hour nationally.
The cost factor is 1.43, from US private-industry compensation, June 2026.
| Input | Sample assumption |
|---|---|
| Monthly tasks | 500 |
| Minutes, manual → assisted | 6 → 2 |
| Build budget | $5,000 |
| Monthly operations | $100 |
| Potential value | US example |
|---|---|
| Hourly wages + benefits | $33.93 |
| Monthly capacity value | $679 |
| Monthly net capacity value | $579 |
| First-year capacity ROI | 31% |
| Payback, months | 8.6 |
First-year cost: $6,200. ROI divides annual capacity value, less first-year cost, by first-year cost. Payback divides build cost by monthly net capacity value. Slower adoption delays payback.
Released capacity is not automatic cash savings. Workload and time reductions are illustrative, not BLS findings. Internal support is assumed; The AI Operations plan costs extra. The budget and operating allowance are illustrative, not a Ship AI Studio quote. Measure costs before deciding.
What Needs Human Review?
Staff confirm actual availability and handle exceptions. A real build needs customer permissions, a scheduling connection, and a clear staff queue. Decide which changes need notifications and record their delivery status.
Measure status calls, scheduling time, duplicate requests, and time to confirmation. Examine whether customers can understand each status without calling staff. Keep service quality measures separate from administrative capacity.
The first workflow guide helps compare a portal with other recurring work before choosing the scope.