SMS मार्केटिंग सहमति।
प्रचार संदेशों को ऑप्ट-आउट कर चुके नंबरों तक न पहुँचने दें, और कैरियरों के लिए ऑडिट ट्रेल रखें।
ऑप्ट-इन दर्ज किया गया
प्राथमिकता पेज · 12 सित॰ 2026
प्रेषक जाँचा गया
इस श्रेणी के लिए पंजीकरण आवश्यकताएँ पूरी हुईं
मौजूदा प्राथमिकताएँ जाँची गईं
कोई सप्रेशन या बाद का ऑप्ट-आउट नहीं
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.
निर्णय के लिए संचालन गाइड खोजें
- प्रेषक और कैरियर अनुपालनComplete US 10DLC, toll-free verification, and international sender registrations.
- ऑप्ट-आउट और कीवर्डSee how STOP, HELP, and START keywords and sender suppressions work in detail.
- प्रेषक चुनेंCompare local long codes, verified toll-free numbers, short codes, and alphanumeric sender IDs.
SMS अनुपालन से जुड़े प्रश्न
क्या सेंडर पंजीकरण का मतलब है कि मैं अपने डेटाबेस में सभी को टेक्स्ट कर सकता/सकती हूँ?
STOP कीवर्ड क्या ब्लॉक करता है?
क्या प्राप्तकर्ता अल्फ़ान्यूमेरिक सेंडर ID का उत्तर दे सकते हैं?
क्या Bird का उपयोग कानूनी अनुपालन की गारंटी देता है?
अपना SMS प्रोग्राम बनाते रहें
- SMS मार्केटिंगSee how audiences, templates, compliance controls, and broadcasts fit together.
- SMS APISend transactional OTPs, order alerts, and 100-message batches from your backend.
- डिलीवरी एनालिटिक्सTrack delivery rates, latency, and carrier error codes by country and mobile network.
- SMS संसाधन लाइब्रेरीBrowse integration guides, compliance explainers, and the interactive SMS segment calculator.
नियंत्रण खोए बिना स्केल करें।
प्रोडक्शन और सैंडबॉक्स ट्रैफ़िक को अलग-अलग समर्पित वर्कस्पेस में रखें, API कुंजियों का दायरा ठीक उन्हीं चैनलों तक सीमित करें जिनकी हर सेवा या एजेंट को ज़रूरत है, और ऑडिट लॉग में अनुमतियों में हुए बदलावों पर नज़र रखें।