Docs: add Contact Us help article (DALE-1473)

[haleyserrano]

JIRA

DALE-1473: [FDE] Custom Support Portal link from Business App (Done)

Source RFC: RFC: Support Center Link in the Contact Us Modal

Classification

• Type: UI/UX change (Business App end-user experience)
• Repo: Business App (this PR). A companion PR also updates Partner Center docs, since the feature is configured there.

Summary of changes

Added a new article, docusaurus/docs/business-app/contact-us.md, documenting the Contact Us card/modal in Business App navigation:

• Optional message from the service provider, shown at the top of the modal
• Assigned contact card (name/email), when shown
• "Send message" chat button, when enabled
• New: a support center link button that opens the provider's support resource in a new tab

Existing docs vs. new page

• Searched docusaurus/docs/business-app/ for any existing coverage of the Contact Us nav card/modal (getting-started-with-business-app.md, home.mdx, business-app/index.mdx, conversations/index.mdx, administration/) — none exists.
• New page justified: the Contact Us card/modal was previously undocumented for end users, and this is a distinct, standalone workflow (not a natural subsection of Conversations or Administration, which cover the SMB's own settings rather than a fixed getting-help surface).
• Placed as a root-level article alongside home.mdx / getting-started-with-business-app.md (small standalone topics that don't warrant their own folder+category), sidebar_position: 9 (after Administration).

Acceptance criteria coverage

Per the RFC, the story's original AC ("partner can specify a link"; "clicking the nav card opens a modal that takes users to the specified support area") was superseded by three independent, partner-configurable options (assigned-contact visibility, chat, support link) plus a standalone modal description. This article documents all end-user-visible behavior:

• Support link click opens the partner-specified URL, in a new tab ✅
• Modal shows/hides based on partner configuration (including hiding the nav card entirely when nothing is configured) ✅

Figma/visual inputs

None provided or accessible for this ticket. Content is based entirely on the written RFC (UI mockup link included in the RFC was not fetched, since this is a text/behavior-only article with no screenshots). Documented as a limitation below.

Skills used

• generate-help-article (article structure)
• pre-push-validation (frontmatter, tag-balance, and link checks — passed)

Assumptions / limitations

• No screenshots included. No accessible image assets for the new support-link UI; per repo rules, placeholders/fabricated images were not added. Screenshots can be added in a follow-up once available.
• No parent epic found for DALE-1473 (confirmed via Jira parent field and Teamwork Graph relationships) — proceeded directly since the story itself is Done and its linked PRs (14) are all merged.
• Reviewer not auto-assigned. GitHub access for this session is scoped to the docs repos only, so the code PRs linked to DALE-1473 (in the Business App codebase) could not be queried to identify their author for reviewer assignment. The story's assignee/RFC author is Kyle Sheasby (ksheasby@vendasta.com) — please add manually if appropriate.

---

@ahnikakuse @haleyserrano @maryam6samadi

---

Generated by Claude Code