Skip to content

[No QA] Update Expensify Card mailing address article with name and phone details - #84460

Merged
NicMendonca merged 5 commits into
mainfrom
claude-updateCardMailingAddress
Mar 10, 2026
Merged

NicMendonca merged 5 commits into
mainfrom
claude-updateCardMailingAddress

Conversation

@MelvinBot

@MelvinBot MelvinBot commented Mar 6, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • Updates the Update-Your-Expensify-Card-Mailing-Address.md article title to "Update Your Expensify Card Details"
  • Adds a section on how to update the name on your Expensify Card via Legal Name under Account > Profile > Private
  • Adds a section on how to update the phone number linked to your Expensify Card for 3D Secure verification
  • Adds FAQ entry for changing the embossed name on a physical card (update legal name + request replacement card)
  • Reformats existing mailing address sections with "How to" headings per authoring guidelines

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

Test plan

  • Verify the article renders correctly on HelpDot
  • Confirm navigation paths match the current UI (Account > Profile > Private > Legal name / Phone number)
  • Verify cross-link to 3D Secure Verification article works correctly

…ails

Updates the article to:
- Change title to "Update Your Expensify Card Details"
- Add section on how to update the name on your Expensify Card
  via Legal Name under Account > Profile > Private
- Add section on how to update the phone number linked to
  your Expensify Card for 3D Secure verification
- Add FAQ entry for changing the embossed name on a physical card
- Reformat existing mailing address sections with "How to" headings

Co-authored-by: Stephanie Elliott <stephanieelliott@users.noreply.github.com>
@github-actions

github-actions Bot commented Mar 6, 2026

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR meaningfully expands the scope of the mailing address article to cover all cardholder-editable details (name, phone number, and mailing address). The restructuring is well-organized, the new sections follow existing patterns in the Expensify Card documentation, and the FAQ addition is a practical complement. There are a few issues around metadata completeness and content duplication with a sibling article that should be addressed.

Scores Summary

  • Readability: 9/10 - Clear, concise instructions with consistent step formatting. Sentences are at an appropriate reading level, and logical flow from name to phone to address works well. One minor inconsistency in navigation phrasing ("Choose Account" in some sections vs. "Go to Account > Wallet" in others) is acceptable given the different destination pages.
  • AI Readiness: 7/10 - Headings are descriptive and use full task phrasing ("How to Update the Name on Your Expensify Card"), which is strong. However, the YAML front matter is missing the internalScope field that other articles in this folder use (see Expensify-Card-3D-Secure-Verification.md for the expected format). The article would also benefit from the filename being updated to match the new broader title, though that may be a separate concern.
  • Style Compliance: 8/10 - Good adherence to Expensify voice and formatting conventions. Proper bold formatting for UI labels, correct terminology ("workspace admin," "Expensify Visa Commercial Card"), and well-structured FAQ section. Two items to note: (1) the new phone number section uses "Under Private, select Phone number" while the existing 3D Secure article uses "Select Phone number" without the "Under Private" qualifier -- these should be consistent across articles; (2) the link text "Expensify Card 3D Secure verification" should use sentence case consistently with the linked article title.

Key Findings

  • Content duplication with 3D Secure article: The new "How to Update the Phone Number Linked to Your Expensify Card" section substantially overlaps with lines 41-52 of Expensify-Card-3D-Secure-Verification.md, which already documents the same steps. Consider whether one article should be the canonical source with the other cross-linking, rather than maintaining parallel step lists that could drift out of sync.
  • Missing internalScope YAML field: The sibling Expensify-Card-3D-Secure-Verification.md article includes an internalScope field. This article should follow the same pattern, e.g.: internalScope: Audience is Expensify Card cardholders. Covers how to update the name, phone number, and mailing address associated with the Expensify Card. Does not cover card activation, spending limits, or workspace admin card settings.
  • Positive -- "How to" heading format: Reformatting all headings with "How to" prefixes is a strong improvement for both scannability and AI retrieval.
  • Positive -- FAQ addition: The FAQ entry for changing the embossed name on a physical card anticipates a natural follow-up question and provides a concise answer.
  • Minor -- Filename mismatch: The file is still named Update-Your-Expensify-Card-Mailing-Address.md while the title is now "Update Your Expensify Card Details." This mismatch could affect URL routing and discoverability. Consider renaming the file to Update-Your-Expensify-Card-Details.md or similar.

