Skip to content

Update Concierge welcome copy to describe AI agent#81774

Merged
iwiznia merged 1 commit intomainfrom
claude-updateConciergeWelcomeCopy
Feb 10, 2026
Merged

Update Concierge welcome copy to describe AI agent#81774
iwiznia merged 1 commit intomainfrom
claude-updateConciergeWelcomeCopy

Conversation

@MelvinBot
Copy link
Contributor

Explanation of Change

Updates the Concierge welcome text to introduce Concierge as a personal AI agent with a descriptive sentence: "This is your chat with Concierge, your personal AI agent. I can do almost anything, try me!"

Previously, the Concierge chat welcome message was composed by appending askConcierge ("Ask me anything!") to beginningOfChatHistory ("This chat is with Concierge."), resulting in "This chat is with Concierge. Ask me anything!". This PR changes askConcierge to be a standalone welcome sentence and updates SidebarUtils.ts to use it as the complete message for Concierge chats (replacing the generic intro rather than appending to it).

Updated across all 10 supported languages.

Fixed Issues

$ https://github.com/Expensify/Expensify/issues/596193

Tests

  1. Open the app and navigate to Concierge chat
  2. Verify the welcome text below the hero reads: "This is your chat with Concierge, your personal AI agent. I can do almost anything, try me!"
  3. Verify the text does NOT show the old "This chat is with Concierge. Ask me anything!" format
  4. Open a non-Concierge DM chat and verify it still shows "This chat is with [user]." as before
  5. Switch language to Spanish (or another supported language) and verify the Concierge welcome text is translated appropriately
  • Verify that no errors appear in the JS console

Offline tests

N/A - This is a copy-only change that doesn't affect offline behavior.

QA Steps

  1. Open the app and navigate to Concierge chat
  2. Verify the welcome text below the hero reads: "This is your chat with Concierge, your personal AI agent. I can do almost anything, try me!"
  3. Verify the text does NOT show the old "This chat is with Concierge. Ask me anything!" format
  4. Open a non-Concierge DM chat and verify it still shows "This chat is with [user]." as before
  5. Test across different language settings (Spanish, French, German, etc.) to ensure translations render correctly
  • Verify that no errors appear in the JS console

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
  • 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: Native
Android: mWeb Chrome
iOS: Native
iOS: mWeb Safari
MacOS: Chrome / Safari

cc @rushatgabhane

Changes askConcierge copy from 'Ask me anything!' to a full welcome
sentence that introduces Concierge as a personal AI agent. Also updates
SidebarUtils to use the new copy as the complete welcome message for
Concierge chats instead of appending to the generic chat intro.

Co-authored-by: Rushat Gabhane <rushatgabhane@users.noreply.github.com>
@OSBotify
Copy link
Contributor

