Send promotional SMS only to customers who asked for it.
Keep subscriber opt-in records, registered sender IDs, and automatic STOP suppressions connected to every SMS broadcast you run. Prevent accidental texts to opted-out numbers, respect local quiet hours, and maintain a clear audit trail for carriers and regulators.
APAda Park
Opt-in
Prüfen Sie die Details vor dem Senden
Opt-in erfasst
Absender geprüft
Aktuelle Präferenzen geprüft
Registrierung, Kundeneinwilligung und aktuelle Versandberechtigung sind getrennte Entscheidungen.
APAda Park
Opt-in
Prüfen Sie die Details vor dem Senden
Opt-in erfasst
Absender geprüft
Aktuelle Präferenzen geprüft
Registrierung, Kundeneinwilligung und aktuelle Versandberechtigung sind getrennte Entscheidungen.
APAda Park
Opt-in
Prüfen Sie die Details vor dem Senden
Opt-in erfasst
Absender geprüft
Aktuelle Präferenzen geprüft
Registrierung, Kundeneinwilligung und aktuelle Versandberechtigung sind getrennte Entscheidungen.
Keep sender registration, opt-in consent, and suppressions separate.
Approving a sender with carriers does not grant permission to text a phone number, and adding a contact to an audience should never override a prior STOP reply. Bird separates carrier registration, subscriber consent, and active suppressions so your team can verify each requirement before a broadcast launches.
Approved local senders
Match each destination country with a compliant sender, whether that is a US 10DLC campaign, a verified toll-free number, a dedicated short code, or a registered alphanumeric sender ID.
Documented subscriber opt-in
Store when and how each contact agreed to receive marketing texts on their profile so your consent records stay attached to the phone number across campaigns.
Send-time suppression checks
Evaluate sender suppressions and workspace opt-outs at the moment a broadcast executes so a stale CSV import cannot re-message someone who unsubscribed yesterday.
Handle STOP, HELP, and START replies automatically.
When a recipient replies with a recognized opt-out keyword on a two-way number, Bird immediately records a suppression for that sender and subscriber number so future broadcasts skip them automatically.
Instant STOP suppression
Replying STOP (or localized equivalents in supported markets) adds the recipient to your suppression list right away while still forwarding the inbound webhook event to your app.
Sender vs. workspace scope
Opting out of a specific sender number blocks traffic from that sender, while workspace-level preferences let you manage broader marketing eligibility across your account.
Country-specific keyword rules
Automatic keyword handling and confirmation replies depend on the destination country and sender type. Check local rules and include clear opt-out instructions when sending from one-way alphanumeric IDs.
Run every broadcast through a pre-launch compliance check.
Carriers filter campaigns that text subscribers in the middle of the night, hide the sender's identity, or omit opt-out instructions. Build these checks into your standard campaign review before scheduling a send.
Respect local quiet hours
Schedule promotional sends around the recipient's local time zone and account for carrier throughput so large broadcasts finish before evening quiet hours begin.
Identify your brand and opt-out path
Include your brand name and clear unsubscribe instructions (such as Reply STOP to opt out) in the message body so recipients never have to guess who texted them.
Keep an auditable trail
Link each broadcast record to its target audience, template version, sender ID, and per-recipient delivery status so your team can answer carrier or regulator inquiries quickly.
Finden Sie den operativen Leitfaden für die Entscheidung
Fragen zur SMS-Compliance
Bedeutet Absenderregistrierung, dass ich alle in meiner Datenbank anschreiben darf?
Was blockiert ein STOP-Schlüsselwort?
Können Empfänger auf eine alphanumerische Absenderkennung antworten?
Garantiert die Nutzung von Bird die Rechtskonformität?
Bauen Sie Ihr SMS-Programm weiter aus
Skalieren, ohne
die Kontrolle zu verlieren.
Organisieren Sie Teams in Workspaces, steuern Sie den API-Zugriff und verfolgen Sie Änderungen über Audit-Logs.
Organisation
Harbor
Zugriff bleibt in seinem Workspace.
Produktion/API-Schlüssel
Zustellagent
AktivAlex Lee
Admin
Heute · UTC
Audit-Protokoll
Organisation
Harbor
Zugriff bleibt in seinem Workspace.
Produktion/API-Schlüssel
Zustellagent
AktivAlex Lee
Admin
Heute · UTC
Audit-Protokoll
Organisation
Harbor
Zugriff bleibt in seinem Workspace.
Produktion/API-Schlüssel
Zustellagent
AktivAlex Lee
Admin
Heute · UTC
Audit-Protokoll