Running Weekly Community Calls People Attend

A weekly community call is one of the simplest ways to keep a crypto community connected to the team. It gives members a regular moment to hear updates, ask questions and see the people behind the project. Many calls, though, shrink after a few weeks to the same six listeners and a team member reading a changelog.

Calls that keep their audience share a few habits: a predictable schedule, a clear format, real answers and a recap for people who missed it.

Pick a platform your members already use

Choose the platform where your community spends time. Discord stage channels suit communities centred on Discord. X Spaces reach people who follow the project on X but never joined the server. Telegram voice chats work for Telegram-first groups.

Stick with one platform for the regular call. Moving between them confuses people and splits the audience.

Choose a time and keep it

Consistency builds attendance. Pick a day and time and keep it for at least two months. If your community spans many time zones, consider:

• A time that overlaps with evenings in your two largest regions
• Alternating between two times every other week
• Recording the call and posting a written summary for everyone else

Announce the time in UTC and in a few major local times. Remind people a day before and an hour before.

Use a simple, repeatable format

A thirty to forty-five minute format works well:

Segment	Length	Purpose
Welcome and agenda	3 minutes	Set expectations
Product update	10 minutes	What shipped, what is next
Community spotlight	5 minutes	Highlight a contributor, guide or project
Questions	15 to 20 minutes	Answer submitted and live questions
Wrap up	2 minutes	Next steps and where to find the recap

Repeating the format helps members know what they will get and helps the team prepare quickly each week.

Collect questions in advance

Open a thread or form a day before the call for questions. This helps shy members participate, surfaces the most common concerns and gives the team time to prepare accurate answers. During the call, answer the most upvoted questions first, then take a few live ones.

If a question needs research, say so and commit to answering it in the recap. Following through on those promises builds more trust than a quick guess.

Answer honestly

Members can tell when answers dodge the question. If something is delayed, explain why. If you cannot share details, for example about a partnership that is not final, say that plainly. Avoid price talk and speculation about token value. Keep answers focused on the product and the plan.

Make it about the community too

Calls where only the team speaks feel like broadcasts. Invite contributors to present their work, feature a member project or guide, or bring in a guest from a partner project. Recognition on a live call means a lot to people, and it encourages others to contribute.

Follow up with a recap

Most members will miss most calls. Post a short written recap within a day:

• Key updates in three to five bullet points
• Answers to the main questions
• Links mentioned during the call
• The date and time of the next call

Pin the recap in your announcements channel and share it on X. Over time the recaps become a useful public record of what the project has done.

Measure what matters

Track live attendance, recording plays and recap views. Watch whether the number of questions submitted grows. A slow rise in questions usually means members feel heard.

If you feature a community project or member each week, a public spotlight can live beyond the call. Some communities keep a running list of featured members and projects, and many of those projects plant their own flag on the Proud Globe so listeners can find them later.