EveryHello documentation
Add support and feedback to your website.
Install Messenger for ongoing customer conversations, Feedback for contextual reports and ratings, or both. Each product uses its own public key and domain allowlist.
Choose the customer moment
The products can share a site, but they create different records and set different expectations for the visitor.
Messenger
For visitors who expect an answer.
A persistent web conversation with approved AI answers, conversation history, and a path for a person to take over in the shared inbox.
Read the guideFeedback
For moments when you want a signal.
A contextual form or five-face experience rating that creates a reviewable submission without starting a support conversation.
Read the SDK guideInstall one line before closing body
Copy the real key from the matching setup page in your EveryHello workspace. Public widget keys are intended to appear in site source and are protected by your domain allowlist.
Messenger
<script
src="https://www.geteveryhello.com/widget.js"
data-key="wgt_YOUR_KEY"
async
></script>Feedback
<script
src="https://www.geteveryhello.com/sdk.js"
data-feedback-key="fdb_YOUR_KEY"
async
></script>How the products fit together
| Customer intent | Use | Result |
|---|---|---|
| I need help | Messenger | A customer, conversation, and message history in the Messenger inbox. |
| I found a problem | Feedback report | A bug, idea, or general submission in the Feedback inbox. |
| How was that? | Experience rating | A one-tap score from 1 to 5 in Experience Ratings. |
Before you go live
- 1
Add every production domain
Requests fail closed when the embedding site is not on the product’s allowlist.
- 2
Test on the real host
A local preview confirms appearance. A production-host test confirms the script, iframe, domain policy, and content security policy together.
- 3
Collect only useful context
Do not place secrets, payment information, health information, or unnecessary personal data in widget context.
Need the security details?
Read Privacy and security before adding customer identity or application context.