Account – Settings – Comment Responder – Sentiment

Route

• Path: /account/settings/comment-responder/sentiment (TBD)
• Parent: settings-comment-responder.md

Purpose (business goal)

Configure sentiment analysis thresholds and how they influence automation, prioritization, and escalation.

User roles & permissions

• Workspace Admin, Manager
• Permissions: comment_responder.manage (TBD)

Reference: Roles & Permissions Model

Layout structure

• Threshold configuration
• Routing outcomes per sentiment band (TBD)

Components used

TBD

States

• Empty: TBD
• Loading: fetch thresholds
• Error: save failure
• Complete: updated

Business logic (high-level)

Sentiment scoring affects queues and escalation; it must be explainable and auditable where required.

Domain refs:

• Domain: Comment Responder

API dependencies

• GET /apps/comment-responder/settings/sentiment
• PUT /apps/comment-responder/settings/sentiment

Enterprise constraints

• Sentiment-driven routing impacts operational workload; require explainability/auditability where needed (TBD).
• Thresholds must be workspace-scoped and consistently applied across channels.

Edge cases

• Sentiment model drifts or changes; thresholds may need recalibration (TBD).
• Conflicting routing outcomes for borderline scores; tie-break rules are TBD.

Security & compliance considerations

• Changes can alter automation/escalation outcomes; audit configuration updates.

Reference: Security & Compliance

Analytics events (if applicable)

• comment_responder.sentiment.updated

Reference: Analytics Events (MVP)