Frequently asked questions.

An SMM panel is an account-based workspace for choosing social media services and tracking orders. On IamProvider, you select a service, review its description, enter the requested target and quantity, and confirm the charge in your account.

Create an account or sign in, review the available services and add funds using a method shown in your account. Choose a service, enter the required target and quantity, then review the final charge before submitting. Save the order ID from your order history.

Yes. You can explore services and estimate a charge before signing in, but the order is reviewed and placed through your IamProvider account. Selecting a service on a public page does not submit an order or charge a payment method.

Do not enter a social media password, recovery code or two-factor authentication code in an order. Provide only the profile, content link, username or other target requested by the selected service. Your IamProvider password is used only to access your panel account.

Compare the same metric and target type, then the exact service ID, quantity limits, audience specification, start/delivery notes and refill conditions. For example, a one-off post service and an automatic future-post service are different purchases. Labels such as premium, real or non-drop do not replace these details. Ask support before ordering if a condition essential to your campaign is missing.

No. Your location and the audience coverage of a service are different. A country guide does not make every option country-targeted. Rely only on geography or language conditions explicitly included in the selected description.

For a rate per 1,000, multiply the displayed rate by your quantity and divide by 1,000. For example, a rate of $2 per 1,000 gives a $0.50 estimate for 250 units. Package, subscription or special service types can use different rules. Review the final charge in the native order form.

Open Add funds in your account to see the methods currently available. Review the selected method, currency, minimum amount and final payment details there. A country page does not guarantee a particular bank, wallet or local settlement method.

Use the currency displayed in your account and on the final order form. Do not assume the country page changes billing currency. If a payment provider applies a conversion or fee, review its final information before continuing.

Check the payment instructions and current status first. Keep the relevant transaction reference and contact support with a clear description if needed. Do not send passwords or full payment-card details. Avoid repeating a payment merely because the balance has not refreshed immediately.

The estimate helps you compare the selected quantity and rate. The current service availability and final charge on the native order form are the details to review before confirming. Local design previews use labelled sample data and do not establish live prices.

Use exactly the target format requested by the selected service. A profile, page, post, video and channel are different assets. Some services request a username or invitation instead of a URL. Check the target before submission and do not put unrelated instructions into the link field.

Where the selected service requires public access, keep the profile or content accessible while it runs. The published terms exclude adjustments for certain private, incorrect or changed targets. Resolve visibility and link problems before submitting; do not change the username, delete the post or hide it during delivery.

Use a quantity within the current minimum and maximum for the selected service. Those limits describe an accepted order, not a recommended campaign size or retention promise. Presets are shortcuts. A package, custom-comment service or subscription can use different quantity rules, so confirm the actual form fields and final charge.

Read the start and delivery notes for the exact service ID. Catalogue average times describe previous delivery and are not guaranteed deadlines. Use your order history to follow the current status. A public estimate does not reserve a delivery slot.

Wait for the existing order on a target to finish before ordering that target again, in line with the published service terms. Overlapping orders can use the same starting count and make delivery or refill assessment unreliable. Keep a separate record for each order and resolve an unfinished one through its status or support instead of duplicating it.

Find the order in your history and note its order ID. Contact support with that ID and a clear explanation of what you are seeing. Include relevant target details when needed; never send social media passwords or authentication codes.

No. Refill is available only for services that state it, and eligible drops must meet the original order conditions and request window. It is a replacement process, not permanent retention or an automatic refund. Check the refill action and its result; a service marked no refill does not include later replacement.

Only where the service and current order allow it. Use the available action or ask support with the order ID, then follow the recorded result. A submitted cancellation request does not confirm that work has stopped. If cancellation is essential to your plan, check the conditions before placing the order.

The published terms provide automatic adjustment of unused amounts for qualifying partial or canceled orders, with exclusions including private targets and incorrect input. Check the order charge and account balance record. Loaded balance is generally non-refundable under the terms, subject to their stated exceptions; an order adjustment is not automatically a reversal to your original payment method.

No. You can manage your own orders through an IamProvider account. Agencies and resellers can also organise client work, but should keep separate target and order records. You do not need to operate a separate panel to start comparing services.

