Scoutinternal

Unsolicited, Misdirected, and Spam Emails Sent to BitGo Support

Unsolicited, Misdirected, and Spam Emails Sent to BitGo Support

Problem

BitGo support regularly receives unsolicited emails that are not legitimate support requests. These include automated replies from third-party institutions (e.g., "Banfers International Bank & Trust" notifications), spam messages, generic inquiries about buying/selling Bitcoin from non-customers, and other misdirected correspondence. These tickets consume agent time and require a consistent triage and closure process. Separately, a small number of legitimate client inquiries in this cluster involve token price display discrepancies on the BitGo portal, where the USD value shown for a token (e.g., LDO, WCT) does not match the market price on external sources like CoinMarketCap.

Diagnostics

  • Check whether the sender is a known BitGo customer. Look up the sender's email address in the admin tool / Salesforce to determine if they are associated with an active enterprise or individual account.
  • Review the email subject and body for signs of spam or misdirection. Common patterns include:
    • Third-party auto-reply templates (e.g., "Notification – Banfers International Bank & Trust")
    • Generic subjects like "bitcoins," "Buy Bitcoin," "bitcoin adres," "Selling bitcoin"
    • Marketing solicitations, trademark offers, or pricing for unrelated products
    • Messages in languages other than English with no clear BitGo context
  • For price discrepancy tickets: Open the customer's wallet in the BitGo admin portal and compare the displayed USD balance to the token quantity multiplied by the current market price on a reference source (e.g., CoinMarketCap, CoinGecko). Check whether the token's price feed has a known issue by searching the internal #support-escalations Slack channel or engineering channels for the specific token ticker.
  • For price discrepancy tickets: Identify the token type string (e.g., "type": "opeth:wct") and the tokenContractAddress to confirm the correct token mapping.

Resolution

Scenario: ic15-commentary-nicehash-index#spam-misdirected-email

Trigger: The inbound email is an unsolicited auto-reply, spam, or generic inquiry from a non-customer with no actionable BitGo support request.

Signals: Banfers International Bank, spam, misdirected email, buy bitcoin, sell bitcoin, non-customer, generic inquiry, bitcoins, satoshi

Steps:

  1. Verify that the sender is not associated with any active BitGo account in Salesforce or the admin tool.
  2. If the sender is not a customer, reply with a standard clarification response asking for more details about their issue:
    • "Thank you for reaching out to BitGo Support. We are glad to assist you further, however, we require more information from you to assist you further. Could you please elaborate on the issue you are experiencing?"
  3. If no response is received within 5 business days, send a follow-up:
    • "We wanted to follow up and check if you require further assistance. We look forward to your response."
  4. If no response is received after the follow-up, close the ticket as resolved with no further action required.
  5. Do not share any account details, internal processes, or sensitive information with unverified senders.

Notes: These emails arrive periodically in waves. The "Banfers International Bank & Trust" auto-reply is a recurring pattern observed across many tickets. These are not phishing attempts targeting BitGo customers but rather misdirected auto-responses that arrive at support@bitgo.com.

"Thank you for reaching out to us at Banfers International Bank & Trust. We deeply appreciate your contact and are committed to providing you with the highest level of service. ... Our response times are 24 to 48 business hours" (ticket #219011)

"We are glad to assist you further, however, we require more information from you to assist you further. Could you please elaborate on the issue you are experiencing?" (ticket #225557)

Scenario: ic15-commentary-nicehash-index#token-price-display-discrepancy

Trigger: A customer reports that the USD value of a token displayed on the BitGo portal is significantly different from the current market price on external price aggregators such as CoinMarketCap.

Signals: price discrepancy, incorrect price, token price, LDO, WCT, USD balance wrong, API glitch, price feed, market price mismatch

Steps:

  1. Ask the customer to confirm the specific token, the price they see on the BitGo portal, and the current market price from their reference source.
  2. Verify the discrepancy by checking the customer's wallet balance in the admin tool. Calculate the expected USD value: token quantity × current market price from CoinMarketCap or CoinGecko. Compare against the displayed value.
  3. Check if the issue is transient — ask the customer to refresh and confirm whether the price has corrected itself. In some cases, the price self-corrects (as observed with LDO).
  4. If the discrepancy persists, escalate to the engineering team via the internal Slack channel (e.g., #support-escalations or the relevant coin/pricing channel). Include:
    • Token type string (e.g., "type": "opeth:wct")
    • Token contract address
    • Wallet ID
    • The displayed price vs. the expected market price
    • Screenshot from the customer if available
  5. Keep the customer updated on engineering progress. Provide periodic status updates until the fix is deployed.
  6. Once engineering confirms the fix is deployed, verify the price is now correct and notify the customer.

Notes: Price discrepancies are typically caused by issues in the price feed or API integration with external price sources. These are not balance discrepancies — the on-chain token quantity is correct, but the USD conversion uses an incorrect price. Resolution requires engineering intervention and may take several days to weeks. The LDO issue was intermittent (self-correcting then recurring), while the WCT issue persisted until an engineering fix was deployed.

"There is still a API glitch from your end with an exchange to get accurate prices. I am being misled. My balance for LDO is supposed to be. 69,955 Tokens x @$0.71 each is about 50,000 USD. I have a balance of approx $95,000 USD. Almost double…." (ticket #219346)

"WCT price is $0.39 - where do you all get the WCT price as we see $6,666 value?" (ticket #248437)

Scenario: ic15-commentary-nicehash-index#non-customer-account-inquiry

Trigger: A person contacts support@bitgo.com asking basic questions about buying, selling, or using Bitcoin but does not appear to be an existing BitGo customer or enterprise client.

Signals: buy bitcoin, sell bitcoin, how to use, selling my bitcoin, trading, 2FA setup, non-customer

Steps:

  1. Look up the sender in Salesforce / admin tool to determine if they have an existing account.
  2. If they do have an account (e.g., the "selling my Bitcoin" inquiry in Ticket #322215), assist them normally:
    • Verify 2FA status. If 2FA is not configured, guide them to reset and reconfigure it at https://app.bitgo.com/web/auth/login
    • Once logged in, direct them to the Trade option in the portal. They will need to review and sign the trading agreement before the trading feature is enabled.
  3. If they do not have an account and the inquiry is generic, respond with a clarification request and direct them to https://app.bitgo.com/auth/log-in for account creation if appropriate.
  4. If no response is received, follow up once and then close the ticket.

Notes: BitGo is an institutional custody platform; many generic "how to buy Bitcoin" inquiries come from individuals unfamiliar with BitGo's services. These can typically be closed after a single clarification attempt.

"It appears that 2FA is not configured on the account. Kindly reset the 2FA. Once you log in, you will be able to see the Trade option. When you click on it, you will be prompted to review and sign the agreement. After completing the agreement, the trading feature will be enabled." (ticket #322215)

Related

  • transferring-assets — Relevant if a non-customer or new customer asks about sending or withdrawing Bitcoin after account setup.
  • prime-lending-borrowing — May be tangentially relevant if inquiries relate to BitGo Prime trading or pricing.
  • none identified — No direct KB match for token price feed discrepancy issues.