Visitor approval and sensitive fields
Learn which Pro Agent browser requests are read-only, which await approval, and how sensitive page fields are handled.
2 min read
- Project
- Assistant
- Behavior
Configure the Pro assistant in Behavior, then test it as a visitor to see which browser operations stay read-only and which require visitor approval.
- Read onlyRead/display
Snapshot, read, highlight, or wait within the current page session.
- ConfirmVisitor approval
Scroll, fill, click, select, or navigate only after the visitor approves that request.
- Strong approvalSensitive data
Passwords, payment data, codes, and similar data are outside safe flows.
Pro Agent actions occur in the visitor's browser context. A tool request identifies the action, its parameters, and whether approval is required; the browser-side widget is asked to execute it only under that control.
Default action policy
The following browser capabilities are read/display operations by default: get_page_snapshot, read_element, highlight, and wait_for_element. They can still fail if the page no longer contains the requested element or the session ends.
scroll_to, fill_input, click_element, navigate, and select_option require approval by default. Treat scroll as a visible browser action as well: it may change what a visitor sees even where it does not submit data. The agent should describe the purpose, target, and expected effect before a visitor decides.
Do not position a visitor approval as general permission for later actions. Each browser request is a bounded request, and a denial returns a denied result to the agent rather than performing the action.
Sensitive fields and page boundaries
The browser workflow applies safeguards intended to avoid common sensitive targets and reduce sensitive-field exposure in page context. These are not complete data-loss-prevention controls: page markup, custom fields, and browser extensions can alter what appears on a page.
- Passwords or account-recovery data
- Payment-card data or payment authorization
- One-time authentication codes
- Health, government-ID, regulated financial, children’s, or similarly sensitive data
If a visitor provides sensitive information in the conversation, route them to an appropriate human or dedicated secure flow. Do not ask the Pro Agent to paste it into a form.
Consent and customer responsibility
Chat4U's browser approval is an interaction safeguard, not a substitute for your legal notice, consent, accessibility, or consumer-protection obligations. Customers control the website, page content, allowed domains, and visitor disclosures. Before enabling a browser-assisted journey, publish the appropriate notice, decide whether consent is required for your context, and validate the flow with your privacy/security owners.
A safe visitor-facing pattern
For a synthetic site, a safe sequence is: “I found the billing section. I can highlight it now.” → visitor sees the highlight request → the assistant explains that the plan selector is next → visitor approves selection or navigation. The assistant should stop and offer alternatives if the visitor declines, the page changes, or the request would touch a sensitive form.
Last updated on
Configure and test a Pro Agent
Enable Pro Agent mode for an eligible assistant, review domain boundaries, and test the visitor journey before publishing.
Pro Agent operations and safety
Handle approvals, failures, changed pages, time limits, fallback behavior, and plan boundaries for browser-assisted conversations.