Resources / Fictional demonstrations

Keep public demonstration sessions separate

Prevent one visitor from seeing or influencing another visitor's fictional inquiry.

01

The operational decision

Prevent one visitor from seeing or influencing another visitor's fictional inquiry. A public legal-intake demonstration should show a useful conversation while remaining separate from real inquiries and firm decisions. Visitors must understand that the caller, matter and result are fictional.

02

Prepare the workflow

Use per-session records and unguessable private result links where needed; clear prior state and avoid public lists of demo conversations.

03

Example wording for approval

“Each example session starts independently. Its result belongs only to that demonstration and should not reveal another visitor's questions or contact information.”

04

Worked example

Complete a fictional demo in one browser, then open a fresh session in another. The second visitor should not see the first request's fields, transcript or private result link. Test both the visible page and direct access to a previous result URL. A shared example fixture may be public, but visitor-specific conversation data should not become the next person's demonstration. The reviewer should also check expiry behavior so an old recap does not remain publicly discoverable through a resource index.

05

Handoff record

Record these task-specific fields: session identifier, result access rule, expiry, reviewer.

06

Acceptance check

Run two synthetic demos in separate browsers. The second session must not inherit the first one's fields, transcript or result link.

Legal intake capacity 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