Nitewtch - Path to voice escalation flow Animated flow showing a vendor email moving through Postfix edge capture, durable storage, email worker processing, backend analysis, escalation, and voice acknowledgment. Nitewtch - Path to voice escalation flow Vendor email -> Postfix edge -> durable handoff -> worker -> analyzer -> escalation -> voice acknowledgment Color key Processing / movement Durable or gated state Accepted / success path Escalation / retry path Vendor Email SMTP alert Postfix Edge receive + route Durable Handoff outbox + object + job Email Worker claim + process Backend Processor parse .eml + normalize Analyzer Rules decision + incident Escalation voice call Voice Ack digit closes loop Postfix edge receives the alert email Fast edge work: accept SMTP, identify tenant, and reject obvious bad senders. SMTP :25 monitoring email Route recipient tenant Whitelist sender domain Durable handoff before deeper processing The edge captures raw mail first, then creates work that workers can safely retry. Local Outbox emergency copy Object Store raw .eml Ingest Queue retryable work Email worker claims and bridges into processing The worker turns durable queued mail into the backend's internal process-email request. Claim Job atomic lock Policy Recheck backup gate Download raw .eml Track Email status + audit Backend processor reads the stored email The backend is where email content becomes a normalized alert candidate. Load .eml spool path Parse headers/body Profile rules + fields Normalize alert input Analyzer rules decide what happens next Published rules handle known mail; guarded fallback helps avoid silently missing unknown alerts. Rules Match known patterns Confidence Gate safe threshold AI Fallback guarded backstop Alert Decision log / suppress / call Escalation places one voice call at a time Routing resolves primary/failover groups, then tracks call attempts and outcomes. Resolve primary/failover Pick Target next user Call Attempt INITIATED Voice API voice callout Voice outcome decides the next step Answered calls can acknowledge; missed or wrong responses continue escalation. Decision answer + digit? Ack? correct digit Next User no ack Failover secondary group