Skip to main content
NewNMC’s advertising guidelines for doctors are in force from 6 Oct 2026. See what to change, and get a free compliance auditNew NMC advertising rules for doctors: what to change
AI & Automation

WhatsApp Quality Rating and Messaging Limits: Protecting a Hospital Number From Blocks

How messaging tiers scale, what Meta documents about template quality and recipient feedback, and a monitoring and ramp-up routine that keeps a hospital WhatsApp number healthy.

WhatsApp Quality Rating and Messaging Limits: Protecting a Hospital Number From Blocks

This article is for marketing operations leads and CRM owners who run outbound WhatsApp for a hospital, a hospital group or a multi-clinic chain and want to scale volume without damaging the number. It assumes you already have a verified account and approved templates. For the basic strategy, read our WhatsApp marketing guide for healthcare first. This post goes into the mechanism: tiers, quality signals, ramp plans and what to do when quality drops.

A healthcare number has one advantage and one weakness. The advantage is that many of its messages are wanted: reminders, report alerts, confirmations. The weakness is that a single bad campaign to an unengaged list can produce blocks and reports that affect the delivery of those useful messages. In a hospital, a throttled number is not a marketing inconvenience. It can delay appointment reminders.

We rely on Meta's current developer documentation. Where Meta does not publish a number or state, we say so and describe how to measure instead.

How messaging limits work

According to Meta's messaging limits documentation, a limit is the maximum number of unique WhatsApp users a business can message with business-initiated messages in a moving 24-hour period. The documented levels are 250 for new portfolios, then 2,000, 10,000, 100,000 and unlimited.

Several details change how you plan:

  • Limits belong to the business portfolio. They are shared by every phone number in the portfolio. If a hospital group runs separate numbers for the main hospital, the cancer centre and the diagnostics arm under one portfolio, one number's campaign can consume capacity the others need.
  • The count is unique recipients, outside customer service windows. Sending three messages to one patient counts once. Replies inside an open 24-hour window do not count against the limit.
  • It is a moving period, not a calendar day. A burst at 10 am can still be limiting at 9 am the next day.

How to move up a tier

To reach 2,000, Meta lists three scaling paths: verify your business, have your partner verify it if a partner onboarded you, or send 2,000 delivered messages outside customer service windows to unique numbers within a 30-day moving period using high-quality templates. Meta then analyses message quality before approving.

Above 2,000, scaling is automatic and needs both of the following: high-quality messages across all numbers and templates, and use of at least half the current limit in the last seven days. When both hold, the limit rises one level within six hours.

You can read your current limit in WhatsApp Manager under account tools, or through the API field whatsapp_business_manager_messaging_limit. The older messaging_limit_tier field is deprecated, so check integrations that still read it.

The implication for a hospital is that you cannot ramp by volume alone. A large, low-engagement send does not move you up and can set you back. Quality is the gate.

What "quality" is built from

Meta does not publish a formula. The documentation points to three kinds of signal that you can observe or influence.

Recipient feedback. Meta's opt-in guidance notes that people can block or report a business, can stop marketing messages from an individual business through WhatsApp's user preferences, and that sustained low quality can lead to rate limiting.

Template quality. Meta's template quality documentation describes four ratings reported by the API: green for high quality, yellow for medium, red for low, and unknown while no feedback or read-rate data exists yet. Yellow and red arise from negative feedback from multiple users or low read rates. Both can still be sent, but a template at risk can be paused or disabled, and a template that leaves the approved status cannot be sent.

Read behaviour. Low read rates count against a template. A message that recipients do not open is a signal that they did not want it or did not expect it.

Meta does not hand you a block count for each campaign. You infer problems from proxies, which is why monitoring needs to be designed rather than assumed.

Build the monitoring layer

Track these at the template and segment level, daily during a ramp and weekly otherwise.

SignalSourceWhat it tells you
Template quality scoreTemplate API field quality_score, or Manage templates panelDirect Meta rating per template
Template status changesmessage_template_status_update webhookPause or disable events
Delivery rateMessage status webhooksWrong numbers, unreachable users
Read rateMessage status webhooksInterest and expectation
Opt-out repliesInbound text such as STOPDirect dissatisfaction
"Wrong number" or "who is this" repliesInbound text classificationCapture-process failures
Messaging limit fieldBusiness portfolio APITier movement

Set alert owners. Someone must read the pause webhook the same day. A template that has quietly turned yellow for two weeks is a campaign someone sent without looking.

Treat inbound objections as a metric

Tag inbound messages that contain opt-out phrases, "wrong number", "I did not ask for this" and complaints. Count them per thousand delivered messages by template and by source of the number. This is the closest practical proxy for block behaviour you can build yourself, because every blocked recipient was first someone who did not want the message. If one source, such as an old camp list, produces most of the objections, you have found the problem.

