Skip to content

[No QA] Docs updates for E/A#96065 interactive Concierge spend charts - #97738

Merged
inimaga merged 1 commit into
mainfrom
docs-victory-chart-clickable-96065
Aug 7, 2026
Merged

inimaga merged 1 commit into
mainfrom
docs-victory-chart-clickable-96065

Conversation

@MelvinBot

Copy link
Copy Markdown
Contributor

Explanation of Change

#96065 adds clickable/hoverable metadata support to the embedded Victory bar charts that Concierge renders in chat. When you ask Concierge for spending as a chart, you can now hover a bar to see a tooltip and click a bar to open the matching expenses on the Search page (web).

The existing help article How Concierge Analyzes Spend covers asking Concierge about your expense data but did not mention that Concierge can return an interactive chart. This PR adds a short, task-based section documenting that behavior.

What changed

  • Added a new ## How to explore a Concierge spend chart section to How-Concierge-Analyzes-Spend.md describing:
    • Concierge can reply with an interactive bar chart in chat.
    • On web, hover a bar to see a tooltip.
    • On web, select a bar to open its matching expenses on the Search page.
  • Added spend chart, bar chart, and Concierge chart to the article keywords for retrieval.

Authoring compliance

  • Reused the existing article (single workflow, in-scope) rather than creating a new one.
  • Task-based ## How to… heading, exact UI labels (Search), #/## headings only — per HELP_AUTHORING_GUIDELINES.md, HELPSITE_NAMING_CONVENTIONS.md, and TEMPLATE.md.
  • Scoped the interactive behavior to web, matching what the source PR implemented and tested (web hover tooltips); no unverified mobile parity claims.

Source


@inimaga, please review the files changed and confirm they reflect the current behavior. Then post a new comment saying @MelvinBot mark this PR as ready for review.

…earch)

Co-authored-by: Issa Nimaga <inimaga@users.noreply.github.com>
@MelvinBot MelvinBot added the HelpDot Apply this label if the issue relates to ExpensifyHelp label Aug 3, 2026
@github-actions github-actions Bot changed the title Docs updates for E/A#96065 interactive Concierge spend charts [No QA] Docs updates for E/A#96065 interactive Concierge spend charts Aug 4, 2026
@OSBotify

OSBotify commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

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

Updated articles:

@inimaga
inimaga marked this pull request as ready for review August 4, 2026 15:12
@github-actions

github-actions Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR adds a single new section, How to explore a Concierge spend chart, to the existing How-Concierge-Analyzes-Spend.md article, plus three new keywords (spend chart, bar chart, Concierge chart). The addition documents the interactive bar chart Concierge can return in chat and how users can hover or select a bar to drill into expenses on the Search page. The change is well-scoped, stays within the article's single workflow, and is a clean, additive contribution.

Scores Summary

  • Readability: 9/10 - Clear, concise prose with a scannable bullet list and a benefit-focused closing sentence. Minor nit: the intro sentence is slightly long.
  • AI Readiness: 8/10 - Heading is task-based and starts with "How to", uses the full feature phrase, and keywords were updated to match real search intent. Heading hierarchy stays at ##. Retrieval readiness is strong.
  • Style Compliance: 8/10 - Correctly bolds the Search page reference and uses exact UI terminology. Web-only behavior is stated ("On web, you can interact..."), aligning with the Cross-Platform Clarity Rule. Consider stating explicitly whether chart interaction is available on mobile per the "If a Feature Is Not Available on Mobile" rule, rather than implying it via "On web".

Key Findings

  • New ## How to explore a Concierge spend chart heading is task-based and compliant with Section 2 heading rules.
  • The Search reference is correctly bolded as a UI destination.
  • Web-specific behavior is scoped correctly, but mobile behavior is only implied. Governance requires an explicit statement when a feature is not available on mobile ("This feature is not available on mobile") rather than leaving it inferred.
  • Keywords were thoughtfully expanded to match likely user queries (bar chart, spend chart).
  • No ### headings, no generic headings, single workflow preserved — clean structure.

Recommendations

  • Add an explicit mobile statement if chart interaction is web-only (e.g., "This feature is not available on mobile.") to fully satisfy the platform-clarity rules, instead of relying on "On web".
  • Optional: standardize the em dash / curly-quote example for consistency with the rest of the doc.

Files Reviewed

  • docs/articles/new-expensify/concierge-ai/How-Concierge-Analyzes-Spend.md — Approved with minor suggestions. New section is well-written, task-based, and correctly scoped; only the implicit mobile-availability wording needs tightening.

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

@stephanieelliott
stephanieelliott requested a review from a team August 6, 2026 05:12
@melvin-bot

melvin-bot Bot commented Aug 6, 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 @johncschuster

@melvin-bot
melvin-bot Bot requested review from johncschuster and removed request for a team August 6, 2026 05:12
@melvin-bot

melvin-bot Bot commented Aug 6, 2026

Copy link
Copy Markdown

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

@inimaga inimaga closed this Aug 7, 2026
@inimaga inimaga reopened this Aug 7, 2026
@inimaga
inimaga merged commit 61544d3 into main Aug 7, 2026
26 checks passed
@inimaga
inimaga deleted the docs-victory-chart-clickable-96065 branch August 7, 2026 09:42
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/inimaga in version: 9.4.52-0 🚀

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

@quinthar quinthar added the #ai label Aug 11, 2026
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/roryabraham in version: 9.4.52-11 🚀

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

Bundle Size Analysis (Sentry):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

HelpDot Apply this label if the issue relates to ExpensifyHelp

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants