A plumbing demo script that tests the hard parts

The decision to make first

A demonstration that only asks for opening hours may sound convincing without showing whether the assistant handles an actual service-request exception. Choose a small sequence that includes a normal request, an unsupported promise and a correction, all using fictional information.

What the handoff should contain

Prepare expected intake fields, a boundary statement, a changed callback detail and the sample summary that should result at the end.

Suggested wording to approve

Example wording: “Try a fictional service request, then change one detail and ask whether a technician is definitely on the way. Ava should preserve the correction and explain the limit.”

Test the difficult case

Run the same scenario through phone, web voice and chat where those channels are enabled, comparing the essential final record. Do not judge the demo solely by voice quality if the assistant invents availability or loses the corrected information.

Worked example

Fictional example: The visitor gives a fictional callback number, corrects one digit, then asks whether a technician is guaranteed to arrive. The sample outcome should contain the correction and an explicit unconfirmed service state. Passing this case demonstrates useful request handling; a pleasant greeting alone does not establish that the workflow preserved the important details.

Review it in operation

Review differences between channels and prioritize missing or incorrect handoff information before polishing optional conversational flourishes.

Check before you launch

• Choose a small sequence that includes a normal request, an unsupported promise and a correction, all using fictional information.
• Prepare expected intake fields, a boundary statement, a changed callback detail and the sample summary that should result at the end.
• Run the same scenario through phone, web voice and chat where those channels are enabled, comparing the essential final record.
• Review differences between channels and prioritize missing or incorrect handoff information before polishing optional conversational flourishes.

Related guides