Docs: Inbox timeline reputation activity updates (401814)

[cursor]

Jira

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

Change classification

• Feature behavior change (UI/UX behavior in Inbox timeline)

Summary of documentation updates

• Updated existing page: docusaurus/docs/business-app/conversations/index.mdx
• Added a concise subsection under Standard Features (Included): Reputation activity in Inbox
• Documented that:
  • NPS feedback and review matched updates appear as conversation activities in Inbox
  • These updates stay in the same customer conversation timeline as other interactions
  • Teams can review sentiment and review-attribution context from Inbox
  • Existing messaging and review request workflows continue in the same Inbox experience

Existing docs updated vs new docs created

• Updated existing documentation
• No new page created

Placement reasoning

• The story changes how events appear in the existing Inbox timeline experience.
• business-app/conversations/index.mdx already describes core Conversations behavior, so this is the most accurate and lowest-duplication location.
• No navigation changes were required because placement remained in an existing page.

Acceptance criteria coverage

Acceptance criterion	Doc impact	Coverage
NPS Feedback and Review Matched CRM activities appear in Inbox timeline	Yes	Documented explicitly as Inbox conversation activities
NPS Feedback communication type + source identifier format	No (implementation detail)	Not documented as user guidance
Review Matched communication type + source identifier format	No (implementation detail)	Not documented as user guidance
System channel used so events render in Inbox	Partially (user-facing outcome)	Covered by documented Inbox timeline visibility
Events appear with correct context and existing workflows remain unaffected	Yes	Covered by timeline context note and explicit workflow continuity line

Figma/images usage

• No Figma links or image attachments were available in the webhook payload for this story.
• Update was based on Jira story text and acceptance criteria.

Skills used

• Repository skill read: sprint-review
• Repo discovery tools: rg, Glob, ReadFile

Assumptions / limitations

• I searched accessible vendasta PR metadata for related code-author handles, but only docs/bot PRs were discoverable from this environment.
• I did not add uncertain code-author tags to avoid tagging incorrect users.

Mentions

@ahnikakuse
@haleyserrano
@maryam6samadi