Your facts. Your approval. Clear limits.

AI Guide is designed to use facts the owner approves. The planned flow requires factual answers to show their source and date, and approval for new or corrected content.

When an approved source is missing, it is designed to explain the gap and offer a person. Prices, availability, deadlines and business policies need approved sources. AI can make mistakes; these requirements are not a guarantee of error prevention.

The planned flow requires an answer before a contact form, then the visitor’s choice of contact method when requesting a reply. Call, text, email and marketing require separate controls, unchecked by default.

The design calls for a decline to stop unsolicited capture offers. Restarting capture requires an explicit action request. Withdrawal must take priority over a new request, with a way to change or stop contact.

The planned flow requires consent records with the wording and version, purpose, chosen channels and affirmative action. Public contact wording still needs counsel review.

The Guide is designed to alert the owner with a short request summary and permitted contact method, rather than a full transcript in the alert.

“Request sent” is not “owner notified.” A delivered alert is not an acknowledgement. The planned flow requires evidence for each state and a fallback contact path if delivery fails.

The planned chat session ends after at most two hours. This does not mean transcripts or contact records are deleted after two hours. Your choice to decline contact offers is intended to last while the browser tab stays open.

The planned flow requires contact details and consent records to use the agreed server-side path. Retention and deletion terms must be agreed before installation. The design keeps consent records with the lead; a client record needs its own purpose and retention terms.

The planned terms require deletion of your content and the Guide's data on request, while keeping the signed agreement and records required by law or the agreement.

The product design calls for no cookies or third-party trackers inside the conversation panel. The prototype does not prove privacy or accessibility, or that other software on a website cannot read what a visitor types. These protections still need to be verified before installation.

The scripted example on this marketing site has no editable visitor details and sends or saves no demo messages. It does not verify the planned production boundary. The request form below has its own privacy notice.

The planned flow requires these limits:

• Refer professional advice to a qualified person.
• Identify the assistant as AI.
• Do not send automatic texts or calls to a visitor.
• Require provider confirmation before describing an appointment as confirmed.
• Require permission before voice capture.
• Avoid promising business results.

These are product requirements subject to verification, not a certification or a claim of compliance.