Skip to content

[No QA] AZ training: improve card feed guidance for AgentZero#71830

Merged
stephanieelliott merged 2 commits into
mainfrom
stephanieelliott-patch-17
Oct 9, 2025
Merged

[No QA] AZ training: improve card feed guidance for AgentZero#71830
stephanieelliott merged 2 commits into
mainfrom
stephanieelliott-patch-17

Conversation

@stephanieelliott

Copy link
Copy Markdown
Contributor

Explanation of Change

Updated the Direct Feeds and Commercial Card Feeds help docs to clearly explain the differences between commercial and direct card imports. Clarifying the purpose and eligibility of each feed type, adding notes in the Commercial Card Feeds article to redirect users to the Direct Feeds article when applicable (and vice versa), updated for AI-friendly structure and terminology

https://expensify.slack.com/archives/C090U774ZH7/p1758770016926869

@stephanieelliott stephanieelliott self-assigned this Oct 3, 2025
@stephanieelliott stephanieelliott requested a review from a team as a code owner October 3, 2025 19:36
@melvin-bot

melvin-bot Bot commented Oct 3, 2025

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 October 3, 2025 19:37
@melvin-bot

melvin-bot Bot commented Oct 3, 2025

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]

**Tip:** Contact your bank directly to check if your cards are eligible for a commercial feed.
Commercial feeds are the most reliable way to import company card expenses. These feeds are not affected by login credential changes or banking UI updates, making them ideal for growing teams and finance admins.

---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Formatting violation: Unnecessary horizontal rule separator. Remove this extra --- line as it creates visual clutter and doesn't follow standard markdown formatting patterns for help documentation.

- **Control plan** members can add an unlimited number of company card feeds.
- Workspace creation is required before connecting cards.

---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Formatting violation: Unnecessary horizontal rule separator. Remove this extra --- line as it creates visual clutter between related sections.

@github-actions

github-actions Bot commented Oct 3, 2025

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR significantly improves the card feed documentation by clarifying the critical differences between commercial and direct feeds, restructuring content for better AI readability, and enhancing user guidance. The changes address a key user pain point around understanding which feed type to choose.

Scores Summary

  • Readability: 8/10 - Clear, concise language with improved structure and logical flow
  • AI Readiness: 9/10 - Excellent use of descriptive headings, proper terminology, and structured content
  • Style Compliance: 7/10 - Generally strong, with minor formatting inconsistencies

Key Findings

Strengths:

  • Clear differentiation: The updated Commercial-feeds.md now clearly explains that commercial feeds are "file-based connections provided directly by your bank" vs direct feeds requiring login credentials
  • Improved structure: Better heading hierarchy and logical flow throughout both documents
  • Enhanced cross-references: Effective bidirectional linking between commercial and direct feed articles
  • Simplified language: Removed jargon and improved clarity (e.g., "expenses will begin importing immediately" vs "transactions will begin importing immediately")
  • Consistent UI terminology: Proper use of "member" instead of "employee" and standardized button labels

Areas for Improvement:

  • Numbering error: Line 70-72 in Commercial-feeds.md has incorrect step numbering (5. 3. In Expensify... 4. Choose... 7. You'll be notified...)
  • Missing step: American Express setup section appears to skip step 6 (entering the delivery file name)
  • Minor inconsistency: Mix of "Company Cards" vs "company cards" capitalization throughout

Recommendations

Priority Actions:

  1. Fix step numbering in the American Express Corporate Card Feed section (lines 70-72)
  2. Add missing step 6 for entering the delivery file name in Amex setup
  3. Standardize capitalization of "Company Cards" throughout both documents

Enhancement Suggestions:

  • Consider adding a comparison table in the FAQ section showing commercial vs direct feeds side-by-side
  • The cross-reference additions effectively guide users between the two feed types

Files Reviewed

  • Commercial-feeds.md: Major restructuring with significant quality improvements - content is much clearer and more actionable
  • Direct-feeds.md: Minor but effective keyword additions that improve discoverability

Note: The structural improvements and clear differentiation between feed types will significantly improve user experience and reduce support inquiries about feed selection.


Expensify will notify you when the feed is live.

---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Formatting violation: Unnecessary horizontal rule separator. Remove this extra --- line as it creates visual clutter between related sections.


---


Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Formatting violation: Remove the extra blank line. Only one blank line is needed between sections to maintain clean formatting.


Expensify will notify you when the feed is connected.

---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Formatting violation: Unnecessary horizontal rule separator. Remove this extra --- line as it creates visual clutter between related sections.

4. Wait for the **Production Letter** containing your feed’s file name.
5. In Expensify, go to **Workspaces > [Workspace Name] > Company Cards > Add Cards > American Express > American Express Corporate Cards**
6. Enter your delivery file name to submit.
5. 3. In Expensify, go to **Workspaces > [Workspace Name] > Company Cards > Add Cards**.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Numbering error: This line shows "5. 3." which is incorrect numbering. Should be "5." to continue the sequence properly.

5. In Expensify, go to **Workspaces > [Workspace Name] > Company Cards > Add Cards > American Express > American Express Corporate Cards**
6. Enter your delivery file name to submit.
5. 3. In Expensify, go to **Workspaces > [Workspace Name] > Company Cards > Add Cards**.
4. Choose **Commercial Feed**, then select **American Express Corporate Cards**.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Numbering error: This line shows "4." but should be "6." to continue the sequence properly after the previous step.

6. Enter your delivery file name to submit.
5. 3. In Expensify, go to **Workspaces > [Workspace Name] > Company Cards > Add Cards**.
4. Choose **Commercial Feed**, then select **American Express Corporate Cards**.
7. You’ll be notified once the feed is live.

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Numbering error: This line shows "7." but should be "7." - wait, this is actually correct, but the previous steps need to be renumbered. This should be the final step in the sequence.

4. Choose **Commercial Feed**, then select **American Express Corporate Cards**.
7. You’ll be notified once the feed is live.

---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Formatting violation: Unnecessary horizontal rule separator. Remove this extra --- line as it creates visual clutter between related sections.

@@ -96,33 +96,37 @@ Once a commercial feed is connected:

---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Formatting violation: Unnecessary horizontal rule separator. Remove this extra --- line as it creates visual clutter between related sections.


![Manage the card on the card details page]({{site.url}}/assets/images/commfeed/commfeed-07-updated.png){:width="100%"}

---

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Formatting violation: Unnecessary horizontal rule separator. Remove this extra --- line as it creates visual clutter between related sections.

@github-actions github-actions Bot changed the title AZ training: improve card feed guidance for AgentZero [No QA] AZ training: improve card feed guidance for AgentZero Oct 3, 2025
@OSBotify

OSBotify commented Oct 3, 2025

Copy link
Copy Markdown
Contributor

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

Updated articles:

@stephanieelliott stephanieelliott merged commit eb5c004 into main Oct 9, 2025
10 of 11 checks passed
@stephanieelliott stephanieelliott deleted the stephanieelliott-patch-17 branch October 9, 2025 21:32
@melvin-bot melvin-bot Bot added the Emergency label Oct 9, 2025
@melvin-bot

melvin-bot Bot commented Oct 9, 2025

Copy link
Copy Markdown

@stephanieelliott 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.

@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/mountiny in version: 9.2.29-5 🚀

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