Dynamic priority for tasks pushed to Breezeway

Priority: High

Problem / context

Tasks currently arrive in Breezeway at the lowest priority regardless of situation. That is a visibility problem: a guest reporting an issue while still in the home lands at the same priority as a mildly negative post-departure review, so genuinely urgent items are easy to miss in the queue. Priority should reflect how time-sensitive the task actually is.

Requested capability

Set task priority dynamically based on the guest's stay status and the sentiment of what triggered the task, instead of a single static lowest-priority default.

Detail / spec

Proposed mapping:

• In-home guest (issue raised while the guest is still on site) → high priority
• Post-departure negative → medium/high priority
• Post-departure positive → low priority

• Priority is set at task creation from the trigger context (in-home status plus sentiment or score).
• Ideally the thresholds are configurable rather than hard-coded, so operators can tune what maps to which priority.

Acceptance criteria

• An in-home guest issue creates a high-priority Breezeway task.
• A post-departure negative creates a medium/high task; a post-departure positive creates a low task.
• Priority is written at creation and reflects the trigger, not a static default.