How it would work
1
An email arrives
It resolves to a person and to their open thread.
2
The agent replies, or waits
It answers now, or schedules a follow-up.
3
No reply in two days
The flow places a call, with the thread as context.
4
The outcome is written back
The thread, and the person, carry what happened on the call.
The shape
Illustrative - not callable today
What it waits on
Build it today
Nothing email-native ships yet. The closest working version keeps email in your own stack and puts the voice step on Unpod:- Your system sends and receives the email.
- When a thread needs a voice, your system places a call and passes the thread summary as call data.
- Attach an analytics block to the agent, read
the outcome with
client.analytics.for_call(call.call_id), and write it back to the thread.
call_from_thread.py