Download ticket_route.jsonl from fastino/fast-decisions: direct link, hf CLI and curl.
- Browser
- Download file 140 kB
-
https://huggingface.co/datasets/fastino/fast-decisions/resolve/main/ticket_route.jsonl
- Command line
-
hf download hf://datasets/fastino/fast-decisions/ticket_route.jsonl
-
curl -L -o ticket_route.jsonl https://huggingface.co/datasets/fastino/fast-decisions/resolve/main/ticket_route.jsonl
140 kB
| {"input": "[channel] chat\n[subject] Follow-up on compliance check for delayed invoice payment\n[body] After the latest order update, I noticed that the payment for invoice number INV-209384 issued on 2027-03-15 at 13:45 UTC has not been processed due to account verification issues. Despite submitting all required documentation previously, the system still restricts order modifications and payment submissions. The message displayed during checkout was \"Verification pending: action required.\" Kindly escalate this matter for compliance review and advise the rectification steps necessary to enable smooth transaction completion. Your prompt attention is appreciated as this concern was recently reopened following an initial resolution.", "output": {"classifications": [{"task": "queue", "true_label": ["compliance"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Inquiry on identity verification progress for joint promo collaboration\n[body] A customer on our team reported that the merchant representative for Flixon Retail contacted us regarding the joint promotional campaign launch scheduled for next quarter. They mentioned that their identity verification via the PartnerConnect portal faced an unexplained delay despite submitting all required documents on 15.09, 2027, including the updated GDPR compliance certificate. The last message from the support agent Mr. D. Haugen stated, \"Your identity validation is marked complete pending final compliance review,\" but no further update has been received since then. Could you kindly inform us if the verification is currently under review or if additional information is necessary? We rely on the PartnerConnect v3.8 interface to manage these account maintenance tasks efficiently.", "output": {"classifications": [{"task": "queue", "true_label": ["identity"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Request to close account due to unresolved refund issue\n[body] Good afternoon this is Lee from SG I purchased two sets of dining chairs on 2024-04-07 from FurniHub SG The order was delivered on 2024-04-12 but one set arrived damaged I initiated a refund on 2024-04-13 through your customer portal and the confirmation email said the refund would reflect within 3 to 5 working days However it is now 2024-04-22 at 14 30 and there is no sign of the refund credited back to my credit card statement My last call on 2024-04-20 at 10 00 promised escalation but I have not received any update Please arrange for my account closure as I cannot trust this service If necessary I can verify my identity by phone at 65 9123 4567 Thank you for your assistance", "output": {"classifications": [{"task": "queue", "true_label": ["account_closure"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Delivery wording after each account renewal\n[body] Hi team, I administer the Southern Kite profile and wanted to check a recurring delivery issue. After each annual renewal, several customer orders remain in carrier transit with the order page stating, “Delivery date will be provided when the parcel is received by the local depot.” Our carrier settings still show the old depot code, so customers cannot see a useful estimate. The policy says delivery changes cannot be made once parcels are in transit, but could you advise whether that applies to a merchant configuration correction? This has happened after the last three renewals, including 14-08-2026 and 14-09-2026. We are not seeking compensation, only a practical fix.", "output": {"classifications": [{"task": "queue", "true_label": ["general"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Request to cancel order due to recurring checkout error\n[body] Hello team, I am following up regarding the payment authorization outage for my order placed with Sapphire Supply. After initially receiving a resolution email, this morning at 07:45 I got another automated notice stating that payment verification failed again, and the order remains on hold for reconciliation. I wish to cancel this transaction rather than attempt another authorization cycle. My records show the billing address as 108 King Street West, Rochester, ON M5V 1M1. Please confirm cancellation and remove the pending charge. Thank you for your prompt attention to this reopened case.", "output": {"classifications": [{"task": "queue", "true_label": ["outages"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Renewal payment flagged although order is still pending\n[body] Although the payment appears complete, I am tracking an incoming order for our monthly tea subscription renewal and the checkout message showed “renewal authorised, fulfilment pending” at 21:10 Singapore time. The charge was S$86.40, but the parcel has not moved and my account now displays a second renewal warning. The earlier agent said it was only a display delay, but that explanation does not fit both messages; one may be a duplicate charge. Please cancel any extra renewal and confirm the correct shipment status. Order reference SG-T41M8. My delivery address is 18 Kestrel Walk, Singapore 548210.", "output": {"classifications": [{"task": "queue", "true_label": ["fraud_review"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Confirmation of proposed fix for renewal order mismatch\n[body] This is Rohan Mehta from Northstar Bazaar calling about our API setup during business integration. For the last three monthly renewals, the payment authorization succeeded through UPI, but the fulfillment webhook returned HTTP 409 with “order state cannot transition”, so the parcel was either created late or not created at all. After delivery, our buyers contacted support because the subscription invoice and delivered quantity did not reconcile. The latest request, renew-91F2, received a 422 response stating that the renewal reference was already consumed. We have been manually matching nearly ₹1.4 lakh in transactions each cycle, which is not sustainable. Your team proposed disabling automatic retry, issuing one replacement fulfillment event, and adding an idempotency check before the next renewal. Please confirm that this resolution is acceptable and will preserve the successful authorization without creating another charge. There is no active outage or immediate loss at present; I am recording the matter for the integration review and would appreciate written confirmation. The buyer-facing checkout message displayed “payment received”, although the fulfilment record remained pending.", "output": {"classifications": [{"task": "queue", "true_label": ["fraud_review"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Re: Recurring checkout failures on mobile app - duplicate payment block\n[body] According to the notice I received, the payment for our monthly renewal of Business Plus (₹1,89,500.00) failed again this morning during checkout on the mobile app, even though I authorised the UPI request at 09:36 IST. When I attempted payment a second time, the app created a duplicate pending transaction without confirming the order. Previously, your team suggested I clear the payment cache, but the issue recurred this billing cycle too. I noticed my statement now shows two pending debits, both timestamped minutes apart. I apologise for repeated follow-ups, but could you please escalate this and reverse any extra authorisations? I am sharing my work contact, +91-82105-49736, as your team needed it before for callback authorization.", "output": {"classifications": [{"task": "queue", "true_label": ["mobile_app"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Return approved but account lock blocks next steps\n[body] Hi team, following up on my earlier chat about the completed return for the linen set. The parcel was delivered back on 18:40 yesterday, but the receipt excerpt says, “Return accepted — refund S$86.40 to original payment method within 5 working days.” I cannot open the order page now because my account is locked after the sign-in verification failed, so I am unable to confirm the refund destination or upload the carrier handover record. The purchase itself was completed successfully, but the unexpected result is that I have no access to manage the closed return. Could you please help restore access or tell me another way to verify this case? I am happy to provide the order reference through the secure portal.", "output": {"classifications": [{"task": "queue", "true_label": ["returns"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Inconsistent account activity and duplicate payment hold\n[body] This is Martina Greco from Hermes Financial Services. I'm reviewing a client account and noticing discrepancies that I need help clarifying. The order was placed on 14,07,2027, and initially, the delivery status stated \"Processing - Estimated to dispatch by 20,07\". Yet, the client only received an update on 22,07, indicating \"Shipment delayed due to stock unavailability\". Meanwhile, our records show a failed checkout attempt on 15,07 followed by a duplicate authorization hold of €145.80 on the same client's card ending in 3487. These authorizations have not cleared nor reversed, causing confusion in the reconciliation process. Our client expects timely updates and clear billing entries. Could you verify the identity associated with these transactions and confirm why the standard order status was not updated promptly? For identity verification, the registered address is 12 Rue de la Liberté, Paris. I am seeking swift resolution given the financial reporting deadlines. My contact number is +33 1 23 45 67 89 if a call-back is necessary.", "output": {"classifications": [{"task": "queue", "true_label": ["identity"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Urgent assistance needed for payment processing failure\n[body] Good afternoon, this is Alan Cross, the account administrator for QuokkaTech Pty Ltd. We recently attempted to renew our annual subscription on 15-06-2024, invoiced for $1,240.75 AUD (Invoice #QT-45219), but the system rejected the payment without clear error details. Subsequent support replies have not resolved the issue, and our access to account management functions remains blocked, preventing any order adjustments. This disruption is jeopardising service continuity and requires immediate escalation to your payments team to restore our account access and process the renewal payment promptly. Please advise on next steps to rectify this as a matter of urgency.", "output": {"classifications": [{"task": "queue", "true_label": ["payments"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Query on partner offer eligibility and account anomaly\n[body] Good afternoon. I am contacting you regarding the Brindle & Shaw promotion scheduled for next quarter. Earlier today an alert from the automated security module stated my access had been temporarily disabled following a flagged transaction attempt of £2,380 on 13-06-2026. As this was unexpected while conducting our routine evaluation, could you kindly confirm whether system verification is pending or if this incident will impact the eligibility review? I wish to ensure all subsequent application steps are properly sequenced. Your guidance is greatly appreciated.", "output": {"classifications": [{"task": "queue", "true_label": ["fraud_review"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Please cancel the pending promotional refund transition\n[body] A customer on our team reported that the refund connected with our joint spring promotion has remained in a pending state, and I am sorry for the repeated follow-up. Could you please cancel the transition rather than allowing it to complete? The transaction history is: 04.09.2026, 09:12 — promotion order authorised, €186,40; 04.09.2026, 09:18 — partner discount applied; 05.09.2026, 16:47 — parcel marked delivered; 07.09.2026, 10:03 — return request accepted; 08.09.2026, 14:26 — refund instruction created; 09.09.2026, 08:51 — refund status changed to pending; 12.09.2026, 11:35 — no movement recorded. The customer has already handed the goods back, so we do not want a second fulfilment or payment action generated. This is related to our co-branded campaign with Northstar Goods, and the order reference is NGS-48271. There is no immediate commercial deadline; we mainly want the record corrected and the incomplete transition cancelled. Please advise whether your support team can stop it and retain the history for reconciliation.", "output": {"classifications": [{"task": "queue", "true_label": ["product_feedback"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Urgent cancellation: duplicate charge seen on renewal attempt\n[body] I'm a merchant trying to cancel my customer's subscription renewal after the checkout system failed. The renewal page first said “Processing, please wait,” then changed to “Payment authorized, but update pending” nearly 30 minutes later (2026-10-12T15:00+00:00). Now our orders dashboard shows two pending debits for the same UveaPro Plus subscription, both referencing the same invoice. The customer’s portal reflects both “authorization received” and “renewal completed” on the same day, but actual fulfillment hasn’t triggered. I am very concerned that this is a duplicate charge. I need a full review of this transaction and an immediate reversal of the extra charge. For reference, payment card 5067-1280-3389-4381 was used by the customer. Please escalate and resolve.", "output": {"classifications": [{"task": "queue", "true_label": ["fraud_review"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Unverified closure request and unexplained activity after API integration\n[body] According to the notice I received from Fane-Kelley, my developer account is due to be closed, but the transition to inactive status has not finalized. While reviewing the activity logs from 03-09-2027 through 03-12-2027, I noticed an unfamiliar authorization for $212.33 and a fulfillment alert linked to an external identifier I cannot reconcile. No personal contact or payment data is visible in the logs; however, the sequence of entries suggests automation. Please clarify the status change and investigate the disputed charge before deactivating the account. Thank you for your attention.", "output": {"classifications": [{"task": "queue", "true_label": ["account_closure"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Confirmation needed on API fix for subscription renewal hiccup\n[body] After the latest order update, we've noticed the consignment status wasn't refreshed for over 36 hours, resulting in a failed checkout attempt when processing the subscription renewal for our joint promotion. The checkout message indicated \"Transaction declined, please retry later,\" and subsequently, we observed a duplicate pending authorisation in the system. Given the explanation about a delayed handoff in your API was given earlier, could you please confirm if the proposed fix addresses these issues fully? We want to be sure the proof of delivery and billing synchronise correctly before the next billing cycle starting 15-07-2024. Thanks, Samantha from Lytrex Solutions.", "output": {"classifications": [{"task": "queue", "true_label": ["api"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Disputed renewal charge linked to unknown profile\n[body] I am escalating this because the last agent response did not address my compliance concerns. Every time my subscription renews—most recently, 02/04/2026 at 07:11—I get a charge for $37.99, but the invoice is always linked to \"G Cedar Services.\" That profile is not mine. My account page shows a second email attached after each renewal and I never receive a security alert. Records indicate: 01/03 $37.99, showing in history as external profile. This pattern keeps repeating despite my previous complaints. Please review and confirm compliance with your account security requirements, or I may need to block future charges. I expect a clear explanation.", "output": {"classifications": [{"task": "queue", "true_label": ["compliance"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Follow-up: reopened merchant access case blocks settlement reconciliation\n[body] Following our earlier exchange, case IN-48271 appeared resolved on 12 September after the integration team refreshed our business API credentials. It reopened on 14 September: the merchant console now rejects my finance login, so I cannot review SKU dispatch records or reconcile the pending lakh-level settlement against the charge. I completed the access reset at 09:42 IST, while the system update timestamp shows 10:18 IST and still marks the account as restricted. Please confirm the compliance review status and restore payment and order-management access. Our UPI settlement file was generated at 10:05 IST, before the restriction returned.", "output": {"classifications": [{"task": "queue", "true_label": ["compliance"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Partner shipment delays recurring after annual renewal\n[body] After the latest order update, I'm calling as the company account administrator; every time our profile renews, the shipment status for our partnered courier seems to get stuck. This morning, the tracking page displayed \"in transit to carrier – check back for update\", which is the same message we saw last renewal. Our client delivery is marked overdue again, raising refund queries downstream. Could you clarify what's causing this repeating carrier handoff issue? I must apologise for raising it repeatedly, but we need to ensure our partners aren’t disadvantaged. For context, the last two renewals (14-05-2022 and 11-05-2023) triggered similar delays. Would you be able to advise whether a manual status push is possible, or if a different integration approach is required to prevent missed deliveries and possible losses (over £450 last time)?", "output": {"classifications": [{"task": "queue", "true_label": ["partnerships"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Inconsistent profile activity and pending transfer dispute\n[body] Hello, this is Elodie Martin calling concerning my pending delivery from Lianix Market. My account shows two separate debits for €73,50 each on 09.06.2027 and 12.06.2027, both referencing an order that has yet to dispatch. However, last night I received a verification prompt linked to a profile email I don’t recognise. None of my previous orders were ever processed via this secondary profile. I’ve tried confirming my details twice this morning, and every attempt ends with an alert about permissions changes I never requested. Given the pattern of unexpected changes in my account activity and the unauthorized access notifications, I need compliance to investigate urgently. My phone number is +49 170 5589132 and primary address: Beethovenstraße 22a, 40233 Düsseldorf. Please respond soon as repeated failed verification leaves my order in limbo.", "output": {"classifications": [{"task": "queue", "true_label": ["compliance"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Account closure process stalled due to pending payment verification\n[body] Dear Support Team, I am coordinating the financial reconciliation for Allbright Supplies and noticed that the closure of our main account has not progressed as per the automated notification received on 02-05-2024. The system indicates a pending payment verification which, according to our records, was submitted and approved on 28-Apr-2024. This discrepancy is causing delays in finalising the account closure and is affecting subsequent invoicing cycles. Please investigate the payment status linked to account number AC-459872 and proceed with the necessary actions to complete the account termination process promptly. Your confirmation of the corrective measures taken would be appreciated to ensure compliance with our internal deadline of 10-May-2024.", "output": {"classifications": [{"task": "queue", "true_label": ["account_closure"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Escalation: merchant verification blocked after failed delivery reversal\n[body] Hi, I run operations for Northstar Pantry in Singapore and am following up because the earlier verification reply did not resolve this. A customer’s delivery was marked successful at 18:40, then reversed in the carrier system after the parcel was returned to our warehouse. We initiated the return and refund, but checkout now shows “Merchant verification required” when I try to complete the adjustment. The account maintenance page also says “Unable to verify business details” (our uploaded registration file is unchanged). The affected refund is S$86.40, reference NS-59031, and the payment attempt was initially approved before being reversed. Please check whether our merchant profile is locked or whether the refund workflow needs re-authorisation; this is holding the customer case open. It is currently 16:25 SGT and we need a definitive next step today, please.", "output": {"classifications": [{"task": "queue", "true_label": ["mobile_app"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Subscription renewal payment mismatch and billing alert\n[body] Good afternoon, this is Rajesh from Sunshine Retail Associates. I am calling about an incident that occurred following the automatic renewal of our annual subscription on the 12th of March. Despite the payment authorization for ₹1.5 lakh debited from our corporate account ending 1234, our system just generated an alert indicating a payment discrepancy and a partial fulfillment of agreed promotional services. We have already received the renewal confirmation email, yet the package features—particularly joint campaign access—are not activated. Additionally, our finance department noted an unexpected additional fee that wasn’t in the initial agreement. Please escalate this billing dispute promptly, as this impacts our ongoing partnership deliverables. You can reach me at +91-9876543210 for any verification.", "output": {"classifications": [{"task": "queue", "true_label": ["billing_disputes"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Reopened case: API issues still blocking order processing\n[body] I am a developer tasked with integrating the payment API during our business onboarding phase. Despite prior support stating on 2028-04-13T09:15Z that configuration issues should have been resolved, we continue facing hanging orders for multiple merchants. The earlier message read: \"Configuration corrected on your account; please verify transaction statuses.\" However, since reopening this ticket last week, the problem persists and impacts all customer checkouts in the European region. Given the critical mismatch in order statuses, I must insist on immediate escalation to prevent revenue loss. Please provide logs or diagnostics, as the prior response did not address the root cause.", "output": {"classifications": [{"task": "queue", "true_label": ["general"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Charge on unfamiliar account after verification update\n[body] A customer on our team reported that they received an automated email alert from OakRow Commerce regarding a $58.90 charge to a credit card ending in 2093 linked to API-integration account ID: OCX-5198-TQX. This occurred immediately after we completed a required verification step, which is outlined in your current integration documentation. However, we have no record of authorizing this payment, and the notification references a shipping address—1257 Willow Ave, Redford, MI 48239—that is not associated with our organization. I apologize if I’ve missed any details in your new account maintenance rules, but I’m concerned this policy may have resulted in a mistaken charge. Please review the event associated with API event ID 7749XPY and advise on how to reverse or dispute this transaction. Thank you for your help.", "output": {"classifications": [{"task": "queue", "true_label": ["fraud_review"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Escalation: reversal handling in merchant API\n[body] Good afternoon, I am calling on behalf of NilaCart regarding our production integration. An initially successful UPI collection for several customer orders was reversed, yet our webhook configuration did not receive the corresponding reversal event. The API response for each callback attempt is HTTP 422, stating “merchant profile reversal mapping missing”. We previously raised this with your integration desk, but the matter remains unresolved and is affecting approximately ₹1.8 lakh in customer settlements. Kindly escalate this to the payments engineering team and advise which configuration must be amended. My contact number is +91 98765 43210.", "output": {"classifications": [{"task": "queue", "true_label": ["payments"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] No renewal confirmation received for monthly subscription after API update\n[body] A customer on our team reported that their recurring charge for the monthly Dalliance subscription, due on 03-14-2027, appeared to succeed according to our internal systems, but the status remains \"Pending\" in the account view even after 24 hours. Previous renewal receipts have arrived instantly, but this time, the only communication we received was an autogenerated payment summary: \"Invoice #VJ8237, Amount: $12.00, Billed to: Maxine Drover, Card ending 5742\". We escalated last night after receiving no resolution from support. The customer’s subscription benefits have not reactivated. Please verify API processing for this renewal and advise on restoring full access. The account card is set to expire in August, but the charge did go through successfully.", "output": {"classifications": [{"task": "queue", "true_label": ["api"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Unexpected charge after product evaluation\n[body] A customer on our team reported that a completed S$86.40 test order for the Lumenfield display unit showed “Delivered to merchant collection point” on the order page, although no parcel reached our shop. The same page then triggered an unfamiliar account notification saying a second payment had been authorised. We are a seller reviewing the item before listing it for pre-purchase enquiries, and this result needs investigation. The customer is frustrated but has not threatened escalation. Please check the disputed charge and notification trail; our merchant account is still operating normally.", "output": {"classifications": [{"task": "queue", "true_label": ["general"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Unable to verify account and complete payment\n[body] After the latest order update, my checkout repeatedly fails at the verification step. Although my account was re-confirmed last month for the transaction on 03-07-2026, today I'm again seeing a “Could not authenticate payment details. Please review your security settings or contact support. Error code: PT-EU-4312” message with every attempt. I can’t access my saved cards or change delivery details because the endpoint freezes and no webhook is firing post-response. My registered address is 15 Oakfield Road, Penham, BR3 6DP. Please urgently restore my account access so I can process the payment (£112.40). My mobile is 07700 945783 if you need additional verification. I require immediate action to unblock my account as the order is time-sensitive.", "output": {"classifications": [{"task": "queue", "true_label": ["payments"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Follow-up on cancellation and refund request for client account\n[body] Good morning, this is Eliza Quinton, the account administrator for Meridex Solutions. I am contacting you to revisit the cancellation I requested earlier this month regarding the subscription linked to our corporate client ID 908-45231. Though initially processed and a temporary credit issued on the 05-03-2024 invoice, discrepancies remain unresolved due to persisting access issues with our account dashboard preventing payment adjustments or order review. Enclosed within this correspondence are details extracted from the original payment receipt showing the debited amount of AUD 1,395.00 from Guthrie Tech Supplies dated 28-02-2024. Kindly advise on rectifying this matter promptly, as we require confirmation that the cancellation was effective and the refund has been properly applied. I appreciate your attention to this matter and look forward to your courteous assistance during this verification process.", "output": {"classifications": [{"task": "queue", "true_label": ["refunds"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Query on refund status for returned batch\n[body] Hello, this is Priya from FinServe reconciling recent payment entries. We noticed an initial refund of ₹1.5 lakh was processed on 15th March for order #MD-998742, but later a reversal entry appears dated 18th March without a clear reason. This has affected multiple refunds from the merchant, causing discrepancies in our settlement report. Could you please confirm the current status of these refunds and clarify why the reversal was posted? We require this information urgently to update our ledgers before dispatch. The transaction log shows: 15/03 refund approved ₹1.5L, 18/03 reversal ₹1.5L, and pending reversal confirmation. Kindly advise.", "output": {"classifications": [{"task": "queue", "true_label": ["returns"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Clarification on payment 'capture pending' status after reopening\n[body] Hello, this is Julian from PremiumTech Solutions partnering on the Spring Sale promo. I’m calling regarding the order fulfilment for the campaign that was supposed to dispatch last week. While the case was temporarily closed last Monday after your team addressed our concern, we've noticed the order page now states 'capture pending' beside the payment status, which differs from the 'authorization held' message we received previously. Given that I can’t access the merchant portal to complete payment adjustments or confirm shipment, could you please clarify why this change occurred? The lack of portal access limits our ability to manage the transaction effectively. I’m quite sceptical about the initial explanation involving the reversal—they didn’t align with what we see on the order details (order ref PS-31098). Your prompt assistance will help ensure smooth processing before dispatch.", "output": {"classifications": [{"task": "queue", "true_label": ["partnerships"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Request to review delivery policy for joint campaign orders\n[body] Dear Meridian Commerce Support, I write on behalf of Kestrel & Wren regarding our joint promotion, which generated several customer orders for the LumaFold SKU. Although the parcels were released for carrier transit, repeated checkout attempts by separate customers displayed “delivery unavailable for this postal sector” during payment, and some orders subsequently failed to settle. Our merchant configuration permits dispatch to Singapore addresses and should not apply a blanket carrier restriction; may this policy be reviewed urgently? The failures occurred at 14:10, 15:05, and 16:32 SGT on 22 September 2026, affecting multiple baskets. We would be grateful if you could confirm whether the delivery rule is overriding the campaign setting and advise how these consignments can proceed to final delivery. The disputed orders total S$1,284.90.", "output": {"classifications": [{"task": "queue", "true_label": ["fraud_review"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Please confirm the proposed refund for affected consignments\n[body] I am confirming that the proposed resolution is acceptable: please return the duplicate delivery charge to the original payment method. The consignment was handed off and marked delivered, but the merchant’s shipment profile appears to have applied the same delivery fee across several customer orders. Our receipt excerpt reads, “Delivery service: Priority handoff — $18.00; status: delivered 2026-09-18 16:40.” The proof of delivery changed to complete, yet the refund status has not updated since then. Please confirm the refund will proceed today, as this is urgent. The order reference is CN-58214; no phone or address is included.", "output": {"classifications": [{"task": "queue", "true_label": ["refunds"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Duplicate pending charge after failed return\n[body] According to the notice I received, there is still a pending authorization on my card for €98,50 from the failed return attempt on 18.05.2026. I was told by Javier in support chat yesterday that the return would be processed and the charge released within 24 hours. Instead, my card statement now shows two identical charges, but only one package was ever picked up. I am following up because the refund has not appeared and my card is still blocked for both amounts. My account ID is EU-49679381. Please advise urgently—my address is 12 Rue du Pont, 75006 Paris, if further verification is needed.", "output": {"classifications": [{"task": "queue", "true_label": ["identity"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Please cancel return freight and reverse the refund request\n[body] Hello Support, I manage dispatch for Wattle & Finch Homewares. A customer’s parcel was delivered to the wrong suburb on 12-09-2026, then returned to our warehouse after the carrier marked it “delivery exception”. During checkout, the payment screen displayed: “RETURN SHIPPING INCLUDED — refund available after scan”, with the word INCLUDED shown in capitals. That message appears to have caused the buyer to expect a prepaid label. Please cancel the current return-freight request and confirm whether the associated refund hold can also be cancelled. We have not issued a replacement, and the order is now back with us. This is a process correction rather than an urgent escalation; the reference is WF-59031. Please advise which status should be recorded in the merchant console.", "output": {"classifications": [{"task": "queue", "true_label": ["shipping"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Reversal of refund not reflected in customer accounts\n[body] Could someone clarify why a reversal of a refund we processed on 12 March isn't showing up in the ledgers of several customers? The initial refund of SGD 120.75 to order VXT-3098 was successful at 11:45 but then reversed shortly after due to a merchant config error. Yet, account statements from client invoices INV-4521 and INV-4522 still reflect the refund. I’m the finance contact handling returns and this inconsistency is making reconciliation tricky. Please provide a detailed explanation. Thanks.", "output": {"classifications": [{"task": "queue", "true_label": ["outages"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Renewal orders reverting after checkout confirmation\n[body] Although the payment appears complete, our subscription renewals are being reversed across several customer orders. I am calling as the seller managing merchant operations for Northstar Pantry, following yesterday’s support exchange. The order page first showed “Delivery scheduled for 28 September”, then changed to “Payment reversed—action required” after the renewal was accepted. Because this affects multiple subscribers, our fulfilment queue is now paused. The merchant dashboard configuration appears to be applying an incorrect renewal rule; we have not changed it since 19-09-2026. I am frustrated, but mainly need the setting checked and the affected renewals restored. You can reach me on +44 7700 900321.", "output": {"classifications": [{"task": "queue", "true_label": ["outages"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Delivery status after recurring API renewal orders\n[body] Although the payment appears complete, I’m sorry to trouble you, but every renewal purchase made through our VelaCart integration develops the same delivery issue. The order page first says “Dispatched — awaiting carrier collection”, then changes to “Delivery delayed: address or label query” after two days, and finally shows “Return initiated by courier”. This has happened on the renewals dated 14-06-2026, 14-07-2026, and 14-08-2026. Could you tell me the current status of the latest order and whether its return has actually reached your warehouse? We are using the v3 business API, and the checkout response is marked successful, so I’m trying to establish whether the fault is in our integration or in fulfilment. The previous two parcels were refunded, but the newest refund has not appeared yet. I realise this may be partly our setup, and apologies for the repeated contact. Could someone confirm what the status means and advise whether we should pause the next renewal? There is a small configuration erroer in our notes, though the request itself is valid. Order reference VC-59031.", "output": {"classifications": [{"task": "queue", "true_label": ["api"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Policy challenge: duplicate authorisation after failed checkout\n[body] Although the payment appears complete, our shop’s checkout showed “card verification required—do not retry” and then declined the purchase on 18-09-2026. A second attempt was not made, yet the dashboard now displays a pending £86.40 authorisation against the same basket. We are evaluating your platform before moving our seasonal catalogue across, so this behaviour conflicts with the stated policy that failed payments release automatically within a few minutes. It has remained pending since yesterday, and the customer cannot tell whether stock is reserved. Please explain the transition status and confirm when the hold will disappear. We are frustrated, but want a clear answer before approving the integration. The message also said “try again later,” which autocorrect changed to “try again latter.” Reference cart EV-59217.", "output": {"classifications": [{"task": "queue", "true_label": ["general"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Recurring charges and identity alerts after campaign renewals\n[body] Hi support, as one of Blue-Raven's business partners, I'm requesting a full review of the recurring charge discrepancies after each quarterly promo renewal. On 04-12-2027, our client was billed $98.50—which they did not authorize—right after receiving an account update notification at 8:14AM. The last time this happened, your team said it was a sync delay, but timestamps show the authorization attempt (8:12AM) predated the notification. I am skeptical of the prior resolution and need corrective action, along with documentation verifying account holder identity. For follow-up, please call me at +1-555-022-7396.", "output": {"classifications": [{"task": "queue", "true_label": ["identity"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Unexpected charge after returned parcel\n[body] I am sorry to trouble you; I am writing for my brother, Elian Voss. His parcel was returned on 14/09/2026, yet the receipt says “Order LV-5831 — charge €72,40 — completed”. He then received an unfamiliar account notification showing the same charge. Could you investigate whether this payment belongs to another account and correct it? We would be grateful for assistance.", "output": {"classifications": [{"task": "queue", "true_label": ["billing_disputes"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Urgent: onboarding delayed due to shipping status mismatch\n[body] As the finance contact for Glenfield Outfitters, I’m reviewing our recent orders in the fulfillment phase when I noticed that several shipments display conflicting statuses on the order page. While the batch is marked as \"Ready for dispatch,\" the delivery status mistakenly reads \"Awaiting pickup by courier,\" which hasn’t occurred yet. This discrepancy is preventing the completion of onboarding for our new merchandise program, v3.8, and is holding up downstream processes. Please investigate the merchant’s configuration settings, as this issue impacts multiple customer orders and requires immediate correction before dispatch scheduled for 24-11-2027. Your prompt assistance will greatly help avoid further delays.", "output": {"classifications": [{"task": "queue", "true_label": ["onboarding"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Cancellation needed for recurring API order failures\n[body] Yesterday, I noticed multiple parcel order attempts failed due to repeated '400 Bad Request' errors from the API endpoint. The integration was set up last week, but now our clients’ shipments are held up. Can you assist in halting further orders until we resolve the configuration issue? My contact is +44 7920 555123 and address 12 Elmwood Cres, Manchester M14 7AB.", "output": {"classifications": [{"task": "queue", "true_label": ["partnerships"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Issue with subscription renewal charge processing\n[body] Hi, I'm calling because every time my monthly subscription renews, I get two failures: first, the payment gateway returns error code 502 during token validation, and then the service status dashboard shows 'Subscription status: Interrupted' until I manually refresh my account. I was told last week these would be resolved, but the problem persists. I want to confirm if the suggested fix—to update my payment method details and retry after 24 hours—is still the recommended solution? Also, please let me know if you can monitor the API logs for unusual timeouts. Thanks for your help.", "output": {"classifications": [{"task": "queue", "true_label": ["outages"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Corrective action needed for partner promotion checkout\n[body] According to the notice I received, our joint promotion with Northstar Mercantile is failing during the business integration. We have made three separate attempts today to create the promotional payment through the mobile app’s partner flow, at 09:10, 11:35, and 14:05, and each attempt ended before fulfilment could be triggered. The customer later received the parcel, but post-delivery support cannot retrieve the purchase record to apply the agreed promotional credit. The receipt excerpt reads: “Partner offer: MapleCart Spring Event — discount pending; payment reference: MC-48271; fulfilment status: unavailable.” Please correct the mobile workflow, reconnect the order record to support, and confirm when our next test can run. No customer details are included here.", "output": {"classifications": [{"task": "queue", "true_label": ["mobile_app"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Duplicate pending charge appears after every renewal\n[body] According to the notice I received, our company account keeps getting an extra pending payment of £89.50 after each subscription renewal. The latest invoice dated 18-05-2027 shows only one annual fee, but the bank shows two authorisations. I'm sorry if I've missed something before, but could you tell me whether this duplicate is expected or if it's being fixed?", "output": {"classifications": [{"task": "queue", "true_label": ["billing_disputes"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Verification pending for my partner’s account\n[body] I am writing on behalf of my partner, Elian Voss, to challenge the policy requiring a new identity check before the account can be maintained. The dashboard has shown “verification pending” since 14/09/2026, although the transition was expected to finish within one business day. The transaction history contains entries dated 12/09/2026 and 13/09/2026 marked “review requested,” followed by two unchanged pending deposits of 86,40 € and 19,95 €. Several household orders from the same merchant configuration now appear affected. Your earlier explanation blamed routine checks, but the repeated entries suggest a configuration problem. Please investigate and confirm whether the policy can be reviewed.", "output": {"classifications": [{"task": "queue", "true_label": ["identity"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Follow-up on unresolved API billing discrepancy during order sync\n[body] I was recently integrating the new payment gateway via API, and on 12-04-2024, the connected account notified me of a chargeback linked to invoice #INV-209834, which I hadn't seen before. Initially, the test transactions during setup didn't show this issue, and the problem seemed fixed when the billing alert stopped last week. However, while syncing live order data today at 09:15 AEST, I received the error \"Transaction rejected: insufficient permissions\", which matches the disputed charge from the earlier invoice. I have attached a snippet from the official payment record highlighting the chargeback entry for your reference. Kindly confirm if your proposed fix—updating the API keys and refreshing account tokens—is sufficient to prevent this from recurring. Our business cannot afford further disruptions, and we appreciate your prompt evaluation.", "output": {"classifications": [{"task": "queue", "true_label": ["api"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Escalation: payment authorised but delivery was not completed\n[body] Hi, I am escalating this because the earlier chat response only advised me to wait, but the completed purchase now needs a compliance review. I authorised payment for a Northstar Homeware order at 2026-09-18T09:42:11Z; the checkout page changed to “confirmed” at 09:42:16Z, and the system later marked the parcel as delivered at 2026-09-21T16:08:37Z. Nothing was delivered to my address, and the courier image belongs to a different building (the visible entrance number is not mine). I contacted support at 2026-09-22T10:15:04Z and was told the record showed successful delivery, although the tracking update was posted only after the stated delivery window had ended. Please investigate the payment authorisation and delivery record together, then explain how I can return or obtain a refund when the goods never arrived. I am not asking for another purchase; I need a written resolution and the relevant transaction history (reference NS-48271).", "output": {"classifications": [{"task": "queue", "true_label": ["compliance"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Repeated carrier status errors and missing delivery updates\n[body] On behalf of my spouse, I am reaching out to seek further assistance related to the ongoing shipment of their recent Dorcey Home purchase (order ref: ZXH-005183). The initial inquiry last week was regarding a missing tracking update post-dispatch; your team had reassured us that the courier scan would appear within 24 hours. Unfortunately, not only does the system continue to display 'Pending at Facility' as of 04-29-2026, but each probe via the tracking API returns either a 404 error or 'Carrier Timeout' message, depending on the attempt. This pattern has occurred across multiple browsers and devices. Additionally, we have noticed that while the order page shows the shipping fee billed on 04-25-2026 ($14.99), the transit timeline is still not updating as expected. Kindly investigate these discrepancies, as we would greatly appreciate your guidance and help in resolving both the tracking and system response issues.", "output": {"classifications": [{"task": "queue", "true_label": ["shipping"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Confirmation of proposed resolution for reversed payment authorizations\n[body] According to the notice I received, I am calling on behalf of my spouse regarding several household orders placed through Northstar Homeware on 2026-09-18. The merchant’s checkout configuration appears to accept the payment authorization, then reverse it shortly afterward; this affected four orders rather than a single attempt. Their integration team supplied an API response showing HTTP 409 with the message, “authorization state invalid,” followed by a reversal webhook. As the proposed resolution is to correct the merchant endpoint mapping and reprocess the affected authorizations, I respectfully confirm that this approach is acceptable to us. Could you please verify whether the original payment holds will be released automatically? The latest response was recorded at 16:40 UTC, and no replacement charge should be submitted until your team confirms the configuration is stable.", "output": {"classifications": [{"task": "queue", "true_label": ["billing_disputes"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Request to cancel refund processing for consignment AB-1934\n[body] Hello, this is Warren from Brandley Supplies. I wanted to check on a refund I initiated for order AB-1934, which according to the tracking page shows 'Delivery confirmed; awaiting handoff completion.' Since the package has actually arrived and the buyer contacted us directly to reverse the return, I'd like to cancel the refund procedure before it completes. I can confirm the payment was processed correctly on 14.07.2026, €178.45 was debited, and the fulfillment was completed yesterday. Could you please advise the next steps so we can update our merchant dashboard accordingly? Appreciate your help in coordinating this reversal swiftly, as the buyer is cooperative and expects immediate updates.", "output": {"classifications": [{"task": "queue", "true_label": ["onboarding"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] API settlement case reopened after access fix\n[body] Finance contact here from Northstar Ledger, reconciling a $1,284.40 charge linked to our business integration. We could not access the merchant account, so payment and order management were blocked. The case appeared resolved Tuesday, then reopened after the connector failed again. The prior representative wrote, “API access has been restored; allow 24 hours for settlement activity to normalise.” It is now 14:30, and the charge still appears as pending while the order remains locked. Could you explain this account activity and confirm whether the integration credentials or permissions changed? Our reconciliation report also says the webhook was “recieved” twice. Please outline the next process step.", "output": {"classifications": [{"task": "queue", "true_label": ["outages"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Refund cancellation for duplicate wallet recharge on behalf of my mother\n[body] Greetings, I am writing to request the cancellation of a previously approved refund related to my mother’s wallet recharge from last month. Initially, we identified a duplicate charge of ₹15,000 (INR), credited via UPI after her order was marked as completed in version v3.8 of the app. After our call on 12 May, support updated the status to “refund scheduled” on 14 May. However, last night, while processing a new grocery payment, the same duplication alert briefly reappeared in her transaction feed, but this time the amount disappeared moments later. Since there is now no billing discrepancy in her May and June statements, and the app no longer shows any balance mismatch, kindly halt any further refund processing for this case. I apologise for any inconvenience as this situation seems resolved, and we appreciate your assistance in closing this out.", "output": {"classifications": [{"task": "queue", "true_label": ["refunds"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Challenge on policy impacting joint campaign fulfillment\n[body] As a partner in the upcoming autumn joint campaign with Greenfield Retail, we have encountered consistent failures when trying to reconcile promotional codes across the API integration. Since 02-10-2026 09:15 BST, each attempt to authorize discount applications has returned an error code REF-2035 in our logs, despite following the documented protocol. The last three reconciliation attempts at 02-10-2026 10:00 BST, 02-10-2026 11:30 BST, and 02-10-2026 13:05 BST, all failed without triggering the expected update in the backend system. This has delayed order fulfilment and could impact customer returns and refunds. We request a review of the current policy that may be causing these repeated discrepancies. Please note the business reference JVPT-21X7-998 and contact me at +44 7700 900123 for further details.", "output": {"classifications": [{"task": "queue", "true_label": ["product_feedback"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Ongoing charges after successful delivery, flagged as recurring\n[body] Yesterday, I noticed a new €53,40 debit on our Zoarix company card marked \"delivery release confirmed\"—this always seems to happen just after each annual renewal. Checking our transaction records for 21.06.2027–24.06.2027, every cycle includes a payout reversal after the courier drop-off, along with a third-party notification referencing an account I've never registered: \"You have access to expedited dispatch.\" Your last explanation said the system merges delivery fees, but I’m seeing unexplained charges followed by partial refunds, none matching the messages shown at checkout like \"Estimated delivery before 17:00.\" Please review all related withdrawals, cancel any automatic charges linked to that unknown account, and confirm a full refund to IBAN DE38756329011230487826. Need a written correction for our accounts team.", "output": {"classifications": [{"task": "queue", "true_label": ["refunds"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Confirming proposed fix for renewal notification mismatch\n[body] Hello support. I manage subscriptions for Northstar Loom, and I am confirming that the proposed resolution is acceptable: please correct the renewal state on the mobile app and remove the duplicate charge notice from the unfamiliar merchant profile. A customer approved renewal for plan SL-48291 at 2026-09-18 09:12 UTC. The app showed the plan as renewed at 09:14 UTC, but the account notification did not arrive until 2026-09-19 16:40 UTC and described a charge against an account name our team does not recognise. At 17:05 UTC on the same date, the dashboard still displayed “renewal pending”, although the card processor recorded the transaction at 09:13 UTC on 2026-09-18. The customer has disputed the charge because the notification appeared to reference a different account. We have no phone, address, payment number, or government identifier to provide. Please confirm that applying the correction will preserve the valid renewal and close the misleading alert. This is time-sensitive for reconciliation before tomorrow’s settlement run, but no further customer action is required.", "output": {"classifications": [{"task": "queue", "true_label": ["mobile_app"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Reopened: charge for parcel not shipped\n[body] Hello team, I am reopening ticket #4712 as multiple charges reappeared on checkout for parcels still showing 'Processing: Estimated delivery unavailable' on the orders page. The previous fix did not solve incorrect billing and it's now affecting other customers as well. Please investigate the payment configuration for all orders processed on 2026-03-06. My direct number is 416-311-0882 if you need to discuss findings. Amounts are listed as $89.50 CAD per parcel.", "output": {"classifications": [{"task": "queue", "true_label": ["returns"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Investigation requested: return credit pending after delivery exception\n[body] Hello support, I am the finance contact for Northstar Mercantile and am reconciling invoice NM-48317 dated 2026-09-18. The receipt excerpt lists “integration platform fee — EUR 86.40 — pending,” although our business API setup in v3.8 has not completed the transition to active. A consignment was marked delivered without proof of delivery, so our warehouse rejected the handoff and opened a return. The carrier scan shows the parcel moving back, but the refund remains pending. Please investigate the account setup and confirm whether the charge will be reversed. I can provide additional records if useful. Times are in UTC.", "output": {"classifications": [{"task": "queue", "true_label": ["compliance"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Checkout authorization reversed after approval\n[body] I’m integrating your API for checkout at Northstar Cart, and I’m trying to verify the current status of one payment authorization. Our customer completed checkout on 23.09.2026 at 14:07, and the authorization response was approved at 14:07:12. The API then marked it reversed at 14:09:41, although the card issuer shows no decline. Your earlier explanation suggested a timeout, but our logs show the confirmation request completed before that update. Could you check whether the customer’s identity verification caused the reversal and tell me if we should retry authorization? The affected request is payreq-6F2Q9; contact number +33 6 12 34 56 78.", "output": {"classifications": [{"task": "queue", "true_label": ["identity"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Immediate investigation required: unresolved delivery issue\n[body] A customer on our team reported that despite multiple scheduled drop-offs by Omega Distribution, all attempts to deliver invoice 44BHD-171 failed with no notice left. The tracking page showed \"in transit\" three separate times over the past week, but the status returned to \"pending carrier action\" daily. Previous correspondence from your support representative on 06-10-2026 stated: “The shipment will be re-attempted tomorrow and should arrive by 06-12.” As of today, 06-14-2026, no delivery or update has occurred. Due to our reconciliation deadlines and the potential financial exposure, we request an urgent review into whether the parcel has been lost. Please investigate immediately, as further delays may impact our ability to process necessary returns and refunds.", "output": {"classifications": [{"task": "queue", "true_label": ["account_closure"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Investigation needed: duplicate pending authorization on household account\n[body] Hello support, I am writing for my partner, Lucas Adair, regarding an unexpected issue with checkout on our shared SplendidFrames account. After our last return request was completed in March, everything seemed sorted. However, yesterday at 17:10 EDT, our attempt to purchase SKU-3261 failed at payment confirmation. Minutes later, a second authorization appeared in our transaction summary (ending 76), showing as pending in our RBC banking app alongside an earlier returned amount. Both authorizations are linked to the same shipping address: 4 Pinebrook Ct, Guelph, ON N1L 2V9. Could you verify the account holder's identity and review why this has reoccurred? Happy to provide more details if needed.", "output": {"classifications": [{"task": "queue", "true_label": ["identity"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Escalation regarding disputed checkout authorization\n[body] Dear Merchant Operations Team,\n\nI respectfully request a further review of an unresolved checkout matter. Our transaction history shows an authorization for €186,40 on 14.09.2026, a reversal marked on 15.09, and a second debit entry posted on 16.09, although the dashboard notification identified the account as unfamiliar. The status has remained pending since the apparent reversal, and no explanatory update has reached our console. The associated consignment is prepared for carrier handoff, but we cannot release it without confirming whether the payment authorization is valid. A previous enquiry was answered with general guidance rather than a finding. Kindly reconcile these entries, clarify the unfamiliar notification, and advise whether proof of delivery may be retained against this order. Reference TXN-58304 and merchant case MO-2197.", "output": {"classifications": [{"task": "queue", "true_label": ["billing_disputes"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Subscription renewal failure despite earlier confirmation\n[body] Yesterday, on behalf of my husband, I contacted your support team regarding his subscription for the AlphaChoice account, which was due for renewal on 2026-07-05. Although the error previously encountered ('Renewal could not be processed – please update your payment method') seemed to have been cleared after your agent updated the billing information, a new message appeared during this morning's login: 'API connection interrupted – unable to confirm renewal status.' While the order page now reports 'Payment successful; awaiting final confirmation,' the API dashboard continues to display an outdated status from his last transaction. I would appreciate your advice on whether we should retry the process, as we have already provided his NRIC (S1234567D) and our mobile number (8765 1234) for prior authentication. Kindly let us know the next best step at your earliest convenience. Thank you for your continued assistance and patience in this matter.", "output": {"classifications": [{"task": "queue", "true_label": ["api"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Unexpected reversal of payment after integration test\n[body] During our business API integration, the payment of ₹1,25,000 was approved at 10:15 AM but reversed by the system at 10:17 AM without alerting our account. Because the audit log shows no manual cancellation, we need an urgent review to identify if this was a system error or fraudulent activity flagged under another profile. The account admin flagged a suspicious login shortly before this event. Please advise on the investigation steps to reconcile this swiftly.", "output": {"classifications": [{"task": "queue", "true_label": ["general"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Request to ensure account closure is correctly processed before new order cycle\n[body] As the administrator for Elmatix GmbH I am respectfully requesting urgent verification that our company profile is fully deactivated ahead of the upcoming product selection term Each year following plan renewal on 22.03 the checkout prompts a message stating Pending account review prevents completing payment 12,00 € despite closeout steps previously completed I ask that you immediately investigate this error and formally confirm our account is marked closed Kindly note VAT ID DE246124143 and address Spitalgasse 17, 90403 Nürnberg should be removed from any active records Thank you for your assistance", "output": {"classifications": [{"task": "queue", "true_label": ["account_closure"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Checkout outage conflicts with no-duplicate-authorization policy\n[body] I administer the company profile for Northstar Atelier and was evaluating the Atlas Ledger subscription before purchase. At 09:12 UTC on 2026-09-21, checkout failed immediately after I selected the annual plan; the page showed a timeout and no confirmation. I tried again at 09:16 UTC, with the same result. At 09:19 UTC, the account activity screen updated to show a pending authorization hold, although the checkout page still reported failure. A second pending hold appeared after the retry at 09:23 UTC. Your policy says failed checkouts should not create duplicate authorizations, so this appears inconsistent. Please investigate whether either hold will be captured, and reverse both if no order exists. The repeated failures are blocking our product assessment, and the status page has not updated since 08:50 UTC.", "output": {"classifications": [{"task": "queue", "true_label": ["outages"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Confusing transaction issues on my sister's account\n[body] Good afternoon, I am reaching out on behalf of my sister who resides in Chennai. Over the past week, she has made three attempts to top up her prepaid mobile service via your portal. Each time, the payment is confirmed on her bank statement by 10:45 PM IST, but the service balance on her app only updates after 1:30 AM the following day. Additionally, there have been two instances where the transaction failed, yet the amount of ₹1.5 lakh was debited and later reversed after several hours. She feels quite distressed by these delays and inconsistencies, especially as she relies on her phone for work calls. We apologize for any inconvenience caused, but would appreciate your prompt attention to clarify why the account isn't reflecting the recharge immediately and why those reversal delays happened. Thank you for your understanding and assistance.", "output": {"classifications": [{"task": "queue", "true_label": ["general"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] <phone>\n[subject] Account closure required after repeated payment errors\n[body] Hello, I’m calling for my husband, Oliver Thomas, who’s listed on our family account with Veyronia Market. We completed checkout for order UKB-67A4-PQ22 on 14-06-2024, paying £229.90, and received a confirmation. But less than an hour later, we were notified the payment authorisation failed and the order was automatically cancelled. This isn’t the first time—similar problems have happened before with different recent orders. The notification suggests there may be a recurring issue with the merchant’s account set-up. We’d like Oliver’s profile fully closed and our details removed from the system. I can confirm our address is 22 Manor Crescent, Sheffield, S17 8WN. Please action this as soon as possible and confirm the account has been deleted.", "output": {"classifications": [{"task": "queue", "true_label": ["account_closure"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Inquiry on Account Closure Process and Pending Payment Status\n[body] After the latest order update, I would like to respectfully inquire about the current status of account closure for my firm’s profile, which I submitted last week on 12 March 2024 at 15:45 IST. Despite multiple attempts to finalize closure through the dashboard on 14 March at 10:30 IST and again this morning at 09:05 IST, the account remains active. Additionally, payment transactions initiated on 13 March at 16:15 IST have not been reflected in the ledger updates as of 14 March 11:00 IST. Would you kindly clarify the reasons behind these discrepancies and inform me of any further actions required? I appreciate your guidance as I continue integration efforts.", "output": {"classifications": [{"task": "queue", "true_label": ["account_closure"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Subscription partnership renewal: unresolved API payout issues and duplicate confirmation\n[body] While we were able to finalize the renewal for our joint premium subscriptions with Seraphix Partners on 2026-09-04 (UTC+2), our integration was met with two issues that blocked a smooth rollout. First, our system received the API response \"success: payment_created\" but no corresponding payout initiated to our partnership ledger; simultaneously, a checkout message appeared saying \"Your subscription was renewed successfully,\" yet a second, duplicate confirmation email was triggered to all recipients. Last time I reported this, support mentioned escalating to the technical team, but there has been no follow-up or resolution after four business days. I request an urgent investigation by your partnerships management to clarify both anomalies, as further delayed payouts will impact our mutual affiliate reporting.", "output": {"classifications": [{"task": "queue", "true_label": ["partnerships"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Reopened: Subscription fee refund after conflicting renewal alerts\n[body] Hi there, I'm hoping you can help clarify what's happened with my subscription renewal. I received an alert on 10-03-2027 that my Premium Coffee Plan (v3.8) renewed successfully, and my account was charged £19.99. However, when I checked the order page today, it now says \"Renewal incomplete: payment under review\". Last week, the case was apparently resolved after my card was charged the first time, so I'm confused why this charge appeared again and the status is different. I'm now seeing a delivery-status note: \"Paused – account renewal pending verification.\" Can you please look into the duplicate charge and confirm if a refund should be processed? I'm not worried, just want to make sure I'm not being billed twice. Happy to provide any extra details if you need them.", "output": {"classifications": [{"task": "queue", "true_label": ["refunds"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Confirmation to proceed with account closure request\n[body] Dear Support,\n\nI accept your proposal to close my account following our prior discussion about my recent purchase issue. To confirm, the checkout failure on 13 June 2026 at 17:54 SGT resulted in two authorisations (SGD 92.10 each) showing as pending on my bank slip, although only one item was intended for purchase. The previous temporary hold released last night but the secondary charge remains. Thank you for clarifying this in Ticket CP-88214. Please close my account as agreed, and confirm if any further action is needed from my side. Attached is the relevant receipt excerpt as evidence.", "output": {"classifications": [{"task": "queue", "true_label": ["account_closure"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Reconciliation reversal and verification hold\n[body] Good afternoon. I am calling as the finance contact for Nivara Housewares to request corrective action on our account maintenance review. Yesterday, the ₹1.18 lakh authorisation for our supplier settlement completed successfully, but it was reversed this morning, and the related fulfilment record now shows pending verification. A separate dashboard message also states that our settlement profile requires renewed verification. Your representative previously advised, “The reversal is temporary and the funds will be restored once the account check is completed.” Kindly confirm whether the reversal and the verification hold have a common cause, restore the authorisation if appropriate, and advise which account documents are required. We are reconciling the ledger and do not require an urgent response; a written update within the normal service period will suffice.", "output": {"classifications": [{"task": "queue", "true_label": ["outages"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Clarification Needed on Recent Compliance Check Failure\n[body] Hello, I am the administrator for Acropel Group’s merchant account. During yesterday’s profile update, a compliance verification was automatically triggered as part of our regular maintenance. The system flagged our VAT ID (DE123456789) as invalid and temporarily restricted payout access, even though no changes were made to our legal details. At checkout, the message stated, “Unable to process: Account compliance issue – contact support.” Could you confirm the status of this check and advise how to resolve this? I apologize for any inconvenience caused, and can provide further documentation if needed. Our registered address is Calvinstraße 12A, 12489 Berlin. Thank you for your prompt attention to this matter.", "output": {"classifications": [{"task": "queue", "true_label": ["compliance"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Unrecognised charge at checkout following renewal\n[body] Hi, this is Megan Porter from Ledbury Stationery. I need to raise an urgent issue with payment authorisation during our monthly renewal. Each cycle, after confirming our cart, the checkout screen displays a message stating, \"Payment of $79.95 AUD declined due to account limitation.\" This morning, we noticed a pending debit for the same amount, but our records do not match any completed orders for today. Previously, you've assured us the renewal charge wouldn't process unless the order is confirmed. However, each time, we receive an unfamiliar account notification and no corresponding invoice. This is impacting our financial reconciliations and making monthly close difficult. Please investigate and correct this recurring charge mismatch as soon as possible.", "output": {"classifications": [{"task": "queue", "true_label": ["payments"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Escalation: app listing remains pending after merchant review request\n[body] I am writing on behalf of Northstar Pantry Pte. Ltd. We are evaluating whether to launch our new grocery range through your merchant app, but the product submission has stayed in “pending” status since yesterday afternoon. The earlier reply advised us to wait for the normal review cycle, which has now passed without any change. When I check the merchant endpoint, the request returns HTTP 202 with an empty review_state field, although the submission reference is accepted. This is the only issue preventing our pre-purchase assessment. Please investigate why the mobile app has not reflected the completed review transition and either refresh the status or advise the exact next step. We are frustrated by the delay, but would appreciate a clear response by 16:00 Singapore time. The proposed price is S$38.90.", "output": {"classifications": [{"task": "queue", "true_label": ["mobile_app"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Request for Account Partnership Access Clarification\n[body] Greetings,\n\nI am a developer with PayFleet, currently integrating our platform with NeerajaMart's Direct API to automate the order fulfillment stage for high-volume transactions prior to package dispatch. Yesterday, our account was temporarily restricted following a notification referencing irregular sign-in attempts and issues with settlement authorisation for orders exceeding ₹1.2 lakh. Although access was restored after escalation, I received another automated communication today indicating that our payment privileges have again been limited. This hinders our ability to process, review, or modify live orders, impacting the seamless handoff to logistics partners. Please clarify the underlying partnership access conditions and whether formal documentation is required to reactivate our direct integration. You may contact me at +91-99111-23568 for verification. I appreciate your assistance and await your response at the earliest convenience.", "output": {"classifications": [{"task": "queue", "true_label": ["partnerships"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Ongoing integration friction with partner dashboard API and consignment notifications\n[body] This ticket is being reopened following your last update on case PR-44ZQ-1197. Despite following the integration protocol advised by Leon on 2026-03-08T10:45+02:00, our merchant dashboard still receives consignment dispatch alerts referencing account ID 2X21-881-RZT, which does not match any of our partner profiles. The most recent notification included a disputed charge and cited delivery handoff failed due to proof-of-delivery mismatch. Your policy requiring manual overrides in such situations is causing operational latency. Quoting Leon: \"Once the API triggers a notification for an unfamiliar ID, escalate to L3 team for verification.\" As a seller, I need clarification on how handoff verification aligns with partnership SLAs. Please review the attached case notes and advise recurrence prevention steps. You may reach me directly at +44 7551 640993 if further confirmation is required.", "output": {"classifications": [{"task": "queue", "true_label": ["partnerships"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Renewal charge not reconciled after returned orders\n[body] A customer on our team reported that the same reconciliation problem has appeared after each monthly renewal since 2026-06-01. Several orders were delivered and then returned, but the merchant account continues to show the renewal charge as open instead of linking it to the refund entries. I am the finance contact reviewing the ledger and apologise for raising this again after the earlier response. Your representative wrote, “The adjustment should attach automatically once the return is scanned; please allow two business days.” More than a week has passed after each scan, and the pattern now affects six customer orders under merchant profile MRC-48271. Could you escalate this to the payments configuration team and confirm whether the renewal rule is applying the wrong transaction type? We are not disputing the returned goods themselves; the issue is the repeated charge matching failure. The latest affected batch was processed on 2026-08-19 at 09:30 UTC. Sorry for the extra detail, but our month-end close is approaching and the account still does not balance.", "output": {"classifications": [{"task": "queue", "true_label": ["payments"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Persistent errors during payment gateway integration\n[body] As the designated account administrator for Greenfield Traders Ltd., I must report ongoing issues encountered during the API integration phase for our payment processing module. Following our last support correspondence dated 21-04-2027, my development team has attempted multiple transaction initiations between 09:15 and 14:30 on 23-04-2027, yet all attempts were met with failure responses from your payment endpoint. The errors consistently show a \"timeout\" status with no transaction settlement. Notably, the internal logs record a payment request at 11:47 accompanied by a failure notice at 11:48. The cumulative effect has stalled order fulfillment workflows and delayed our invoice reconciliation. This sequence includes both payment authorization and post-payment status confirmation phases. Additionally, some transactions that appeared initially successful were later invalidated without explanation. Please review these repeated failures with urgency; the disruption is severely affecting our operational capability. Should you require verification or further details, I can be contacted directly at +44 20 7946 0987. Awaiting your prompt and thorough update to resolve these critical integration setbacks.", "output": {"classifications": [{"task": "queue", "true_label": ["outages"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Escalation regarding suspicious refund reversal on renewal invoice\n[body] Dear Support, as the account administrator for NeelWeb Solutions, I am concerned about a refund reversal related to our recent subscription renewal. Initially, a payment of ₹1.75 lakh was processed successfully, but subsequent API logs indicate a failed refund attempt flagged under transaction ID TXN-993423. We also received an unexpected alert of a new linked account that we do not recognize. Previous assistance suggested the issue was resolved; however, the error persists, and our billing dashboard shows inconsistent data. Please escalate this matter urgently to verify potential fraudulent activity. Apologies for the inconvenience, but your prompt support is critical.", "output": {"classifications": [{"task": "queue", "true_label": ["fraud_review"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Feedback: Invoicing & shipment tracking discrepancies\n[body] Hello again, I’m the financial operations contact for procardholder supplies at Prismix Inc. We are following up because our last two chats with frontline support did not address our reconciliation concern. According to our ledger, shipment No. NLX-1327 was recorded as paid on 2027-11-13 14:17 for CAD$164.00, the exact invoice from your initial fulfillment summary. However, the transaction history downloaded from your merchant portal yesterday shows a “ready for fulfillment” status at 17:50 with no waybill assigned, plus a negative line entry for the same amount at 18:03.\n\nOur accounting workflow expects a clear reference for the expected receipt, but the reversal is blocking our year-end handoff and causing confusion with auditors. We are not seeking a return at this time but need to understand if this processing sequence means the order will dispatch or if we should expect a future credit. Are your refund triggers explicit in the billing report, or must we wait for a shipment release? Would also appreciate insight into transaction code NLX-1327 to clarify. Thank you. – Mira, finance team", "output": {"classifications": [{"task": "queue", "true_label": ["product_feedback"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Fulfillment status changed, but return workflow has not started\n[body] According to the notice I received, parcel Kestrel-492 was marked “ready for dispatch” at 2026-09-21 08:10 UTC, then changed to “address issue” at 08:47 UTC. Our integration recorded the customer’s delivery confirmation at 08:32 UTC, so the sequence is unexpected. The order has not left the warehouse, and the recipient now wants to return the purchase and receive a refund if delivery cannot be restored. I maintain the order-status API for Northvale Systems and have attached request timestamps from 08:30–09:00 UTC. Could your team investigate which event caused the reversal and advise whether we should create a return case or wait for a corrected dispatch update? I am happy to provide additional logs.", "output": {"classifications": [{"task": "queue", "true_label": ["fraud_review"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Unexpected payment during household subscription renewal\n[body] Could someone clarify why my spouse’s household subscription renewed on 09-12-2026 when we had removed my payment permission from the profile? I am calling on behalf of the profile owner, and I apologize for the confusion, but please reverse the completed renewal payment and restore the correct account permissions. The shipment arrived after renewal, so fulfillment itself was completed, and we contacted post-delivery support when the package contained the wrong accessory. The receipt excerpt reads: “VelaHome Plus Annual Renewal — 09-12-2026 — $129.00 — Payment status: captured — Renewal reference VH-62841.” We did not expect this charge because the saved card was not supposed to remain authorized for recurring billing. Please verify the profile, cancel the unintended renewal, and confirm whether the delivered item can remain while the payment is corrected. For verification, the profile owner’s phone number is +1-555-016-9042. No additional purchase is being requested; we only want this single completed renewal corrected.", "output": {"classifications": [{"task": "queue", "true_label": ["payments"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Confirmation needed for return compliance case\n[body] A customer on our team reported that their refund for a returned consignment was delayed despite evidence of handoff last week. The system continues to send \"return incomplete\" notifications even though Royal Parcel records confirm delivery on 20-03-2026. We have now attempted resolution twice, each time receiving automated compliance alerts about a possible regulatory breach and mismatched proof of delivery. Can you confirm if accepting the submitted documents will finally resolve this case? If you need the claimant’s full address or payment card last four digits, let me know. We want to ensure compliance is maintained on both sides.", "output": {"classifications": [{"task": "queue", "true_label": ["compliance"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["high"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Cancel recurring renewal orders before dispatch\n[body] Could someone clarify why our merchant configuration is creating fulfilment orders for every renewal, despite the account being set to require manual approval? The issue has occurred after each renewal since 14-08-2026 and now affects several customer orders awaiting dispatch. Our API returns error code CFG-418 with the message “approval policy not recognised”, while the dashboard still shows automatic release enabled. As the company account administrator, I request cancellation of these pending orders and confirmation that the configuration complies with your fulfilment controls. Please investigate the recurring behaviour and advise on the required correction.", "output": {"classifications": [{"task": "queue", "true_label": ["compliance"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Follow-up on shipment delay compensation for multi-order error\n[body] After the initial delay last week was supposedly resolved, I noticed during my most recent transaction at 15:40 today that the carrier still misrouted packages for three customers, including my own. My invoice number CN-452982 shows a $35.50 credit meant to cover inconvenience costs; however, it isn't reflected in my account balance. The merchant indicated the issue was due to a configuration error affecting several shipments; I would like to confirm if issuing additional compensation is the agreed resolution before proceeding. I appreciate your attention to this recurring problem.", "output": {"classifications": [{"task": "queue", "true_label": ["partnerships"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Escalation: \"Payment failure at checkout after renewal\" persists\n[body] This is Siddharth Rao, administrator for Saffron Exports Pvt Ltd. We're again blocked at checkout: after our enterprise plan auto-renewal, every payment attempt triggers \"UPI mandate could not be verified\". Last time, updating the GSTIN in the company profile resolved it, but the same step fails now. Repeated transaction history: Rs 1.35 lakh debited, all reversed. Please directly activate onboarding so recurring gateway issues stop. Registered PAN is ABCDP1234E.", "output": {"classifications": [{"task": "queue", "true_label": ["onboarding"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Inquiry on delayed shipping updates after subscription renewal\n[body] Although the payment appears complete, every time our subscription renews on the 05-15-23, the system oddly takes until 05-17-23 to update the shipment status for orders processed through version v3.8 of your platform. This recurring delay confuses customers who see their order as unshipped initially. Our seller account ID is MER-56473, in case you need it for lookup. Can you clarify if this lag is a known issue, and advise on how we might expedite accurate shipping notifications? Previous explanations pointing to processing time don't fit when tracking shows no activity on renewal dates. Hoping for a straightforward fix this time.", "output": {"classifications": [{"task": "queue", "true_label": ["shipping"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Cancellation request due to recurring billing issue\n[body] As a buyer integrating with ZephyrTrade API, I received a notification on 23.05, 14:32 stating a charge of €89,90 was processed on my account. I had believed the billing problem had been resolved last week after contacting support, but this new charge appeared without any prior notice. The transaction corresponds to a vendor I do not recognize within the system. I am requesting an immediate cancellation of the connected service and a review of this recurring charge. Despite the frustration this causes during our integration phase, I appreciate a prompt response to prevent further issues.", "output": {"classifications": [{"task": "queue", "true_label": ["partnerships"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Subscription renewal failed and duplicate invoice sent\n[body] Hi, I am following up about my recurring Seakraft News subscription problem. Last time, my renewal completed after support updated my card, but this month the payment failed again and I received two invoices. Invoice excerpt: “Inv# SKN-0237 - S$19.90 billed at 16:12 06/06/2026 to MR. LIM KAI, (+65 8555 7282).” Please investigate as the duplicate billing returned. Thanks.", "output": {"classifications": [{"task": "queue", "true_label": ["api"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Misleading charge on delivered parcel\n[body] Hi there, I’m reaching out as I’m quite puzzled. Our last batch shipped out on 12-05-2027, and the records show all parcels delivered successfully. After talking with your team, I was told the payment we received was in full, but our accounts officer flagged a discrepancy in the total charged. The support rep, Laura, mentioned it was likely a system error and suggested to wait, yet it’s been over a week with no update. Could you please review our transactions and rectify any errors? Our merchant ID is MERC3045. Looking forward to a prompt fix.", "output": {"classifications": [{"task": "queue", "true_label": ["general"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] email\n[subject] Urgent: Refund not processed after order cancellation\n[body] Dear Support Team,\nI reopened case MRK-30921 regarding a refund for order TG-9843-SJM, which was cancelled last week. The order page still shows ‘Pending refund approval’ and ‘Shipment cancelled’, yet the buyer hasn’t received any notification or amount credited. I verified the payment method linked to the merchant account ending in 5621 but no transaction has been reversed. Please prioritize this issue and update me on the refund status promptly as the customer is awaiting resolution. Date of cancellation: 12,03,2027. I expect corrective action without further delay.", "output": {"classifications": [{"task": "queue", "true_label": ["refunds"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Partner Onboarding Discrepancy in Promotional Access\n[body] Greetings, this is Priya from Fernway Distribution. We received the automated onboarding notification last evening confirming activation of our partner dashboard for the Capri Granule launch. However, when our technical team attempted sign-in, we were unable to access real-time inventory data, and the promotional rate link is missing from the pricing module. Both anomalies occurred after receiving the system-generated completion alert at 19:21 IST. The notification referenced only the dashboard status, not feature accessibility. Could your onboarding specialists investigate both the missing inventory connection and absent rate offer as soon as possible? We need confirmation before our buyers' evaluation call tomorrow. No sensitive information shared during the process.", "output": {"classifications": [{"task": "queue", "true_label": ["onboarding"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] chat\n[subject] Clarification on compliance issues affecting merchant onboarding\n[body] Good afternoon, I am in the process of listing new products with Velconx Ltd. However, during checkout, a persistent alert states that the compliance review is pending clearance before final approval; I understand this is crucial but kindly request explicit details on the criteria causing the delay. Given that my business is eager to commence sales and the funds are already earmarked for initial inventory, prompt resolution would be greatly appreciated. I trust you will treat this matter with the due formality it warrants. Thank you very much. Contact number: +65 9123 4567.", "output": {"classifications": [{"task": "queue", "true_label": ["compliance"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["low"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Escalation: Urgent request for return initiation stuck at pending\n[body] A customer on our team reported that the product return initiated via API integration has remained at a 'pending' status for more than 36 hours, far exceeding the typical processing time. The account involved is KMF-CORP-5809. Our transaction logs show the request was submitted on 15 May at 09:42 SGT and acknowledged at 09:46, but no movement since then—subsequent entries confirm no handover to return logistics. We kindly request immediate manual intervention to release the return process, as the client’s payment reversal is contingent on this action. You may reach me via +65 6123 4008 for verification.", "output": {"classifications": [{"task": "queue", "true_label": ["returns"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["yes"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] phone\n[subject] Repeated checkout update failure before dispatch\n[body] According to the notice I received, my purchase was accepted at 09:12 on 18-09-2026, but the order page still showed “awaiting payment” at 09:26. I tried again at 09:31 and 09:44; each attempt produced the same stale status, although £27.50 was displayed as authorised. Nothing has been dispatched. Please investigate the repeated updates and clear the order for fulfilment, if payment is valid. I’m happy to confirm details.", "output": {"classifications": [{"task": "queue", "true_label": ["fraud_review"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["normal"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |
| {"input": "[channel] portal\n[subject] Follow-up on compliance status for delayed return shipment\n[body] As a developer working on API integration with your parcel tracking system, I'm following up on case #C-99347 that was recently reopened after being marked resolved last week. Our records show that the return package was logged in transit as of 09/12/2026 16:30 PST; however, the system still reflects \"pending delivery confirmation\" as of 09/18/2026 14:10 PST. Since the carrier transit phase extended beyond expected timeframes, it may impact compliance with your stated return/refund policies. Could the compliance team please provide updated status and confirm if any procedural adjustments are required to avoid refund processing delays? Thank you.", "output": {"classifications": [{"task": "queue", "true_label": ["compliance"], "labels": ["billing_disputes", "refunds", "shipping", "returns", "identity", "payments", "outages", "mobile_app", "api", "account_closure", "compliance", "fraud_review", "onboarding", "partnerships", "product_feedback", "general"], "multi_label": false}, {"task": "urgency", "true_label": ["critical"], "labels": ["low", "normal", "high", "critical"], "multi_label": false}, {"task": "contains_pii", "true_label": ["no"], "labels": ["yes", "no"], "multi_label": false}]}} | |