Use case · Internal helpdesk
A hundred employeesand the same fifteen problems.
What this actually looks like in the product: the questions it asks, where the answer comes from, and the point a person takes over.
- 24
- published processesreadable before you sign up
- 30
- languagesgenerated from the API constant
- 8
- native integrationsSlack, Teams, WhatsApp, Zoom, SMS and Zapier — everything else goes through a signed webhook
How it runs
Step by step.
Step 01
An employee asks in Teams or Slack
“How do I set up the VPN?” typed where they already work, not in a portal.Step 02
AI answers from your docs
The handbook or IT wiki answer, delivered in seconds, in the same thread.Step 03
Unsure? It hands off
Low-confidence or sensitive questions route to IT or HR with the transcript.Step 04
Your team resolves it
From the shared inbox or straight from Teams and Slack. The employee never left their chat.
Where it runs
The channels this reaches.
Native channels only. Anything not listed here goes through Zapier or a signed webhook, and the integrations pages say which is which.
- 01Microsoft TeamsNative
- 02SlackNative
- 03ZoomNative
- 04Website widgetNative
- 05WhatsApp BusinessNative
Questions
Before you start.
- Do employees need to install anything or learn a new tool?
- No. EzyConn runs natively inside Microsoft Teams and Slack, so employees ask questions in the chat tool they already have open all day. There is no separate portal to bookmark, no new login, and no ticket form to learn. IT and HR manage everything from the EzyConn dashboard and shared inbox on their side.
- How does the AI learn our internal policies and IT docs?
- You point EzyConn at the pages where your answers live, such as your handbook, IT wiki, or policy pages, and it trains on them through no-code crawling. It re-crawls nightly, so when HR updates the leave policy, the bot answers from the new version the next day. On security posture: EzyConn holds no SOC 2 certification.
- What happens when the AI cannot answer?
- Every answer carries a confidence score. When it drops below your threshold, or the employee asks for a person, the conversation hands off to your IT or HR team with the full transcript. They see it in the shared inbox, or reply right from Teams or Slack, and the employee gets the answer in the same thread they started in.
What EzyConn deliberately does not do is on the scope page.
Start with one process.
The free tier is enough to put this on a real page and route it to a real channel.