[No QA] Create How-Concierge-Analyzes-Spend.md

[stephanieelliott]

Summary

Update the help documentation to describe the Concierge management report feature (internally known as "virtual CFO"). This is an evolving feature that proactively analyzes workspace data and surfaces helpful insights to users.

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

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR introduces a new article explaining how Concierge proactively analyzes workspace spend. The article is well-structured, clearly written, and covers a single focused workflow. However, there are a few governance compliance issues that should be addressed before merging — most notably the use of full URLs instead of relative links, a missing required "How to..." heading, and a missing question mark on one heading.

Scores Summary

• Readability: 9/10 - Clear, scannable prose. Bullet lists are well-organized, FAQ answers are concise and direct. The article flows logically from what Concierge does, to where it appears, to how it relates to Insights.
• AI Readiness: 7/10 - YAML metadata is complete and well-crafted (title, description, keywords, internalScope all present). However, the article is missing at least one "How to..." heading, which is a mandatory requirement for AI retrieval optimization (Section 6 of HELP_AUTHORING_GUIDELINES.md). All headings do start with question words (What, Where, How), which is good.
• Style Compliance: 6/10 - Three cross-links use full URLs (https://help.expensify.com/...) instead of relative links, which violates the cross-linking standards. One heading is missing a question mark. Insights is correctly bolded as a UI/feature reference throughout.

Key Findings

• Full URLs must be converted to relative links. HELP_AUTHORING_GUIDELINES.md Section 7 states: "Use relative links only. Do not use full URLs." All three links in the article use full URLs.
• Missing "How to..." heading. Section 6 requires "at least one full 'How to...' heading using feature name." The current headings use "What kinds of..." / "Where does..." / "How ... relate to..." — none use the "How to..." format. Consider restructuring one heading, e.g., "How to understand Concierge spend analyses" or adding a "How to" section.
• Missing question mark. The heading ## Where does Concierge share spend analyses is phrased as a question but lacks a trailing ?. Other question-format headings in the article do include the question mark — this should be consistent.
• Positive: Strong metadata. The internalScope field is well-written and clearly defines the audience (Workspace Admins and Members) and explicitly excludes related workflows (Insights, custom reports).
• Positive: Good cross-link discipline. Links are used sparingly and with descriptive anchor text (e.g., "learn how to use Insights," "use search operators to filter and analyze spend"). No "click here" or "read more" phrasing.
• Positive: Single workflow focus. The article stays tightly scoped to Concierge spend analysis without drifting into Insights usage or report configuration.

Recommendations

1. Convert all three full URLs to relative links. For example, change https://help.expensify.com/articles/new-expensify/insights/How-to-Use-Insights-in-Expensify to /articles/new-expensify/insights/How-to-Use-Insights-in-Expensify.
2. Add or restructure a heading to include "How to..." phrasing. For example, rename "How Concierge spend analyses relate to Insights" to "How to use Concierge spend analyses with Insights," or add a new section such as "How to review Concierge spend analyses."
3. Add a question mark to the heading ## Where does Concierge share spend analyses.

Files Reviewed

• docs/articles/new-expensify/concierge-ai/How-Concierge-Analyzes-Spend.md — New article. Needs relative link fixes, a "How to..." heading, and a punctuation correction. Otherwise well-written and well-structured.

Note: Detailed line-by-line feedback has been provided as inline comments.

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://183ff725.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/concierge-ai/How-Concierge-Analyzes-Spend

[melvin-bot]

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 @lydiabarclay

[melvin-bot]

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

[stephanieelliott]

Resolved all bot comments

[github-actions]

Duplicate keyword: "spend analysis" appears twice in the keywords array. Remove the duplicate to keep metadata clean.

Suggested change

	keywords: [New Expensify, Concierge, spend analysis, Concierge management report, insights, AI, expense trends, proactive insights, spend monitoring, spend analysis, flux analysis]
	keywords: [New Expensify, Concierge, spend analysis, Concierge management report, insights, AI, expense trends, proactive insights, spend monitoring, flux analysis]

[github-actions]

Missing required "How to" heading / non-task-based heading: Per HELP_AUTHORING_GUIDELINES Section 6, every article must include at least one full "How to..." heading using the feature name. This article has no "How to" heading. Additionally, "How Concierge spend analysis relates to Insights" describes a relationship rather than a user task or action.

Consider restructuring this heading (or another section) to include a "How to" task. For example:

## How to use Concierge spend analysis alongside Insights

This would satisfy both the task-based heading requirement and the mandatory "How to" heading requirement.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds a new informational article explaining how Concierge proactively analyzes workspace spend. The article is well-structured, clearly written, and covers a single workflow as required. YAML metadata is thorough and cross-links are properly formatted. A few governance compliance gaps need attention before merge.

Scores Summary

• Readability: 9/10 - Clear, scannable prose with effective use of bullet lists. Paragraphs are concise and benefit-focused. The article flows logically from what Concierge does, to where insights appear, to how it relates to Insights.
• AI Readiness: 7/10 - YAML metadata is complete and well-formed with good keyword coverage. However, the article is missing a required "How to..." heading (Section 6 of HELP_AUTHORING_GUIDELINES.md mandates at least one). The keyword array also contains a duplicate entry ("spend analysis" appears twice).
• Style Compliance: 8/10 - UI feature names like Insights are consistently bolded. Cross-links use relative paths with descriptive anchor text and are never placed inside numbered steps. All section headings begin with question words (What, Where, How), satisfying the task-based heading rule.

Key Findings

• Missing required "How to..." heading. Per Section 6 of HELP_AUTHORING_GUIDELINES.md, every article must include at least one full "How to..." heading using the feature name. None of the current ## headings qualify. Consider renaming one, for example: ## How to find Concierge spend analysis insights or adding a new section such as ## How to review Concierge spend analysis insights in the #admins room.
• Duplicate keyword. The keywords array lists "spend analysis" twice. Remove the duplicate to keep metadata clean.
• No "Who can use..." section. The TEMPLATE.md recommends a ## Who can use [feature name] section to clarify required roles, plans, and permissions. Since the internalScope specifies Workspace Admins and Members, adding this section would strengthen the article and improve retrieval for role-based queries.
• Positive: Single-workflow focus. The article correctly limits scope to Concierge spend analysis and defers Insights and search operators to linked articles.
• Positive: Cross-links are well-placed. Links appear after explanatory content, use descriptive anchor text, and point to relevant companion articles.
• Positive: FAQ section is clean. All FAQ questions are task-based and include the feature name, consistent with governance rules.

Recommendations

1. [Required] Add or rename a heading to include "How to" phrasing (e.g., ## How to find Concierge spend analysis insights). This is a mandatory requirement per the authoring guidelines.
2. [Required] Remove the duplicate "spend analysis" entry from the keywords array.
3. [Suggested] Add a ## Who can use Concierge spend analysis section clarifying that insights are delivered to the #admins room and visible to Workspace Admins (and any Members with access to that room).
4. [Minor] Verify that "#admins room" matches the exact UI label in the product. If the UI displays it differently (e.g., #admins), adjust to match.

Files Reviewed

• docs/articles/new-expensify/concierge-ai/How-Concierge-Analyzes-Spend.md -- New file. Well-written informational article with minor governance gaps noted above.

Note: This review is based solely on the proposed changes in the PR diff, scored against the HelpDot governance files (HELPSITE_NAMING_CONVENTIONS.md, HELP_AUTHORING_GUIDELINES.md, TEMPLATE.md).

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.3.70-0 🚀

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

Bundle Size Analysis (Sentry):

• iOS

[OSBotify]

🚀 Deployed to staging by https://github.com/stephanieelliott in version: 9.3.72-0 🚀

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

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to production by https://github.com/lakchote in version: 9.3.72-1 🚀

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