A weekly burst or a monthly rhythm
Weekly and monthly bundles serve different community moments. A weekly plan can focus on a launch announcement or event. Monthly support gives your team a repeating rhythm for moderation, activity, and check-ins.
We begin with the practical shape of your week: which channels need coverage, what your team plans to announce, and who can answer questions. That gives us a useful basis for setting moderator hours and preparing activation around real project updates. If you are still shaping the wider launch, token launch and growth can help connect this work to the rest of your plan.
| Format | A good fit when | Planning starts with |
|---|---|---|
| Weekly | A defined event or launch moment is near | Channel hours, approved prompts, and a handover point |
| Monthly | You need recurring community care | Regular check-ins, repeated questions, and updated guidance |
For either format, we agree what moderators can answer and what needs your team. We also decide how the work will be shared back with you. A simple plan avoids asking moderators to fill gaps in project information. It gives your members a clearer place to bring questions and gives your team a manageable way to respond.
Start with the place your members already use
Picture the marketing lead of a wallet app, deciding which channel to start with. They have a product update ready, but the team is unsure where members will need the most help. We would review the active conversations, existing rules, and team availability before recommending a first channel.
That choice is about readiness, not a platform ranking. Telegram may suit a team whose members already gather there for direct updates. Discord may fit a community that needs several distinct spaces and clear channel roles. If both matter, we agree separate responsibilities for each rather than copying one set of instructions across them.
We use a channel checklist at kickoff: active links, community rules, approved project information, planned announcements, and escalation contacts. It helps us spot missing answers before moderators begin. For broader audience work, compare this service with community growth and engagement; this bundle focuses on activation and moderator care, not every growth activity.
Say your wallet team has a product question expected after an announcement. We can prepare moderators to share the approved resource, keep replies respectful, and pass anything unresolved to the named contact. That way, members can take part without moderators speaking beyond their role.
How can prompts invite replies without outrunning the facts?
Activation gives members a reason to join a conversation; moderation helps keep that conversation clear and welcoming. We plan prompts around updates your team has approved, then prepare moderators for the replies those prompts may invite.
Before a prompt goes live
We check the source material, official links, community rules, and any topics that need a team answer. Your team names an escalation contact and confirms which statements moderators may repeat. We also note what should stay private or wait for approval.
While members respond
Moderators can direct people to official information, answer routine questions within the agreed guidance, and flag sensitive or unanswered issues. They keep the channel aligned with your rules and pass decisions back to your team. In a small example, suppose members ask whether a planned feature is already available. A moderator can share the confirmed status and route any new product question to the right person.
When your team needs a wider plan
This bundle can sit beside a token launch plan, but it does not replace product support or launch communications. If your community activity needs to connect with a TGE, see token launch marketing. For support after the launch moment, post-launch support may be a useful next step.
The work moves through five clear steps
A simple sequence helps your team and moderators know what happens next. We use the kickoff to agree the channel plan, then keep the work visible through handover and review.
- Share the channel context. Send active Telegram or Discord links, current rules, project materials, and your next milestone. Tell us who can approve official answers.
- Agree the bundle. We set the weekly or monthly period, channels, moderator responsibilities, and coverage expectations. We also record where team approval is needed.
- Prepare the guidance. We review approved information and write down how to handle routine questions, sensitive topics, and open requests.
- Run the planned activity. We coordinate approved prompts and moderate within the agreed plan. Questions that need a project decision go to your named contact.
- Review and hand over. We share a written note with completed work, recurring questions, notable discussions, and open items.
We can set two useful check-in points in the plan: one before activity begins and another at the agreed review. The timing follows your bundle period and calendar. If your team already has a working process, we can use it; otherwise, we help make the handoff easy to follow.
Give moderators room to help and clear lines to follow
Good community care starts with clear roles. Your team supplies accurate project information and decides who can approve new answers. We handle the agreed activation and moderator work, and bring questions back when they need a project decision.
Before the first week, prepare three things: current official links, rules moderators can apply, and a person available for escalations. It also helps to list recurring questions and any topics moderators should not address on the project’s behalf. We can turn that material into practical guidance and note gaps for your team to resolve.
Telegram and Discord control their platform features and enforcement. Members decide how they respond. We commit to the agreed work, not a particular participation level. A written activity note lets you see what was done and what still needs your attention.
To get started, send Brand Community your channels, next milestone, current rules, and the hours your team can respond. We’ll review the information, identify decisions still needed, and propose a weekly or monthly plan for you to approve.
How it works
- Share the channel contextSend your active Telegram or Discord links, rules, project materials, and next milestone. Name the person who can approve official answers.
- Agree the bundleWe confirm the period, channels, moderator responsibilities, activation needs, and escalation route before work begins.
- Prepare moderator guidanceWe review approved information and note how moderators should handle routine questions, sensitive issues, and open requests.
- Run the planned activityWe coordinate approved prompts and moderate within the agreed plan, raising questions that need a project decision.
- Review and hand overWe share a written note of completed work, recurring themes, and open items for your team.
Frequently asked questions
What should I send before the first moderator shift?
Share your official project links, current channel rules, planned announcements, and the name of someone who can approve answers. A short list of topics moderators should not address is useful too. We review those materials at kickoff and flag missing information before the agreed coverage begins.
Can one bundle cover Telegram and Discord together?
Yes, if we define the responsibilities for each channel separately. Telegram and Discord may have different rules, roles, and escalation contacts, so we confirm those details rather than treating them as one space. For example, your team might use one channel for announcements and another for longer member discussions.
How do I know whether weekly or monthly support fits?
Weekly support is a practical choice for a specific launch moment or event. Monthly support suits ongoing moderation and recurring check-ins. We look at your calendar, channel needs, and team availability before recommending a format, so the plan fits the work you actually expect.
Can moderators answer questions about our product or token?
They can share information your team has approved and point members to official resources. A new product claim, token detail, or technical judgment should go to your named contact. We record that route before activity begins, so moderators know when to help directly and when to ask your team.
What can you promise for Telegram or Discord activity?
We can commit to the activation and moderation work agreed for your bundle. Telegram and Discord make their own decisions about platform features and enforcement, while members choose whether to join a conversation. For example, we can prepare an approved prompt and moderate its replies, but we cannot decide how members respond.
What will I see in the review note?
You’ll receive a written account of completed work, recurring questions, notable discussion points, and items awaiting a project answer. We agree when to share it and who should receive it. That gives your team a usable follow-up list instead of a vague account of channel activity.
Tell us about your project
Answer four quick questions and a manager will send you a plan, timing and a price range within the hour. Everything stays confidential.
Loading the form…