---

​

Introduction

​

Best practices!

We created this topic to share everything we’ve learned about best practices to avoid issues with blocks and bans on the application. We’d like to start with the following reflection: You probably receive several SMS messages daily with ads from stores, promotions, phone carriers, and so on. Now think — how many of those types of messages do you receive via the application? Probably none or very few, right? Even so, the application lets you mark messages as spam and even block the contact.

​

THE APPLICATION DOES NOT ALLOW SPAM!

The application is very strict when it comes to spam, which is why we pay more attention to it than SMS. Why do we let SMS messages pile up but can’t resist checking our phone the moment we get an application message? Because we know it’s from someone we know, and we rarely get promotions through it.

---

​

How many messages can I send?

Quantity does matter, but it’s not just about how many messages you send — the factor of WHO you send to is often the key point. We always use the case of one of our oldest clients, who today sends promotional messages via the application to more than 80,000 people daily and has never had their number blocked. When we asked how they managed this, they kindly shared the following technique:

1. Number maturation: Use the phone number on the application normally before starting to send many messages through Z-API.
2. Interact via phone or the web application before connecting to Z-API: This helps show the application that you’re a real user, not a bot.
3. Use text that encourages users to reply: This helps show the application that you’re having real conversations.
4. Offer an option to opt out: This respects user privacy and avoids reports.
5. Fill in profile data on the application: This shows the application that you’re a legitimate user.
6. Scan the QR code 24 hours after registering on the application: This helps confirm you’re a real user.

Sending approach:

• First: For recipients to receive promotional messages, they need to add the company number to their contacts and send a message saying “I want promotions”. This simple action significantly reduces the risk of blocking.
• Second: Personalize messages with recipient data so that all messages aren’t exactly the same.
• Third: Always give recipients an option to stop receiving messages. Example: “Type 2 to stop receiving these messages”, then monitor the webhooks to remove those numbers from the send list.

Summary

• Avoid sending messages to people who don’t have your number in their contacts;
• Personalize messages with recipient information. If not possible, use random attributes to differentiate each message;
• Try to get recipients to interact with your number, especially if you know they don’t have it in their contacts;
• Offer the option to opt out and monitor webhooks to handle these interactions.