Docs: Inbox timeline reputation activity updates (401814)

[cursor]

Jira

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

Change classification

• Feature behavior change (user-facing timeline behavior in Conversations inbox)

Summary of documentation updates

• Updated existing page: docusaurus/docs/business-app/conversations/index.mdx
• Added a concise Inbox timeline activity subsection under standard Conversations behavior.
• Documented that the inbox timeline includes system-generated updates and can include Reputation activity such as NPS feedback and review matched events.

Existing docs updated vs new docs

• Updated existing documentation
• No new page created

Placement reasoning

• This behavior belongs with existing Business App Conversations inbox behavior, so it fits cleanly in the existing Conversations overview page.
• Keeping this update in the current page avoids duplicated content and unnecessary navigation changes.

Acceptance criteria coverage

• AC: NPS Feedback and Review Matched activities appear in Inbox timeline with correct event formatting/titles.
  • Covered by the new timeline subsection describing visibility of NPS feedback and review matched events in Conversations timeline.
• ACs about internal activity type/source identifiers and internal channel validation were treated as implementation details and not documented as user instructions.
• AC about no regression to existing messaging/review request workflows is reflected by explicit note that regular messaging workflows remain unchanged.

Visuals (Figma/images)

• No Jira attachments or Figma links were provided in the webhook payload.
• Documentation updates were based on Jira text and acceptance criteria.

Skills used

• sprint-review (read and applied relevant release-status + evergreen guidance)
• Repository discovery/search tools (rg, Glob, ReadFile) to locate best existing page

Validation

• Ran npm run build in docusaurus/ successfully after installing dependencies.
• Build reports pre-existing repo-wide broken links/anchors unrelated to this change.

Assumptions / limitations

• Webhook payload did not include accessible linked implementation PR metadata for REP-2540 in this repo context.
• I attempted GitHub search for linked PRs/authors; only docs-related bot PRs were discoverable from this environment.
• Because linked code PR authors could not be resolved reliably from accessible data, no additional non-doc code-author tags were added to avoid incorrect tagging.

Mentions

@ahnikakuse
@haleyserrano
@maryam6samadi