Pain
Waiting
An operator loses attention to hold time and repetitive support routing.
CALL-E · Most Practical Use Case
The vendor call you should not be making during an outage.
IncidentBridge gives CALL-E exactly one bounded job: call an authorized vendor support line, collect ticket / status / ETA / workaround facts, and return corroborated evidence. The phone agent never gets authority to declare recovery.
Independent upstream review accepted
Official repoCALL-E
ContributionPR #132
Tests33
Coverage93.80%
01 / Real-world impact
Remove the phone queue from incident response, not the human judgment.
When a SaaS or data dependency fails, an operator often has to stop diagnosing the incident, wait on a support line, repeat context, and manually copy the vendor ticket, status and ETA back into the incident channel. IncidentBridge delegates only that bounded conversation.
Pain
Repetition
The same incident context is re-read to a vendor while the real system is still failing.
Pain
Transcription
Ticket, status, ETA and workaround facts are manually copied back into the response workflow.
Product boundary
Delegate conversation, not authority.
CALL-E gathers facts. Local health checks and the human incident commander still decide whether recovery is real.
02 / External validation
CALL-E maintainers attacked the safety model before accepting it.
The upstream review found two substantive blockers. Both were fixed, regression-tested, and the app was merged into the official CALL-E community repository on August 17, 2026.
Blocker 01
Spoken fields could leak sensitive data.
Privacy validation originally covered only the incident summary. The fix now screens every free-text field that can enter the spoken task for credentials, secrets and personal contact data.
Blocker 02 · fixed
A confident result was not enough.
A successful result must now bind to the exact workflow, incident, call ID and authorized destination, then corroborate the returned vendor ticket against recipient transcript evidence. Otherwise it fails closed to needs_human.
03 / Controlled workflow
Every transition narrows authority instead of expanding it.
The phone call is only one step. Validation, preview, exact authorization, durable dispatch state and evidence corroboration all happen around it.
Validate
Reject secrets, contact data in spoken fields, unsupported identifiers and unauthorized recipients before a task exists.
Preview
Show the masked destination, exact CALL-E task, strict result schema and idempotency identity with zero phone side effect.
Authorize
Live mode needs explicit execute intent, recipient authorization and an exact E.164 allowlist match.
Reserve + call
Write durable state before dispatch. Ambiguity becomes reconciliation, never a blind second dial.
Corroborate
Bind workflow, incident, call and destination, then require recipient evidence for the ticket. Recovery still remains human-owned.
04 / Product experience
Three paths. No hidden success.
The console separates public live-provider evidence, a no-call authorization preview, and a deterministic success-path simulation. The labels are explicit so a judge can see what is real, what is previewed, and what is simulated.
Public live provider runLoading
Final route
Loading…
Incident closedfalse
Loading evidence…
Successful live-call behavior has also been validated privately through direct testing, packaged external testing, and testing with randomly selected users. Those materials are intentionally not published because they contain real participant and conversation data. A one-shot consented synthetic live-success runner is now included so the full real success boundary can be published without exposing the participant.
05 / Technical implementation
Built to survive a skeptical read, not just a happy-path demo.
The published CALL-E Python SDK is actually imported and called at runtime. The final award-sprint GitHub Actions run verifies lint, 33 regression tests, 93.80% total coverage, and demo-source syntax.
Automated tests33CI verified
Coverage93.80%90% enforced gate
Live proof runner99%module coverage
Official adoptionMergedCALL-E PR #132
The agent may
Collect bounded operational facts.
- Disclose AI identity and ask for consent
- Confirm the correct support desk
- Collect ticket, status, ETA, workaround and callback window
- Return a structured, corroborated result
The agent may not
Turn a phone result into recovery authority.
- No credentials, payments or contract changes
- No ambiguous automatic redial
- No uncorroborated
vendor_acknowledged - No incident closure without human + local health verification