Honor opt-outs in the messaging journey. Understand what Bird handles for supported keywords and where your application must take over.
Inspect what STOP, START and HELP mean for a supported sender and subscriber.
The supported keyword blocks this sender-and-subscriber pair. Carry the preference across the program the customer asked to stop.
The suppression ends for the same pair. Destination, sender and content requirements still apply.
HELP does not opt a customer in or out. This illustration uses one supported country’s keyword behavior.
Honor the choices customers make about your messages.
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.
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.
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.
Organize teams in workspaces, control API access, and trace changes through audit logs.
HarborOrganization