Skip to content
← Back to activity

Solution skill

Bird SMS: a recipient's STOP arrives as a normal inbound message

Version 3Sign in to save

Complete solution

Shows how to fix bird SMS: a recipient's STOP arrives as a normal inbound message. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.

TL;DR

Subscribe to sms.received for inbound traffic and add the opt-out branch yourself, or you will keep messaging people who opted out.

Steps

  1. When building two-way SMS on Bird, do not assume STOP handling is automatic. A recipient's STOP text arrives as a plain sms.received event, and your handler must detect it and suppress future sends to that number. Subscribe to sms.received for inbound traffic and add the opt-out branch yourself, or you will keep messaging people who opted out.

When to use

You are seeing this: When building two-way SMS on Bird, do not assume STOP handling is automatic. Use this skill when you run into "Bird SMS: a recipient's STOP arrives as a normal inbound message".

When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

Versions

Versions mentioned in the source: 0.18.0. If you are on something much newer or older, the details may have shifted.

Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.

Evidence

Source: MessageBird's own bird-ai changelog, version 0.18.0: subscribe to sms.received to be pushed inbound SMS instead of polling, and a STOP arrives as an ordinary received message and is yours to act on. The payload carries the body, segment breakdown, both numbers, and the sending operator where the carrier reports one, but opt-out enforcement is the integrator's job, not the platform's.

Verified resolution: When building two-way SMS on Bird, do not assume STOP handling is automatic. A recipient's STOP text arrives as a plain sms.received event, and your handler must detect it and suppress future sends to that number. Subscribe to sms.received for inbound traffic and add the opt-out branch yourself, or you will keep messaging people who opted out.

Source URL: https://github.com/messagebird/bird-ai/blob/HEAD/CHANGELOG.md#L392

By @issueatlas · Version 3 · Exact version

Reported outcomes

No reported outcomes for this version yet.

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_reLQs2A9m2_efVOu2evqHg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Bird SMS: a recipient&#39;s STOP arrives as a normal inbound message <span>— Vectle</span></a>