Scoutinternal

Replies to BitGo Market Pulse Newsletter Creating Unactionable Support Tickets

Replies to BitGo Market Pulse Newsletter Creating Unactionable Support Tickets

Problem

BitGo sends a weekly marketing newsletter called "Market Pulse" (subject lines such as "Volatility Returns to the Market," "Powell's Jackson Hole Surprise," "Crypto Resilient Amid September Headwinds," "Altcoins Surge as Fed Decision Looms," "The Powell Inquiry while Markets in Limbo") from hello@go.bitgo.com. Recipients — many of whom are not active BitGo platform customers — reply directly to these emails, which routes their messages to support@bitgo.com and creates support tickets. These replies rarely contain an actionable technical issue; instead they include random text, unsubscribe requests, account deletion demands (including DSAR requests), fraud accusations, product/sales questions, CSR collaboration inquiries, or simply blank/garbled content. Agents must triage these tickets efficiently to distinguish genuine platform issues from non-actionable newsletter replies.

Diagnostics

  • Check the originating email: the inbound message will typically quote or forward content from hello@go.bitgo.com containing the "Market Pulse" header and the line "Curated weekly briefing on crypto markets—delivered to your inbox." (or the variant "Curated weekly briefing on crypto markets, delivered to your inbox.").
  • Check the subject line: it will usually start with "Re:" followed by a Market Pulse newsletter title (e.g., "Re: Volatility Returns to the Market," "Re: The Powell Inquiry while Markets in Limbo," "Re: Altcoins Surge as Fed Decision Looms").
  • Look up the sender's email address in the admin tool under Checking Ent / account lookup. Determine whether the sender has an active BitGo account. Many of these senders have no account, or are flagged as individual (starter) Retail user, or return "No Results Found."
  • Read the body of the customer's reply (above the quoted newsletter content) to classify the intent: unsubscribe request, account deletion/DSAR demand, fraud/scam accusation, general product question, sales/partnership inquiry, or unintelligible/blank content.
  • Check whether the account has already been deactivated (some users request deletion of accounts that were previously closed).

Resolution

Scenario: market-weekly-crypto-cap#unsubscribe-request

Trigger: The customer explicitly asks to be removed from the mailing list or to stop receiving newsletter emails.

Signals: unsubscribe, remove, distribution list, stop emails, no more emails

Steps:

  1. Submit an unsubscribe request internally for the customer's email address so they no longer receive Market Pulse newsletters.
  2. Confirm to the customer that the request has been submitted and they will not receive further notifications from BitGo.
  3. If the customer's account is already deactivated but they still receive emails, advise them to also check their email client settings (e.g., Gmail settings) to filter or block emails from hello@go.bitgo.com.

Notes: Some customers whose accounts were already deactivated still receive the newsletter. Confirm the deactivation date if visible, and communicate it to the customer.