Open the API documentation linked on this site. It covers POST/JSON requests for services, supported order types, order status, balance and eligible refill or cancellation actions. Use your own account credentials and keep the API key on your server, out of browser code, public logs and screenshots.

API orders still use the selected service’s current target format, type, quantity rules, price and conditions. Default orders, custom comments and subscriptions need different fields. Save the returned order ID and inspect errors. If submission times out, resolve whether an order was created before retrying; a network error does not prove rejection.

Maintain a separate record for each target, service ID, quantity and resulting order ID. Keep your client pricing and business reporting separate from the panel charge. Recheck current conditions before repeating a previous service selection.

No. Free-service pages describe requests with their own eligibility and conditions. Read the particular page before applying. A request or successful form submission should not be treated as confirmation that a paid order has been placed.

No. A free request can be submitted only when its campaign and conditions allow it. Completing tasks or sending the form is separate from manual approval and fulfillment. Keep the request reference or status information provided on that page; do not treat a waiting screen or local demonstration as confirmed delivery.

No social media password, account token or authentication code should be supplied. Use only the input needed for the task: a text draft for a text tool, or a supported public username/link for a lookup. Browser utilities and public-data lookups have different data requirements; read the method and limitations on the chosen tool page.

No. A tool result, profile lookup or estimate serves its stated purpose and does not guarantee the outcome of a service order. Read the tool’s limitations and review the selected paid service separately before ordering.

An Instagram profile and one of its posts are separate targets. Decide whether you are comparing an account-level service or an individual content service. Reels, Stories and automatic options can have additional requirements.

Check whether a Story must still be active, whether a profile must remain public and whether the service requests a username rather than a full URL. A profile follower count does not describe the audience’s interest in any particular post.

Compare equivalent actions: one post’s likes, one Reel’s views and profile followers have different targets. Check whether an automatic or old-post option covers multiple uploads and how its quantity is defined. Read the rate unit and final total for the selected scope instead of assuming every Instagram rate buys the same package.

A channel subscription and a video view measure different things. Compare services for the exact target type and read any video-length or format requirements. A Shorts link is not interchangeable with a channel link.

If your goal involves watch time or monetisation, do not infer eligibility from a view quantity. Platform rules and your own channel analytics remain separate from a service order. Check current service descriptions instead of assuming a result from the label.

A subscriber, a video view and a like measure different actions. Choose a channel or specific video first, then compare supported format, audience specification, quantity and delivery notes. A price for views does not by itself buy watch hours, monetisation eligibility or likes on the video.

A TikTok profile can contain many videos, but a standard video order concerns the specific URL requested by the service. Identify that video before comparing rates. Live and automatic options may use different inputs.

Check whether the target must remain public and whether the option covers existing or future posts. A service for a published clip does not automatically monitor the account’s next uploads. Keep separate content targets in separate order records.

Compare the same target and action: profile followers, video views, comments or a live-session service. For live options, check duration and start conditions; for standard video options, check the exact upload. Do not compare a time-based live service with a per-quantity video order as if their units matched.

Facebook pages, profiles, posts and videos use different target types. Start with the asset you want to order for, then compare the matching category. A page-like service should not be selected for an individual post.

Review the exact reaction or metric in the service name and description. Public access and target stability may be required. Do not assume a profile, page or group accepts the same address format as another service.

First distinguish page likes, page followers, profile followers and post reactions. They concern different assets or actions. For reactions, check any supported reaction type; for a video, check format and access requirements. Compare equivalent specifications and the final charge for your quantity.

Choose between account-level and post-level activity before comparing X services. A profile address identifies an account; a post address identifies one published item. Service descriptions may still use the name Twitter.

Check whether the requested metric is a repost, like, reply or view and follow the exact target instructions. Similar-looking links or quoted posts can identify different content. Record the specific post associated with each order.

A repost, like, reply, view, profile click and link click are different X actions. Compare the same action and target before rates. A view quantity does not include a matching number of clicks to your website. Record the selected post or profile alongside its service ID and total charge.

