📘
Sinch | Documentation Global
  • Introduction
  • Glossary
  • GETTING STARTED - MENU
    • Sinch Messaging Platform
      • Login, Language & Menu
      • Account & Settings
      • Dashboard
      • Contacts
      • Groups
  • Credits and limits
    • Signing of plans
    • Limits
  • Send a message
    • Send a fast message
    • How to Send a Message
    • How to Set Up a File
    • Mapped errors
    • Campaigns
    • Correlation ID
    • Tracking Sent Messages
    • Cancelling a Message
    • Character Limit Setting
    • MM2: New Report: Chat (MT + MO)
    • SMS Report > RCS
  • Reports
    • Viewing & Exporting Reports
      • New WhatsApp Conversation report
      • Getting to know the new reports
    • Saved Reports
    • WhatsApp Lists
    • Billing Report
  • Permission
    • System User Role
    • Managing Customers | Subaccounts
    • Permission Levels
    • Subaccounts & Users
    • IP Restriction
    • Two-step Verification
  • SMS
    • SMS Template
    • SMS BOT
  • RCS
    • RCS (Native)
  • WHATSAPP
    • WhatsApp Embedded Signup
      • Prerequisites
      • Registering your WhatsApp Number
      • Verifying your Company on Business Manager
      • Potential Errors During the Embedded Signup Flow
    • Human Assistance Policy
    • WhatsApp Guidelines
    • Instructions & Good Practices
      • Channel Rules
      • Learn More About Tiers
      • Good Practices
    • WA Template - What Is It?
    • Registering a Template
    • Deleting a WA Template
    • WhatsApp Account Settings
    • WhatsApp Dashboard
    • Tech Providers - What is it and how does it work?
  • IA CONVERSATIONAL
    • Planning your bot
    • Creating a new bot
    • Adding content to your bot
      • Detecting information in expressions
      • Asking user info through input validation
      • Flow navigation with variables
    • Bot dialogs
      • Bot message
      • Go To
      • Input Validation
      • Action
    • Publishing & platform URLs FAQ
  • TECHNICAL DOCUMENTATION
    • API & Integrations
      • Introduction - Integrations
      • SMS API
      • Email API
      • Fallback API
      • WhatsApp API
      • WhatsApp Groups API
      • Listing Message Templates
      • WhatsApp Interactive API
      • WhatsApp Lists via API
      • WhatsApp Messaging via SFTP
      • Campaigns API
      • TTL - Time to Live
      • Webhook
  • SUPPORT
    • Status
    • Glossary - Status Page Components
    • Support
  • STATUS PAGE
    • Components status page
      • Integrations
        • SMPP
        • Web service API
        • Web Interface
      • Callback / Delivery Report
        • Webhook DLR (delivery to handset)
        • SMPP DLR (delivery to handset)
        • SMPP Callback (delivery to carrier)
        • Webhook Callback (delivery to carrier)
      • OPERATORS
      • WhatsApp Sending messages to the user (MT)
        • Internal Queues MT
      • WhatsApp Receiving User Messages (MO)
        • Internal Queues (MO)
Powered by GitBook
On this page
  • Understanding the Tiers
  • How to Upgrade Your Tier?

Was this helpful?

  1. WHATSAPP
  2. Instructions & Good Practices

Learn More About Tiers

PreviousChannel RulesNextGood Practices

Last updated 3 years ago

Was this helpful?

The indicators shown on influence your message sending limitation.

The message deliverability limitations determine to how many unique users your company can send messages daily. This includes new chats and existing chats with users.

Your message limit does NOT restrict the number of messages your company can send, only the amount of users who can receive them.

It does also NOT apply to messages sent in reply to a message initiated by the user within a 24-hour period.

Understanding the Tiers

Upon registering its phone number, a company begins at Level 1, which has a limit of 1,000 messages sent every 24 hours.

  • Tier 1 - Allows you to send messages to 1,000 unique users every 24h.

  • Tier 2 - Allows you to send messages to 10,000 unique users every 24h.

  • Tier 3 - Allows you to send messages to 100,000 unique users every 24h.

A number that is in Tier 3 can drop to a lower tier due to poor quality.

How to Upgrade Your Tier?

A company’s phone number will be upgraded to the following level if:

  1. Its quality rating is not too low.

  2. The cumulative number of users to whom it sends notifications adds up to twice the current message limit within a 7-day period. A company will be upgraded from Level 1 to Level 2 when it sends messages to a total of 2,000 users within a 7-day period, for instance.

The minimum amount of time in which this change can occur is 48 hours after the 1st trigger.

A few possible scenarios below:

Scenario 1: Every number begins at tier 1. The company will move up to the following level once it sends messages to a total of 2,000 users within a 7-day period, for example, and has a good quality rating.

​Scenario 2: A low quality level (Red) causes the number’s status to change from Connected to Flagged.

During its Flagged period, the number had good quality (Green/Yellow) in its deliveries. After the 7-day period, the customer goes up to the next Tier.

Scenario 3: A low quality level (Red) causes the number’s status to change from Connected to Flagged.

​

During its Flagged period, the number continues to have poor quality (red). After the 7-day period, the customer goes back to the previous Tier, which allows their company to send a smaller number of messages.

Channel Rules
Scenario 1
Scenario 3