Template health and quality ratings

Template health in Arino One is checked at Templates → Health (/templates/health), a live table of every WhatsApp template with its current approval status, Meta quality rating and most recent lifecycle event — the fastest way to see whether a template is about to be paused before it actually stops sending.

Status vs quality: two different signals

It's easy to conflate these, but they answer different questions:

A template can be approved and still carry a red quality rating — approval only means it passed initial review; quality reflects how real recipients are reacting to it in the field. Watching status alone misses the templates that are quietly damaging your number's standing.

Reading the Health screen

Each row on /templates/health shows:

• Template — name plus language and category
• Status — draft, pending, approved, rejected, paused or disabled, colour-coded
• Quality — green, yellow, red, or a dash if Meta hasn't rated it yet
• Last event — the most recent lifecycle event (submitted, approved, rejected, paused, quality changed) with any detail Meta returned
• When — the timestamp of that event, or the template's last update if no event is recorded

Summary tiles at the top count templates by approved, pending, rejected and paused, so you can see at a glance whether your library is trending toward a healthy or troubled state before drilling into individual rows. Clicking any row opens the template itself.

Why quality matters beyond the one template

A template's quality rating rolls up into your WhatsApp Business number's overall quality rating, which in turn governs your daily conversation and messaging limits. Running one poorly-received template at volume can drag down the number's standing enough to restrict every other template sending from it — so a red-rated template is not just a problem for that campaign, it's a risk to your whole sending capacity. Pause or replace a template the moment it turns yellow, rather than waiting for red.

Common causes of quality decline:

• Sending to a cold or purchased list that hasn't genuinely opted in, driving block and report rates up
• Content mismatched to the approved category — a marketing message sent as a utility template, for instance
• Overuse — the same template sent too frequently to the same audience, read as spam even when the content is legitimate
• Broken personalisation — a variable resolving to a blank or wrong value at scale looks careless and gets reported

RCS templates: a separate library, and sometimes mandatory

RCS templates live at Templates → RCS (/templates/rcs), registered with the operator through Infobip, supporting text, text-with-PDF, card and carousel formats. This is a distinct library from WhatsApp templates with its own approval workflow — creating, syncing status and deleting an RCS template are separate actions from anything on the WhatsApp template screens.

The compliance angle matters even if you never intend to send RCS deliberately: an approved RCS template is mandatory for traffic to India (+91) and Indonesia (+62). Sends to those country codes without one are blocked before dispatch, regardless of which channel your automation or campaign was actually configured to use. If you have contacts in either country, check the RCS template library exists and is approved before you rely on any broadcast reaching them.

A routine worth keeping

• Check Template health weekly, not only after a rejection or pause notification arrives.
• Treat a yellow rating as an action item, not a warning to note and move past — quality tends to keep sliding once recipients start reacting badly, it rarely self-corrects while volume continues.
• Cross-check Template analytics periodically for library composition — a growing pile of rejected or disabled templates is worth cleaning up even if none of them are currently sending, since it makes the health screen noisier than it needs to be.
• If you send to India or Indonesia, confirm an approved RCS template exists before scaling volume to those markets, rather than discovering the block when a campaign under-delivers.
• When a template is rejected, see Template rejected for the fix-and-resubmit path rather than deleting and starting over, which loses your send history against that template name.

Frequently asked