A SoundCloud profile and a track have different metrics and input formats. Choose the release or account you intend to order for before comparing rates. Playlist support must be stated by the service.

Do not combine play counts with unique listeners or royalties. Track availability and service conditions matter independently. Keep the target link stable and use your own artist analytics to evaluate listener behaviour.

Choose whether the order concerns a track play, track interaction or profile follow. Check whether a playlist is supported and how quantity is allocated if it is. Repeated plays do not establish the same number of unique listeners or royalties, so compare the stated metric rather than the size of a number alone.

Spotify services may refer to different music assets and measurements. Read whether the option requests a track link, artist link or another supported target. A service name alone does not establish the input format.

A delivered count does not establish unique listeners, royalties, editorial playlist placement or platform eligibility. Review the conditions and platform requirements for your intended use. Do not infer a commercial result from the order quantity.

Artist followers, track plays, listeners and saves are different measurements. Check the exact target and how the selected service defines its quantity and delivery period. A plays rate should not be presented as a price for royalties, unique fans or playlist placement.

Telegram members and post views concern different targets. Identify whether you are ordering for a channel, a supported group or one post. Check whether the service requires a public address or another specific format.

Check whether the service accepts a public channel, group invite or a specific post, and whether the link remains usable. Joining restrictions or an expired invite can prevent the intended action. A permitted invite is a target link, not permission to disclose an account password, login code or session token.

Member services concern a supported community; post-view and reaction services concern a message. Compare the same target type and check public/invite requirements before rates. An order for one message does not automatically distribute its quantity across the channel’s post history.

LinkedIn profiles, company pages and posts are distinct assets. Compare services only after identifying the exact target. A company follower service may not accept a personal profile or an individual post URL.

A follower or interaction count does not establish professional endorsement, a qualified lead or hiring interest. Keep your own business outcomes separate from ordered metrics and avoid describing purchased quantities as testimonials.

Identify whether the service accepts a company page, personal profile or post. Followers and post interactions have different scope. Compare equivalent target and metric conditions; a purchased count is not a qualified lead, connection request or professional endorsement.

A Twitch channel follower service and a live-stream service can have different timing and target requirements. Read whether the channel needs to be live and whether the selected option is appropriate for the intended stream.

Do not treat a listed average time as a reservation for a particular broadcast. Review start conditions before ordering around a fixed schedule. An ordered metric does not establish affiliate, partner or monetisation eligibility.

Channel follows, clip/video views and live viewing have different scope. For a live service, compare the duration, timing and target requirements alongside the price. A follower rate does not buy a paid subscription or establish Affiliate/Partner eligibility.

Discord member services depend on the target invitation and any conditions stated in the description. Check whether the invite is usable, whether it expires and whether entry restrictions are compatible with the selected service.

An order count does not represent active conversation or a community’s quality. Keep onboarding and moderation in your own server workflow. Do not provide an account token, password or recovery code as an order input.

Compare the supported invite, entry requirements, quantity and any stated retention/refill conditions for server members. A larger count does not include conversation, moderation or server boosts. Do not assume an entry restriction is supported unless the service explains it.

Pinterest account services and Pin services point to different targets. Copy the intended public asset and read the exact metric before selecting a quantity. A general profile address may not identify a specific Pin.

A saved Pin or follower count does not establish website visits or purchases. Use your own site analytics for those outcomes. Keep image and content rights in your publishing workflow rather than assuming a service grants them.

Choose between profile followers and actions on a specific Pin. A save/repin label, like or share can have a different service definition, so check the actual target and metric before comparing rates. Pin interactions do not establish outbound website traffic or sales.

Snapchat services can refer to different public content formats. Read the accepted target type and its availability requirements before ordering. Do not assume a private account or expired asset can be used.

If the content has a limited lifetime, consider that alongside the delivery notes. Check whether the service requires the asset to remain active. An average delivery time is not a promise that a time-limited target will remain eligible.

First choose the specific metric and target type: followers, views and other listed public metrics. Compare equivalent service descriptions, quantity ranges and current rates. Use the estimate for the intended quantity, then review the final charge and conditions in the native order form.

