Docs: document Inbox reputation event behavior (REP-2538)

[cursor]

Tags

@ahnikakuse
@haleyserrano
@maryam6samadi

JIRA

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

Change classification

• Feature behavior change (user-facing behavior in Conversations Inbox for Reputation-related events)

Summary of documentation updates

• Updated existing page: docusaurus/docs/business-app/conversations/index.mdx
• Added a new subsection under Standard Features (Included):
  • Reputation events
  • Clarifies that NPS feedback and Review matched activities appear in Inbox as conversation events
  • Clarifies that NPS feedback updates apply to the existing Inbox event so the latest feedback is shown without duplicate events

Existing docs updated or new docs created

• Updated existing docs only
• No new page created

Placement reasoning

• The change affects how users experience events inside Conversations Inbox
• business-app/conversations/index.mdx is the canonical overview page for Conversations behavior and features
• Adding a brief subsection here keeps the behavior beside related channel/features content and avoids duplicative pages

Acceptance criteria coverage

Mapped from REP-2538 acceptance criteria:

• Add new event types for NPS feedback and Review matched
  • Documented as visible Inbox conversation events under Reputation events
• GetEventCardTitle returns correct label keys
  • Reflected indirectly via user-facing event naming in docs (NPS feedback / Review matched)
• GetMultiActivity call ordering + skip-check processing fix
  • Internal implementation detail, not documented directly
• Use CRMObjectID idempotency key for reputation_nps_feedback create/update
  • Reflected user-facing result: existing Inbox event updates rather than duplicate events
• NPS updates processed using existing event type
  • Reflected in docs as update behavior for existing event

Visual inputs (Figma/images)

• No Figma links or screenshots were provided in the payload for this story
• Update is based on the JIRA acceptance criteria and shipped behavior summary

Skills used

• sprint-review skill (workflow and repo-compliance guidance)
• Repository discovery/search tools to locate best-fit existing docs and avoid new-page creation

Linked code PRs and author tagging

• I checked for linked PRs by issue key/title across available GitHub search views but could not reliably identify the associated code PR(s) from this environment.
• To avoid incorrect tagging, no additional code-author tags are included here.

Assumptions and limitations

• Assumed terminology shown in JIRA acceptance criteria (NPS feedback, Review matched) is the intended user-facing wording.
• Could not run full local typecheck because tsc is unavailable in this environment (npm run typecheck failed with tsc: not found).