Recommendations

  1. Add internalScope to YAML front matter to match the pattern established by other articles in the same folder.
  2. Reconcile phone number update steps with the 3D Secure article to avoid duplication. One option: keep the detailed steps in one article and add a brief mention with a cross-link in the other.
  3. Align step phrasing for the phone number update across both articles (the "Under Private" qualifier is present here but absent in the 3D Secure article).
  4. Consider renaming the file to match the updated title, or note this as a follow-up task.

Files Reviewed

  • docs/articles/new-expensify/expensify-card/Update-Your-Expensify-Card-Mailing-Address.md - Expanded from mailing-address-only to cover name, phone, and address updates. Two new instructional sections and one FAQ entry added. Existing sections reformatted with "How to" headings and minor cleanup.

Review based on the proposed diff only. Unchanged content from the previous version was not evaluated.

Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
@OSBotify

OSBotify commented Mar 6, 2026 •

Copy link
Copy Markdown
Contributor

@stephanieelliott

Copy link
Copy Markdown
Contributor

@MelvinBot can you also compose a new article titled How to Request a New Expensify Card, scoped to how to report a card damaged, lost or stolen in New Expensify? Then cross link the new article and Update-Your-Expensify-Card-Mailing-Address.md where appropriate

…pdate Your Expensify Card Details

Co-authored-by: Stephanie Elliott <stephanieelliott@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

Done! I've added the following changes to this PR:

New article: How-to-Request-a-New-Expensify-Card.md

  • Covers how to report a damaged card (replacement without immediate deactivation)
  • Covers how to report a lost or stolen card (immediate deactivation + replacement)
  • FAQ section addressing common questions (what happens on report, address updates during replacement, virtual card impact, name-update replacements)

Cross-links added to Update-Your-Expensify-Card-Mailing-Address.md:

  • "request a replacement card" link in the name update section (line 24)
  • "request a replacement card" link in the FAQ about updating address after card has shipped (line 80)
  • "request a replacement card" link in the FAQ about legal name not changing on physical card (line 92)

Cross-links in the new article back to the Update article:

  • FAQ answer about updating mailing address during replacement links back to Update Your Expensify Card Details
  • FAQ answer about name updates links back to the legal name update instructions

@stephanieelliott
stephanieelliott requested a review from a team March 10, 2026 02:16
@melvin-bot

melvin-bot Bot commented Mar 10, 2026

Copy link
Copy Markdown

Concierge reviewer checklist:

  • I have verified the accuracy of the article
    • The article is within a hub that makes sense, and the navigation is correct
    • All processes, screenshots, and examples align with current product behavior.
    • All links within the doc have been verified for correct destination and functionality.
  • I have verified the readability of the article
    • The article's language is clear, concise, and free of jargon.
    • The grammar, spelling, and punctuation are correct.
    • The article contains at least one image, or that an image is not necessary
  • I have verified the formatting of the article
    • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
    • The article has proper text spacing and breaks for readability.
  • I have verified the article has the appropriate tone and style
    • The article's tone is professional, friendly, and suitable for the target audience.
    • The article's tone, terminology, and voice are consistent throughout.
  • I have verified the overall quality of the article
    • The article is not missing any information, nor does it contain redundant information.
    • The article fully addresses user needs.
  • I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @NicMendonca

@melvin-bot
melvin-bot Bot requested review from NicMendonca and removed request for a team March 10, 2026 02:16
@melvin-bot

melvin-bot Bot commented Mar 10, 2026

Copy link
Copy Markdown

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

@NicMendonca
NicMendonca merged commit 224f488 into main Mar 10, 2026
14 checks passed
@NicMendonca
NicMendonca deleted the claude-updateCardMailingAddress branch March 10, 2026 16:00
@OSBotify OSBotify mentioned this pull request Mar 10, 2026
46 tasks done
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/NicMendonca in version: 9.3.35-0 🚀

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.3.35-1 🚀

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.

4 participants