Docs: document Inbox timeline reputation activities (401814)

[cursor]

Jira

• https://vendasta.jira.com/browse/REP-2540

Change classification

• Feature behavior change

Summary of documentation updates

• Updated existing page: docusaurus/docs/business-app/conversations/index.mdx
• Added a concise subsection under Standard Features (Included):
  • Reputation activities in the inbox timeline
  • Documents that NPS feedback and review matched events appear in the inbox timeline as conversation activities
  • Clarifies that these entries are shown as system activities with event-specific titles and message content

Existing docs updated vs new docs created

• Updated existing docs only
• No new pages created

Placement reasoning

• The story changes what SMB users see in the Business App Conversations inbox timeline.
• business-app/conversations/index.mdx is the existing overview page for this workflow and is the best fit for a concise behavior update.
• This placement keeps timeline behavior guidance with related inbox concepts and avoids unnecessary page creation.

Acceptance criteria coverage

1. NPS Feedback and Review Matched activities are created as communication activities and shown in Inbox
   • Covered by explicitly documenting both event types in the inbox timeline behavior.
2. Events render with correct context in Inbox timeline
   • Covered by documenting system activity entries with event-specific titles and message content.
3. Existing review request and messaging flows remain unaffected
   • Update is additive and scoped to timeline activity behavior only.

Visual inputs (Figma/images)

• No Figma links or image attachments were provided in the Jira payload.
• Documentation update is based on the Jira description and acceptance criteria.

Skills used

• /workspace/.cursor/skills/sprint-review/SKILL.md (applied for evergreen wording and conservative existing-doc update workflow)
• Repository discovery/search tools (rg, Glob, targeted file reads)

Navigation impact

• No sidebar or category changes required (existing page update only).

Assumptions and limitations

• Jira payload referenced linked PRs by count but did not provide resolvable author handles.
• Available GitHub search in this environment did not yield attributable related code PR authors for REP-2540, so no additional code-author tags were added to avoid mis-tagging.

Requested mentions

@ahnikakuse
@haleyserrano
@maryam6samadi