Onboarding - Expensify Card link in onboarding message opens Company cards page

[mitarachim]

If you haven’t already, check out our contributing guidelines for onboarding and email contributors@expensify.com to request to join our Slack channel!

---

Version Number: 9.3.65-0
Reproducible in staging?: Yes
Reproducible in production?: N/A - new feature, doesn't exist in prod
If this was caught during regression testing, add the test name, ID and link from BrowserStack: #88677
Email or phone of affected tester (no customers): jinojionjoinjionjiojoi@gmail.com
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Mac 26.2 / Chrome
App Component: Money Requests

Action Performed:

1. Go to staging.new.expensify.com
2. Create a new Gmail account.
3. Click Skip on work email step.
4. Click Manage my team's expenses.
5. Select 1-4 employees > Continue.
6. Select any accounting > Continue.
7. Select Expensify Card and Travel > Continue.
8. Go to #admins.
9. Click "How do I enable and issue Expensify Cards for my team?".
10. Wait for Concierge reply.
11. Click Expensify Card link.

Expected Result:

Expensify Card page will open.

Actual Result:

Company cards page opens instead.

Workaround:

Unknown

Platforms:

• Android: App
• Android: mWeb Chrome
• iOS: App
• iOS: mWeb Safari
• iOS: mWeb Chrome
• Windows: Chrome
• MacOS: Chrome / Safari

Screenshots/Videos

Bug7142383_1777591679834.3.mp4

View all open jobs on GitHub

[melvin-bot]

You have been assigned to this deploy blocker because you recently merged this PR: #88677

[melvin-bot]

💬 A slack conversation has been started in #expensify-open-source

[github-actions]

👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

1. Identify the pull request that introduced this issue and revert it.
2. Find someone who can quickly fix the issue.
3. Fix the issue yourself.

[OSBotify]

Investigation Summary

Classification: Frontend bug
Causing PR: #88677 - "CompleteGuidedSetup: send selectedInterestedFeatures to shape welcome followups" by @marcochavezf (High confidence)
Related Issues: N/A

Recommendation: REVERT

PR #88677 introduced a logic change that causes the wrong page to open when a user clicks the Expensify Card link in the Concierge welcome followup. The fix requires reverting the App PR since the bug is entirely in the frontend routing/onboarding logic.

Assigned: @marcochavezf (PR author), @hungvu193 and @youssef-lr (approving reviewers) from highest-confidence causing PR only
Labels: DeployBlockerCash kept (Frontend bug — App PR caused the issue). DeployBlocker removed (not a backend bug).

Detailed Analysis

Evidence

• The melvin-bot already assigned PR [Payment due @hungvu193] CompleteGuidedSetup: send selectedInterestedFeatures to shape welcome followups #88677 as the cause via its auto-assignment comment.
• PR [Payment due @hungvu193] CompleteGuidedSetup: send selectedInterestedFeatures to shape welcome followups #88677 is in the StagingDeployCash checklist (entry 113) and was merged on 2026-04-30T15:08:27Z, the same day the deploy blocker was reported.
• The bug is staging-only / new feature (not reproducible in production, as noted in the issue).
• The issue reports that clicking the "Expensify Card" link from the Concierge followup opens the Company Cards page instead of the Expensify Card page.

Verification

• PR [Payment due @hungvu193] CompleteGuidedSetup: send selectedInterestedFeatures to shape welcome followups #88677 modifies src/libs/ReportUtils.ts, specifically the prepareOnboardingOnyxData function.
• The PR reorganized the ordering of shouldPostTasksInAdminsRoom and shouldUseFollowupsInsteadOfTasks computations, and changed which users enter the followups path (previously gated by isPostingTasksInAdminsRoom, now triggering for all MANAGE_TEAM + Phase 1 cohort users regardless of the + email exclusion).
• The onboardingTaskParams object (also in src/libs/ReportUtils.ts) builds corporateCardLink using ROUTES.WORKSPACE_COMPANY_CARDS (the Company Cards / third-party feed page) rather than ROUTES.WORKSPACE_EXPENSIFY_CARD (the Expensify Card page). The backend uses this link when generating the "How do I enable and issue Expensify Cards?" followup button — so the link routes to the wrong page.
• The PR also changed shouldPostTasksInAdminsRoom from being computed independently (based on the existing isPostingTasksInAdminsRoom predicate) to being derived from shouldUseFollowupsInsteadOfTasks, meaning any user now on the followups path also has shouldPostTasksInAdminsRoom = true, broadening the scope of who receives the followups and therefore amplifying the wrong-link bug.

Root Cause

In src/libs/ReportUtils.ts, the corporateCardLink in onboardingTaskParams is set to ROUTES.WORKSPACE_COMPANY_CARDS.getRoute(onboardingPolicyID) which resolves to workspaces/<policyID>/company-cards. This is the Company Cards page for third-party card feeds, not the Expensify Card page. The correct route should be ROUTES.WORKSPACE_EXPENSIFY_CARD.getRoute(onboardingPolicyID) which resolves to workspaces/<policyID>/expensify-card.

PR #88677 expanded the followups path to cover all MANAGE_TEAM + Phase 1 cohort users (MICRO_SMALL, MICRO_MEDIUM, MICRO company sizes), which means more users now receive the Concierge followup message containing this wrong corporateCardLink. The bug was likely latent before this PR but only exposed to more users (or to users for the first time on staging) after the broader cohort expansion introduced here.