[No QA] Fix outdated booking flows on travel docs

[stephanieelliott]

Updating old travel booking flow

[OSBotify]

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

Updated articles:

• articles/travel/booking-travel/Arrange-Travel-for-Another-User
• articles/travel/booking-travel/Book-a-Hotel
• articles/travel/booking-travel/Book-a-Rental-Car
• articles/travel/booking-travel/Book-Rail-Travel
• articles/travel/booking-travel/Book-Travel-for-a-Guest

[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 @sonialiap

[melvin-bot]

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

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR updates 5 travel booking documentation files to standardize the access instructions and modernize the workflow descriptions. The changes successfully remove outdated references to Classic Expensify and streamline the user experience by focusing on the current New Expensify interface. The updates are generally well-executed with improved clarity and consistency across all files.

Scores Summary

• Readability: 8/10 - Clear, concise language with good logical flow. Minor inconsistencies in formatting and structure between files.
• AI Readiness: 7/10 - Good use of descriptive headings and clear context, but some heading hierarchy issues and inconsistent section structuring.
• Style Compliance: 8/10 - Strong adherence to terminology standards (workspace, member) and proper button labels, with minor formatting inconsistencies.

Key Findings

Strengths:

• Consistent standardization of the "Where to find Expensify Travel" section across all files
• Removal of outdated Classic Expensify references (dual-interface documentation)
• Clear, actionable instructions with proper use of Expensify terminology ("workspace", "member")
• Good use of emoji symbols (➕) for visual clarity
• Improved "What happens after booking" section headers that are more descriptive
• Added helpful FAQ entries (e.g., guest booking approval workflow)

Critical Issues:

1. Heading Hierarchy Inconsistency: Mix of H1 (#) and H2 (##) for primary sections. HelpDot standards require consistent use of # for main sections and ## for subsections only.

   • Examples: "# How to book a hotel" (H1) vs "## Where to find Expensify Travel" (H2) in the same document

2. Incomplete File Updates: Two files (Arrange-Travel-for-Another-User.md, Book-Travel-for-a-Guest.md) still contain OLD instructions in the actual file content:

   • Still reference "In New Expensify" vs "In Classic Expensify" dual format
   • Still mention "Account Manager or Concierge to schedule a travel demo"
   • The diff shows changes, but the actual files on main branch weren't fully updated

3. FAQ Heading Structure: Book-Travel-for-a-Guest.md changes FAQ questions from H2 (##) to unmarked text, which reduces discoverability

Recommendations

Priority 1 - Must Fix:

1. Apply the standardized changes to Arrange-Travel-for-Another-User.md and Book-Travel-for-a-Guest.md that match the other three files (they still show old content in the actual files)
2. Standardize heading hierarchy across all files - use # for main sections, ## for subsections consistently
3. Ensure FAQ questions remain as ## headings for better structure and AI parsing

Priority 2 - Should Fix:

1. Add consistent breadcrumb/navigation context in YAML frontmatter if not already present
2. Standardize "What happens after booking with Expensify Travel" heading across all files (currently varies)
3. Consider adding a "Before you start" or "Prerequisites" section mentioning that Expensify Travel must be enabled

Priority 3 - Nice to Have:

1. Add more specific step numbers or screenshots references for complex workflows
2. Consider adding a cross-reference link between related travel booking documents
3. Ensure all FAQs follow a consistent question format (active voice, user-focused)

Files Reviewed

• ✅ Book-a-Hotel.md: Well-structured, good updates
• ✅ Book-a-Rental-Car.md: Clean updates, consistent formatting
• ✅ Book-Rail-Travel.md: Strong improvements, clear instructions
• ⚠️ Arrange-Travel-for-Another-User.md: Updates not fully applied - still shows old content
• ⚠️ Book-Travel-for-a-Guest.md: Updates not fully applied - still shows old content

Summary

This is a valuable documentation update that modernizes the travel booking workflow. The three fully-updated files show excellent improvements in clarity and consistency. However, two files need their updates fully applied, and heading hierarchy should be standardized across all files for optimal AI readability and user experience.

---

Reviewed using HelpDot Documentation Quality Standards

[stephanieelliott]

Reapplying request for @sonialiap's review now that this is off hold

[sonialiap]

Funky spacing in https://f063ad90.helpdot.pages.dev/articles/travel/booking-travel/Book-a-Hotel
But there isn't a space in the code. I'm guessing it has to do with the indented bullet point. @stephanieelliott do you think this matters?

[sonialiap]

@stephanieelliott is this correct?

According to Brandon's post here it seems like it could be up to $25 depending on what actions is taken by the agent

https://f063ad90.helpdot.pages.dev/articles/travel/booking-travel/Book-a-Hotel

[stephanieelliott]

Thanks @sonialiap! Updated to fix the formatting issue, and changed the fee description to Changes made through support may incur a fee of up to $25.

[sonialiap]

Looking good!

[melvin-bot]

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

[sonialiap]

I think the test that didn't pass was the reviewer checklist. I checked it all off after I approved the changes. Was I too fast/not in the right order? The code and the content look fine

[stephanieelliott]

No you're good @sonialiap - that label sounds scarier than it is (we can't turn it off though), the PR CL is not required so it was fine to skip.

[OSBotify]

🚀 Deployed to staging by https://github.com/sonialiap in version: 9.3.5-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/Beamanator in version: 9.3.5-7 🚀

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