Built a network incident agent where the actor is the outage

I built a TypeScript sample on Telnyx Edge where each network incident is represented by its own durable Agent SDK actor.

Code: https://github.com/team-telnyx/telnyx-code-examples/tree/main/network-incident-agent

The interesting part is that the actor is not a temporary incident chatbot. It owns the outage lifecycle:

• Detect and assess severity
• Keep affected customers in KV
• Record every transition in embedded SQL
• Proactively send status updates by SMS
• Answer inbound calls with current incident context
• Write the RCA to CloudFS
• Schedule a delayed recurrence check

The included web dashboard runs a paced flow from detected to investigating, restoring, resolved, and closed.

It defaults to safe demo mode, so SMS delivery is simulated while the state, KV, SQL, CloudFS, and scheduling paths still run. Live mode is a separate explicit option for real Telnyx parameters and opted-in destinations.

Run it locally:

git clone https://github.com/team-telnyx/telnyx-code-examples.git
cd telnyx-code-examples/network-incident-agent
cp .env.example .env
npm install
npm run build
mkdir -p /tmp/network-incident-cloudfs
CLOUDFS_MOUNT_PATH=/tmp/network-incident-cloudfs npm start

The same durable-entity pattern could work for shipments, maintenance cases, SIM lifecycles, or security incidents. I would be interested in what other entities people would model this way.