rp369 Sportsbook & Casino – Liga 1, Piala AFF, QRIS & e-wallet Banking

Support channels

We at rp369 provide support through three channels tailored to different needs. Our in-app live chat offers real-time help for account access, payment status, and game questions — English-speaking agents respond during business hours with typical response times of subject to verification. Email support handles detailed inquiries about withdrawal delays, KYC rejection reasons, and bonus terms; replies arrive within 24 hours on weekdays. The Help Center contact form routes technical issues (crashes, slow loading) and account recovery requests to specialized teams. For urgent matters, escalation from any channel to a support manager is available after an initial response. All channels maintain documented response windows so users know when to expect updates. Multi-language support is available upon request; primary interface language is English.

Common request categories

Login assistance forms the largest category of support requests — forgotten passwords, two-factor authentication resets, and account recovery after extended inactivity. Our team handles password resets via email verification within subject to verification; two-factor resets require KYC document re-confirmation and take 24–48 hours for security reasons. KYC verification rejection is the second common request type. Rejections occur when submitted ID photos are blurry, document edges are cut off, or the selfie does not clearly show both face and document. Resubmission is allowed once; clear, well-lit photos typically pass on the second attempt. Withdrawal delays are tracked and communicated — e-wallet transfers (DANA, OVO) rarely exceed subject to verification; bank transfers (QRIS, BCA) may take subject to verification during high-load periods. Users receive a ticket reference to track progress. Technical issues like app crashes or slow page loading are logged and diagnosed within 24 hours, with workarounds provided (browser alternative, app reinstall) while we investigate.

Response window expectations

rp369 commits to the following general response windows, though exact times vary by issue urgency and time of submission. Account access and payment tracking requests receive first response within subject to verification during daytime hours (8 AM–10 PM Jakarta time) and within 2 hours during off-hours. Bonus and promotion clarification queries are answered within 4 hours as responses require cross-check with the active promotion calendar. KYC document reviews complete within 24 hours of submission for standard cases; edge cases with name mismatches or unclear documents may take 48 hours. Withdrawal status inquiries receive real-time updates via the account dashboard; if an unexpected delay occurs, support proactively notifies the user. Bank holidays (Idul Fitri, Idul Adha, Imlek) may extend response windows by one business day. Users submitting after 10 PM will receive first response the following morning. Escalations to management take an additional 24–48 hours and are used only when standard support cannot resolve the issue or the user requests higher-level review.

Escalation flow

When a support ticket requires escalation, it moves to a senior agent or manager after the initial response. Escalation triggers include: disputes about bonus eligibility (when the user disagrees with terms interpretation), repeated failed KYC attempts (3+ rejections), withdrawal amounts exceeding normal limits, and requests for exception handling (e.g., higher daily deposit cap). To escalate, reply to your support email with "Request Escalation" in the subject and explain why you believe the initial response was incorrect or insufficient. The escalated ticket receives a manager review within 48–72 hours. Provide all relevant documentation — screenshots, transaction IDs, email confirmations, bonus code copies — to speed resolution. Once escalated, the ticket is tracked separately and you receive updates directly from the manager's team. Most escalations conclude with either approval of the requested exception or a detailed explanation of why policy does not permit the exception. Our goal is fair, consistent application of terms with transparency about constraints.