OSBotify commented Feb 7, 2026

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/de.ts b/src/languages/de.ts
index bdf66411..0e74fc61 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -918,7 +918,7 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'Dein Bereich',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `Willkommen in ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `Verwende die +‑Taste, um eine Ausgabe zu ${additionalText}.`,
-        askConcierge: 'Dies ist dein Chat mit Concierge, deinem persönlichen KI-Agenten. Ich kann fast alles, probier es aus!',
+        askConcierge: 'Dies ist dein Chat mit Concierge, deinem persönlichen KI-Agenten. Ich kann fast alles – probier es aus!',
         conciergeSupport: 'Dein persönlicher KI-Agent',
         create: 'erstellen',
         iouTypes: {
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 862003a9..f47280d4 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -922,7 +922,7 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'Votre espace',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `Bienvenue dans ${roomName} !`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `Utilisez le bouton + pour ${additionalText} une dépense.`,
-        askConcierge: 'Ceci est votre chat avec Concierge, votre agent IA personnel. Je peux faire presque tout, essayez-moi !',
+        askConcierge: 'Voici votre discussion avec Concierge, votre agent IA personnel. Je peux faire presque tout, essayez-moi !',
         conciergeSupport: 'Votre agent IA personnel',
         create: 'créer',
         iouTypes: {
diff --git a/src/languages/it.ts b/src/languages/it.ts
index dbb9f1d7..5a28981d 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -918,7 +918,7 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'Il tuo spazio',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `Benvenuto in ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `Usa il pulsante + per ${additionalText} una spesa.`,
-        askConcierge: 'Questa è la tua chat con Concierge, il tuo agente IA personale. Posso fare quasi tutto, mettimi alla prova!',
+        askConcierge: 'Questa è la tua chat con Concierge, il tuo assistente personale basato su IA. Posso fare quasi qualsiasi cosa, mettimi alla prova!',
         conciergeSupport: 'Il tuo agente IA personale',
         create: 'crea',
         iouTypes: {
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 6b497b7c..c7060a0d 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -914,7 +914,7 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'あなたのスペース',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `${roomName} へようこそ!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `+ ボタンを使って経費を${additionalText}します。`,
-        askConcierge: 'こちらはあなた専属のAIエージェント、Conciergeとのチャットです。ほぼ何でもできますので、お試しください!',
+        askConcierge: 'これは、あなた専属のAIエージェントであるConciergeとのチャットです。私はほとんど何でもできます、試してみてください!',
         conciergeSupport: 'あなた専用のAIエージェント',
         create: '作成',
         iouTypes: {
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 5fdfb5e7..c2b5813b 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -917,7 +917,7 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'Jouw ruimte',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `Welkom bij ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `Gebruik de +-knop om een uitgave te ${additionalText}.`,
-        askConcierge: 'Dit is je chat met Concierge, je persoonlijke AI-agent. Ik kan bijna alles, probeer het maar!',
+        askConcierge: 'Dit is je chat met Concierge, je persoonlijke AI-agent. Ik kan bijna alles, probeer me maar uit!',
         conciergeSupport: 'Jouw persoonlijke AI-agent',
         create: 'maken',
         iouTypes: {
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index cb61ad8a..2aac0a95 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -918,7 +918,7 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'Twoja przestrzeń',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `Witaj w ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `Użyj przycisku +, aby ${additionalText} wydatek.`,
-        askConcierge: 'To Twój czat z Concierge, Twoim osobistym agentem AI. Mogę zrobić prawie wszystko, wypróbuj mnie!',
+        askConcierge: 'To jest Twój czat z Concierge, Twoim osobistym agentem AI. Potrafię zrobić prawie wszystko, spróbuj mnie!',
         conciergeSupport: 'Twój osobisty agent AI',
         create: 'utwórz',
         iouTypes: {
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index 98d33c51..0ce546df 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -917,7 +917,7 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: 'Seu espaço',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `Bem-vindo(a) a ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `Use o botão + para ${additionalText} uma despesa.`,
-        askConcierge: 'Este é o seu chat com o Concierge, seu agente pessoal de IA. Posso fazer quase tudo, experimente!',
+        askConcierge: 'Este é o seu chat com o Concierge, seu agente de IA pessoal. Posso fazer quase tudo, faça o teste!',
         conciergeSupport: 'Seu agente de IA pessoal',
         create: 'criar',
         iouTypes: {
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 5b7d00cb..10026d53 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -907,7 +907,7 @@ const translations: TranslationDeepObject<typeof en> = {
         yourSpace: '你的空间',
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `欢迎来到 ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `使用 + 按钮来${additionalText}一笔费用。`,
-        askConcierge: '这是您与 Concierge(您的个人 AI 代理)的聊天。我几乎什么都能做,来试试吧!',
+        askConcierge: '这是你与 Concierge 的聊天,你的个人 AI 助手。我几乎无所不能,来试试我吧!',
         conciergeSupport: '您的专属AI助手',
         create: '创建',
         iouTypes: {

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@codecov
Copy link

codecov bot commented Feb 7, 2026

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines Coverage Δ
src/libs/SidebarUtils.ts 77.18% <0.00%> (ø)
... and 17 files with indirect coverage changes

@rushatgabhane
Copy link
Member

@rushatgabhane
Copy link
Member

@MelvinBot mark this ready for review

@MelvinBot MelvinBot marked this pull request as ready for review February 8, 2026 19:14
@MelvinBot MelvinBot requested review from a team as code owners February 8, 2026 19:14
@melvin-bot melvin-bot bot requested review from JmillsExpensify and QichenZhu and removed request for a team February 8, 2026 19:14
@melvin-bot
Copy link

melvin-bot bot commented Feb 8, 2026

@QichenZhu Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@MelvinBot
Copy link
Contributor Author

Done! PR has been marked as ready for review. ✅

@melvin-bot melvin-bot bot removed the request for review from a team February 8, 2026 19:14
@QichenZhu
Copy link
Contributor

Hi @rushatgabhane,

  1. Does this need C+ testing and review?
  2. Has the copy been approved and Spanish translation been verified?

Thanks!

@iwiznia
Copy link
Contributor

iwiznia commented Feb 9, 2026

  1. Yes
  2. Yes

LMK when you reviewed

@MelvinBot
Copy link
Contributor Author

The failing checklist check is not related to the code changes in this PR. It's a process check that fails because no reviewer checklist comment was found on the PR.

Analysis: The error is No PR Reviewer Checklist was found. This check triggers when a review is submitted and looks for a reviewer checklist comment. The author's PR checklist (in the PR body) passed separately — this second checklist run specifically requires a reviewer to post the standard reviewer checklist.

Resolution: A reviewer needs to copy and post the Reviewer Checklist as a comment on this PR. This is not a code fix — it's a process step that must be completed manually by the reviewer.

@QichenZhu
Copy link
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible 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 checked that screenshots or videos are included for tests on all platforms
    I don't think the agent can add screenshots for now.
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
    https://expensify.slack.com/archives/C02NK2DQWUX/p1769657058877489
  • I verified there are no new alerts related to the canBeMissing param for useOnyx
  • I verified proper code patterns were followed (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
    • 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 verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • 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
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately and each prop has a /** comment above it */
    • The file is named correctly
    • The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
    • The only data being stored in the state is data necessary for rendering and nothing else
    • For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
    • Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
    • All JSX used for rendering exists in the render method
    • The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
  • 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 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.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this 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.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
android-native.webm
Android: mWeb Chrome
android-web.webm
iOS: HybridApp
ios-native.mov
iOS: mWeb Safari
ios-web.mov
MacOS: Chrome / Safari
mac-web.mov

Copy link
Contributor

@QichenZhu QichenZhu left a comment

Choose a reason for hiding this comment

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

LGTM.

cc @iwiznia

@iwiznia iwiznia merged commit 292a97c into main Feb 10, 2026
37 of 38 checks passed
@iwiznia iwiznia deleted the claude-updateConciergeWelcomeCopy branch February 10, 2026 11:25
@github-actions
Copy link
Contributor

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

@OSBotify
Copy link
Contributor

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

@github-actions
Copy link
Contributor

@OSBotify
Copy link
Contributor

🚀 Deployed to staging by https://github.com/iwiznia in version: 9.3.17-0 🚀

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

@OSBotify
Copy link
Contributor

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.17-9 🚀

platform result
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 iOS 🍎 failure ❌

marcochavezf added a commit that referenced this pull request Mar 2, 2026
The LOOKING_AROUND intent still sent a support-era message about expenses,
travel, and corporate card management, which conflicts with the new AI-focused
Concierge welcome shipped in PRs #81331/#81774. This narrows the PR scope to
only the LOOKING_AROUND cleanup:

- Remove onboardingLookingAroundMessage from all 10 language files
- Set message to empty string for LOOKING_AROUND in OnboardingFlow.ts
- Add message guard to prevent pushing empty messages to guidedSetupData
- Add skipSignOff logic to suppress "It's great to meet you!" for LOOKING_AROUND
- Add unit tests for LOOKING_AROUND onboarding behavior

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
marcochavezf added a commit that referenced this pull request Mar 4, 2026
The LOOKING_AROUND intent still sent a support-era message about expenses,
travel, and corporate card management, which conflicts with the new AI-focused
Concierge welcome shipped in PRs #81331/#81774. This narrows the PR scope to
only the LOOKING_AROUND cleanup:

- Remove onboardingLookingAroundMessage from all 10 language files
- Set message to empty string for LOOKING_AROUND in OnboardingFlow.ts
- Add message guard to prevent pushing empty messages to guidedSetupData
- Add skipSignOff logic to suppress "It's great to meet you!" for LOOKING_AROUND
- Add unit tests for LOOKING_AROUND onboarding behavior

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
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.

5 participants