
Describe the scenario
Explain the situation, the roles and what the user wants to achieve. For bot testing, add a link to your bot and a list of things to try.
Scenarios and roles
Link to your bot for testing
Example of a good dialogue
Get real dialogues, the many ways people ask for the same thing and live testing of your bot from everyday users in the countries and languages you choose.
200+
Countries
13,487
Tasks completed
195,000+
Registered workers
~4 Hours
Avg time to results
Launch a dialogue or bot testing task yourself and start receiving real conversations, without long negotiations.

Explain the situation, the roles and what the user wants to achieve. For bot testing, add a link to your bot and a list of things to try.

Select the countries your contributors should come from and the language they should use. See how real users in each market talk to your assistant.

Your task becomes available to workers in the selected countries. They write dialogues, record voice requests or talk to your bot and report what happened.

Read or listen to every submission, approve the ones that follow your scenario and reject the rest. Keep your dataset clean from the start.
Set up a task for the exact conversations your assistant needs. Contributors follow your scenario and use their own words.
Give contributors a goal, such as "cancel my order", and they write or say how they would ask for it. Teach your assistant to understand real wording, not just one phrase.

Contributors write full conversations where the user clarifies, changes their mind or asks again. Train assistants to keep context across several turns.

Workers play a customer with a problem and write or record the conversation with a support agent. Use them to train and test support bots.

Share a link to your chatbot or voice assistant. Contributors try the tasks you list and report where the bot failed, misunderstood or gave a wrong answer.

Contributors record themselves asking an assistant for help, the way they would at home or in the car. Get real accents, pauses and phrasing.

Native speakers write requests with everyday slang, mixed languages and regional expressions. Make your assistant sound local, not translated.

Ask contributors to name what the user wanted next to every dialogue. You get conversations with labels, ready for training.
Your setup
Choose Text or Audio collection, describe the scenario and roles, and ask workers to name the user's goal at the end.
Your view
Each submission arrives with the dialogue or recording and the intent label, ready to review and approve.
You set the pay per task. Adjust the numbers to see what your project will cost, with the 15% platform fee included.
You set the pay for each task, starting from $0.10, plus a 15% platform fee. Long dialogues and bot testing usually need a higher rate than intent variations. A campaign starts from $0.30.
Intent variations, multi-turn dialogues, support role-plays, live bot testing, voice requests and local phrasing. You can ask contributors to name the user's goal next to every dialogue, so conversations arrive with intent labels.
Yes. Add a link to your bot and a list of things to try in the instructions. Workers talk to it and report failures, wrong answers and their rating of the conversation.
Yes. Create a text collection task for written dialogues and an audio collection task for spoken requests, or ask our team to set up a combined workflow.
Any language spoken by workers in the countries you select. Native speakers can use everyday slang, regional expressions and mixed languages like Hinglish, so your assistant sounds local, not translated.
Ask contributors to use fictional names, addresses and numbers in role-plays and tests, and not to share real personal data with your bot. Reject any submission that contains it.
You read or listen to every submission and approve only dialogues that follow your scenario. For larger projects, launch a separate task where other workers check dialogues and labels.