You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Due for payment 2026-11-16] [$175] Home - "Getting started" tile shows "Talk to your account executive" for a user with no assigned Guide; should show "Talk to Concierge" #106108
Version Number: Reproducible in staging?: Needs Reproduction Reproducible in production?: Needs Reproduction If this was caught during regression testing, add the test name, ID and link from BrowserStack: Email or phone of affected tester (no customers): Logs:https://stackoverflow.com/c/expensify/questions/4856 Expensify/Expensify Issue URL: Issue reported by:@flaviadefaria Slack conversation (hyperlinked to channel name): #Expensify Bugs
Action Performed:
Sign in as a user who selected a track intent (e.g., track expenses) during onboarding and has no assigned Guide.
Go to the Home page.
Look at the Getting started tile.
Expected Result:
Since the user has no assigned Guide, the tile should offer the option to talk to Concierge instead.
Actual Result:
The tile shows "Talk to your account executive", even though the user isn't assigned to a Guide.
Workaround:
Unknown
Platforms:
Select the officially supported platforms where the issue was reproduced:
Likely cause (medium confidence): Getting started treats any nonempty account.guideDetails.email as an assigned human Guide. If that email belongs to Concierge, the tile incorrectly shows “Talk to your account executive.” Onboarding intent does not select this label.
This is a verified code defect, but its connection to this report remains unconfirmed: the issue does not include the affected account state, and the supplied web session lacked the Getting started tile.
Truly absent/empty Guide email already selects Concierge, so missing data alone cannot explain the reported wording. A stale human Guide email could produce the same symptom and would require separate confirmation.
To establish the reported cause, inspect the affected account’s guideDetails.email when the tile renders and compare it with freshly fetched account data. No production account evidence was available in this investigation.
What changes do you think we should make in order to solve the problem?
Require a nonempty, non-Concierge Guide email before showing account-executive copy, comparing Concierge’s email case-insensitively. Keep the decision independent of onboarding intent so genuinely assigned Guides still appear for expense-tracking users.
Regression coverage and scope
Extend GettingStartedSectionTest.tsx:467–499 to cover missing/empty Guide email, Concierge, uppercase Concierge, and a human Guide for both tracking intents. Verify the label updates when assignment data changes.
Keep navigation unchanged for this label-only issue: GettingStartedSection/index.tsx:37–50 currently opens the workspace’s admins room regardless of label. This proposal does not change it to a direct chat.
What alternative solutions did you explore? (Optional)
Always showing Concierge for tracking intents would hide legitimate Guide assignments. Changing translations would not correct the assignment check. If the affected account instead contains a stale human Guide email, the proposed Concierge exclusion would not resolve that case.
Next Steps for Contributor+ team: To accept:@MelvinBot implement [this](https://github.com/Expensify/App/issues/106108) to create a draft PR. To refine:@MelvinBot <your feedback> To reject: Explain why you are rejecting Melvin's proposal.
Verified on dev NewDot web: signed in and already on Home, but Getting started is absent. The reported footer mismatch could not be reproduced with this fixture; source inspection supports the hypothesis.
Step
Status
Signed in, track-expenses intent, no human GuideSigned-in state confirmed. Track-expenses intent and absence of a human Guide could not be established. Prestart selected “Something else,” not track expenses. Guide email was not exposed by the inspected UI; no state was injected or mocked.
❌
Go to HomeThe session was already on Home; the full snapshot confirmed the Home heading and expense controls.
✅
Inspect Getting started footerHome contained neither Getting started nor either footer label. This verification was blocked, not confirmation of the reported mismatch.
changed the title [-]Home - "Getting started" tile shows "Talk to your account executive" for a user with no assigned Guide; should show "Talk to Concierge"[/-][+][$175] Home - "Getting started" tile shows "Talk to your account executive" for a user with no assigned Guide; should show "Talk to Concierge"[/+]on Nov 5, 2026
Hi @camesenin I already told you to read the contributor guide in this issue, and you said you had done so. Please read it again.
Submitting a proposal before the “Help wanted” label doesn’t make sense, because such proposals aren’t reviewed by the C+ team, even if that label is added later, and all it does is clutter up the issue thread. This directly contradicts the rule here:
4. Proposals must only be posted after the `Help Wanted` label is added. Any proposals submitted beforehand will be ignored and not reviewed. Do not post proposals in Slack. MelvinBot is an exception: it may post a proposal before `Help Wanted` is applied.
I suspect that if you keep doing this, you’ll receive a warning, and if you do it again after that, you might even get banned.
@MelvinBot I have tried to reproduce this one and i reproduced this, but my guide email is qa.guide@team.expensify.com - is this expected ot this is the same bug?
That wording is expected from the current code, but it does not prove the Guide assignment is correct. The footer treats any nonempty account.guideDetails.email—including qa.guide@team.expensify.com—as an account executive (GettingStartedSection/index.tsx:31–54).
The QA address is also used as an onboarding fallback when a policy has no assigned Guide email (ReportUtils.ts:13730–13752). However, that fallback does not populate account.guideDetails, so it does not explain why your account has this value.
Your case is not covered by my earlier Concierge-only proposal; that change would leave your label unchanged. It reproduces the wording, but we still need confirmation that the account genuinely has no assigned Guide before calling it the same bug. The missing evidence is whether fresh account data still supplies this QA address and whether it represents an intentional test assignment or a placeholder. We should establish that before selecting a fix—not assume the QA address represents a human Guide or simply add it to an exclusion list.
Activity
MelvinBot commentedon Nov 5, 2026
Proposal
What is the root cause of that problem?
Likely cause (medium confidence): Getting started treats any nonempty
account.guideDetails.emailas an assigned human Guide. If that email belongs to Concierge, the tile incorrectly shows “Talk to your account executive.” Onboarding intent does not select this label.This is a verified code defect, but its connection to this report remains unconfirmed: the issue does not include the affected account state, and the supplied web session lacked the Getting started tile.
Code evidence and alternatives checked
hasGuideas!!guideDetails?.emailand uses it to select the label.guideDetails.emailwhen the tile renders and compare it with freshly fetched account data. No production account evidence was available in this investigation.What changes do you think we should make in order to solve the problem?
Require a nonempty, non-Concierge Guide email before showing account-executive copy, comparing Concierge’s email case-insensitively. Keep the decision independent of onboarding intent so genuinely assigned Guides still appear for expense-tracking users.
Regression coverage and scope
Extend GettingStartedSectionTest.tsx:467–499 to cover missing/empty Guide email, Concierge, uppercase Concierge, and a human Guide for both tracking intents. Verify the label updates when assignment data changes.
Keep navigation unchanged for this label-only issue: GettingStartedSection/index.tsx:37–50 currently opens the workspace’s admins room regardless of label. This proposal does not change it to a direct chat.
What alternative solutions did you explore? (Optional)
Always showing Concierge for tracking intents would hide legitimate Guide assignments. Changing translations would not correct the assignment check. If the affected account instead contains a stale human Guide email, the proposed Concierge exclusion would not resolve that case.
Next Steps for Contributor+ team:
To accept:
@MelvinBot implement [this](https://github.com/Expensify/App/issues/106108)to create a draft PR.To refine:
@MelvinBot <your feedback>To reject: Explain why you are rejecting Melvin's proposal.
view run
MelvinBot commentedon Nov 5, 2026
🤖 Web test steps verification results:⚠️ partial
Verified on dev NewDot web: signed in and already on Home, but Getting started is absent. The reported footer mismatch could not be reproduced with this fixture; source inspection supports the hypothesis.
Signed in, track-expenses intent, no human Guide
Signed-in state confirmed. Track-expenses intent and absence of a human Guide could not be established. Prestart selected “Something else,” not track expenses. Guide email was not exposed by the inspected UI; no state was injected or mocked.Go to Home
The session was already on Home; the full snapshot confirmed the Home heading and expense controls.Inspect Getting started footer
Home contained neither Getting started nor either footer label. This verification was blocked, not confirmation of the reported mismatch.Read-only code hypothesis
GettingStartedSection/index.tsx:31–54 treats any nonempty Guide email as an account executive. In contrast, HelpPage.tsx:39–45 explicitly recognizes Concierge. No source edits were made.view run · view recording
melvin-bot commentedon Nov 5, 2026
Triggered auto assignment to Contributor-plus team member for initial proposal review - @Eskalifer1 (
External)[-]Home - "Getting started" tile shows "Talk to your account executive" for a user with no assigned Guide; should show "Talk to Concierge"[/-][+][$175] Home - "Getting started" tile shows "Talk to your account executive" for a user with no assigned Guide; should show "Talk to Concierge"[/+]melvin-bot commentedon Nov 5, 2026
Job added to Upwork: https://www.upwork.com/jobs/~022118355172841450629
camesenin commentedon Nov 5, 2026
melvin-bot commentedon Nov 5, 2026
✅ Contributor details stored successfully. Thank you for contributing to Expensify!
Eskalifer1 commentedon Nov 5, 2026
Hi @camesenin I already told you to read the contributor guide in this issue, and you said you had done so. Please read it again.
Submitting a proposal before the “Help wanted” label doesn’t make sense, because such proposals aren’t reviewed by the C+ team, even if that label is added later, and all it does is clutter up the issue thread. This directly contradicts the rule here:
App/contributingGuides/CONTRIBUTING.md
Line 164 in 9f368d2
I suspect that if you keep doing this, you’ll receive a warning, and if you do it again after that, you might even get banned.
Eskalifer1 commentedon Nov 5, 2026
@MelvinBot I have tried to reproduce this one and i reproduced this, but my guide email is
qa.guide@team.expensify.com- is this expected ot this is the same bug?MelvinBot commentedon Nov 5, 2026
That wording is expected from the current code, but it does not prove the Guide assignment is correct. The footer treats any nonempty
account.guideDetails.email—including qa.guide@team.expensify.com—as an account executive (GettingStartedSection/index.tsx:31–54).The QA address is also used as an onboarding fallback when a policy has no assigned Guide email (ReportUtils.ts:13730–13752). However, that fallback does not populate
account.guideDetails, so it does not explain why your account has this value.Your case is not covered by my earlier Concierge-only proposal; that change would leave your label unchanged. It reproduces the wording, but we still need confirmation that the account genuinely has no assigned Guide before calling it the same bug. The missing evidence is whether fresh account data still supplies this QA address and whether it represents an intentional test assignment or a placeholder. We should establish that before selecting a fix—not assume the QA address represents a human Guide or simply add it to an exclusion list.
view run
32 remaining items
expensify-chore-bot commentedon Nov 15, 2026
Triggered auto assignment to @mallenexpensify (
Awaiting Payment)expensify-chore-bot commentedon Nov 15, 2026
Payment Summary
Resolving PRs:
Upwork Job
BugZero Checklist (@mallenexpensify)
mallenexpensify commentedon Nov 17, 2026
Claude posting on behalf of Matt:
Waiting on C+ checklist from @Eskalifer1.
Job price: $175 (standard, no Help Wanted, assigned 2026-11-05). Eskalifer1 (C+): 100%, via Upwork, once the checklist is in.
No deploy blockers.
Evidence
PAYPREP v1Eskalifer1 commentedon Nov 18, 2026
No Checklist Needed
No reliable ways to reproduce this bug
mallenexpensify commentedon Nov 19, 2026
Payment Summary
Contributor+: @Eskalifer1 paid $175 via Upwork
@Eskalifer1 can you please accept the job below? Please reply here and tag me once you have.
https://www.upwork.com/jobs/~022118355172841450629
Eskalifer1 commentedon Nov 19, 2026
I have accepted, thank you!
mallenexpensify commentedon Nov 19, 2026
@Eskalifer1 paid, summary updated above. Thx.