All templates

Automated Bandwidth Delivery Failure Alerts

Every morning, WebRun opens the Bandwidth dashboard, reads yesterday's messaging and voice activity, compares delivery failures and error codes against the previous seven days, messages you on WhatsApp when a failure rate or a specific error code spikes, and books a Google Calendar review slot when the problem is big enough to need a call with your carrier.

Runs on WebRun · Strict Lockdown policy
Every day at 8:00 AM WebRunorchestrates each step
1 Bandwidth read yesterday's delivery results
2 WhatsApp message you the spikes
3 Google Calendar book a review when it is serious
In short

How do I get alerted when SMS delivery failures spike?

WebRun reads your Bandwidth messaging and voice results every morning, comparing yesterday's delivery failures and error codes against the trailing seven day average. It messages you on WhatsApp naming the error codes, numbers and campaigns that spiked, and books a Google Calendar review slot when the failures cross your threshold.

  • A delivery problem is caught the next morning instead of by a customer
  • The failing number or campaign is named, not just the total
  • Normal days send one line, so alerts keep their meaning

Built for telecom operations · CPaaS teams · support engineering · product operations

Step by step

What does WebRun do on every run?

The exact actions WebRun takes, in order - in plain language, so you can adjust anything.

  1. WebRun signs in and gets to work

    Opens app.bandwidth.com in a real browser with your saved login - no setup, no API keys.

  2. 1
    Bandwidth - read yesterday's delivery results
    bandwidth.com
    WebRun in Bandwidth: read yesterday's delivery results
    WebRun opens Bandwidth to read yesterday's delivery results.
    • Open the Bandwidth dashboard and set the reporting window to yesterday
    • Capture messages sent, delivered and failed, broken down by error code
    • Capture call attempts, completions and failures for the same window
    • Compare each failure rate against the trailing seven day average
    • Flag any error code whose volume more than doubled and any number or campaign carrying most of the failures

    Done when Yesterday's messaging and voice results are captured with each failure rate compared to the weekly baseline.

  3. 2
    WhatsApp - message you the spikes
    whatsapp.com
    WebRun in WhatsApp: message you the spikes
    WebRun opens WhatsApp to message you the spikes.
    • Message your operations group with only the metrics that moved outside the normal range
    • Name the error code, how many messages or calls it hit, and the change against the weekly average
    • Name the sending number or campaign carrying most of the failures
    • Send a one line all clear instead of a wall of numbers when yesterday looked normal

    Done when You have yesterday's exceptions on WhatsApp, or a one line all clear.

  4. 3
    Google Calendar - book a review when it is serious
    calendar.google.com
    WebRun in Google Calendar: book a review when it is serious
    WebRun opens Google Calendar to book a review when it is serious.
    • When failures exceed the threshold you set, add a 30 minute review event to today's calendar
    • Put the affected numbers, error codes and volumes in the event description
    • Skip the event on normal days so the calendar stays a real signal
    • Never change routing, disable a number or open a carrier ticket. WebRun surfaces the problem and you decide

    Done when A review slot exists on days when delivery genuinely broke.

Run settings

How is each run configured?

Starting pageWhere Chrome opens at the start of each run
app.bandwidth.com
ScheduleRuns automatically on this cadence
Every day at 8:00 AM
DeliveryHow each run's result reaches you
Failure alerts · WhatsApp
OutputWhat each run produces - A daily exception note naming the Bandwidth error codes, numbers and campaigns whose failure rate rose against the trailing seven day average.
Text
Setup & safety

Secure by default

Connect once, stays signed in

WebRun signs in once and keeps each session in a persistent environment, so every run picks up right where it left off.

Your credentials stay in your own private environment - WebRun never stores your passwords.
Strict Lockdown

Every action is checked against this policy before it runs.

Domains ALLOWLIST
Typed input ALLOW
Shell command BLOCK
File uploads BLOCK
Runs in a contained environment More on policies
Good to know

Questions, answered

Will it change routing or disable numbers?

No. WebRun only reads the Bandwidth dashboard. Changing routing, disabling a number, editing a campaign and filing a carrier ticket all affect live traffic, so they stay with your team. The run reports and books time.

How does it know a failure rate is abnormal?

It compares yesterday against the trailing seven day average for the same metric. A code that doubled its volume gets flagged; ordinary day to day noise does not, so the alert stays worth reading.

Does it send an alert every morning?

It sends a one line all clear on normal days and a detailed exception message only when something moved. The calendar review slot is booked only when failures cross the threshold you set.

Put this on autopilot.

Turn it on in minutes - or have our team set it up for you.