Scoutinternal

Travel Rule Compliance – Auto-Acknowledgment Loop for Virtual Asset Inquiries

Travel Rule Compliance – Auto-Acknowledgment Loop for Virtual Asset Inquiries

Problem

Customers submitting Travel Rule or virtual asset compliance-related inquiries (such as VASP addition requests, beneficiary information submissions, or AML/CFT compliance questions) receive an automated "Case Received" acknowledgment from BitGo. In a large number of instances, these tickets contain only the auto-acknowledgment text with no substantive resolution recorded. The ticket shows only the standard case-creation confirmation and no evidence of agent investigation or a personalized response being logged in the ticket body itself. This affects all product areas where Travel Rule or compliance workflows generate inbound cases.

Diagnostics

  • Open the Salesforce case linked in the ticket (SF# number in the subject line, e.g., SF#00173703, SF#00176370, etc.) to check whether a substantive reply was sent outside the Freshdesk thread (e.g., directly in Salesforce or via email).
  • Verify the ticket creator ID — all 50 sampled tickets were created by the same automated system user (158009540847), confirming these are system-generated acknowledgments rather than agent-authored responses.
  • Check whether the subject line shows repeated "Case Received" concatenation (e.g., "Case Received - Case Received - Case Received …"), which indicates the auto-reply loop triggered multiple times for the same inbound request.
  • Look at the timestamp cluster — tickets in this batch were created in tight bursts (e.g., dozens within the same minute on 2026-02-09 between 21:04–21:07 UTC and 22:10–22:22 UTC), suggesting a bulk ingest or automation event.
  • Confirm whether the underlying customer request is visible in the linked Salesforce record or whether only the acknowledgment template was captured.
  • Check the resolution confidence field — all sampled tickets show "medium," meaning no agent explicitly confirmed the issue was resolved.

Resolution

Scenario: travel-rule-comply-virtual#auto-ack-loop-no-resolution

Trigger: Ticket body contains only the standard "Case Received" auto-acknowledgment template with no personalized agent response, and the subject line shows repeated "Case Received" concatenation.

Signals: Case Received, travel rule, comply, virtual asset, SF#, auto-acknowledgment, no resolution, repeated subject, 158009540847

Steps:

  1. Open the corresponding Salesforce case using the SF# in the ticket subject (e.g., SF#00173703).
  2. Determine whether a substantive response was already sent to the customer through Salesforce or another channel outside Freshdesk. If yes, document the resolution in the Freshdesk ticket and close it.
  3. If no substantive response exists, identify the customer's original request. Common Travel Rule inquiries include:
    • VASP addition requests
    • Beneficiary / sender information submissions
    • Questions about AML/CFT compliance requirements
    • Travel Rule threshold or applicability questions
  4. Route the ticket to the appropriate team:
    • Compliance team — for VASP reviews, AML/CFT policy questions, or sanction-screening inquiries.
    • Customer Success Manager — for account-specific Travel Rule configuration or VASP addition timelines.
    • Support engineering — if the auto-acknowledgment loop itself needs investigation (e.g., the repeated "Case Received" subject concatenation indicates a system bug in the case-creation automation).
  5. If the customer is asking about Travel Rule applicability, refer to the existing KB article "BitGo's Global Regulated Entities FAQs" for standard answers (e.g., Travel Rule does not apply to hot wallets; Travel Rule does not apply to fiat transactions).
  6. For VASP addition timeline questions, advise the customer to contact their Customer Success Manager or support@bitgo.com.
  7. Once the underlying request is addressed, update the Freshdesk ticket with the actual resolution and close.

Notes: - The auto-acknowledgment loop (repeated "Case Received" in the subject) appears to be a systemic automation issue that generated hundreds of near-identical tickets in a short time window. If this pattern recurs, escalate to the support engineering team to investigate the case-creation automation pipeline.

  • These tickets by themselves do not contain the customer's original question — the actual content lives in the linked Salesforce record.
  • Resolution confidence on all sampled tickets was "medium," meaning none were confirmed resolved. Treat each as potentially still open until the Salesforce record is checked.

"Hello there, We would like to acknowledge that we have received your request and a case has been created. A support representative will be reviewing your request and will send you a personal response (usually within 24 hours)." (ticket #111689)

Related