Help centre
Help centre
Installing the widget, training the assistant, and the checklist for when it does not appear. Written to be read before you email us.
- 01Getting StartedEverything you need to know to get up and running.
- 02Chat WidgetCustomizing and installing the chat widget.
- 03Account ManagementBilling, team members, and workspace settings.
- 04IntegrationsConnecting EzyConn to your favorite tools.
- 05API & WebhooksTechnical documentation for developers.
- 06Best PracticesTips and tricks for better customer support.
Getting started in four steps
EzyConn puts AI chat and a shared team inbox behind every channel your customers already use. Most teams go from sign-up to a working assistant in an afternoon. Here is the path we recommend.
Step 01
Create your workspace
Sign up in the customer portal. The beta is free, needs no credit card, and gives you up to six months of full access while you set things up.Step 02
Connect a channel
Add the chat widget to your website, or connect Microsoft Teams, Slack, Zoom, or WhatsApp so conversations land in one shared inbox.Step 03
Train it on your content
Point the assistant at your own material, your website, help docs, and FAQs, so answers come from your sources instead of generic guesses.Step 04
Go live and review
Turn the assistant on for real conversations, then read transcripts to spot gaps and add the answers your visitors keep asking for.
Installing the chat widget
The website widget installs with a single script tag. There is no build step and no npm package to add. Paste the snippet below just before the closing </body> tag on every page where you want chat to appear, and swap YOUR_WORKSPACE_ID for the ID shown under Settings, then Install in the portal.
<script>
(function (w, d) {
w.ezyconn = w.ezyconn || function () {
(w.ezyconn.q = w.ezyconn.q || []).push(arguments)
}
var s = d.createElement('script')
s.async = true
s.src = 'https://cdn.ezyconn.com/widget.js'
s.setAttribute('data-workspace', 'YOUR_WORKSPACE_ID')
d.head.appendChild(s)
})(window, document)
</script>Prefer to reach people where they already work? The same workspace also connects to Microsoft Teams, Slack, Zoom, and WhatsApp, so you do not have to run the widget to get started. For the full SDK, event tracking, and identity calls, see the developer docs.
Training the assistant on your docs
An assistant is only as good as what it knows. In the portal you point EzyConn at your own content so its answers come from your material rather than the open internet. A few habits keep answers accurate:
- Start with the pages people already ask about: pricing, returns, onboarding, and your top support articles.
- Keep source content current. When you change a policy, update the underlying doc so the assistant follows suit.
- Write in plain, self-contained sentences. Content that answers one question at a time is easier for the model to retrieve.
- Read real transcripts each week and add the answers to any question the assistant had to guess at.
Billing and workspace basics
EzyConn is in free beta. You get up to six months of full access with no credit card required, which is plenty of time to install, train, and run the assistant on live conversations before you commit to anything.
Your account
Sign in, reset a password, and manage your profile from the customer portal.
Team members
Invite teammates into the same workspace so conversations and notes stay shared.
Plans and limits
Details of what the beta includes live on the pricing page, alongside common billing questions.
Data and compliance
Need a DPA or security documentation? Email sales@ezyconn.com and the team will help.
Widget not appearing? Start here
If the chat bubble is not showing up on your site, work through this checklist in order. Most cases come down to where the snippet sits or which workspace ID it carries.
- Confirm the script tag is present in the page source and sits just before the closing body tag.
- Check that the data-workspace value matches the ID under Settings, then Install, with no extra spaces.
- Make sure the page has finished loading. On single-page apps, verify the script runs after the app mounts.
- Look in the browser console for blocked requests. Ad blockers, strict content security policies, or a firewall can stop the script from loading.
- Hard refresh to clear a cached copy of the page, then retry in a private window to rule out a stale cache.
- Verify the domain is one you actually deployed to, not a local preview the workspace has never seen.
Still stuck after those steps? Email contact@ezyconn.com with the page URL and a screenshot of the browser console, and we can trace it from there.
Popular articles
Still stuck?
The contact page lists exactly what to include in a bug report so it can be reproduced on the first reply.