Make the next action dependable.

Begin with a specific request: for example, a customer asking to move an appointment. Identify the customer and the existing booking before discussing a new time. Check which record owns availability and which changes the actor may make. Keep a missing fact or uncertain availability visible; do not turn it into a confident promise. Then test a returning customer and an unrelated customer separately. The evidence should show the correct identity, the authoritative record and a next step consistent with the configured policy. Use the customer/CRM and booking reference for the detailed mechanics.

A customer can send a receipt or state that a transfer was made. That is a payment claim. Preserve the evidence and route it to the authorized human verification step rather than treating an image or convincing message as a verified payment. In a booking that requires a deposit, test the unpaid, claimed and verified cases separately. Observe whether confirmation is withheld or allowed by the actual policy. The useful proof is the authoritative state and the person's verification, not simply a friendly reply from the Agent.

Choose a case where the Agent must pause: an approval, unsupported request, uncertain provider delivery or missing business information. Confirm what the customer is told, which teammate owns the next step and what the record says. A prepared draft must not look like a completed send; an unknown outcome must not become a failure or success by assumption. Repeat the test with restricted permissions and a revoked access grant where applicable. A good handoff explains both the work already done and the decision still required.