OPERATIONS GUIDE

How to Handle SMM Panel Customer Requests Across WhatsApp, Telegram and Panel Tickets

A practical intake process for refill, cancellation and speed-up requests: clarify each order, check the context and give the customer an accurate next step.

For panel owners & support teams8 min readJump to the checklist

01 / THE INTAKE PROBLEM

Different channels.
The same responsibility.

A WhatsApp message, a Telegram reply and a panel ticket can all concern the same order. Treating each conversation as new work can produce repeated instructions, contradictory updates or a request nobody owns.

One message may contain several order IDs and different actions. Another may say only “please fix it.” A customer might repeat a request because they have not seen an update, while the original is already being handled.

The problem gets harder at shift change: the next teammate sees the latest message but not the earlier clarification, provider contact or reason an order is waiting.

Keep the original wording and source, then record what each order needs. A shared sheet or ticket queue can support this method; it does not require ControlSMM.

02 / BEFORE ANY ACTION

Identify the request.
Check who and where it came from.

Extract the panel order IDs and associate an explicit action with each one. Keep the original message beside your interpretation so another teammate can check it.

Name the action for each order.

Refill

A request to address a reported drop. Check the service terms and required evidence before treating it as eligible.

Cancellation

A request to stop an order. “Stop” may be ambiguous; confirm the intended order and action before forwarding.

Speed up

A request for faster progress. Check current status before asking a provider to investigate. Do not promise acceleration.

Resolve missing information first.

Ask a narrow question: “Do you want to cancel order 842611, or are you asking for a status update?” If the message lacks an ID, ask for it. Do not substitute the last order mentioned in an unrelated conversation.

Check the current panel status and the time of that check. If a cancellation request concerns a completed order, or an order belongs to a different account or cannot be found, pause and resolve the mismatch rather than forwarding the requested action unchanged.

An accepted group is not proof of ownership.

For WhatsApp and Telegram, accept requests only from customer groups your team has approved for that purpose. Acceptance determines whether a group may submit work; verification is a separate process with platform-specific limits.

Before sharing order details or acting, check the order’s account context through your authorized records and process. Membership in a chat, a forwarded screenshot or knowledge of an order ID is not sufficient proof on its own. If the relationship is uncertain, use your established private clarification route.

Search your records for the same order, action and customer context across channels. Link a repeated message to existing work after checking whether it adds new evidence or changes the instruction. This is a team review step, not a claim of automatic duplicate detection.

03 / CHOOSE THE NEXT STEP

Route the work, not just the message.

Order lookup establishes context; it does not authorize an action. Provider communication is needed when a clear, eligible request requires provider investigation. Missing information, conflicting instructions or uncertain prior actions require human review first.

MANY SOURCES → ONE INTAKE METHODConceptual team workflow
WhatsAppTelegramPanel tickets*
REVIEW EACH ORDERIdentify · Check context · Check prior work
  • Lookup & update

    Explain the current state using available evidence.

  • Provider contact

    Send a clear request through the agreed provider path.

  • Human review

    Resolve missing, conflicting or uncertain information.

These paths can overlap. *In ControlSMM, supported panel-ticket workflows are PerfectPanel-only. RentalPanel requests use supported chat or manual Cases.

A panel ticket is a source and reply channel, not a different standard of evidence. Where ticket workflows are supported, keep the ticket tied to the order record and use the configured reply path. Do not assume every panel integration can read or answer tickets.

Say exactly how far the work has progressed.

Request received
The message is recorded. It has not necessarily been checked.
Request reviewed
The team has checked the details. Say what is ready and what still needs clarification.
Provider contacted
There is a record of sending the request. Contact is not acceptance.
Provider acknowledged
A reply confirms receipt or investigation for specified orders. It does not confirm resolution.
Outcome confirmed
Order-specific evidence supports the result reported. Record its source and check time; treat conflicting evidence as unresolved.

