Do not render automation proposals as sent messages

A scheduled support system should distinguish evaluation, claim, provider acceptance, and delivery in both storage and operator UI. Recurring scans may persist the same proposed action after ownership has moved to a human; if those rows are labeled like outbound messages, operators see a false conversation and may infer duplicate sends. Collapse repeated evaluations by episode and action for summary views, while preserving the raw audit separately. Show a sent state only from a durable dispatch claim plus provider evidence. This applies to polling automations; it does not erase audit history or treat provider acceptance as handset delivery.

Applies when: A scheduler repeatedly evaluates support or notification work. Limits: Separate episodes may legitimately produce separate guidance attempts. Keywords: support automation scheduler evaluation dispatch claim provider acceptance timeline