The challenge
Email intake, phone contact, scheduling, and case management have different data shapes and execution timelines. Joining them requires more than a synchronous chain of API calls: the workflow must preserve routing context and retain scheduled work beyond the lifetime of the inbound request.
The engineering approach
- Receive email events through Resend and use a signed webhook as the intake boundary.
- Route the intake to the appropriate firm and extract phone information for the next stage of processing.
- Use durable scheduled work to coordinate AI calling through ElevenLabs and Twilio rather than relying on an in-process timer.
- Connect the calling workflow to CasePeer so intake information and follow-up can reach the case-management workflow.
The system, at a glance
- 01Inbound email via Resend
- 02Signed webhook verification
- 03Firm routing and phone extraction
- 04Durable scheduled call
- 05ElevenLabs and Twilio
- 06CasePeer handoff
What this work connects
A connected intake workflow that carries firm-specific context from inbound email through scheduled AI calling to CasePeer, bringing intake processing and case-management follow-up into the same integration path.
Selected contributions, not a claim of sole authorship. Client-specific configurations and operational data are intentionally excluded.