A customer says stop. Future sends listen.

Honor opt-outs in the messaging journey. Understand what Bird handles for supported keywords and where your application must take over.

Get StartedContact Sales

One incoming word.
A changed sending rule.

Inspect what STOP, START and HELP mean for a supported sender and subscriber.

Explore opt-outs and keywords
Interactive illustration with fictional records. No account operation is performed.

Know the coverage.
Keep the preference.

Honor the choices customers make about your messages.

Check the country’s keyword rules.

Default handling covers a subset of countries. Read the applicable rules before relying on automatic replies or suppression. Where there is no coverage, your application must honor opt-outs.

Understand the suppression scope.

A recognized stop keyword blocks one sender-and-subscriber pair and sends a confirmation. Carry the customer’s preference across the program they asked to stop.

Keep incoming handling aware.

A stop message still produces sms.received. Branch on the keyword outcome before business replies. Custom replies can change wording while retaining the protected keyword behavior.

Explore SMS consent & opt-outs

Keep building
with SMS.

Handle the reply, follow its event, and check support in every market you serve.

Two-way SMS

Receive customer texts and reply from your application.

Webhooks

React to incoming texts and delivery changes.

Global delivery

Understand destination support before sending.

Explore SMS

Scale without
losing control.

Organize teams in workspaces, control API access, and trace changes through audit logs.

WorkspacesTeam rolesAPI authentication
Explore Enterprise

Start with SMS.
Build across channels with Bird.

Get StartedContact Sales

Your next idea. Ready to connect.

Get StartedContact Sales