Docs: Clarify edited-review draft behavior (396288)

[cursor]

JIRA

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

Change classification

• Feature behavior change

Summary of documentation updates

• Updated existing documentation in:
  • docusaurus/docs/multi-location-business-app/reputation/review-response-suggestions.mdx
• Added a focused section:
  • How suggested responses behave when reviews are edited
• Documented current behavior:
  • When a customer edits an existing review, the suggested draft response is refreshed using the latest review text and star rating.
  • If a reply has already been posted for the original review, a draft response is not shown in the review card.

Existing docs updated or new docs created

• Updated existing docs only (no new docs created)

Placement reasoning

• This behavior belongs with existing Reputation AI review response guidance in Multi-Location Business App docs.
• The target page already explains suggested responses and review reply flow, so adding this behavior there keeps content discoverable and avoids duplication.
• No nav/sidebar change was required because the update is within an existing page.

Acceptance criteria coverage

• AC: The system should detect when a review is edited.
  • Covered by documenting edited-review behavior in the new section.
• AC: The existing draft response must be updated for the specific review ID.
  • Covered by documenting that the suggested draft response is refreshed for that same review.
• AC: Changes in star ratings or content should trigger the update process.
  • Covered by documenting that updates are based on latest review text and star rating.
• Implementation note in JIRA: If a review comment has already been posted for the original review, draft should not display in review card.
  • Covered explicitly.

Figma / images used

• No Figma links or screenshot attachments were provided in the webhook payload.
• Update was based on JIRA acceptance criteria and implementation note.

Skills used

• sprint-review skill (used for repo writing/compliance workflow guidance)

Assumptions or limitations

• No linked implementation PRs for REP-2489 were discoverable via GitHub search in this repository/org context, so no additional code-author mentions were added beyond known contributors.

Mentions

@ahnikakuse
@haleyserrano
@maryam6samadi

Related code contributors

@haleyserrano