Skip to content

Update Concierge copy to reflect AI agent identity#81331

Merged
iwiznia merged 1 commit intomainfrom
claude-updateConciergeCopy
Feb 4, 2026
Merged

Update Concierge copy to reflect AI agent identity#81331
iwiznia merged 1 commit intomainfrom
claude-updateConciergeCopy

Conversation

@MelvinBot
Copy link
Contributor

@MelvinBot MelvinBot commented Feb 3, 2026

Summary

  • Updates conciergeSupport from "24/7 support" to "Your personal AI agent"
  • Updates askConcierge from "Ask questions and get 24/7 realtime support." to "Ask me anything!"
  • 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 Concierge chat header displays "Your personal AI agent" instead of "24/7 support"
  3. Verify the welcome text in Concierge chat shows "Ask me anything!" instead of the previous support-focused text
  • 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 Concierge chat header displays "Your personal AI agent" instead of "24/7 support"
  3. Verify the welcome text in Concierge chat shows "Ask me anything!" instead of the previous support-focused text
  4. 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 @quinthar

Updates the Concierge description from "24/7 support" to "Your personal AI agent"
and changes the prompt from support-focused text to "Ask me anything!" across
all supported languages.

Languages updated: English, German, Spanish, French, Italian, Japanese, Dutch,
Polish, Portuguese (Brazilian), and Simplified Chinese.

Relates to Expensify/Expensify#596193

Co-authored-by: David Barrett <quinthar@users.noreply.github.com>
@MelvinBot MelvinBot requested review from a team as code owners February 3, 2026 16:56
@melvin-bot melvin-bot bot requested review from JmillsExpensify and iwiznia and removed request for a team February 3, 2026 16:56
@melvin-bot
Copy link

melvin-bot bot commented Feb 3, 2026

@iwiznia 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]

@melvin-bot melvin-bot bot removed the request for review from a team February 3, 2026 16:56
@OSBotify
Copy link
Contributor

OSBotify commented Feb 3, 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 b24add81..ad5370e1 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -911,7 +911,7 @@ const translations: TranslationDeepObject<typeof en> = {
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `Willkommen in ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `Verwende die +‑Taste, um eine Ausgabe zu ${additionalText}.`,
         askConcierge: 'Frag mich alles!',
-        conciergeSupport: 'Dein persönlicher KI-Agent',
+        conciergeSupport: 'Ihr persönlicher KI-Agent',
         create: 'erstellen',
         iouTypes: {
             pay: 'bezahlen',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index 328c35ce..2a59e8a0 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -914,7 +914,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: 'Posez-moi vos questions !',
+        askConcierge: 'Posez-moi toutes vos questions !',
         conciergeSupport: 'Votre agent IA personnel',
         create: 'créer',
         iouTypes: {
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 40cc83c1..e978d8b2 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -909,8 +909,8 @@ 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: 'Vraag me alles!',
-        conciergeSupport: 'Jouw persoonlijke AI-agent',
+        askConcierge: 'Stel me alles wat je wilt vragen!',
+        conciergeSupport: 'Je persoonlijke AI-agent',
         create: 'maken',
         iouTypes: {
             pay: 'betalen',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index cbd35e0a..827b02ff 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -900,7 +900,7 @@ const translations: TranslationDeepObject<typeof en> = {
         welcomeToRoom: ({roomName}: WelcomeToRoomParams) => `欢迎来到 ${roomName}!`,
         usePlusButton: ({additionalText}: UsePlusButtonParams) => `使用 + 按钮来${additionalText}一笔费用。`,
         askConcierge: '尽管问我任何问题!',
-        conciergeSupport: '您的专属AI助手',
+        conciergeSupport: '你的个人 AI 助理',
         create: '创建',
         iouTypes: {
             pay: '支付',

Note

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

View workflow run

@MelvinBot
Copy link
Contributor Author

🤖 Fixed the failing checklist check

The PR body was missing the required ### PR Author Checklist section that the authorChecklist GitHub Action expects. The action was failing with:

TypeError: Cannot read properties of undefined (reading 'split')

I've updated the PR body to include the full PR template with the author checklist section. The checks should pass now.

@MelvinBot
Copy link
Contributor Author

🤖 Check Failure Analysis

The failing checklist check is due to incomplete PR Author Checklist items, not a code issue.

Status: 39 of 51 checklist items completed, 12 remaining.

Unchecked items requiring attention:

  1. ✅ Verify no JS console errors (Testing section + QA section)
  2. ✅ Add steps to cover failure scenarios
  3. ✅ Offline behavior testing verification
  4. ✅ High Traffic account testing
  5. ✅ Include screenshots/videos for all platforms
  6. ✅ Platform testing verification:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  7. ✅ Verify no new canBeMissing param alerts

Required Action: The PR author needs to:

  1. Complete the testing on all platforms
  2. Add screenshots/videos in the designated sections
  3. Check off each box after verification

This is a copy-only change (language file updates), so most of the testing should be straightforward - just verify the new strings display correctly in the Concierge chat on each platform.


⚠️ I cannot fix this automatically as it requires manual testing and verification by the PR author.

@codecov
Copy link

codecov bot commented Feb 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
see 7 files with indirect coverage changes

@iwiznia
Copy link
Contributor

iwiznia commented Feb 4, 2026

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

@iwiznia iwiznia merged commit 48d0778 into main Feb 4, 2026
36 of 49 checks passed
@iwiznia iwiznia deleted the claude-updateConciergeCopy branch February 4, 2026 14:59
@github-actions
Copy link
Contributor

github-actions bot commented Feb 4, 2026

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

@MelvinBot
Copy link
Contributor Author

🤖 CI Check Analysis

The failing check is the PR Author Checklist - not a code or test failure.

Issue: The PR checklist has 50 out of 51 items completed. The unchecked items are:

- [ ] Verify that no errors appear in the JS console

This appears twice in the PR description (once in "Tests" section and once in "QA Steps" section).

Resolution: This is a manual verification step that needs to be confirmed by the PR author. If you've verified there are no JS console errors, please update the PR description to check those boxes:

- - [ ] Verify that no errors appear in the JS console
+ - [x] Verify that no errors appear in the JS console

All other CI checks (linting, tests, builds, type checking, etc.) are passing ✅

@MelvinBot
Copy link
Contributor Author

🤖 Check Failure Analysis

All the code-related checks on this PR are passing

The failing check is the PR Author Checklist workflow. This fails because there are 2 unchecked items in the PR body:

  • [ ] Verify that no errors appear in the JS console (under Tests section)
  • [ ] Verify that no errors appear in the JS console (under QA Steps section)

This is not a code issue - it's a checklist completion reminder for the PR author to confirm they've verified no console errors during testing.

To fix: The PR author should check those boxes once they've verified there are no console errors:

- [x] Verify that no errors appear in the JS console

This check will pass automatically once all checkboxes in the PR template are marked complete.

@OSBotify
Copy link
Contributor

OSBotify commented Feb 4, 2026

✋ 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
Copy link
Contributor

OSBotify commented Feb 5, 2026

🚀 Deployed to staging by https://github.com/iwiznia in version: 9.3.13-1 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Feb 5, 2026

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

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

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.

3 participants