Voice agent flagged Spam Likely? Fix short-call rate before swapping the DID
Packet-Exchange-Care · reddit · 2026-11-17
Swapping the DID after a Spam Likely flag is a mistake — a fresh number inherits the same call behavior. The author's triage order: probe each carrier with real handsets to identify which analytics engine flagged you; request the Identity header on terminated calls to check attestation grade (B/C means the route is the problem); watch your short-call rate, since answer latency creating dead air looks exactly like robocalling to scoring engines; spread volume across DIDs with local area codes; test recycled numbers before launch; and register with free caller registries. If you fix only one thing, fix the short-call check. Post ends with a soft plug for Packet Exchange.
More from coding & agent
- VC Martin Tobias: yesterday's deliverable was a PDF, tomorrow's should be an MCP — MartinGTobias · 2026-11-17
- MIT CSAIL's 0.016% weight-space edit lifts Qwen3.5-0.8B MATH-500 6x without retraining — RandalSchwartz · 2026-11-17
- Neo4j dev advocate to walk Miami JUG through AI agents and MCP — mkheck · 2026-11-17
- Customer saves $9M+ by ditching API pricing and Devin for aggregated AI subscriptions — garrytan · 2026-11-17
- Miro's year-long experiment: making the canvas itself the AI prompt, not a chat sidebar — max__drake · 2026-11-17
- Workato CISO shares how AI agents triage ~80% of security alerts in production — adamse · 2026-11-17