The pilot’s design requirements

Safe for your visitors. Clear about being AI.

The pilot requires approved sources, clear AI disclosure, and consent before sharing contact details.

Request a walkthrough Read the requirements

AI disclosure

A guide that says what it is.

The pilot terms require a visible AI label beside the guide’s identity. Disclosure is designed to stay readable on a small screen and as the panel changes size.

The visitor should not have to open a policy page to learn that the reply came from AI. The guide is designed to offer a person whenever the visitor wants one.

Approved content

An answer needs a source.

The guide is designed to work from the content you approve. Factual answers carry a source line. Missing prices, dates, or availability should produce an honest limit and a route to a person.

Services page

Contact page

Your approved answers

Example source list · approved Nov 12, 2026

How answer approval works

Isolation

A defined place inside your page.

The pilot design calls for a sandboxed iframe with permissions reviewed during setup. The host website and guide have separate responsibilities; the installation review checks the boundary on your site.

Pilot isolation design

Your website

Page content, cookies and forms stay with your website.

Guide frame (sandboxed)

A separate frame with reviewed permissions.

Allowed path: the host and guide exchange explicitly handled messages across the frame boundary.

Design requirement to verify during installation, not a certification.

This describes the intended design. It is not a claim of certification or a substitute for checking the installed pilot.

Data handling

Agree on retention before install.

The pilot terms require a retention period agreed before installation, deletion on request, and no sale of visitor data. The setup review names the handoff destination and who can access the conversation.

Example deletion request

Visitor requests deletion → team locates the agreed record → deletion is handled under the pilot terms.

Retention and deletion responsibilities belong in the signed scope.

Ask about data handling

Human handoff

A person is always a valid next step.

The guide is designed to stop when it does not have an approved answer. The pilot terms require a named owner for handoffs so the visitor’s question has somewhere to go.

Example handoff

“I don’t have an approved answer for that. Would you like me to pass your question to the team?”

Needs a person · question and transcript included

Try the boundaries on a call

Your next step

Ask the awkward questions, too.

Use the walkthrough to ask what the guide can access, where a conversation goes, and what happens when it does not know. We will agree the pilot requirements before installation.

0–5 min
Your website
5–20 min
Try your questions
20–30 min
Scope and next steps

The button opens the Nexus Advisory booking page.

Request a walkthrough What happens on the call

Prefer email? ken@nexusadvisory.io