Participation guide

Welcome. Vzla.io runs a small community, primarily on Telegram, where we share news, answer questions, and gather the feedback that shapes our tools. This guide is the practical companion to that space: it explains what the community is for, how the channels are organized, and how to get the most out of them. It sits alongside the code of conduct, which sets the behavior we all agree to, and the community terms, which set the rules of use. When in doubt, be kind and be clear, and you will be right most of the time.

What this community is for

The community exists so people who use Vzla.io can talk to us and to each other. In practice that means three things:

Getting help. Ask a question, get unstuck, learn how a tool is meant to work.
Giving feedback. Tell us what works, what does not, and what you wish existed.
Following along. See what is coming, weigh in on decisions, and help shape the roadmap.

It is not a support ticket queue or a marketplace. It is a place to have useful, respectful conversations with real people who build and use the same tools you do.

Where we talk

We keep a few Telegram groups, each with a clear purpose so conversations stay easy to follow:

Official Vzla.io group: news, announcements, and general discussion about the app and its tools. Start here if you are not sure where a message belongs.
Beta testers group: for people trying pre-release versions. This is the right place for early bugs, rough edges, and feedback on features that are still taking shape.

Each group has its own rhythm, but the same guide, code of conduct, and terms apply everywhere.

How to participate well

A few habits keep the groups helpful for everyone:

Read the pinned messages first. They hold the essentials: what the group is for, current rules, and answers to the most common questions.
Search before you ask. Telegram’s search often surfaces an answer that already exists, and it saves everyone time.
Post in the right group. General discussion in the official group; pre-release issues in the beta group.
Keep threads tidy. Reply to the relevant message so conversations stay easy to follow, and avoid splitting one topic across many messages.
Give people time. This is a community, not a paid support desk. A thoughtful answer may take a little while.

Asking a good question

The clearer the question, the faster and better the answer. When you ask:

Say what you are trying to do, not only what went wrong.
Include the specifics: which tool or screen, what you did, and what you saw.
Paste the exact message or error text rather than describing it from memory.
Mention what you already tried, so no one repeats it.

A little context up front usually turns a back-and-forth into a single helpful reply.

Feedback is the reason this community exists, so please share it. To make it count:

For a bug, describe the problem, what you were doing when it happened, and what you expected instead. Steps to reproduce it are gold.
For an idea, explain the need behind it, not just the feature. Knowing why you want something helps us find the best way to deliver it.
Report pre-release bugs in the beta testers group so they reach the right eyes quickly.

Posting in the group is the best way to be heard, because others can confirm the issue or build on the idea. If something is sensitive, or you would rather not post it publicly, contact us directly.

What you can post

You are welcome to share:

Questions about the app and its tools.
Suggestions and proposals for improvement.
Your experience using existing features, good or bad.
Participation in surveys and technical discussions about future features.
Bug reports for pre-release versions, in the beta testers group.

What doesn’t belong here

To keep the groups focused, please avoid:

Advertising or self-promotion without prior authorization. Sharing your own product, channel, or link is not what these groups are for; ask an administrator first if you think there is a genuine exception.
Spam, repetitive messages, or flooding a group with rapid-fire posts.
Topics unrelated to Vzla.io and its tools.
False or misleading claims about the app or its features.

Language

The community is bilingual. You are welcome to write in English or Spanish, and the team answers in both. Please write in whichever language you are comfortable with, and keep messages clear so everyone can follow along.

Etiquette

Beyond the rules, a few courtesies make the space genuinely pleasant, and they complement the code of conduct:

Assume good faith. Most confusion is a misunderstanding, not an attack.
Disagree with the idea, never the person. Criticism is welcome when it is constructive and comes with a suggestion.
Say thanks when someone helps you, and pay it forward by answering others when you can.
Keep it public when it helps others; a question answered in the group helps the next person who searches for it.

Moderation

The groups are run by the Vzla.io team with active moderation to keep the environment orderly and productive. Administrators may remove messages that break the rules, mute or remove users who do not follow them, and post official announcements and surveys. Administrators’ decisions are final. If you disagree with one, raise it privately rather than in the group.

Reporting a problem or inappropriate conduct

If you see a message that breaks the rules or run into a problem, contact a group administrator or write to us.

Code of conduct — the behavior everyone agrees to.
Community terms and conditions — the rules of use for the community channels.
Community privacy policy — how we handle data shared in the community.

Updates to this guide

This guide may be revised as the community grows and its needs change. Any change will be announced through our official channels.

Contact

For anything about the community, write to us at community@vzla.io. For technical issues and bug reports, write to support@vzla.io.