Join the Community
EzyConn is built in the open with the people who use it every day. Follow along for updates, contribute on GitHub, or reach the team directly. Here's where to find us.
Follow & contribute
GitHub
Star the repos, open issues, and dig through our open-source SDKs and example projects.
View on GitHubX / Twitter
Product updates, release notes, and the occasional support-automation hot take.
Follow @ezyconnCompany news, hiring, and longer write-ups on where customer support is heading.
Follow the pageTalk to a human
Questions, feedback, or a bug to report? Our team reads every message.
Contact support →Report a bug or request a feature
EzyConn is built in the open, and the fastest way to shape it is to tell us what is broken or what is missing. Here is where each kind of feedback goes.
Found a bug
Open an issue on the relevant GitHub repo with the steps to reproduce it, the surface it happened on, and what you expected instead. If the bug touches your account data or looks like a security issue, email contact@ezyconn.com privately rather than posting it publicly.
Open a GitHub issue →Have an idea
Open an issue that describes the problem you are trying to solve, not only the feature you have in mind, so we can find the best fix together. Search the existing issues first and add a reaction to one that already matches rather than filing a duplicate. Prefer email? Send it to our team.
Share it on GitHub →Contributing and community etiquette
A few simple habits keep our issues, pull requests, and threads useful for everyone who comes after you.
- Search existing issues and discussions before opening a new one, and add to the existing thread when it matches.
- Keep one topic per issue so conversations stay easy to follow and easy to close.
- Give us enough to reproduce a problem: the surface (website widget, Microsoft Teams, Slack, Zoom, Google Chat, or WhatsApp), your environment, and the steps you took.
- Assume good intent, stay civil, and keep the conversation on topic.
- Never paste API keys, tokens, passwords, or customer data into a public issue, and report security vulnerabilities privately to contact@ezyconn.com.
- Pull requests are welcome. For anything beyond a small fix, open an issue first so we can agree on the approach before you write the code.
Stay in the loop
A short monthly note with product updates, new integrations, and practical tips for automating support. No spam, and you can unsubscribe in one click.