EveryHello Messenger
A persistent support conversation on your website.
Messenger adds a floating chat launcher. Visitors can ask questions, receive answers from approved business knowledge, and continue with a person when the conversation needs judgment.
How visitors experience Messenger
The launcher stays available on the page. Opening it reveals the greeting, suggested questions, and the visitor’s existing web conversation when one is available.
Interactive example. Messages stay in this page.
Acme Studio
Rosa, AI assistant
Install the web widget
Create the widget in Messenger → Chat Widget, add your site to Allowed domains, and place the generated script before the closing </body> tag.
<script
src="https://www.geteveryhello.com/widget.js"
data-key="wgt_YOUR_KEY"
async
></script>Use the generated key
Replace wgt_YOUR_KEY with the public widget key shown in your workspace. The widget does not load without a valid key and an allowlisted host.
What happens after the script loads
- 1
A small loader mounts an isolated iframe
The host page supplies only the widget key and its origin. The launcher and conversation UI render from EveryHello.
- 2
The visitor receives a persistent identifier
The identifier is stored in the widget’s browser storage so the visitor can reopen the same web conversation later on that device.
- 3
Messages enter the Messenger workflow
EveryHello can answer from approved knowledge, perform configured booking actions, or mark the conversation for team review.
- 4
Human replies return to the widget
While the panel is open, the widget checks for new team replies and adds them to the same thread.
Configuration
| Setting | What it controls |
|---|---|
| Enabled | Whether the widget can load and accept new web conversations. |
| Brand color | The launcher, visitor messages, and primary widget actions. |
| Logo | The business or assistant image shown in the conversation header. |
| Greeting | The first message visitors see when opening a new conversation. |
| Conversation starters | Up to four suggested questions shown before the visitor sends a message. |
| Position | Bottom-left or bottom-right placement for the floating launcher. |
| Allowed domains | The sites and subdomains authorized to use the public widget key. |
Content Security Policy
If your site uses a restrictive CSP, allow the EveryHello script and widget frame. Merge these sources into your existing policy instead of replacing it.
Content-Security-Policy:
script-src 'self' https://www.geteveryhello.com;
frame-src https://www.geteveryhello.com;Testing and troubleshooting
| Symptom | Check |
|---|---|
| No launcher | Confirm the key, Enabled setting, available plan capacity, allowed domain, and CSP. |
| Widget disappears | The bootstrap request was disabled or rejected. Verify that the exact production host is allowlisted. |
| No AI reply | Review plan usage, assistant mode, approved knowledge, and the conversation in Messenger Inbox. |
| History is missing | Browser storage may have been cleared or blocked. The widget falls back to the current browser session when persistent storage is unavailable. |
JavaScript control is not available yet
Messenger currently installs as an automatic floating launcher. There is no documented EveryHello.messenger.open() API in this version.