Per-Inbox Email Attachment Handling
Per-Inbox Email Attachment Handling
Email inboxes now have an Attachment handling setting that controls what happens when an email arrives with an attachment. Previously, every email with an attachment was handed off to a human agent before the AI Agent could engage. Each inbox can now keep that default, have the AI Agent reply while discarding the attachment, or have the AI Agent reply while keeping the attachment so it’s included if the conversation is later handed off.
To learn more, see Attachment handling.
Transfer outcome and sent metadata in Voice conversations
When a Transfer Call block hands a voice call off, the conversation view now records how the transfer resolved and the metadata Ada sent, instead of a single generic transfer line.
Transfer outcomes
When Ada places the transfer and stays on the call, the conversation view shows one of these outcomes, plus how long the end user waited:
- Connected: the destination answered and the caller was joined to it.
- Busy: the destination returned a busy signal.
- No answer: the destination rang but no one answered before it timed out.
- Failed: the transfer could not be completed, for example an unreachable or invalid destination or a carrier error.
- Canceled: the transfer ended before it connected, for example the caller hung up first.
What each integration records
Outcome shown is whether the outcome above (and the wait time) appears. Sent metadata values are the key-value data recorded from what Ada sent at handoff.
An integration shows No for outcome when Ada hands the call off and leaves it, so there is no result to observe.
To learn more, see Contact center integration.