# Planned changes and feedback

**In short:** before a sale or a deploy, add it under **Known events** on the watch's page (or ask your agent), and alerts hold while it runs. On an alert's page, answer **Was this a real problem?**: **Real problem**, **False alarm** or **Expected change**. CountWatch learns from each answer.

- **Known events.** Before a deployment, campaign or maintenance, `POST /v1/events` with `kind` (and `expect` when the default does not fit): a level change holds both directions for up to 6 hours and then accepts the new level once steady; an expected spike or drop holds that direction until `until`; a no_data holds drops and no-data alerts. Held periods are left out of the usual level. `watch_id: "*"` covers every watch.
- **Feedback.** `POST /v1/alerts/{alert_id}/feedback` with `real`, `false_alarm` or `expected_change`. Real and false alarms teach the weekly rule choice; an expected change on an open alert makes its new level the new normal at the next check and closes the alert.