When a support ticket is also a transaction
Merchant questions are almost always about a specific transaction, payout or invoice. In a general-purpose helpdesk that sits outside the payment panel, a ticket starts as a blank conversation, and the agent has to copy transaction references, merchant IDs and dates between two systems before they can even look at what the merchant is asking about.
Opening a ticket where the record already is
A merchant can instead raise a ticket directly from the transaction, invoice or wallet they are looking at, so the reference travels with the conversation instead of being pasted into it. The operator answering the ticket is looking at the actual record, not a screenshot or a copied identifier.
One queue, the same permissions
Tenant managers work the support queue inside their own panel, under the same role-based access control that governs the rest of their access. Support staff do not need broader rights just to answer a question, and there is no second login, no separate SSO setup and no second place where merchant personal data is stored.
Shared storage instead of a second file system
Attachments such as receipts and proofs use the same document storage and download routes as dispute evidence. Nothing has to be duplicated into a second system, and nothing is lost between an attachment and the record it was meant to support.
What this changes day to day
Because tickets are tenant-scoped and queued inside the platform, response-time reporting is a property of the platform rather than something assembled afterwards from two systems. And because tickets open from context, there is one less category of mistake: the wrong transaction reference copied into the wrong conversation.
An optional layer, and where disputes fit in
On top of the support inbox, a separate module can triage incoming tickets and draft suggested replies grounded in the same transaction and merchant context the operator already sees — the operator still edits and sends, and nothing goes to a merchant automatically. This sits alongside the platform's own dispute workflow, where a merchant can open a dispute on a payment or payout with a reason and up to five evidence files, and a manager resolves it with balances rolled back and re-posted automatically — keeping the support conversation and the dispute it may lead to in the same place.