These are educational distinctions, not ControlSMM status names. For detailed provider follow-up practices after intake, see the provider follow-up guide.

04 / WORKED EXAMPLE

Three orders.
Three different next steps.

All customer details, orders, providers, messages and outcomes below are fictional. This is a conceptual example, not product UI or an automatic workflow.

CUSTOMER → SUPPORT · APPROVED WHATSAPP GROUP
“842610 dropped, please refill. Stop 842611. Can you hurry 842612?”

The team saves the message and checks the account context. All three orders belong to the customer account identified through its authorized process.

Separate the requested action from the next decision.
Panel orderActionFirst decision
842610RefillCheck drop evidence
842611“Stop”Clarify cancellation
842612Speed upCheck prior contact
  1. 1

    Clarify and look up.

    The customer confirms that “stop” means cancel 842611 and supplies the requested drop evidence for 842610. The team checks refill eligibility against the service terms. Order lookup maps 842610 to Atlas Supply order 51026; 842611 and 842612 map to Harbor Supply orders 77231 and 77232.

  2. 2

    Find the work already underway.

    Order 842610 shows completed before the reported drop; 842611 and 842612 show in progress. A linked Telegram conversation records a speed-up request already sent for 842612. The new WhatsApp message adds no changed instruction for that order, so the team records it against the existing work instead of sending again.

  3. 3

    Route only the ready requests.

    The team sends the refill request for 51026 to Atlas Supply’s agreed Telegram contact and the clarified cancellation request for 77231 to Harbor Supply’s agreed contact. Atlas acknowledges the refill request. That reply provides no evidence that a refill has occurred.

  4. 4

    Keep each result visible.

    At a later check, the panel records 842611 as cancelled. The team records that source and check time; any refund is a separate question. The refill has no confirmed outcome, and 842612 remains in progress. Both stay open in the team’s record, with an owner and next review point.

Send an update that matches the evidence.

“842610: the provider acknowledged the refill request; a refill is not yet confirmed. 842611: the panel now shows cancelled. 842612: still in progress; your earlier speed-up request is already with the provider.”

At handoff, leave the original request, clarification, ID mapping, contact history, latest evidence and next action together. If you cannot establish whether an earlier instruction was sent, investigate before issuing it again. Escalate uncertain ownership, conflicting actions or unexplained status changes to a responsible teammate.

05 / KNOW THE BOUNDARIES

The panel connection changes what is available.

Within ControlSMM, these integrations have different scopes. Select the workflow your connection supports rather than assuming all customer channels are interchangeable.

PerfectPanel
Admin API v2. Order lookup, supported panel-ticket workflows and ticket-based group verification. Ticket permissions and reply configuration still matter.
RentalPanel
Admin API v1. Order lookup for supported chat and manual Cases. No panel-ticket workflows or group verification.

Group acceptance and group verification are distinct. PerfectPanel’s verification flow has a specific account-linking purpose; it is not a universal ownership guarantee. RentalPanel does not gain that capability by connecting WhatsApp or Telegram. Use the integration comparison for current scope and setup limits.

06 / KEEP THIS HANDY

The customer-request checklist.

Use this with any shared sheet, ticket system or support workspace. Checks stay on this page only; they are not saved between visits.

Identify and verify
Route and record
Update and hand off
Use your browser’s Save as PDF option.

07 / PUT IT INTO PRACTICE

Where ControlSMM fits.

ControlSMM brings supported customer requests, Cases, order context and provider communications together. Its configured provider contact paths help connect the request to the recorded communication.

It does not execute panel-side refunds, cancellations, refills or partials. A provider acknowledgement remains separate from the actual order outcome. Your team still needs to review uncertainty and communicate what the evidence supports.

The duplicate checks, ownership checks and human handoffs in this guide are recommended team practices. They are not promises of automatic duplicate detection, universal identity verification or automated escalation.

Keep the customer’s request intact. Make every order’s next step clear.