Web engagement
Core Widget: Add an AI Chat and Voice Assistant to Any Website With One Line of Code.
One script tag. The widget lives in an isolated frame, so it never breaks or restyles your site. Visitors talk in real time — interrupting naturally, like a phone call — or type, in the same conversation.
Its strongest capability is doing real work on the page. The assistant reads the page the visitor is on, drafts text straight into the form field they are filling — nothing inserted without their acceptance — and can take confirmed actions: escalate to a human, or take a deposit.
Start a conversationYou're looking at it — the assistant in the corner of this site is Core Widget.
What visitors get
- Voice and text in one widget — real-time speech with instant barge-in: talk over the agent and it stops
- Answers grounded in your documents — the agent answers only from what it retrieves, not generic knowledge
- Aware of the page the visitor is on, with server-side redaction of personal data
- Co-writing: drafts or improves text directly in the form field the visitor is filling — the visitor reviews and accepts
- Farewell intelligence: recognizes the visitor is done — any language, judged by intent — says goodbye, and closes the session cleanly
- Mobile-friendly: fits any phone screen and keeps the display awake during a conversation
- Captions for accessibility; voice degrades gracefully to text if the speech provider has an outage
- Resizable, draggable, remembers its size and position — and every agent discloses it is an AI
Actions — with the visitor's explicit consent
- Define the actions your agent may take: web calls to your systems, or pre-approved database operations
- Any write requires the visitor's explicit spoken or typed confirmation — enforced server-side, audited row by row
- Built-in actions include escalate-to-a-human and secure deposit-taking
- Test Draft: a real chat inside the configuration page that talks to your draft with the real AI models — tool actions simulated, nothing metered, nothing touching real systems
- Draft → publish workflow: published versions are immutable, with full version history
Built for agencies
Many clients, one platform
- Each widget is one end client — its own configuration, keys, documents, and published agent
- Nothing shared between widgets: isolation enforced at the database level
- Roles for the platform owner, the agency, agent builders, and client viewers
- Start new agents from vertical templates
A portal for your clients
- Invite an end client by email; they sign in with a magic link — no password
- They see only their own widget's transcripts and flagged leads
- No configuration, no keys, no usage data, no other clients — ever
Know what happened — and be told when it matters
- Transcript explorer: every session, voice and text unified, turn by turn with timestamps
- Leads page: the sessions worth following up, each linking to the full conversation
- Dynamic alerts written in plain language — "fire when the visitor wants a callback" — evaluated by AI when each session ends
- Notifications by email and SMS, naming which client fired the alert, with a secure, expiring report link: AI summary plus full transcript, no login needed
- Usage dashboards: sessions, minutes, and actions per day
Your data, in your systems
- Pull API for transcripts, leads, confirmed actions, and usage — filtered per widget, paginated
- Daily CSV files for any day — downloaded from the portal with no code, or fetched automatically
- Signed daily webhook tells your systems when yesterday's files are ready
- API documentation with ready-to-run Python and C# examples — authentication, pagination, downloads, signature verification
Security
- Widget keys with per-key domain allowlists, rotation with grace periods, and immediate revoke
- Passwordless sign-in by email magic link; optional two-factor, required for platform administrators
- Keys and tokens stored only as hashes; tenant data isolated at the row level; an append-only audit trail of every significant action
Try it right now.
Open the assistant in the corner of this page and ask it something about CoreEdge.