Scoutinternal

Spam and Unsolicited Marketing Emails Sent to BitGo Support Inbox

Spam and Unsolicited Marketing Emails Sent to BitGo Support Inbox

Problem

The BitGo support inbox (support@bitgo.com) receives a high volume of unsolicited commercial emails — primarily TechCrunch Disrupt promotions, startup pitch competition invitations, webinar announcements, venture capital newsletters, and other marketing or media solicitations. These messages are not legitimate BitGo customer support requests. They consume agent time during triage and can occasionally be confused with real tickets when migrated into the support system. In rare cases, completely unrelated or incoherent messages (e.g., AWS IP address research, general grievances) are also sent to the support inbox and auto-generate tickets.

Diagnostics

  • Check the ticket subject line: look for characteristic phrases such as "Disrupt," "TechCrunch," "Startup," "Early Stage," "webinar," "startup pitch," "save," "early bird," "sessions," or "AI Stage." These are strong indicators of marketing spam.
  • Check the sender domain: common spam senders in this cluster originate from TechCrunch/Marketomail (info.techcrunch.com), venture capital firms, webinar platforms, and startup event organizers — not from BitGo customers or known enterprise contacts.
  • Check whether the ticket body is empty or contains only a subject line with no actionable BitGo-related content. The majority of tickets in this cluster have completely empty problem descriptions, with only a migrated subject line referencing an event or promotion.
  • Check whether the email contains unsubscribe links pointing to external marketing preference centers (e.g., https://info.techcrunch.com/Preference-Center-2021.html or https://info.techcrunch.com/Unsubscribe-Confirm-2021.html). This confirms the message is a marketing newsletter.
  • Check whether the message was sent directly to support@bitgo.com or CC'd to it among many other recipients. Spam frequently arrives as a CC or bulk send.
  • For messages that contain seemingly technical content (IP addresses, AWS references, forensic claims), verify whether the sender is a known BitGo customer with an active enterprise or wallet. If not, the ticket is likely misdirected or incoherent.

Resolution

Scenario: disrupt-techcrunch-ai-stage#marketing-spam-newsletter

Trigger: The ticket subject and/or body contains TechCrunch, Disrupt, startup event, webinar, or other marketing newsletter content with no BitGo-related request.

Signals: disrupt, techcrunch, TC Early Stage, startup, webinar, save, early bird, sessions, AI stage, Startup Battlefield, Startup Alley, Databricks, Pegasus VC, Tycoonstory, pitch competition, unsubscribe

Steps:

  1. Confirm the ticket body is either empty or contains only marketing/event promotional content with no BitGo product question or customer account reference.
  2. Classify the ticket as Spam / Not a Support Request in the ticketing system.
  3. Close the ticket without sending a customer response. No reply is needed for unsolicited marketing emails.
  4. If TechCrunch newsletters are arriving in high volume, escalate to the IT or email administration team and request that unsubscribe actions be taken using the links provided in the emails (e.g., https://info.techcrunch.com/Unsubscribe-Confirm-2021.html) or that sender-domain-level filtering rules be added for repeat offenders.

Notes: These tickets were historically migrated from Salesforce into the current ticketing system and may appear in bulk. They have no customer impact and require no technical investigation. Do not reply to these senders — doing so may confirm the email address is active and invite further spam.

"This email was sent to support@bitgo.com. You can adjust your communication preferences here: https://info.techcrunch.com/Preference-Center-2021.html ... To be removed from all TechCrunch event emails you may unsubscribe at any time. https://info.techcrunch.com/Unsubscribe-Confirm-2021.html" (ticket #20407)

"This email was sent to support@bitgo.com. You can adjust your communication preferences here: https://info.techcrunch.com/Preference-Center-2021.html ... To be removed from all TechCrunch event emails you may unsubscribe at any time. https://info.techcrunch.com/Unsubscribe-Confirm-2021.html" (ticket #29592)

Scenario: disrupt-techcrunch-ai-stage#misdirected-incoherent-request

Trigger: The ticket contains non-BitGo technical content (e.g., AWS IP analysis, Apple iCloud questions) or incoherent claims, sent to support@bitgo.com but with no identifiable BitGo account or product issue.

Signals: AWS, IP address, iCloud, Apple Digital Services, Amazon Web Services, tampering, forensic, undefined

Steps:

  1. Review the ticket content to confirm there is no legitimate BitGo support request embedded in the message.
  2. If the sender claims to be a BitGo customer but cannot provide basic account identifiers (Enterprise ID, Wallet ID, User ID/email), send the standard information-request template asking for environment, Enterprise Name, Enterprise ID, Wallet ID, Transaction ID, User ID/email, and error message.
  3. If the sender responds but still cannot provide any identifiable BitGo account details, inform them: "We do not store any user details, especially wallet information or login credentials. The key card is unique for each user, so you will need to provide the details for our understanding."
  4. If no further actionable information is received, close the ticket as Unresolvable — Insufficient Information.
  5. Do not engage with non-BitGo technical questions (e.g., questions about AWS services, Apple iCloud data). Politely clarify that BitGo Support can only assist with BitGo product and service inquiries.

Notes: BitGo Support will never ask for passwords, API tokens, or keycard documents. If a sender makes claims about wallet tampering but cannot identify any BitGo account, there is no actionable investigation path. These tickets should not be escalated to engineering.

"We do not store any user details, especially wallet information or login credentials. The key card is unique for each user, so you will need to provide the details for our understanding." (ticket #270454)

"BitGo Support will never ask for your password, API tokens, or keycard document." (ticket #270454)

Related

  • keycards-and-private-keys — Referenced in the context of keycard-related claims from misdirected senders; agents should be familiar with what BitGo does and does not store.
  • none identified — The marketing spam tickets have no relationship to BitGo product functionality.