Русский
Turkish
Português (Brasil)
한국어
العربية
Español
ไทย
Tiếng Việt
Français
中文
Deutsch
Bahasa Indonesia
Italiano
日本語
Polski
Українська
فارسیFree service requests
Choose a request category and read its conditions before applying. Our team reviews each request before deciding whether it can be fulfilled.
TikTok
YouTube
X (Twitter)
Spotify
Telegram
Twitch
Brawl Stars
PUBG Mobile
Start with the exact outcome you want reviewed
The request directory groups categories by platform so you can identify an appropriate public destination and proposed scope. Choose the service by its meaning, not simply by the platform name. Followers concern an account relationship; likes concern a reaction; views concern exposure to content; written comments need a specific conversation context.
A category listing does not mean a campaign is currently open or that every proposed request can be fulfilled. Read the page for the chosen category and the conditions displayed with its form. The useful first step is to make the request understandable before considering quantity.
Match the category to its destination
An account-level request usually needs a public profile or channel link. A request about one post, video, message or track needs that item’s link. A story or live broadcast adds an availability problem because the content may expire or end before review. Game-related requests use the player reference specified by the form.
Check a copied destination yourself. Similar names, repeated thumbnails and several accounts managed by one team can make it easy to choose the wrong reference. Do not replace a public link with an editing page, private invitation, password or account token. A reviewer needs an identifiable target, not access to your account.
Keep metric definitions separate
Several categories can describe the same piece of content without measuring the same thing. A share does not equal a unique viewer, a follower does not equal a customer, and a requested view does not define viewing duration. Spotify plays and monthly listeners also differ because actions and a rolling audience measure are not interchangeable.
Some categories need additional clarification before any scope could be agreed. Watch hours concern duration; a live category can depend on timing; a chatbot request needs a proposed function; game currency is not an automatically generated balance. The category-specific guides explain these distinctions without converting them into delivery claims.
Choose a clear reference
Use the destination type shown by the selected request page.
| Request focus | Reference to check | Common confusion |
|---|---|---|
| Account or channel | The intended public profile or channel | An individual post from that account. |
| One content item | The exact public post, video, message or track | A homepage containing several items. |
| Story or live content | The available public destination | Assuming the request reserves a time window. |
| Game benefit | The exact player ID or tag | A display name, email or login credential. |
Make one request that is easy to discuss
Use an integer quantity from 1 to 100 and keep the category, target and date in your own notes. Complete the listed community tasks yourself and confirm only the actions you actually completed. Opening a task link is not automatic verification of a follow, subscription or membership.
When a submission is saved, keep its request ID. That ID is a reference to a stored proposal awaiting manual review. It is not an approved order, a reserved allocation or evidence that a social metric or game balance changed. A reviewer may decline the request or adjust its quantity or scope.
Plan around confirmed information
If timing is essential, do not use a pending request as committed capacity for an event or client campaign. Keep the underlying content useful on its own: a clear announcement, accurate profile, readable description and appropriate public destination are decisions you can control while a request is being considered.
The nearby form explains the current account, privacy and availability conditions. Submit only the permitted details and keep credentials private. If your immediate task is to prepare text, calculate an explicit scenario or inspect a limited public snapshot, the separate free-tools directory may provide a more direct next step without a manual service request.
Frequently asked questions
What is a free service request?
It is a limited application for a listed platform activity when its campaign is open. It is not an instant order, a reservation or a guarantee of approval, quantity, timing or delivery.
What is the maximum request quantity?
The current form allows up to 100 units. A reviewer can approve less, postpone a decision or decline a request when the target or campaign conditions do not fit.
Do free service pages ask for a social password?
No. Use the requested public profile, post, video, channel, track, live destination or player ID. Keep passwords, codes, cookies, payment details and private account information out of every form.
Why are there separate pages for each platform activity?
A follower request, post like, video view, live destination and player benefit use different targets and measurements. Separate pages make the required destination and limitations clear before submission.
When should I use a paid service instead?
Use the paid catalogue when you need to compare current prices, minimums, maximums and defined service conditions. Read the selected service description before placing an order.