FTB dialer: fill in IVR sequence + telephony credentials to go live #1
Labels
No labels
backlog
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Circuit-Forge/osprey#1
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Context
Bootstrapping the Osprey government hold-line dialer using the FTB (Franchise Tax Board) as the first real-world test case.
The webhook service and dialer script are built and deployed:
https://circuitforge.tech/webhooks/twilio/(path kept for compatibility; will update when provider is confirmed)/Library/Development/CircuitForge/osprey/Blocked on
OSPREY_IVR_SEQUENCE— the DTMF (dual-tone multi-frequency) key sequence to navigate the FTB IVR (interactive voice response) tree (800-852-5711) to reach a live agent — see #3Format: comma-separated digits where each comma = 0.5s pause.
Example:
"1,,,2,,,0"= press 1, wait 1.5s, press 2, wait 1.5s, press 0.Set in
/Library/Development/CircuitForge/osprey/.envasOSPREY_IVR_SEQUENCE=...To complete setup
/Library/Development/CircuitForge/osprey/.envfrom.env.exampleconda run -n cf uvicorn api.main:app --host 0.0.0.0 --port 8520 --app-dir /Library/Development/CircuitForge/ospreyconda run -n cf python -m app.dialers.ftbFiles
api/webhooks/twilio.py— TwiML (Twilio Markup Language) handlers (navigate IVR, status callback, bridge)app/dialers/ftb.py— retry loop dialer script.env.example— all required env vars documentedcircuitforge-plans/osprey/superpowers/specs/2026-04-04-telephony-backend-design.md— provider comparison and architecture decisionspyr0ball referenced this issue from Circuit-Forge/roadmap2026-04-02 19:07:31 -07:00
FTB dialer: fill in IVR sequence + Twilio credentials to go liveto FTB dialer: fill in IVR sequence + telephony credentials to go live