It allows users to select available services, submit public target details, place orders, track status, and open support tickets when a real review is needed.
This FAQ answers common questions about orders, payments, delivery, refills, cancellations, no-password service flow, and support tickets. If you use a facebook smm panel, these answers help you place cleaner orders and avoid common mistakes.
Use the category buttons to switch between FAQ sections. Each section includes 10 focused answers written for real buyer concerns before and after placing an order.
These answers explain services, public targets, order preparation, and responsible expectations.
It allows users to select available services, submit public target details, place orders, track status, and open support tickets when a real review is needed.
You need the correct public link, page URL, post link, profile link, video link, group link, or username required by the selected service. You should also check quantity, service notes, and delivery rules.
Most services need public and accessible targets. Private, deleted, hidden, restricted, or changed targets may delay delivery, cause partial results, or block support review.
Yes. Service notes may explain minimum and maximum quantities, delivery speed, refill rules, drop expectations, target format, and special restrictions.
It is better to avoid overlapping active orders on the same target unless the service note clearly allows it. Duplicate orders can create tracking confusion.
No. Services may support visibility or activity signals, but they do not guarantee sales, leads, revenue, purchases, or customer behavior.
Changing the target after ordering may not be possible, especially if processing or delivery has started. If you submitted the wrong link, open a ticket quickly.
The target should stay public so the service can identify and process it correctly. If it becomes private, deleted, restricted, or unavailable, delivery may fail or become partial.
You can review available service options on the Services page and read the service notes before placing an order.
Start by choosing the correct service, submitting the correct public target, placing a small test order, reading service notes, and tracking the order status before scaling.
These answers cover balance, card payments, failed payments, transaction review, and billing support.
You can add balance through the available payment area inside your dashboard. Follow the payment instructions shown on the website when adding funds.
If card payment is available in the dashboard, you can use the listed card option. Availability may depend on region, provider support, account status, and gateway rules.
Check card details, bank approval, payment limit, available balance, and provider restrictions. If you were charged but balance did not appear, open a ticket with payment details.
Balance may take time to update because of payment confirmation, gateway review, provider delay, or manual checks. If payment is confirmed but balance is missing, contact support through a ticket.
Include payment method, amount, approximate payment time, transaction ID or reference, current balance shown, and a short issue summary.
Refund or balance correction depends on payment status, account history, order usage, service status, and support review. Some cases may be handled as account balance correction.
Open a ticket with both payment references, amounts, payment times, and screenshots if available. Support can review your balance and payment records.
Some payment methods may include gateway fees, card fees, network fees, or currency conversion costs. Review the final amount before confirming payment.
If balance has already been used for orders, cancellation becomes more limited. If balance has not been used and there is a payment issue, support can review the case.
No. Do not send bank passwords, card PINs, private financial login details, or recovery codes in any support ticket.
These answers explain order status, delays, partial orders, cancellations, refill rules, and drops.
Pending means the order has been submitted but may not have started yet. It may be waiting in the system or provider queue.
Processing means the order may be entering preparation or provider review. At this stage, cancellation or link correction may become limited.
In Progress means delivery has started or is actively moving through the service queue. Keep the target public and unchanged while the order is active.
Completed means the system has marked the order as delivered. If there is a valid issue, open a ticket with the order ID, submitted link, and clear details.
Partial means only part of the order could be delivered. This can happen because of target restrictions, service limits, provider conditions, or technical issues.
Delays can happen because of queue volume, provider availability, service speed, target condition, wrong links, or technical changes.
Cancellation depends on the order status. Pending orders may be easier to review, while processing, in-progress, partial, or completed orders may not be cancelable.
A refill is a review option for certain services when delivered activity drops within the listed refill conditions. Not every service includes refill.
Open a support ticket immediately with the order ID, wrong link, and correct link. If delivery has already started, correction may be limited.
You can review the Order Process page for a full explanation of order status, delivery flow, support review, and post-delivery checks.
These answers explain password safety, support ticket rules, private information, and responsible help requests.
No. Standard service orders do not need your password. Orders should use public links, page URLs, post links, profile links, video links, group links, or usernames.
Never share passwords, two-factor codes, recovery keys, private email access, owner access, admin access, bank passwords, or card PINs in order forms or tickets.
Support is handled through tickets inside the website. This keeps your order ID, payment history, submitted link, account details, and support messages organized.
A support ticket should include order ID, service name, submitted public link, current status, issue summary, and screenshot when useful.
No. Keep the same issue inside one ticket thread. Repeated tickets for the same order can slow review and make support history harder to follow.
No. Support can review order records and service rules, but it cannot guarantee external platform behavior, sales, permanent retention, monetization, or approval.
Do not share it. Standard orders and normal support review do not require passwords, two-factor codes, or recovery information. Read No Password Required for guidance.
If a target becomes private, deleted, restricted, renamed, or unavailable, delivery and support review may be limited. Keep the target public and stable until completion.
You can read Support Standards to understand how tickets are reviewed and what details support needs.
The safest way is to use correct public links, read service notes, avoid duplicate orders, keep targets public, never share private access, and open one clear ticket only when support review is needed.
Open a support ticket with your order ID, submitted public link, service name, current status, and a clear explanation. Support is handled through tickets.