Skip to content

Change subscription warning for enterprise#23630

Open
tdraier wants to merge 1 commit intomainfrom
change-subscription-warning-for
Open

Change subscription warning for enterprise#23630
tdraier wants to merge 1 commit intomainfrom
change-subscription-warning-for

Conversation

@tdraier
Copy link
Copy Markdown
Contributor

@tdraier tdraier commented Apr 2, 2026

Description

Soften end-of-subscription warning messages for Enterprise plans.

Fixes https://github.com/dust-tt/tasks/issues/7290

The current wording ("Connections will be deleted and members will be revoked") is too alarming for Enterprise customers in the process of renewing or upgrading.

  • Subscription page (SubscriptionPage.tsx): Enterprise plans show "Please reach out to your account manager to ensure continuity." instead of the destructive warning.
  • Navigation banner (TrialBanner.tsx): Enterprise plans get "Your current subscription period ends in X days" with "Please reach out to your account manager to ensure continuity." The "Subscribe to Dust" button is hidden (not relevant for enterprise).
  • Pro plans: description updated to "When your subscription wraps up, your connections and team member access will be removed. Subscribe now to keep everything." (unchanged behavior, just refactored alongside enterprise branching).

Non-enterprise plans keep existing behavior unchanged.

Tests

Type-checking passes. UI-only change, gated on isEntreprisePlanPrefix(plan.code).

Risk

Low — display-only change scoped to enterprise plan banners. No impact on non-enterprise plans.

Deploy Plan

Standard deploy, no special steps needed.

@tdraier
Copy link
Copy Markdown
Contributor Author

tdraier commented Apr 2, 2026

This change is part of the following stack:

Change managed by git-spice.

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 2, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments
Project Deployment Actions Updated (UTC)
playground Ignored Ignored Preview Apr 3, 2026 11:56am
storybook Ignored Ignored Preview Apr 3, 2026 11:56am

Request Review

Copy link
Copy Markdown
Contributor

@dust-agent dust-agent bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Coding Rules LGTM \o/

@tdraier tdraier force-pushed the change-subscription-warning-for branch 2 times, most recently from 779ffce to 337d1fc Compare April 2, 2026 12:10
let description: string;
if (isEnterprise) {
description =
"Please reach out to your account manager to ensure continuity — no changes will be made without prior notice.";
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If they do nothing we still remove data after x days so I'm afraid they need to still act and this wording is misleading 🙉

{title}
</span>
<span className="text-sky-800 dark:text-sky-800-night">
When your {isTrial ? "trial" : "subscription"} wraps up, your
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why not keeping a proper wording for trials?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes but it's hard to get the full picture when you look at the code no?
I don't think he thought about trials when he built his card, this is our job to think about edge cases :D

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually the wording the one we had in SubscriptionPage, same for trials and pro (when there is an endDate) - do we want to have different messages for both ?
Note that for pilots I have no clean way to detect them.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants