Add Concierge to the Side Panel = Concierge Everywhere!

[blazejkustra]

Explanation of Change

Adds concierge chat into the side panel so users can access it from whatever point for the app. It's part of a bigger project.

Latest slack convo about this.

Fixed Issues

$ #75804
PROPOSAL: N/A

Tests

For now concierge button and side panel will only be accessible on staging/adhoc/locally

• Verify that Concierge button is displayed on web and on native it's not available
• Verify that it opens concierge chat on the side (on smaller screens it should be a RHP)
• Verify it looks good on different sizes of the screen
• Verify that the chat works well (attachments, emoji picker etc) - navigation won't happen in the panel instead if you navigate it should be in the app
• Verify that modal looks good with tooltips displayed on the screen and other modals such as attachment screen, popovers etc

Offline tests

N/A

QA Steps

Same as tests

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
• If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
• If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
• If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
• If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
  • I verified that all the inputs inside a form are aligned with each other.
  • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
• If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
• If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: mWeb Chrome

iOS: mWeb Safari

Simulator.Screen.Recording.-.iPhone.15.Plus.-.2025-12-05.at.17.26.44.mov

MacOS: Chrome / Safari

Screen.Recording.2025-12-05.at.17.19.29.mov

[codecov]

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
src/CONST/index.ts	83.47% <ø> (ø)
...ponents/FocusTrap/FocusTrapForScreen/index.web.tsx	0.00% <ø> (ø)
src/components/HeaderWithBackButton/index.tsx	90.78% <100.00%> (ø)
src/components/Modal/ReanimatedModal/index.tsx	82.75% <100.00%> (+0.30%)	⬆️
src/components/Navigation/TopBar.tsx	100.00% <100.00%> (ø)
...MeasuredContent/PopoverWithMeasuredContentBase.tsx	75.92% <100.00%> (-0.44%)	⬇️
src/components/ScreenWrapper/index.tsx	94.73% <ø> (ø)
.../Search/SearchPageHeader/SearchPageHeaderInput.tsx	36.87% <ø> (ø)
...mponents/Search/SearchRouter/SearchRouterModal.tsx	100.00% <100.00%> (ø)
...ponents/SidePanel/SidePanelButton/index.native.tsx	100.00% <100.00%> (ø)
... and 23 more
... and 11 files with indirect coverage changes

[github-actions]

🚧 @marcochavezf has triggered a test Expensify/App build. You can view the workflow run here.

[github-actions]

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪
Built from App PR #76277.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/76277/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/76277/index.html

Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/76277/NewExpensify.dmg	https://76277.pr-testing.expensify.com

---

👀 View the workflow run that generated this build 👀

[blazejkustra]

In case of minor bugs, please raise them but we can fix in a follow up early next week 🙏 I'm OOO today and hope there won't be any major problems, thank you all!

[aimane-chnaif]

Approved. Please fix conflict

[blazejkustra]

Back to you @marcochavezf @marcaaron

[marcochavezf]

🎉

[OSBotify]

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

[OSBotify]

🚀 Deployed to staging by https://github.com/marcochavezf in version: 9.2.85-0 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[lanitochka17]

This PR is failing because of issue ##78171

The issue is reproducible in: Web

Bug7034049_1766188543832.1.mp4

[OSBotify]

🚀 Deployed to production by https://github.com/marcaaron in version: 9.2.85-7 🚀

platform	result
🖥 desktop 🖥	success ✅
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

[linhvovan29546]

Following the checklist from #82291. This function auto close the Side Panel on narrow screens, which caused the bug described there. We fixed this by preventing the side panel from closing when open the attachment page.

[FitseTLT]

Flagging a latent bug from this PR, caught in #96580 and fixed by #98982.

SidePanelOverlay.tsx L28-L29 opted the backdrop into reanimated entering/exiting layout animations. On web those keyframes run for only DEFAULT_IN = 1ms, and reanimated's web layout-animation path can leave the element stranded at visibility: hidden.

That one stuck property produces both reported symptoms at once, because the backdrop is both the dimming layer and the outside-press catcher: the page stops being dimmed, and nothing sits above the FAB to intercept the press — so it reads as a frozen page rather than a missing animation.

The fix drops the layout animation entirely; the overlay is already opacity-driven via styles.sidePanelOverlayOpacity(shouldBeVisible), so nothing visual was lost.

Worth a general note for reviewers: a reanimated layout animation on an element that also does hit-testing is risky on web, because a failed animation degrades interactivity and not just appearance.