Resources / Fictional demonstrations

Reset a demonstration between public sessions

Keep one visitor's interaction from appearing in another visitor's example.

01

The operational decision

Keep one visitor's interaction from appearing in another visitor's example. A public demonstration should reveal how the conversation works without becoming a live front desk. Visitors need to understand that the office, caller and operational result in the example are fictional.

02

Prepare the workflow

Use isolated session results, clear prior sample state and test a fresh visit after a completed demo; do not reuse public recap links.

03

Example wording for approval

“A new demonstration starts with the fictional office facts only. It should not recognize a previous visitor or display another person's conversation.”

04

Worked example

The first synthetic visitor asks about evening hours, and the second visitor opens the demo from a different browser. The second session should begin with the standard fictional facts rather than greeting the prior visitor or displaying their result. Test private recap access as well as the visible interface. A reset that clears the page but leaves another session's result accessible is incomplete. Public examples should be deliberately shared fixtures, not leftovers from previous interactions.

05

Handoff record

Record these task-specific fields: session boundary, reset action, result access rule, reviewer.

06

Acceptance check

Complete two fictional sessions in separate browsers. The second must not inherit the first session's answers, identifiers or private result view.

Front-desk time calculator ↗

Try Ava with your business’s public information ↗

Related guides

Your workflow, first

Let’s map your first week.

Bring the calls you want covered. We’ll agree the script, handoff and limits.

Start a pilot