# 6.4 Strategies to keep people involved

It’s easy to get people to help short-term, but harder to get long-term commitment. In [TWB Voice](#user-content-fn-1)[^1], we used the following strategies:

* **Recognition as well as rewards:** Acknowledging people’s help in public, and not just at payout stages. Each day and even week, we send out a message about our data collection milestones, and set targets for the day/week. This gives contributors something to look forward to.
* **The chance to progress:** Allowing active contributors to move up to the role of “trusted linguists". This means they can do validation and not just recording. People who contribute more and reach certain thresholds become trusted linguists. This motivates them to do more.
* **Transparent communication:** Regular updates about the impact of the project, progress towards goals, and future opportunities.
* **Flexible task structures:** Allowing contributors to move between recording and validation to help prevent tiredness. You need to be careful with this and perhaps check on the output of certain individuals.&#x20;

[^1]: **TWB Voice:** A platform for collecting voice data. It was developed by CLEAR Global, who also own it. Users can make voice recordings to help with active data collection projects in TWB Voice by [signing up to the TWB Community](https://translatorswithoutborders.org/join-the-twb-community/). The main goal of TWB Voice is to help to develop voice technology for speakers of marginalized languages. For example, by creating the voice datasets that are needed to build language models for TTS and ASR.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://twbvoiceplaybook.clearglobal.org/6.-community-engagement/6.4-strategies-to-keep-people-involved.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
