Guest
0

Bot testing with microtasks

Microtasks help quickly check a Telegram bot or another bot scenario: start, commands, buttons, messages, errors, delays and clarity for a new user.

Create a bot task Bots and games

Bot testing with microtasks: tasks and rewards

See what has already been posted and what workers are currently paid. This can help you set clear terms for your own task.

Create a bot task
0Active tasks
0Available completions
No available tasksPayment per completion

Activity in this area

See how many clients and workers were active and how many results were accepted during the last 30 days.

Last 30 days
0customers with open tasks
0accepted results
0workers with accepted work
Not enough data yetaverage payout per accepted result

Calculate the budget for Bot testing with microtasks

Set the reward for one completion and the number of results you need. You can carry these values directly into the creation form.

Price for you2 USD

The form validates your final price and available balance again before publication.

Create a task with this budget

Set the number of results and reward in advance

For testing, surveys, feedback, and data work, you can define how many results you need and how much you will pay for each accepted report.

Create a microtaskLearn about pay per result
When advertising is useful

Advertising is useful when you need reach and new visitors. It pays for impressions or visits, but it does not guarantee that a person completes a specific sequence of actions.

When microtasks are useful

Microtasks work well when you need a specific result: a form check, an answer, an app test, data verification, or another report completed to instructions.

They can work together

Test a page, form, or offer with a small number of workers first, fix the issues, and then run advertising.

Microtasks do not replace advertising. They are useful for small jobs that can be clearly described and reviewed by result.

Choose a ready example

Open a suitable option and add your link, instructions, number of completions, and reward.

What to check in a bot

Order bot testing: commands, responses, scenarios, errors, instruction clarity and a worker report.

Clear conditionsThe link, steps, deadline, and required report are visible before starting.
Reward shown in advanceWorkers see the amount before starting, and clients pay for accepted results.
Reports in one placeWorker text, links, and files arrive in the review section.
Ready task typesChoose the closest option and fill in only the conditions needed for your task.

What clients should know

When this task type is useful, what to include in the instructions, and how to review the result.

When to use itUse it when you need several small results: website or app checks, answers, scenario testing, or data work.
What to add to a taskA link, goal, step-by-step instructions, payment per accepted completion, deadline and proof format.
How to review resultsA worker submits text, a link, screenshot or file, and the customer accepts the result or sends it back for revision.
What you receiveA report for each completion: text, feedback, a link, screenshot, file, or another proof type defined in the task.

Popular microtask options

Choose a suitable job for your project or see which kinds of work are available to workers.

Test the first launchAsk a new user to review the welcome message, menu, prompts, and clarity of the first action.
Cover the key commandsList the required buttons, commands, and branches that should be tested in order.
Include edge casesUseful checks include empty input, repeated taps, invalid data, delays, and returning to a previous step.
Collect a reproducible reportRequest the device, error step, expected behavior, actual result, and a screenshot.

How to get a clear result

A microtask works better when the client describes the action, review criteria and report format in advance. This helps the worker complete the task without extra questions.

Clear instructionsAdd the link, goal, steps and the exact proof the worker should send.
Pay for accepted resultsThe worker is paid after review, while the client controls the report and proof.
Result reviewRequest a text report, link, screenshots or files to approve the work quickly.
Verifiable conditionsFor reviews and ratings, define the context, questions, and criteria for a detailed result in advance.
Beginner friendlyReady-made scenarios help create a task even if the user has never used microtasks before.
Budget controlEvery task has its own budget, result count, requests, statuses and remaining funds.

What you can order with microtasks

This section is useful for small tasks such as testing, surveys, registration, data work, Telegram tasks, reviews, comments, or a custom task.