A Reddit post and one of its comments are different targets. Use the precise link requested by the service and review the relevant community and platform rules before deciding whether to proceed.

Do not use a service to impersonate community members, fabricate personal experiences or harass someone. A delivered metric is not evidence that a community independently endorses your content. Keep genuine feedback separate in your own analysis.

Read whether the service targets a post, a comment, a community subscription or a user profile. These are different assets and metrics. Compare the current scope and conditions while considering the community’s rules; an ordered count does not represent independent approval or a guaranteed displayed score.

A Threads profile and a Threads post serve different ordering purposes. Start with the exact target and metric before comparing services. A similarly named account on another platform is not an interchangeable destination.

Check the public link, visibility and any repeat-order conditions. Keep replies or other text-based requirements within the supported native fields only. Do not treat an ordered count as an independent recommendation by real customers.

A profile follow, post like, reply, repost and share are separate actions. Choose the exact Threads profile or post, then compare compatible service specifications and quantity rules. Do not infer views or clicks from a package that only describes likes or reposts.

Read the WhatsApp service description carefully to identify the supported target. A public channel address, group invite and personal phone number are different inputs. Do not substitute one for another because they belong to the same app.

Never provide a login code, account password or private contact list. Use only the target format required by the service. An order does not grant permission to message people or demonstrate their consent to marketing.

Compare a supported channel membership or channel-post reaction service by its target, metric and quantity. A personal number and a channel URL are not interchangeable. Membership does not include permission for direct messages or a promise that people will read every update.

Review-related services require particular care. A page or catalogue label does not establish that a service is appropriate under a review platform’s rules. Read the description and use only legitimate workflows that preserve authentic customer experiences.

Do not commission invented experiences, impersonate customers or present paid endorsements as independent reviews. If an option does not explain a compliant process, ask support before considering it. This page does not promise ratings or a particular review score.

Clarify the process and intended output before considering a price. A listing must not be treated as permission to commission invented customer experiences or undisclosed paid endorsements. If the offer cannot explain an appropriate workflow for authentic experiences, ask for clarification rather than purchasing a target rating.

No. The service describes a defined action or quantity. A delivered count does not establish purchase intent, platform recommendations or eligibility for a creator programme. Evaluate those outcomes in your own business and platform analytics.

It is still in the order workflow. Check the submitted target, required visibility, elapsed time and the service’s stated start estimate. The status alone does not identify the cause. If the wait needs review, contact support with the order ID; do not place a duplicate order to try to make it start.

The order ended before the full quantity was delivered. Review the remaining amount and recorded charge or balance adjustment. The published terms cover qualifying unused amounts and exceptions. Partial delivery is different from a later drop after completion, which is reviewed under refill conditions.

Completion describes the recorded delivery outcome. Public metrics can update at a different time or change afterward, and overlapping orders can make attribution difficult. Check the exact target, metric and order record. Send support the order ID and observed difference so it can be assessed without assuming permanent retention.

Record the order ID and contact support promptly with the correct explanation. Do not assume the target can be edited after submission or that a new link will automatically replace it. The terms exclude refunds for wrong inputs, so check the target carefully before future orders.

Check order history and the account balance first. A missing response does not prove the order failed. If its outcome is unclear, ask support with the approximate time, service and target before repeating the submission. This also applies to API clients.

Availability and specifications can change. Search by the original service ID and check current catalog information. A similarly named option may have different conditions. Compare a replacement before ordering, especially if a client expected a particular audience, delivery type or refill term.

The published terms state that the compensation button activates 24 hours after completion. The original service must still include eligible refill/compensation, the target must meet its requirements and the request must be within the stated window. A waiting period does not add refill to a no-refill service.

No. Refill requests replacement of an eligible drop under the original service’s conditions. A refund or balance adjustment concerns the charge and applicable order outcome. Keep the original order ID and describe whether the issue is unfinished delivery or a later decrease.

Keep the original target unchanged. The published compensation terms exclude username changes after ordering and require a public profile. Save the original order record and ask support before changing a target on which you may need an eligible refill.

