SMS campaign controls
Respect the person behind the number.
Keep the permission to contact someone connected to the message you send. Review consent, the destination and the sender before a campaign launches. Honor replies and preference changes, and keep the evidence your team needs to explain why a person was included.
The decision behind one message
Example campaign
Campaign review
A clear permission trail
Opt-in recorded
The customer asked for SMS offers. Source, time and scope are retained.
Sender checked
The sender is eligible for the destination and campaign purpose.
Current preferences checked
Suppressions and later preference changes determine whether this send can proceed.
Illustrative review workflow. Registration, customer consent and current send eligibility are separate decisions.
Three checks. Three different questions.
Registering a sender does not create customer consent. An audience membership does not override an opt-out. Give each decision a clear place in your campaign review.
Sender readiness
Choose a sender that supports the destination and use case. Complete the country or carrier registration it requires.
Customer permission
Record how the person opted in, the scope they agreed to and the relevant source and time. Keep communication preferences connected to the contact.
Current eligibility
Check suppressions and preference changes when preparing and sending the campaign. A stale exported list should not override a later opt-out.
A reply should change what happens next.
Bird recognizes supported opt-out keywords and records a suppression for the sender-and-subscriber pair. Workspace-wide SMS preferences are a separate control.
Honor STOP
A supported stop keyword opens a suppression for that sender and number. The inbound event remains available to your application.
Keep the scope clear
A sender-level suppression and a workspace-wide preference are different records. Use the control that matches what the customer requested.
Review local behavior
Keyword recognition and automatic replies vary by country. Check the current catalogue and test the path for each market you launch.
Build a repeatable launch review.
Choose appropriate sending windows and a clear opt-out route. Use Bird’s operational controls alongside your organization’s review of the rules that apply to the campaign.
Timing
Set the schedule deliberately and account for the recipient’s local time. A large send may continue beyond the moment it starts.
Content
Make the brand, purpose and next action clear. Review links, offers and the instructions a person uses to stop messages.
Evidence
Keep the campaign, audience, permission records and delivery outcomes connected so your team can investigate an individual message.
Questions about SMS compliance
Does sender registration mean I can text everyone in my database?
What does a STOP keyword block?
Can recipients reply to an alphanumeric sender ID?
Does using Bird guarantee legal compliance?
Put it into practice.
Continue with the documentation, guides and examples for this topic. Resources are in English.
Make permission part of the program.
Connect consent records, sender readiness and suppression handling before your next campaign.