The moment it happens
Get alerts for bounced and failed Bird messages
Bounces, spam complaints and failed SMS or WhatsApp sends are posted to Slack with the recipient and reason.
- Runs
- The moment it happens
- Apps
- Bird
- AI
- Not needed
- Access
- read
Send this to your assistant
Create a ClickRuntime automation: when a Bird email bounces or gets a spam complaint, or an SMS or WhatsApp message fails, post the recipient, channel and reason to #messaging-alerts in Slack.
First time? Adding ClickRuntime to your assistant takes about two minutes.
Why use it
Why teams use this automation
Teams that send SMS and WhatsApp messages through Bird, such as appointment reminders, order updates or one-time codes, often learn about failures from customers. A number is no longer in service, a WhatsApp template is rejected or a carrier blocks a batch, and the status sits quietly in message logs. Meanwhile, patients miss appointments and shoppers never get their delivery code.
Bird sends an event to ClickRuntime as soon as a message status changes. The workflow keeps only the failures, such as bounced or undelivered messages, and posts each one to your channel with the recipient and the reason. If you want, failure counts are kept in state so a daily rollup can summarize how many failed overall.
Support and messaging operations teams use it to act on failed sends while they can still be fixed.
What you get out of it
Failed reminders get a second try
When an appointment reminder bounces, someone can call the patient or send an email that same hour. A missed appointment avoided is revenue kept. Reaching the person by another channel the same day often saves the appointment entirely, and it costs a phone call.
Bad numbers get cleaned from your list
Repeated failures to the same recipient point to a number that no longer works. Removing it keeps future sends cheaper and your sender reputation healthier. Lists full of dead numbers waste send volume and distort delivery rates.
Template and carrier problems appear fast
A burst of failures with the same reason signals a rejected WhatsApp template or a blocked route. Seeing it in minutes limits how many customers are affected. Marketing can fix the template or switch route before the rest of the campaign goes out.
Support sees what the customer sees
When a customer complains they got no message, the agent can search the channel and find the failure and its cause. The answer is immediate and credible. Nobody needs to open Bird and filter the logs to answer a basic question from a worried customer.
A record for delivery disputes
Failure posts with timestamps document that a message was attempted and why it failed. That helps when a customer or regulator asks whether you notified them. That documentation can be decisive when a dispute arrives weeks later.
How it works
What happens, step by step
Each time Bird reports a delivery event, it tells ClickRuntime straight away.
The automation ignores successful sends and keeps bounces, spam complaints and failed SMS or WhatsApp messages.
Each failure is posted to #messaging-alerts with the recipient, the channel and the reason.
Before it runs live
- Connect Bird
- Paste your automation's link into the other app's webhook settings
What you get
Build your own
Need it to work differently?
Your own rules
Conditions, thresholds, filters and exceptions, written the way you'd explain them to a colleague.
Any number of apps
One automation can read from one app and update several others. Over 248 apps are ready, and anything with an API works too.
AI where it helps
Summaries, classification, extraction and drafts use ClickRuntime's built-in AI, with no extra key.
On a schedule or on each event
Runs as often as every 5 minutes, or the moment an app sends an event, and keeps track of what it already handled.
Changes you can ask for
- Act only on the items that match your own rules, and skip the rest
- Add an AI step, for example to summarize, sort or draft a reply
- Add another app, for example also send it to Slack
- Combine it with other Bird steps into one automation
Under the hood
The code that runs this automation
from clickruntime import on_event, notify
@on_event
def handle(event):
body = event.json or {}
msg = body.get("payload", {})
status = msg.get("status")
if status not in ("failed", "rejected", "bounced", "complained"):
return {"skipped": status}
receiver = msg.get("receiver", {}).get("contacts", [{}])[0].get("identifierValue", "unknown")
reason = msg.get("reason") or msg.get("failure", {}).get("description") or status
notify.slack(f":x: Bird {status}: {receiver}\nChannel: {msg.get('channelId', body.get('service'))}\nReason: {reason}",
channel="#messaging-alerts")
return {"posted": True}FAQ
Common questions
Which message statuses count as a failure?
Can I get one summary a day instead of every failure?
Does it work for both SMS and WhatsApp?
What permissions does it need?
Does it need AI?
How many runs does it use?
Can I change how it works?
Related
You might also like
Email yourself new SMS and WhatsApp messages from Bird
When a customer texts or WhatsApps our Bird number, I get an email with who sent it and what they said.
See how it worksPost new orders and sign-ups to Slack
When something happens in your shop, app or form, the details land in the right channel straight away.
See how it worksBook appointments only when you're free
Booking requests are accepted only for free slots within your hours, and land on your calendar with the attendee.
See how it worksKeep exploring
Set up “Get alerts for bounced and failed Bird messages” from your assistant
Copy the prompt above, or connect your assistant first. Free plan, no credit card.
