EveryHello documentation
Set up one front desk across every launch channel.
Activate your US business number for calls and texts, install Web Chat, and collect Feedback. All four surfaces use the same approved business knowledge and workspace access rules.
Choose where customers say hello
Each surface creates the record its channel needs, while your team works from one inbox and one customer context.
Phone and SMS
For customers who call or text your business.
One provisioned US number for incoming Voice and SMS. Number readiness and messaging registration are completed during onboarding.
Read the guideWeb Chat
For visitors who expect an answer.
A text-only website conversation with approved AI answers, 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 the website surfaces
Phone and SMS activate in onboarding. For Web Chat and Feedback, copy the matching public key from your workspace. The keys are public installation identifiers; domain checks and shared abuse limits are layered around them, but they are not authentication credentials.
Web Chat
<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 to call or text | Phone and SMS | A call or message record associated with the customer in the shared inbox. |
| I need help on this site | Web Chat | A customer, conversation, and message history in the shared 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
Normal widget requests fail closed when the claimed embedding site is not on the product’s allowlist. Treat that list as deployment policy, not as proof of caller identity.
- 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.