Where supported, drip-feed divides an order into runs separated by an interval. Check whether quantity means units per run: 100 units across five runs is 500 units in total. Review the actual form’s calculation and final charge. Scheduling runs does not guarantee an exact finish time.

No. Drip-feed schedules runs for a supported order. A subscription can monitor supported uploads and create related orders using settings such as username, post limit, quantity range and delay. Existing-post coverage is separate. Review the exact form before enabling recurring activity.

Yes. The public reference documents a status action with comma-separated order IDs, up to 100 in one request. Inspect each response item because an invalid ID can return its own error. This batch size is not a published requests-per-second limit.

The public API reference states that omitting the posts parameter creates a subscription for an unlimited number of future posts. Use an intentional limit where appropriate and check the selected service’s supported controls. Do not assume a blank limit means the subscription is inactive.

Use the availability message on the particular page. A closed campaign does not accept a new live request just because its steps can be viewed. Do not treat preview preparation or a visible countdown as an approval or a delivery promise.

Not necessarily. The input may be unsupported, the account may be unavailable to the data source or the lookup service may be offline. Read the error, check the target and follow the tool’s limitations. Do not turn an unavailable result into an ownership, safety or account-status conclusion.

Yes. Treat generated text as a draft. Check facts, names, tone and relevance to the actual post before publishing. A caption or hashtag suggestion does not promise reach, ranking or conversions, and a tool does not publish or order a service merely by producing text.

No. A standard post order concerns the submitted content. Stories have their own availability and input requirements, while automatic or old-post options define separate scopes. Choose the matching category and settings rather than assuming every upload on the profile is included.

No. A standard video order applies to its requested target. For several videos, keep separate supported orders or use an option that explicitly states a multi-upload scope. A channel link does not identify which video should receive a video-specific action.

Use a dedicated live option if that is the intended service. A published video and an active broadcast have different targets, timing and possible duration settings. Read those requirements before ordering; a standard clip-view quantity does not reserve live viewers at a scheduled time.

No. Page likes concern the page, while post likes concern a particular published item. Page followers and reactions can also be separate categories. Confirm the asset and desired action before copying the target link or comparing rates.

Use the URL of the item you actually intend to target. A quote post and the original have separate addresses and interaction counts. Open the submitted link and verify its author and content before ordering.

Only if the chosen service explicitly supports that target. A playlist contains multiple tracks and does not itself define how a track quantity should be distributed. Use the correct track address or a documented playlist option.

No. A play describes an event, while a unique-listener metric counts listeners over its defined period. Read what the selected service actually measures and use the corresponding analytics. Do not infer royalties or audience retention from a play quantity.

A standard post-view order applies to the specified message. A general channel URL may not identify that post. Use its direct target or an option that explicitly describes multiple-post coverage; do not assume past and future messages are included.

A follow and a connection are different relationships. Use only the metric and target supported by the selected service. A delivered follow does not establish a mutual connection, endorsement or qualified business lead.

No. An estimate is not a booking. Check the live service’s start, availability and duration requirements before ordering around a stream. A clip or channel-view option should not be assumed to deliver concurrent viewers during a broadcast.

An unusable invite can prevent entry. Prepare a supported invite that will remain valid and check entry restrictions before submitting. If access changes during delivery, contact support with the order ID; do not provide an account token as a substitute.

No. Saving a Pin and opening its outbound destination are different actions. Match the order to its stated metric and measure website visits in the appropriate analytics. Do not treat save quantities as a guarantee of traffic or purchases.

A post and an individual comment have separate targets. Use the exact comment link when the service requires it, and review the community’s rules. Do not assume that activity on the post will be allocated to a selected comment.

Use the Threads target requested by the service. Related accounts on different platforms still have different URLs and metrics. Verify the actual Threads profile or post rather than substituting an Instagram address with the same username.

Use the supported channel link, not a personal phone number, unless the service explicitly defines another appropriate input. Channel follows and post reactions concern channel assets. Never send a login code or private contact list to complete the target.

A genuine review depends on a real person’s experience and the review platform’s rules. An ordered rating or invented story is not evidence of that experience. Clarify the actual workflow and do not describe paid or fabricated endorsements as independent customer feedback.