Souredoutlook/feat/billing ask support intercom#115390
Closed
souredoutlook wants to merge 5 commits into
Closed
Conversation
Wire the checkout side-panel "ask Support" link to Intercom when the intercom-support feature is enabled, falling back to the existing Zendesk widget otherwise. Mirrors the pattern in the primary nav help menu and adds intercom_link.viewed/clicked analytics with source: 'checkout'. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
When showIntercom throws and Zendesk is unavailable, the catch block silently swallowed the error, leaving the user with no way to reach support. Fall back to mailto using the configured supportEmail, mirroring the pattern in the primary nav help menu. Co-Authored-By: Claude <noreply@anthropic.com>
Wire the remaining "Contact Support" surfaces in the billing flow to
Intercom when the intercom-support feature is enabled, falling back to
the existing ZendeskLink otherwise. Affects:
- gsBanner suspension modal
- TrialEnded alert on the subscription overview
- PlanMigrationActive panel for scheduled legacy-plan migrations
Mirrors the pattern in the primary nav help menu and checkout side
panel. On Intercom failure, falls back to mailto with the same subject
the ZendeskLink used. Adds intercom_link.viewed/clicked analytics with
sources matching each surface's existing Zendesk source
('account-suspension', 'trial', 'billing').
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Contributor
📊 Type Coverage Diff✅ No new type safety issues introduced. Coverage: 93.49% |
Contributor
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 2 potential issues.
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 82ce5a3. Configure here.
scraps Button's discriminated union requires children when no
aria-label is provided. The tct-interpolated <Button /> in TrialEnded
and PlanMigrationActive has neither at the JSX site since children
are injected at runtime by tct's cloneElement. Pass {null} as a
placeholder so the type checks; tct overwrites it.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
The Intercom failure path on the checkout side panel fell back to a bare mailto, dropping the "Billing Question" subject the original ZendeskLink provided. Restore it for consistency with the suspension, trial, and plan-migration surfaces, which all include their original subjects in the mailto fallback. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

We missed some areas of the product that still have invoke the Zendesk form
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.