Diagnostics → Messages — see every text we sent and whether it actually delivered

Feature

Week of May 25, 2026

When an advocate or prospect says “I never got your text,” you can finally answer “yes you did” (or “no, here’s why”) without asking us. Every text the platform sends or receives now writes a row to a new diagnostics log, with the carrier-confirmed delivery status and the trigger that sent it.

Settings → Diagnostics → Messages — paginated list of every message, filterable by channel, direction (outbound/inbound), status, trigger type, recipient (name or phone), and date range
Per-message detail page — full status timeline (queued → sent → delivered, or → failed with the carrier’s reason) and a deep link back to the conversation or introduction the message belonged to
Per-conversation and per-introduction delivery log — a collapsible “Delivery log” section on the detail page shows every send attempt against that record
Per-person Messages tab — see every text we’ve sent or received from a specific advocate or prospect, with a one-click jump into the filtered Diagnostics view
Delivery-failed indicators on inbox cards — when a notification actually fails (bad number, opted out, carrier rejection), the inbox card flips to a red Delivery failed pill and the conversation/introduction detail page shows a yellow alert with the carrier’s reason
Real delivery status from Twilio — we now subscribe to Twilio’s delivery callbacks, so the log reflects what the carrier actually did, not just what we accepted. A message that ends up “undelivered” hours later updates automatically.

No action required from community admins or advocates — the log starts collecting on rollout. WhatsApp messages will flow into the same log when that integration ships.