01
Real conversation
Customer messages persist as tickets and follow the same AI and human ownership rules as connected channels.
Website support widget
Put a real support conversation on the customer’s current page.
Configure the message, brand, position, privacy behavior, allowed domains, and human handoff—then verify the exact production embed from an interactive installation guide.
Website widget
Illustrative product motion
Evnao supportReady
How can I help?
Where is my order?
Allowed origin verified
Widget delivery flow
The approved website opens the saved widget and creates a real conversation.
System view
Signals in
01Your websiteAllowed origin
Evnao Widget
Saved configuration
Outcomes
01Shared inboxPersisted thread
What breaks
A widget fails at first value when its preview differs from production, opens inside a clipped frame, or accepts requests from an unapproved domain.
The operational change
The builder and live embed consume the same saved configuration, exchange origin-checked resize events, and show explicit unavailable states.
Product view
See the widget from website load to live conversation.
Illustrative layout of the shipped workflow. Live workspace screens use tenant data and permission checks.
Install and verify the real widget
Website widget · product workflow
store.example.com/orders
Evnao support
Can someone help with my order?
Your request is now in the support inbox.
Production checks
Allowed origin verified
Check 01
Saved widget configuration loaded
Check 02
Visitor capability issued
Check 03
Live conversation
The preview and production embed use the same saved contract.
Capability map
Built around this job.
Every surface below maps to a working product state, server action, or provider-backed workflow.
02
Allowed domains
Embed tokens are bound to configured origins instead of trusting a workspace identifier by itself.
03
Interactive installation
The settings guide covers common platforms, copy, verification, and recovery without an obsolete snippet.
04
Capability tokens
Visitor ticket access uses hashed, expiring capabilities with rate limits and tenant checks.
Release path
From configuration to a working result.
- 01
Configure
Set content, brand, behavior, and allowed origins.
- 02
Preview
Inspect the same contract used by the production widget.
- 03
Install
Add the canonical loader once to the customer website.
- 04
Verify
Check open, close, resize, mobile, and message delivery.
Verify the widget before it reaches customers.
Open the guided demo, then use the installation workflow to test the exact configuration on an approved domain.