"We've successfully submitted a request on this. You will not receive any such notifications from BitGo." (ticket #270812)

"Your account is deactivated. Please use Gmail settings to stop receiving the emails." (ticket #244506)

Scenario: market-weekly-crypto-cap#account-deletion-dsar

Trigger: The customer demands account deletion, data erasure, or invokes a DSAR (Data Subject Access Request) — often with hostile language.

Signals: delete account, DSAR, delete all data, close account, deactivate

Steps:

  1. Look up the customer's email in the admin tool to confirm whether an account exists.
  2. If an account exists, send the standard account deactivation confirmation message requesting the customer reply with the consent phrase and verification code: "You have my consent to deactivate my BitGo account tied to the email address through which I am sending you this message and the verification code is [CODE]".
  3. Once the customer replies with the confirmation text, proceed with account deactivation.
  4. Confirm completion to the customer.
  5. If no account is found under the sender's email, inform them that no account is registered under that address and ask whether they may have an account under a different email. Provide the official login URL: https://app.bitgo.com/web/auth/login

Notes: Legally, BitGo cannot delete the account until the customer provides the consent reply. Communicate this clearly but calmly, even if the customer is hostile. If the customer refuses to cooperate, you may still proceed once they eventually send the required confirmation.

"Legally, we cannot delete your account until you provide the needed reply we are asking you to send to us. Let us know if there is confusion around this. Once we receive the needed reply, we are more than happy to wipe you and your information from our system." (ticket #270835)

"We've reviewed your account details and can confirm that your account has already been deactivated. As noted, we also sent you an email on June 30, 2025 confirming this deactivation." (ticket #244506)

Scenario: market-weekly-crypto-cap#fraud-scam-accusation

Trigger: The customer accuses BitGo of being a scam or fraud, often in an emotionally charged message, possibly in a non-English language.

Signals: fraud, scam, scammers, estafadores, ESTAFADORES

Steps:

  1. Respond calmly and professionally. Affirm that BitGo is a legitimate business.
  2. Ask the customer to explain their issue in detail so support can investigate.
  3. If the customer indicates they did not open an account and someone may have done so on their behalf, offer to provide a confirmation email to delete the account.
  4. If the customer is uncooperative, encourage them to file a criminal complaint with law enforcement. Provide the FBI Internet Crime Complaint Center link: https://www.ic3.gov/
  5. State clearly: "BitGo will gladly comply with law enforcement agencies to provide any information that we can to help further investigations into criminal activity."
  6. Remind the customer of BitGo's legitimate contact channels: a member of BitGo will not contact them outside of the @bitgo.com email domain; the official site is https://www.bitgo.com; BitGo does not currently have a mobile platform app for withdrawing or purchasing funds; BitGo does not accept outside investment; and BitGo does not feature the ability to earn profits by depositing funds.
  7. If the customer remains uncooperative after follow-up, close the ticket.

Notes: These customers are often victims of third-party scams impersonating BitGo. The fraud accusation is directed at the impersonator, not necessarily at BitGo itself. Handle with empathy.

"A member of BitGo will not contact you outside of the BitGO domain. We have one site, https://www.bitgo.com. We will not contact you outside of an @bitgo.com email address. We currently do not have a platform app that can be used on mobile to withdraw or purchase funds. We do not accept outside investment. We do not feature the ability to earn profits by depositing funds with us." (ticket #240628)

"If you are unwilling to help us help you, we encourage you to file a criminal complaint with federal or local law enforcement agencies. The FBI Internet Crime Complaint Center can be found at https://www.ic3.gov/ -- this site links to a form where you can file a complaint." (ticket #240628)

Scenario: market-weekly-crypto-cap#product-sales-inquiry

Trigger: The customer asks product questions (e.g., trading costs, available assets, app download links, partnership or revenue-share opportunities, CSR collaborations) prompted by newsletter content.

Signals: transaction costs, buying selling, trailing order, stocks, revenue share, cooperate, CSR, pricing, XAUm, download app

Steps:

  1. For sales, pricing, partnership, or product offering questions: forward the request to the BitGo Sales team. Ask the customer for their country of location so Sales can assign a representative in their time zone.
  2. For app download requests: provide official links — BitGo Mobile Apps are available via Apple Store and Google Play Store. Also provide: official site https://www.bitgo.com/ and official platform https://app.bitgo.com/login. Clarify that the "BitGo Verify" app is used for approving transaction requests and is different from the BitGo platform. For viewing wallets, recommend logging in via a web browser on a computer.
  3. For transaction fee questions: explain that there is no fixed amount; fees depend on factors such as transaction size, network congestion, desired speed, order type, trade volume, and the specific fee structure. Refer detailed pricing questions to the Sales team.
  4. For 2FA setup confusion (e.g., "What is Add label"): explain that the 2FA label is a custom name the user chooses to identify the device or app used for authentication (e.g., "My Phone," "Work Device") — it is for their reference only.

Notes: Many of these senders are retail individuals exploring BitGo for the first time after receiving the newsletter. They may not understand that BitGo is primarily an institutional custody platform.

"For inquiries related to pricing, product offerings, or partnership opportunities, our Sales team would be the best point of contact. I've forwarded your request to them, and someone from the team will follow up with you shortly." (ticket #253924)

"Please note that the 2FA label is a custom name you can choose to identify the device or app you are using for authentication (e.g., 'My Phone,' 'Work Device'). It's just for your reference." (ticket #270860)

Scenario: market-weekly-crypto-cap#no-account-gibberish-reply

Trigger: The customer's reply is blank, contains only gibberish/random characters, or is an unintelligible forwarded newsletter with no clear request.

Signals: blank reply, gibberish, Dsghn, random text, no clear issue, emoji only

Steps:

  1. Look up the sender's email in the admin tool.
  2. If no account is found, respond informing the customer that no account is registered under that email address. Provide the official login URL (https://app.bitgo.com/web/auth/login) and official domain (https://www.bitgo.com/).
  3. If an account exists, ask the customer to elaborate on their issue and provide relevant details.
  4. Remind the customer: "We currently provide support exclusively via email. We do not have a phone support line or online chat support."
  5. If no response is received after follow-up, close the ticket.

Notes: These tickets are commonly generated by accidental replies (e.g., pocket-dials on mobile) to the newsletter email. They are almost never actionable.

"It appears that we don't have an account registered under this email address in our system. Is it possible that you have an account with us under a different email? If so, please reach out to us using that email address. Could you also confirm the URL where you are trying to log in? Our official domain is https://www.bitgo.com/, and the main login portal can be accessed from this domain at https://app.bitgo.com/web/auth/login." (ticket #270845)

Scenario: market-weekly-crypto-cap#feature-flag-legitimate-request

Trigger: A legitimate institutional customer replies to a newsletter thread to loop in support@bitgo.com for a specific platform action, such as enabling a feature flag.

Signals: feature flag, stAVAX, liquid staking, enable, turn on, AVAX, staking, onboarding

Steps:

  1. Verify the customer's account and enterprise in the admin tool.
  2. Confirm the request with the internal BitGo team members referenced (e.g., Customer Success Manager, Sales representative) via the email thread or internal channels.
  3. Enable the requested feature flag or configuration change as directed.
  4. Confirm completion to the customer.

Notes: These are rare but legitimate. The customer typically CC's or mentions specific BitGo employees (e.g., from Customer Success or Sales) in the thread. The newsletter reply is simply a convenient email thread being reused. Treat as a standard operational request.

"I'm adding support@bitgo.com to this thread for them to turn on the feature flag for stAVAX liquid staking on my account." (ticket #252824)

"We turned on the feature flag as requested." (ticket #252824)

Scenario: market-weekly-crypto-cap#third-party-newsletter-spam

Trigger: The inbound email is not a reply to a BitGo Market Pulse newsletter but is instead a third-party crypto newsletter (e.g., Be[in]Crypto, Global Ledger, MelegaSwap) that was forwarded or sent to support@bitgo.com.

Signals: BeInCrypto, Global Ledger, MelegaSwap, bic.tools@beincrypto.com, third-party newsletter, Daily Digest, Weekly Digest

Steps:

  1. Confirm the email is from a third-party source and not a customer request.
  2. Send a generic acknowledgment if a ticket was auto-created, requesting more details if the sender has an actual issue.
  3. If no response or actionable content, close the ticket as non-actionable / marketing.

Notes: These appear to be third-party newsletters addressed to support@bitgo.com rather than customer replies. They generate noise in the queue and should be closed promptly.

Related