Sign in Sign up
Support Standards

Support Standards

These Support Standards explain how tickets are reviewed, what details support needs, and what users should expect when asking for help. When using a facebook smm panel, support works best when every request includes the order ID, submitted public link, current status, and a clear explanation.

01
Tickets only Support questions are handled through tickets inside the website, not scattered messages.
02
Order context Support needs order ID, selected service, submitted link, status, and issue details.
03
No passwords Support does not need passwords, 2FA codes, recovery keys, or admin access.
04
Review-based help Support can review records and service rules, but cannot guarantee external outcomes.
Ticket Review Lab

Choose the Issue Type

Different ticket types need different details. Select the closest issue so you know what to include before opening a support ticket.

Order Issue

Include the order ID and submitted public link.

For order issues, support needs the order ID, service name, submitted public target, current status, and a short explanation. If the target was changed, deleted, private, or restricted, mention it clearly.

Ticket Quality Needs order context
8 Support Standards

How Customer Help Is Reviewed

These standards keep support organized, fair, and based on real order records. They also help users understand what support can and cannot review.

01
Ticket-based review Support is handled through tickets so account, order, and message history stay connected.
02
Order ID required Most reviews need the order ID to locate the exact request in the dashboard.
03
Submitted link checked Support compares the submitted public target with the order and current target condition.
04
Status-aware review Pending, processing, in-progress, partial, completed, and canceled orders are reviewed differently.
05
No private access Support does not need passwords, 2FA codes, recovery keys, or private admin access.
06
Service-rule comparison Refill, cancellation, delivery, and drop questions are checked against service terms.
07
Evidence helps Screenshots, current counts, payment references, and clear explanations can speed review.
08
No outcome guarantees Support cannot guarantee sales, retention, monetization, approval, or external platform behavior.
Helpful link: For order status meanings, review Order Process. For delivery rules, read Service Policy.
Better Ticket Checklist

What a Good Ticket Includes

A clear support ticket helps the team review the issue faster and with fewer follow-up questions.

✓
Order ID The order ID helps support find the exact request.
✓
Submitted public target Include the page, post, profile, video, group, username, or link used in the order.
✓
Current status Tell support whether the order is pending, processing, partial, completed, or canceled.
✓
Clear issue summary Explain what happened, what you expected, and what you already checked.
Do Not Send

What Support Does Not Need

Support can review normal orders with dashboard records and public target details. Private account access is not required.

!
Password Never send your password, session access, or private login credentials.
!
2FA or OTP codes Do not send login approval codes, SMS codes, or two-factor authentication codes.
!
Recovery details Do not share recovery keys, backup codes, reset links, or private email access.
!
Admin access Do not provide private ownership access to pages, groups, profiles, or accounts.
For account safety details, read No Password Required.
Review Flow

How a Support Ticket Is Reviewed

Support review follows a practical process. The goal is to understand the request from account records, service terms, order status, and user-provided details.

01
Ticket is received The support request is connected to your account and ticket history.
02
Order is checked Support reviews order ID, service name, submitted link, and current status.
03
Rules are compared Delivery, refill, cancellation, and limitation rules are checked where relevant.
04
Reply is sent Support replies inside the same ticket thread with the next step or explanation.
Support Boundaries

What Support Can and Cannot Guarantee

Support can review order records, payment records, submitted public links, and service rules. However, support cannot control external platform systems, user behavior, long-term retention, or business outcomes.

A
Can review order records Status, service, quantity, submitted link, and delivery notes can be checked.
B
Can review payment records Balance, card payment, duplicate payment, or missing payment cases can be checked.
C
Cannot guarantee outcomes Sales, retention, monetization, approval, or external platform behavior cannot be guaranteed.
D
Cannot fix private targets If a target becomes private, deleted, renamed, or restricted, support options may be limited.
For broader limits, review Service Limitations. For responsible use, read Platform Awareness.

Need help with an order?

Open one clear support ticket with your order ID, submitted public link, current status, and a short explanation. Support is handled through tickets.

Open a Ticket