Galxe and Zealy quests, planned around your community

What should people carry away from a Galxe or Zealy quest?

A strong quest gives participants a clear reason to act and a useful next step afterward. Start by naming one audience and one outcome you want the activity to support. That keeps the campaign understandable for people and manageable for your team.

A useful outcome might be learning how a product works, trying a feature, or sharing structured feedback. Each calls for a different task and different evidence. A social action by itself may show that someone clicked or posted, but it may not tell you whether they understood the project.

Write a short brief before opening either platform. Include the audience, the action you hope to encourage, how you will check completion, and where participants go next. Keep those choices close to your wider token launch checklist, so the quest supports the same message as the rest of the launch.

Then read the brief as if you were new to the project. Can you tell what to do, where to do it, and what happens after? If any answer is unclear, simplify the goal before adding more tasks. A focused campaign is easier to explain, support, and review than a long menu of loosely related actions.

Make the first visit feel easy to follow

A participant should be able to understand the campaign without private instructions from your team. Picture a volunteer who runs a fan group, checking a quest the morning after a listing announcement. They want to share a useful activity with members. They also need to know what each task asks and how rewards work. We would help turn that moment into a short route, with one clear opening task and a visible place to ask questions.

The route might begin with a plain introduction. It can continue with a task connected to the project. End with a clear next step in the community. Keep the wording friendly and specific. “Read this guide and answer one question” gives a participant more direction than “learn about the project.”

Before building, walk through the route on a fresh account or device where practical. Check that links open, instructions match the destination, and the confirmation makes sense. Ask someone outside the campaign team to try it too. They can point out missing context that feels obvious to people who wrote the tasks.

This first-visit check also helps you decide whether a community channel needs a pinned explanation or a named moderator. If participants will have questions after finishing, connect the quest to a Telegram community guide and prepare a short welcome message there.

Build each task around one action

A task works best when its action, destination, and proof all fit together. Keep one main action in each instruction, then make the completion rule visible before someone starts. That way, participants know what counts, and reviewers share the same standard.

Use this checklist while drafting:

• Action: Start with a clear verb and name what the participant should do.
• Destination: Link to the exact page, community, or product step.
• Proof: State what evidence you will accept and how it is checked.
• Help: Tell people where to go if a link or submission does not work.
• Next step: Explain what happens after this task is complete.

For example, imagine a task asking people to try a demo and share one point of feedback. The instruction can name the demo, give a short prompt, and say whether a written response will be reviewed. It should also tell participants where to submit that response. The team can then review feedback against the same prompt rather than guessing what each person intended.

Match the amount of review to the importance of the task. A simple learning check may need a light review. A contribution that could inform a product decision deserves a closer read. Before publishing, test each task’s links and proof instructions, and make sure the support route is active.

Put eligibility and rewards in plain sight

Participants should see the eligibility rules and reward terms before they invest time. State which actions qualify, what counts as valid proof, and how your team will handle incomplete or unclear entries. Use the same wording on the campaign page, in community posts, and in support replies.

A simple planning sequence helps keep the rules aligned:

1. Decide which actions matter and which ones are optional.
2. Match each action to evidence your team can review consistently.
3. Set eligibility conditions that fit the value and availability of the reward.
4. Name who answers questions and who handles reward delivery.
5. Read the final terms beside the task instructions before publishing.

Choose a reward your project can actually provide. It could be a credential, access, recognition, or another defined benefit. If availability is limited, describe the selection method clearly. Avoid suggesting that completing a quest creates an investment return or promises future benefits.

For token-related rewards, have the project review the wording and delivery plan before publication. Make it clear whether the quest is one activity or part of a separately explained eligibility process. If you are comparing support options, our quest campaign pricing guide can help you understand what to ask before planning the work.

Keep Galxe and Zealy decisions in view

Your team can set the brief, task text, evidence rules, reward terms, support plan, and review process. Galxe and Zealy control their own policies, available setup options, moderation decisions, and campaign display. Neither a particular placement nor a participation total can be promised. Check current platform information before relying on a feature or publishing a rule tied to it.

That limit is a reason to keep your campaign plan practical, not a reason to make it vague. Save the final task text and reward terms. Name the person who can update them. Check the live participant route before sharing it widely. If the platform changes an available option, pause the affected task and update participants before asking them to continue.

Decide in advance how your team will handle an unclear submission. A short internal note can record what was checked and why a decision was made. That helps the team answer questions in a steady way, especially when several people review entries.

If the quest is part of a wider community plan, keep its message consistent with your community growth and engagement plan. A small number of well-explained tasks is easier to support than a crowded campaign with rules that shift as it runs.

Close the loop after the campaign

A useful closeout connects what people did with what the project should do next. Review task activity beside the original goal, and separate raw submissions from entries that passed your stated checks. This gives your team a clearer picture than a single completion total.

Keep the review simple enough to use. Note which instructions caused questions, where participants stopped, what evidence was accepted, and whether people took the next step you planned. If the campaign included a learning task, for example, look at the answers as well as the number submitted. Record useful themes without treating every response as a product decision.

At Brand Community, our first review brings task instructions, proof rules, reward wording, and the participant route together. We also check who will answer questions and who owns reward delivery before the campaign goes live. A one-page note after the campaign can then capture what the team learned and what it wants to change next time.

For a managed campaign, quest campaign support can help with planning, task checks, and reporting. To prepare, send us your campaign goal, audience, draft tasks, reward details, and preferred platform. We’ll review those pieces together and suggest a clear next step.

How it works

1. Name the useful actionWrite down who the campaign is for and what action would make the experience worthwhile. Choose one main goal to guide the tasks.
2. Map the participant routeSketch a 3-step journey from the first instruction to the next community action. Test the route as someone new to the project.
3. Write tasks and proof rulesGive each task one action, one destination, and a clear completion rule. Match the review to the task’s importance.
4. Agree on eligibility and rewardsPublish the conditions before launch, and name one owner for participant questions and reward delivery.
5. Check, run, and learnReview the live participant route, answer questions, and compare reviewed activity with the goal you set at the start.