Most “urgent” P2P tickets fail for a boring reason: the first message is a screenshot with no order ID, no timeline, and no reproducible filters. Support teams are not mind readers—they route tickets through templates. Give them a clean story and you get a clean response.

P2PIndex cannot open tickets for you, freeze wallets, or override an exchange decision. What we *can* teach is how to describe what you saw on https://ngn.lol/board in a way that matches how engineers triage ingestion, filters, and UI drift.

Before you click “Submit”: collect these 8 fields

  • Venue + app version (or web) + approximate timezone.
  • Order ID (copy from inside the order screen—never from a DM).
  • Side (Buy/Sell), asset (USDT/USDC/BTC/ETH), fiat (NGN).
  • Ad limits you saw (min/max) and whether you changed quantity inside the flow.
  • Payment rail you selected (Opay/PalmPay/Kuda/bank) and whether the counterparty asked for a different rail.
  • Timestamps in plain language (e.g., “opened ~22:10 WAT, paid ~22:18”).
  • What broke: frozen chat, missing release button, wrong credited name, API mismatch, etc.
  • What you already tried: cancel request, appeal opened, relogin—short list.

Copy-paste template (edit the brackets)

Subject: `[Venue] P2P NGN order [ORDER_ID] — [one-line symptom]`

Body: `Venue: [Bybit|Bitget|MEXC|LocalCoinSwap] | Platform: [iOS/Android/Web] | App version: [x.x.x] | Account tier: [if known]` → `Order ID: […]` → `Side/Asset/Fiat: [Sell|Buy] / [USDT|…] / NGN` → `Amount locked: […]` → `Payment method on ticket: […]` → `Counterparty claim (summary, no insults): […]` → `Timeline (WAT): opened […], paid […], appealed […]` → `Evidence attached: [redacted bank alert / venue chat export / screen recording yes/no]` → `Comparison context (optional): I used P2PIndex board filters: [Sell|Buy] + [asset] + [payment keywords] and saw [describe row behavior] at ~[time]` → `Request: [refund path | appeal escalation | technical reproduction]`.

How to attach proof without leaking PII

Venues need enough to adjudicate, but you should still avoid sending full account numbers in email bodies. Prefer venue chat exports and in-app receipts when available. If you must include a bank alert, blur middle digits and beneficiary identifiers that are not required for the dispute fact.

When the issue is “board looks wrong” vs “order is wrong”

If your money is stuck in an active order, treat it as venue priority. If you only saw a display mismatch while comparing ads, include filter state and a short description (“Bitget column empty while venue app shows rows”) so the team can separate ingestion bugs from settlement disputes.

📚 Internal links

  • Dispute evidence archive — https://ngn.lol/blog/p2p-dispute-evidence-what-to-archive
  • Why board can differ from app — https://ngn.lol/blog/why-p2p-board-can-differ-from-exchange-app
  • Never pay outside escrow — https://ngn.lol/blog/never-pay-outside-venue-escrow-ngn-p2p-safety
  • P2PIndex login / data minimization — https://ngn.lol/blog/p2pindex-login-google-email-what-we-store-and-never-ask

External

Use each exchange’s official help domain from inside the app settings—never follow “support” links from unsolicited DMs.

⚖️Disclaimer

Operational writing guidance—not legal advice. Each venue defines evidence rules and timelines.