Email conversations now show who each message is from and who it went to, and the composer shows the address your reply will be sent from. Replies appear in the thread the moment you hit Send, and if one can't be delivered it's marked "Failed to send" with the reason.
How it behaves
- Composing an email reply: above the editor you see "To" (the customer) and "From" (your support address). When Aide sends from its own domain, a note explains that replies still come back to your support address.
- Hitting Send: the reply shows up in the thread right away as "Sending…", then "Sent" once the email provider accepts it. You can keep working while it sends.
- Reaching the customer: once the customer's mail server accepts the reply, it shows as "Delivered".
- Bounced after sending: if the customer's mail server bounces a reply it first accepted (an address that no longer exists, a full mailbox), the reply changes to "Failed to send" with the reason that it couldn't be delivered to this customer.
- Delivery fails: the message is outlined in red with "Failed to send" and the reason, such as the provider refusing the email, no connected mailbox, or the provider being unavailable. Temporary outages are retried automatically before a reply is marked failed.
- Reply never reached Aide (for example, your connection dropped): it's marked "Failed to send" with Retry, which sends the same text again, and Discard, which removes it.
- Reading the thread: each email message shows the sender's and recipient's addresses.
For developers
GET /v1/conversations/:id/messages: each message addsfromandto({ name, address }ornull) anddelivery({ status: 'queued' | 'sent' | 'delivered' | 'failed', failedReason }ornull, set only on outbound email replies). A reply that bounced after sending isfailedwithfailedReason: 'undeliverable'.GET /v1/conversations/:id: addsemailSender({ name, address, replyTo, usesOwnDomain }ornull) for email conversations.- The realtime
message.patchedevent carries the updated delivery status.