Scoutinternal

Custodial Withdrawal Requests — Bulk Processing for Fund Entities

Custodial Withdrawal Requests — Bulk Processing for Fund Entities

Problem

Customers associated with various custodial fund entities (e.g., DARMA Capital, ETC, Interledger, Bloccelerate, Salt Platform, Hard Yaka, Blockblox, Trade Republic) submit withdrawal requests that are processed through BitGo's custodial withdrawal workflow. These tickets represent individual withdrawal requests that are created, logged, and resolved as part of standard custodial operations. The tickets in this cluster were bulk-processed by a single agent in a short time window, suggesting a batch administrative action or routine queue clearance rather than a novel technical issue.

Diagnostics

  • Ticket pattern: Check whether the tickets were created and resolved at nearly the same timestamp by the same agent (e.g., all resolved by the same created_by ID within a single session on the same date). This indicates batch processing rather than individual troubleshooting.
  • Entity name in subject line: Identify the fund or client entity referenced in the ticket subject (e.g., "DARMA - Withdrawal Request", "ETC - Withdrawal Request", "Trade Republic - Custodial Withdrawal Germany", "Interledger - Withdraw Request", "Salt Platform - Withdrawal Request", "Hard Yaka - Withdrawal Request", "Bloccelerate - Withdrawal Request", "Blockblox - Withdrawal Request").
  • Resolution confidence: These tickets carry a "medium" resolution confidence rating. Confirm whether the withdrawal was actually executed or simply administratively closed.
  • Salesforce reference: Each ticket has an associated Salesforce case number (SF#). Cross-reference the SF case to verify the withdrawal status and any downstream processing details.
  • No diagnostic content available: The source tickets contain no problem descriptions, no agent diagnostic notes, and no resolution details beyond timestamps. If a customer references one of these tickets, the agent should look up the corresponding Salesforce case for actual transaction details.

Resolution

Scenario: discord-username-discordcom-ppll#bulk-custodial-withdrawal-processing

Trigger: A large batch of custodial withdrawal request tickets for multiple fund entities were created and resolved by the same agent within a very short time window, with no substantive problem description or resolution notes recorded.

Signals: withdrawal request, custodial withdrawal, DARMA, ETC, Interledger, Bloccelerate, Salt Platform, Hard Yaka, Blockblox, Trade Republic, bulk processing, batch close

Steps:

  1. Identify the Salesforce case number (SF#) associated with the ticket.
  2. Open the corresponding Salesforce case to retrieve the actual withdrawal details, including asset type, amount, destination address, and processing status.
  3. If the customer is inquiring about the status of their withdrawal, confirm whether the withdrawal transaction was submitted on-chain and provide the transaction hash if available.
  4. If the withdrawal has not yet been executed despite the ticket being marked resolved, escalate to the custodial operations team to clarify whether the batch closure was administrative (ticket hygiene) or indicative of completed processing.
  5. For entity-specific workflows (e.g., "Trade Republic - Custodial Withdrawal Germany"), verify whether any region-specific or entity-specific approval processes apply.

Notes: The source tickets contain no problem descriptions, agent diagnostics, or resolution details — only timestamps and the resolving agent ID. All 50 sampled tickets share the same agent and were resolved on 2026-02-09 within a roughly two-hour window. This strongly suggests a bulk administrative action (e.g., queue cleanup or batch confirmation of completed withdrawals) rather than individual issue resolution. Any customer follow-up on these tickets should be resolved by consulting the linked Salesforce case rather than the ticket record itself.

Related

  • custodial-enterprise-overview — General overview of custodial enterprise management and user roles relevant to withdrawal authorization.
  • none identified — The source tickets lack sufficient detail to confidently link to other specific articles.