[Due for payment 2026-04-14] Update CTA and Workspace Chat Copy for track-intent users

[MelvinBot]

Linked to https://github.com/Expensify/Expensify/issues/614730

As part of the track updates we're making to increase paidAdoption, we need to ensure the copy across the product mirrors this intent's primary functionalities. These include:

• Updating the user's workspace chat to have the header be, "This is where you will track expenses"
• Updating the CTAs for expenses/reports to be, "Mark as done"
• Updating the corresponding system messages to be, "marked as done"

[samranahm]

@jayeshmangwani Is this open for external contributors?

[jayeshmangwani]

@samranahm, thank you for asking, but it’s currently not open for external contributors.

[samranahm]

Appreciate your feedback, Thank you 😊

[jayeshmangwani]

@MelvinBot implement this.

[MelvinBot]

🤖 Cannot proceed: jayeshmangwani does not have write access to the target repository (Expensify/App). MelvinBot will not create branches or PRs on repos that the requesting user cannot access themselves.

[dylanexpensify]

@MelvinBot implement this

[MelvinBot]

I ran out of time before I could finish helping you. This usually means the task was too complex or I got stuck exploring. Please try again with a more specific request or post in the #melvinbot-ai.

Run details: https://github.com/Expensify/Expensify/actions/runs/23596009038

[dylanexpensify]

@MelvinBot please propose how you'd solve this as part of this issue

[MelvinBot]

Proposal

Please re-state the problem that we are trying to solve in this issue.

For users who onboarded with the "Track and budget expenses" intent (PERSONAL_SPEND / TRACK_WORKSPACE), the product copy still uses generic expense management language — "submit expenses", "Submit", "Approve", "submitted", "approved" — instead of language that reflects the track-intent workflow. We need to update three areas: the workspace chat welcome text, the expense/report CTA buttons, and the corresponding system messages.

What is the root cause of that problem?

The App currently uses the same copy for all workspace types regardless of onboarding intent. Track-intent workspaces are created with approvalMode: OPTIONAL and reimbursementChoice: REIMBURSEMENT_NO (see Policy.ts:2462-2470), but no UI copy branches on these settings or on the user's NVP_INTRO_SELECTED.choice.

What changes do you think we should make in order to solve the problem?

Detection: Create a utility function (e.g., isTrackExpenseWorkspace(policy)) that identifies track-intent workspaces. Two viable approaches:

• Option A (workspace-level): Check policy.approvalMode === OPTIONAL && policy.reimbursementChoice === REIMBURSEMENT_NO. Pro: per-workspace granularity. Con: could false-match if a user manually sets these settings on a non-track workspace.
• Option B (user-level): Check NVP_INTRO_SELECTED.choice is PERSONAL_SPEND or TRACK_WORKSPACE. Pro: directly reflects onboarding intent. Con: applies to all of the user's workspaces.

I'd recommend Option A (workspace-level) since it's more precise and these settings are the defining characteristics of a track workspace. A follow-up enhancement could be to have the backend store engagementChoice on the policy object for an even cleaner signal.

Change 1 — Workspace chat welcome text:

• Add a new translation key in en.ts (near line 904): beginningOfChatHistoryPolicyExpenseChatTrack: 'This is where you will track expenses'
• In SidebarUtils.ts:1261-1274, inside the isPolicyExpenseChat branch, before the existing fallback, check isTrackExpenseWorkspace(policy) and use the new translation key

Change 2 — CTA button labels ("Mark as done"):

• Add translation keys: common.markAsDone: 'Mark as done' and actionBadge.markAsDone: 'Mark as done'
• In MoneyReportHeader.tsx (lines ~1388-1428), for the Submit/Approve/Pay button implementations, check isTrackExpenseWorkspace(policy) and override the button text to translate('common.markAsDone')
• In MoneyRequestReportPreviewContent.tsx (lines ~740-876), apply the same override for preview CTA buttons
• In the action badge rendering (sidebar), use actionBadge.markAsDone for track-intent reports

Change 3 — System messages ("marked as done"):

• Add translation key: iou.markedAsDone: 'marked as done'
• In PureReportActionItem.tsx (lines ~1354-1451), for SUBMITTED and APPROVED action types, check isTrackExpenseWorkspace(policy) and use the new translation instead of iou.submitted / iou.approvedMessage
• Note: The optimistic messages in ReportUtils.ts:getIOUReportActionMessage() (line ~7062) are stored server-side and shown in notifications — these may need a backend change to conditionally use "marked as done" text, or can be left as-is if only the rendered UI needs updating

Translation parity: All new English keys need corresponding Spanish translations in es.ts.

What alternative solutions did you explore? (Optional)

1. Overriding policy.description during workspace creation to set "This is where you will track expenses" — simpler but couples a workspace setting to a UI copy concern, and users could accidentally edit/delete it
2. A single boolean flag policy.isTrackWorkspace stored by the backend — cleanest long-term signal but requires a backend schema change. Could be pursued as a follow-up
3. Passing track-intent through translation parameters (e.g., translate('common.submit', {isTrack: true})) — avoids new keys but overloads existing translations and makes them harder to maintain

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[dylanexpensify]

@jayeshmangwani on to you!

[jayeshmangwani]

@MelvinBot, we should use NVP_INTRO_SELECTED to identify the track user. Since this is selected once during account creation, we don’t need to check it at the workspace level, checking at the user level should be sufficient. For example: introSelected?.choice === CONST.ONBOARDING_CHOICES.TRACK_WORKSPACE or introSelected?.choice === CONST.ONBOARDING_CHOICES.PERSONAL_SPEND