How to test a website or Telegram bot with real people in 2026

In 2026, automated tests and emulators cover regression, but they can't see what a real user stumbles on: broken layout, a scenario that dead-ends, a button that doesn't respond in Telegram. In this guide we'll look at how to test a website or Telegram bot with real people through the task marketplace Zelenka.Work — a micro-task platform by Lolzteam. The executor goes through your steps and sends a report with a screenshot.

Why real people and not bots

• Different devices. The same screen breaks in different ways on a phone, in Chrome and in Safari.
• Real Telegram. The bot is checked from live accounts, not from a sandbox.
• A report you can reproduce. A screenshot, the browser or Telegram version, and the steps leading to the error.
• Payment for results. Funds are reserved and charged only for accepted reports.

What you can send for checking

• a website and a landing page;
• a web app: sign-up, payment, account area;
• a Telegram bot: commands, buttons, payment, sign-up flow.

This is a search for interface and scenario bugs. The task is not about finding vulnerabilities and is not a bug bounty program: the executor goes through the steps you described and records where the product behaves incorrectly.

There is no separate category for bots on the platform. Both websites and Telegram bots are posted under one subtype — "Website and app testing". You put the bot link and commands in the brief.

Step-by-step guide: finding bugs through Zelenka.Work

1. Sign up on the platform and top up your balance — the money will go toward paying executors.
2. Click "Post a task" in the side menu.
3. Choose the type "Work and services" and the subtype "Website and app testing".
4. Describe the brief: a link to the site or an @bot, 3–7 scenarios, what counts as a bug and what to attach to the report — screenshot, browser and OS (or Telegram version) and the steps to reproduce the error.
5. Set the price per completion and the number of executors, then launch the task.
6. Accept reports: approve the suitable ones, reject empty ones or ones that don't follow the brief with a comment. Disputed cases are resolved by the platform's arbitration.

Post a testing task Category "Website and app testing"

How to write a brief so the bugs get found

• Give different scenarios to different people, rather than the same checklist to everyone at once.
• Write what should happen at each step and what to send if something breaks.
• For the bot, list the commands and expected responses: /start, menu buttons, payment, error message.
• Ask them to specify the device: phone or computer, browser, and for the bot — Android, iOS or Telegram Desktop.

How much it costs and how quickly

You set the price yourself: the price per check is multiplied by the number of executors. The more specific the scenarios and the higher the payment, the faster the task gets picked up. A small package of several checks is usually completed within a day.

Frequently asked questions

Are real people or bots doing the testing?

Real people. The executor goes through the scenario themselves and attaches proof, and you accept or reject the report.

Can I test only a Telegram bot?

Yes. Specify the @bot, commands and buttons in the brief and choose the subtype "Website and app testing".

What if the report is empty or has no screenshot?

Reject it with a comment — no payment will be charged for such a report.

Is this a bug bounty?

No. You pay a fixed price for going through the scenario and reporting an interface bug, not a reward for a vulnerability.

Ready to send your product for checking?

Post a task — real people will go through the scenarios and send you where the site or bot breaks.

Post a testing task Browse all tasks