Skip to content

[No QA] Create Concierge AI hub and docs [2]#74111

Merged
strepanier03 merged 20 commits intomainfrom
conciergeai-docs-create
Nov 3, 2025
Merged

[No QA] Create Concierge AI hub and docs [2]#74111
strepanier03 merged 20 commits intomainfrom
conciergeai-docs-create

Conversation

@stephanieelliott
Copy link
Contributor

Replaces #73906

@stephanieelliott stephanieelliott self-assigned this Nov 3, 2025
@stephanieelliott stephanieelliott requested a review from a team as a code owner November 3, 2025 18:24
@melvin-bot
Copy link

melvin-bot bot commented Nov 3, 2025

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

@melvin-bot melvin-bot bot requested review from inimaga and strepanier03 and removed request for a team November 3, 2025 18:24
@melvin-bot
Copy link

melvin-bot bot commented Nov 3, 2025

@inimaga @strepanier03 One of you needs to 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]

@github-actions github-actions bot changed the title Create Concierge AI hub and docs [2[ [No QA] Create Concierge AI hub and docs [2[ Nov 3, 2025
@OSBotify
Copy link
Contributor

OSBotify commented Nov 3, 2025

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

Updated articles:

@github-actions
Copy link
Contributor

github-actions bot commented Nov 3, 2025

HelpDot Documentation Review

Overall Assessment

This PR introduces comprehensive documentation for the new Concierge AI feature across 4 well-structured articles totaling 425+ lines of content. The documentation is exceptionally well-written, user-friendly, and provides a thoughtful introduction to a complex AI-powered feature. The structure follows a logical learning progression from basics to advanced concepts, making it accessible to users at all levels.

Scores Summary

  • Readability: 9/10

    • Clear, conversational tone that feels natural and approachable
    • Excellent use of examples and analogies ("Think of Concierge as your product expert...")
    • Strong logical flow with well-organized sections
    • Minor: A few sentences could be slightly shorter for even better scannability
  • AI Readiness: 8.5/10

    • Descriptive headings clearly identify topics ("What is Concierge AI in New Expensify?")
    • Good YAML metadata with relevant keywords
    • Clear context throughout without vague references
    • Minor: Some headings could be more specific (e.g., "How Concierge works" → "How Concierge AI determines user intent")
    • Missing breadcrumb path in most files (only Support-Agent.md includes one)
  • Style Compliance: 9/10

    • Excellent conversational tone matching Expensify voice
    • Proper use of Workspace terminology
    • Good balance of bullet points, examples, and prose
    • Strong FAQ sections address common user questions
    • Minor: Inconsistent markdown formatting between files (e.g., Support-Agent.md uses <div id="concierge-ai"> while others use <div id="new-expensify">)

Key Findings

Strengths:

  • Exceptional user empathy: The docs anticipate user questions brilliantly ("Can I talk to a real person?" appears prominently)
  • Progressive disclosure: Content flows from simple (Basics) to complex (Intelligence) perfectly
  • Practical examples: Every feature includes concrete, actionable examples users can try immediately
  • Technical transparency: The Intelligence article explains AI concepts without overwhelming users
  • Privacy focus: Security and data handling addressed proactively in multiple places
  • Comprehensive FAQ sections: Each article includes 4-8 relevant FAQs

Areas for improvement:

  • Breadcrumb inconsistency: Only Support-Agent.md has a breadcrumb path ("Account > Help and Feedback > Concierge")
  • Div ID inconsistency: Support-Agent.md uses <div id="concierge-ai"> while others use <div id="new-expensify">
  • Heading hierarchy opportunities: Some sections could benefit from more descriptive H1 headings
  • Navigation clarity: The index.html file is empty - needs content or clarification on purpose

Recommendations

Critical (Must Address):

  1. Standardize breadcrumb paths: Add breadcrumbs to all 4 articles following the pattern in Support-Agent.md, or remove from all if not needed
  2. Standardize div IDs: Choose either "concierge-ai" or "new-expensify" and apply consistently across all files
  3. Populate or explain index.html: The empty index file should either have content or a comment explaining its purpose

High Priority (Strongly Recommended):
4. Enhance heading specificity: Consider more descriptive H1 headings in Concierge-Intelligence.md ("How Concierge works" → "How Concierge AI interprets user requests")
5. Add visual hierarchy markers: Consider adding Pro tips or Important callouts for critical information
6. Cross-reference articles: Add "See also" sections linking related articles (e.g., from Basics to Expense-Assistant)

Medium Priority (Nice to Have):
7. Add timestamp examples: When showing expense creation examples, include date formats users might say
8. Expand limitations section: In Expense-Assistant.md, the "not yet supported" list is valuable - consider similar sections in other docs
9. Consider a quick-start guide: A "5-minute getting started" section in Concierge-Basics.md could help new users

Files Reviewed

  1. Concierge-Basics.md (94 lines) ✅ Excellent introduction, clear structure, strong FAQ
  2. Concierge-Intelligence.md (133 lines) ✅ Impressive technical depth, well-balanced complexity
  3. Expense-Assistant.md (124 lines) ✅ Practical and actionable, great use of examples
  4. Support-Agent.md (73 lines) ✅ Concise and clear, good troubleshooting focus
  5. _routes.yml (5 lines) ✅ Proper integration with navigation structure
  6. index.html (1 line) ⚠️ Empty file - needs content or explanation

Overall Score: 8.8/10

This is high-quality documentation that successfully introduces a complex AI feature in an accessible, user-friendly way. The content demonstrates strong understanding of both the technical capabilities and user needs. With minor consistency fixes and the critical items addressed, this would easily be a 9.5/10.

Recommendation: Approve with minor revisions focused on consistency (breadcrumbs, div IDs) and the empty index file.


Review completed by HelpDot Documentation Quality Specialist

fix hub linkage
@stephanieelliott stephanieelliott changed the title [No QA] Create Concierge AI hub and docs [2[ [No QA] Create Concierge AI hub and docs [2] Nov 3, 2025
Copy link
Contributor

@strepanier03 strepanier03 left a comment

Choose a reason for hiding this comment

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

I reviewed the content for accuracy, readbility, and formatting via the the build. I also navigated through the new pages and confirmed things are functioning as normal.

My only comment is to do with the page the hub is visible on, the visual design of the how the hub appears on the page is different than the other hubs so it stands out. Maybe this is intentional but I wanted to mention it in case.

Image

@strepanier03 strepanier03 merged commit 94b0bf7 into main Nov 3, 2025
12 of 14 checks passed
@strepanier03 strepanier03 deleted the conciergeai-docs-create branch November 3, 2025 22:00
@melvin-bot
Copy link

melvin-bot bot commented Nov 3, 2025

@strepanier03 looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

@strepanier03
Copy link
Contributor

I passed this with the failed PR reviewer checklist and PR author checklists on purpose to get this out with the newsletter.

@OSBotify
Copy link
Contributor

OSBotify commented Nov 3, 2025

🚀 Deployed to staging by https://github.com/strepanier03 in version: 9.2.43-0 🚀

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

@OSBotify
Copy link
Contributor

OSBotify commented Nov 4, 2025

🚀 Deployed to production by https://github.com/luacmartins in version: 9.2.43-2 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 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