Resources / Fictional demonstrations

Review demo screenshots before publication

Prevent private information from entering public marketing assets.

01

The operational decision

Prevent private information from entering public marketing assets. 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 synthetic fixtures, inspect every visible panel and check browser chrome and notifications; replace real calls rather than blurring only a name.

03

Example wording for approval

“This screenshot illustrates a fictional public-information answer. Its names, times and office facts are sample data and do not show a patient interaction.”

04

Worked example

A synthetic call card appears safe, but a browser notification in the corner contains a real person's name. Inspect the complete exported image, including browser tabs and sidebars, rather than only the focal card. Recreate the asset with synthetic material instead of depending on a small blur that may miss another identifier. The review record names the fixture and asset version so a later crop or edit can be checked against the same approved source.

05

Handoff record

Record these task-specific fields: asset filename, fixture source, review date, approver.

06

Acceptance check

Zoom into sidebars, tooltips and notification areas. A screenshot fails if a real identifier or conversation remains visible anywhere in the image.

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