Brilo AI voice widget display rules let you control when the Brilo AI voice agent appears to website visitors by using configurable triggers such as time on page, page URL, or custom events. Brilo AI can be configured to show the voice widget after a visitor has spent a configured amount of time on a page (for example, 30 seconds) when you enable a time-based trigger in the embed settings or via the client-side SDK. Display rules are enforced client-side so they respond to session duration, page visibility, and event signals; they can also be combined with server-side routing or webhook checks when required. Use conditional triggers to reduce interruptions and target high-intent visitors while keeping the voice widget behavior auditable and consistent.

Can I make the widget appear after 30 seconds on a page? — Yes. Brilo AI can be configured to use a time-based trigger to show the voice widget after a set session duration.

Show the widget only on checkout pages? — Yes. Brilo AI supports page URL targeting or page-level rules to limit where the widget appears.

Can the widget wait until a user clicks something first? — Yes. Brilo AI supports event-driven display rules (for example, waiting for a click or form interaction) when configured to listen for those client-side events.

Enterprise teams ask about voice widget display rules to balance proactive engagement with user experience and compliance needs. Showing a voice widget too early can interrupt sensitive workflows in healthcare or banking, while showing it too late can miss a conversion opportunity. Buyers want predictable, testable controls for when the Brilo AI voice agent appears so legal, product, and ops teams can align on acceptable engagement windows, privacy disclosures, and monitoring.

Brilo AI implements display rules as configurable triggers that evaluate visitor state and page signals before rendering the voice widget. When enabled, a time-based trigger counts session-visible seconds and opens the widget only after the configured threshold is reached. Other triggers include page URL matching, element visibility, custom JavaScript events, and attribute checks that your site can emit. These triggers can operate entirely in the client (browser) or be combined with server-side checks via your webhook endpoint for additional routing logic.

In Brilo AI, voice widget is the on-page UI component that invites visitors to start a Brilo AI voice interaction.

In Brilo AI, display rule is a configured condition (time-on-page, URL, event) that determines when the voice widget is rendered.

In Brilo AI, time-based trigger is a widget rule that counts visible session seconds before showing the Brilo AI voice widget.

Brilo AI display rules should be configured to avoid interrupting sensitive tasks and to preserve user privacy. Do not rely solely on client-side timers for compliance-sensitive contexts unless you also enforce server-side verification or consent capture. Brilo AI display rules are not a substitute for explicit consent flows; when required by your policy, capture consent before opening a voice interaction. Limit rule complexity if you need deterministic behavior for auditing and incident investigation.

In Brilo AI, escalation condition is a configured event (for example, failed authentication or a flagged phrase) that prevents the widget from opening or immediately hands the session to a human agent.

Brilo AI voice widget display rules can be paired with handoff logic so that when the widget opens and the call requires escalation, the session can route to a human agent or an alternate workflow. Typical handoff behaviors include transferring the session to a live agent queue, triggering a callback request to your contact center, or opening a ticket in your CRM via webhook. Configure escalation conditions (for example, authentication failure, specific intents, or a “transfer” command) so that Brilo AI performs a controlled handoff without re-triggering the widget display rule.

Properly configured Brilo AI voice widget display rules reduce unwanted interruptions, improve lead quality by engaging higher-intent visitors, and lower false-positive voice sessions that waste contact center resources. For regulated sectors like healthcare and banking, display rules help align proactive engagement with operational policies and provide a clearer audit trail for when and why the Brilo AI voice agent appeared.

What is the minimum time delay I can set for the widget to appear?

Brilo AI supports configurable time-based triggers; the practical minimum depends on your client-side implementation and testing. Use staging to determine a value that balances engagement and nonintrusiveness.

Can I combine multiple rules (time on page + URL + click)?

Yes. Brilo AI display rules can be combined so the widget appears only when all configured conditions are met, or when any one of several conditions is true, depending on how you set the rule logic.

Will the widget show if the user switches browser tabs?

By default, time-based triggers count visible session time; Brilo AI can be configured to pause timers when the page is not visible to avoid showing the widget to inactive visitors.

Can I prevent the widget from appearing for logged-in users?

Yes. You can add a rule that checks a client-side attribute or emits an event (for example, a logged-in flag) so Brilo AI does not render the widget for those sessions.

Does changing display rules require a code deploy?

Many display-rule changes can be made in the Brilo AI admin console without a code deploy. Event-driven configurations that require new page events will require a small front-end update to emit those events.