Scoutinternal

Client Account Status Change — Voluntary Termination

Client Account Status Change — Voluntary Termination

Problem

BitGo receives internal requests to change a client entity's account status to "Voluntary Termination" (or "Closed - Voluntary Termination"). These tickets are generated in bulk as Salesforce-linked status-change records (prefixed with "SF#") and represent the administrative closure of client accounts that have elected to terminate their relationship with BitGo. The tickets typically follow a standardized subject-line format: "Status change for [Entity Name]: Voluntary Termination" or "Status change for [Entity Name]: Closed - Voluntary Termination." Occasionally, a non-standard or unrelated ticket may be clustered with these records.

Diagnostics

  • Verify the Salesforce case link: Confirm the ticket subject contains an "SF#" reference number and that the corresponding Salesforce record exists and is in a terminal/closed state.
  • Confirm the entity name: Check that the entity name in the ticket subject matches the client record in the internal CRM / Salesforce. Entity types observed include corporations (Ltd, Limited, Pte, S.A., GmbH, SAPI DE CV, OU, N.V., s.r.o., FZE, Inc.), trusts, and individuals.
  • Distinguish status variants: Two labeling conventions appear across tickets:
    • "Voluntary Termination" (e.g., Ticket #13639, #17073, #20943)
    • "Closed - Voluntary Termination" (e.g., Ticket #14857, #14877, #28969) Both indicate the same outcome — client-initiated account closure. Confirm which label the Salesforce record carries.
  • Check for non-standard tickets: Occasionally a ticket in this cluster is unrelated to a voluntary termination status change (e.g., Ticket #2170 — a petition-related email, Ticket #20486 / #28140 — service-delivery queries for a specific client). Identify these by the absence of the "Status change for … Voluntary Termination" subject pattern.
  • Check for alternative statuses: At least one ticket (Ticket #27979) uses the status "Frozen" rather than "Voluntary Termination." Confirm the intended target status in Salesforce before processing.

Resolution

Scenario: voluntary-termination-change-status#standard-voluntary-termination

Trigger: The ticket subject follows the pattern "Status change for [Entity Name]: Voluntary Termination" or "Status change for [Entity Name]: Closed - Voluntary Termination" and a valid SF# case reference is present.

Signals: voluntary termination, closed, status change, SF#, account closure, entity termination

Steps:

  1. Open the Salesforce case using the SF# number referenced in the ticket subject.
  2. Confirm the client entity listed in the Salesforce record matches the entity name in the ticket subject.
  3. Verify the account status in Salesforce has been updated to "Voluntary Termination" or "Closed - Voluntary Termination" as appropriate.
  4. If the status has not yet been updated, change the account status in Salesforce to the target status indicated in the ticket subject.
  5. Confirm that any downstream systems or internal records that depend on the Salesforce status reflect the closure (e.g., wallet access restrictions, billing cessation).
  6. Close the support ticket. No customer-facing response is typically required for these internal status-change records.

Notes: These tickets are generated in bulk and processed by a single internal agent (evidenced by identical creator IDs and near-identical timestamps across hundreds of tickets). They are administrative records, not customer-initiated support requests. The resolution confidence across all sampled tickets is "medium," likely because the tickets contain minimal diagnostic detail beyond the subject line and SF# reference.

Scenario: voluntary-termination-change-status#frozen-status-variant

Trigger: The ticket subject indicates a status change to "Frozen" rather than "Voluntary Termination" (e.g., "Status change for [Entity Name]: Frozen").

Signals: frozen, status change, SF#, account frozen

Steps:

  1. Open the Salesforce case using the SF# number referenced in the ticket subject.
  2. Confirm the target status is "Frozen" — this is distinct from voluntary termination and may indicate a compliance or risk-driven hold rather than a client-initiated closure.
  3. Before processing, verify with the Compliance team whether the freeze is intentional and whether any additional restrictions (e.g., withdrawal blocks) need to be applied.
  4. Update the account status in Salesforce to "Frozen" once confirmed.
  5. Close the support ticket.

Notes: A "Frozen" status appeared in Ticket #27979 (Holt Financial Limited). Do not conflate this with voluntary termination — different downstream actions may apply. Escalate to Compliance if uncertain.

Scenario: voluntary-termination-change-status#unrelated-ticket-in-cluster

Trigger: The ticket subject does not follow the "Status change for … Voluntary Termination" pattern and instead references a general inquiry, petition, or service-delivery question.

Signals: query, service delivery, petition, no status change, miscategorized

Steps:

  1. Review the ticket subject and body to determine the actual nature of the request.
  2. If the ticket is a legitimate customer inquiry (e.g., service-delivery question as in Ticket #20486 / #28140), route it to the appropriate support queue or account manager.
  3. If the ticket is spam or irrelevant (e.g., Ticket #2170), close it with no action required.
  4. Do not apply any account status change.

Notes: Ticket #2170 (change.org petition) and Tickets #20486 / #28140 (service-delivery queries) were clustered with voluntary-termination tickets but are unrelated. Always verify the ticket subject before processing a status change.

Related

  • account-closure-offboarding — General guidance on client offboarding procedures and final withdrawal steps.
  • salesforce-case-management — How Salesforce case references (SF#) map to support tickets and internal workflows.
  • none identified — No direct relation to the existing KB articles on Prime Lending, Electronic Trading, or Off-Exchange Settlement was found in the source tickets.