Reviews and commentsCollect meaningful feedback, comments, and opinions through predefined questions.
Website or form checksAsk a user to follow a scenario, find an error, test registration or submit a request.
Surveys and researchCollect answers, opinions and mini research from workers using prepared questions.
Telegram and botsCheck channels, bots, message flows, subscriptions and how clear the actions are.
Data and publishingCreate tasks for data checks, form filling, posting or a short report.
Custom taskIf there is no ready scenario, choose the free format and describe the needed action.

How a client gets results

Choose a task type, describe the result, fund the budget, and review worker reports.

1Choose a scenarioChoose a suitable task type and open the creation form.
2Describe the resultAdd the link, steps, payment per accepted result and proof format.
3Launch the taskFund the task budget so workers can start completing it.
4Review reportsAccept correct results or return a report for revision with a clear note.

Tasks you can launch quickly

Choose a similar example and adapt the instructions, reward, and proof requirements to your task.

Review the bot onboardingA new user starts the bot, follows the prompts, and identifies unclear steps.
Test an order flowThe worker follows the button sequence to the final message and reports where the flow becomes difficult.
Verify notificationsThe worker performs a specified action and checks whether the correct message arrives at the right time.
Test an error recovery pathThe worker enters invalid data and checks whether the bot helps them return to a working step.

Bot tasks

Choose a task and check which bot commands, buttons, or branches need to be tested.

All tasks
No matching tasks yet

Change the selected action, category, or search query. New tasks appear automatically.

Other task types

If this option is not right for you, choose another category or return to the full task list.

Order microtask completion onlineCreate DitWork microtasks: define the action, reward, number of results, instructions and review worker reports.Microtasks for businessUse DitWork microtasks to check a website, app, form, business listing, text, survey or custom scenario with payment for accepted results.Microtasks with payment per accepted resultCreate microtasks with payment per accepted result: exact action quantity, fixed price, worker report and controlled budget.Microtask pricingUnderstand microtask pricing: a client sets payment per accepted completion, number of results and task budget.Microtask examplesDitWork microtask examples: reviews, testing, registrations, surveys, Telegram, bots, data entry, posting and custom tasks.DitWork microtask platformOn DitWork, clients post small tasks with payment shown in advance, while workers choose suitable work and submit results for review.
Bots, games, and scenariosTesting bots, game actions, and short step-by-step flows.Social content feedbackClosed evaluation of publications, design, and content plan.Content feedbackReview the clarity of an article, page, description, script, or instruction.Website testingTest forms, pages, navigation, and user journeys on real devices.Surveys and researchShort surveys, interviews, hypothesis checks, and structured responses.Data workTag, check, transfer, and structure small amounts of open data.

Related microtask directions

Compare related directions to choose the right scenario, proof format, and expected result.

Microtasks for TelegramCreate Telegram tasks: test a bot, channel, scenario, instruction or submit a report for a completed action.User feedbackGet user feedback through DitWork microtasks: website, product, content, form, app or service card checks.Order microtask completion onlineCreate DitWork microtasks: define the action, reward, number of results, instructions and review worker reports.Microtasks for businessUse DitWork microtasks to check a website, app, form, business listing, text, survey or custom scenario with payment for accepted results.Microtasks with payment per accepted resultCreate microtasks with payment per accepted result: exact action quantity, fixed price, worker report and controlled budget.Microtask pricingUnderstand microtask pricing: a client sets payment per accepted completion, number of results and task budget.Microtask examplesDitWork microtask examples: reviews, testing, registrations, surveys, Telegram, bots, data entry, posting and custom tasks.How microtasks workHow DitWork microtasks work step by step: a client creates a task, a worker follows the instruction, the result is reviewed and paid after approval.

Questions about bot testing

What should I provide for bot testing?

Add the bot link or username, start command, scenario, expected replies, and report format.

How many users are needed for an initial test?

A small number of independent runs is enough for an initial check, and the volume can be increased later.

What makes a useful bug report?

A useful report includes the device, action sequence, actual result, and a screenshot of the problem.

Can I retest the bot after fixes?

Yes. Create a new task with the updated scenario and list the issues that should be checked again.