In short#
I can also answer on your website, in a chat bubble that a visitor opens from any page. You add me with one script tag: a snippet you copy in your workspace and paste in your site. There is nothing to install, no plugin, and no account to create for the visitor.
Two things before you start. Your Eva partner must allow the widget channel for your workspace, so if the place described below is missing, contact your partner. And you can talk to the widget before touching your website, which is where I suggest you begin.
So the job is short: open Settings → Messaging → Web widget, try the demo, copy the snippet, paste it on your site.
Try the live demo#
Open Settings → Messaging → Web widget.
Click Open live demo.
A demo page opens on
widget.eva.be/demo, with the key of your workspace already in the address.Open the bubble and have a real conversation.
The bubble on that page is the real widget, connected to your workspace. So ask what a visitor would ask, and read my answers as a visitor would. Those conversations land in your inbox like any other, which also lets you check that the follow up works before anyone sees the bubble on your site.
Do this first. It is much easier to fix my answers on a demo page than to discover a wrong answer live on your home page.
Paste the snippet on your site#
Stay in Settings → Messaging → Web widget and go to Embed snippet.
Copy the snippet. It looks like this:
<script
id="eva-widget-script"
src="https://widget.eva.be/v1/eva-chat-widget.js"
data-widget-key="wk_xxxxxxxx"
async
></script>Paste it in your site template, just before the closing
</body>tag, so the bubble is available on every page.Publish on a staging page first, open that page, wait for the bubble in the corner, and send a test message.
When the test conversation arrives in your inbox, publish the same snippet in production.
The data-widget-key value is the public key of your workspace. It starts with wk_, and you copy it from the field in settings. The wk_xxxxxxxx above is only a placeholder, it will not connect to anything.
Two optional attributes handle the language of the bubble. Fix one language for the whole site:
data-locale="fr-BE"Or map the language to the path of the page, for a multilingual site:
data-locale-prefixes="/fr/:fr-BE,/nl/:nl-BE"There is no language switcher inside the bubble. The language is decided when the script loads, so a visitor who changes the language of your site gets the other language on the next page load.
One point on the key. There is no domain allowlist, so anyone who reads the snippet can load the bubble on another page. Treat that key like any other public asset of your site, such as a logo or an analytics id: it is not a password, and it does not open your workspace. It is still worth keeping it out of random third party builders and playgrounds you do not control.
Visitor messages and appearance#
The same place holds what the visitor reads and how the bubble looks.
In Messages & presentation you write the first thing a visitor sees. Welcome suggestions are up to 4 short prompts, 80 characters each, that a visitor can tap instead of typing. The Floating teaser is the small message that invites the visitor to open the bubble, shown once per browser tab so it never becomes noise.
In Appearance you set the position on page, left or right, and check the result. The colors come from the branding of your workspace, so the bubble matches your site without any extra work.
Leave a field empty and I fall back to the primary language of your workspace, so an unfinished translation never shows an empty bubble. Write short prompts as real visitor questions, for example "Are you open on Saturday" rather than "Opening hours". A question invites a click, a label does not.
Which instructions I follow#
The chat itself follows your messaging instructions, the same ones as your other written channels. There is no separate script for the website: what I answer by email or on WhatsApp is what I answer in the bubble. You edit them in Settings → Messaging → Messaging instructions.
If you want to know what to write there, and how much detail I need, read how to write instructions.
If the bubble does not appear#
Three causes cover almost every case.
The widget channel is not allowed or not ready for your workspace. That is a partner setting, so contact your Eva partner.
The snippet is not on the page. Check that it survived your publication, that it sits before
</body>, and that the key is the one from your settings field, complete and without spaces.Your site blocks the widget. A content security policy can stop a page from loading a script from another host, or from keeping a connection open. Ask your webmaster to allow the Eva widget host
widget.eva.be, script and connection.
When in doubt, open Open live demo again. If the bubble works there and not on your site, the problem is on the page, not in your workspace.
Other ways to reach me#
Phone: how a phone call reaches me.
Email: how an email reaches me.
WhatsApp: How WhatsApp works with EVA, and Connect WhatsApp if you still have to link your Meta account.