Segment before you send

Quality is controlled mostly before the send button. Segment on four axes:

  1. Consent purpose. Only patients who agreed to promotional messages receive marketing templates. Our opt-in management service covers the consent side.
  2. Recency of relationship. A patient seen last month is a different audience from one seen in 2021. Send to the recent group first.
  3. Engagement history. Contacts who replied, clicked or booked via WhatsApp go ahead of those who have never responded.
  4. Specialty relevance. A cardiology awareness message to a paediatric list is the kind of mismatch that generates blocks.

Exclude numbers that bounced, patients flagged as deceased in the records, and people who withdrew consent. Excluding them costs nothing and protects the portfolio.

Want this applied to your practice? Get a free ai & automation audit.

Book my free audit

A ramp plan for a new campaign or number

The numbers below are a hypothetical plan for a 300-bed hospital in Pune with a portfolio limit of 10,000. They illustrate the logic and are not Meta thresholds.

  1. Day 1-2, canary send. Send to the 500 most engaged contacts. Check delivery, read and objection counts after 24 hours.
  2. Day 3-4. If objections are low and template quality remains green or unknown, send to 2,000 recent patients.
  3. Day 5-7. Expand to 4,000, still within the recency and consent filters.
  4. Week 2. Open to the wider promotional list, in batches no larger than half the portfolio limit per day, never close to the cap.
  5. Stop rule. If a template moves to yellow, or objections spike against the previous batch, pause that template and review wording and audience before another send.

Keep a buffer. The limit applies to unique users in a moving 24 hours, so a campaign that uses all of it leaves no room for the transactional templates the hospital needs that day. Reserve a block of capacity for utility traffic and do not let campaigns spend it.

Separate numbers or one number?

Many hospitals ask whether to run reminders and campaigns on separate numbers. Because limits are portfolio-level, a second number under the same portfolio does not give you a second pool of capacity. It does give you isolation of reputation signals at the number level, but you should confirm the current behaviour in Meta's documentation before architecting around it, as we found no clear statement in the pages we reviewed. A more reliable separation is operational: clean utility templates, strict consent filters, and a campaign calendar that avoids stacking sends.

When quality drops

If a template turns red or is paused:

  • Stop sending that template immediately and do not duplicate it under a new name to continue the same message.
  • Identify the audience that produced objections. Look at source, recency and consent.
  • Check the template wording against what was promised at opt-in. Mismatch between expectation and content drives reports.
  • Fix the audience before the text. A good message to the wrong people still fails.
  • Return to a smaller send and watch.

Be careful with appeals and replacements. Meta's template pages describe review routes for category and rejection decisions, but a quality problem is a signal about recipients, not about paperwork.

Operating checklist

  • Record your current tier and the portfolio's numbers in a runbook.
  • Reserve capacity for transactional sends every day.
  • Subscribe to the template status webhook and name an owner.
  • Tag and count inbound objections per template.
  • Segment on consent, recency, engagement and specialty.
  • Use a canary send for every new template and list.
  • Review quality weekly and before any seasonal camp.
  • For planning outbound sends and managing replies in one place, WaCRS helps plan WhatsApp outreach campaigns and manage business conversations.
  • Align the campaign calendar with the WhatsApp automation service design so reminders and campaigns do not collide.

Hospitals that grow WhatsApp reliably treat it as a permission channel with a reputation to protect. Quality is the product of consent, relevance and restraint.

Filed underwhatsapp quality rating messaging limitswhatsapp messaging limit tierswhatsapp number blocked reports hospitalwhatsapp template paused low qualitywhatsapp business api scale campaigns

About the author

Co-Founder & CTO · Gurugram, India

Arush builds the systems the rest of the company runs on — the patient-acquisition pipelines, the AI chatbots, the analytics that tie a single click to a booked appointment. If a campaign reports a number, it's because something his team built is tracking it.

Free guide · 15 pages

The Patient Acquisition Blueprint

A 90-day plan from first search to booked appointment.

The Pioneers Brief — one essay, three benchmarks, one teardown, every Thursday. Subscribe free →

Free ai & automation audit

Your next chapter starts with a conversation.

Three quick questions. We come prepared with a plan for your specialty and city.

  • A 30-minute call with a healthcare specialist
  • Your top three growth opportunities, in writing
  • Honest advice — even if that means not hiring us
  • No obligation and no hard sell
You’ll speak with a senior strategist
Consultations are hosted by Arush Thapar’s team.
Step 1 of 3Takes 30 seconds

What do you want to improve first?

Details stay privateNo obligationReply within 1 working day

Client portfolio · BTL & activations

Work relevant to whatsapp quality rating and messaging limits protecting a.

Explore client work →