Dropped email recipients need proactive visibility (notifications, attribute or conversation reopening)Submitted
The issueThe new dropped recipients behavior is a sensible safeguard, and I appreciate that the drop reason is now shown in the conversation. The problem is that this is the only signal. A dropped recipient is surfaced passively — a red icon, red text, and a hover tooltip inside the conversation stream — and nothing else happens:No notification or alert to the sender, the assignee, or the team. No attribute set on the contact or the conversation to flag that a drop occurred. The conversation is not reopened, or moved to any view. No event/webhook we can hook automation onto.So unless someone happens to reopen that exact conversation and read the recipient line, the failure is invisible.Why this matters for usThese are not marketing emails. We use Intercom for account and support communication — replies to tickets, account notices, security- and billing-related messages. When one of these silently drops, the customer simply never hears back from us.In practice we only find out one of tw
