Deliverability is not one score. It is the result of a sender's identity, consent, message category, recipient timing, channel route, and the feedback that arrives after each send. In 2026, teams that treat those inputs as one operating loop can spot a weak route or a tired audience before a campaign compounds the problem.
This almanac is a working guide for that loop in Devotel Orbit. It brings together the WhatsApp quality-rating wave, recipient-local SMS quiet hours, and Insights export guide so the same review covers channel policy, send timing, and evidence.
The 2026 deliverability picture
Start with four questions for every channel and campaign:
- Can this recipient receive this message? Confirm consent, suppression state, and any channel-specific eligibility before scheduling.
- Is this the right route? A delivery attempt, a carrier acceptance, and a recipient-visible message are different events. Compare outcomes by channel, sender, destination, and route rather than relying on a single total.
- Is this the right time? A message that is legal and consented can still create complaints when it arrives during a recipient's night. Evaluate send windows in the recipient's local time.
- Can the team explain the result? Keep message-level evidence and aggregate trends available to the people who make routing and campaign decisions.
The dashboard is where operators act; exports are where teams compare periods, investigate a route, and share a dated snapshot with Finance or BI. Use both surfaces together instead of treating an export as a replacement for live operational review.
WhatsApp quality ratings and template pauses
Meta's quality rating is a per-phone-number signal based on recent recipient feedback. Blocks, reports, and negative responses can move a number's rating even when another number in the same WABA is healthy. A green number is not permission to send every message at every volume; it is a snapshot of how recent traffic was received.
Marketing templates add another boundary. Meta can pause an individual template when its feedback deteriorates. The pause does not remove the rest of a template library, and retrying the same copy does not repair the underlying signal. Treat a pause as a prompt to examine the offer, opening line, audience, consent record, and frequency. Revise the template, submit the revision for review, then restart with a smaller and more deliberate audience.
The WhatsApp quality-rating explainer covers the rating, per-template pause, and per-recipient cap mechanics in detail. On Orbit, keep the review practical:
- Separate utility, authentication, and marketing intent when you author templates.
- Use recorded consent and frequency controls to keep an expected message from becoming a surprise.
- Pace a new or revised campaign so feedback is visible before the full audience receives it.
- Compare status and feedback by sender and template, not only by workspace total.
Meta owns the thresholds. Your copy, audience, cadence, and consent posture determine the traffic those thresholds measure.
Quiet hours by channel
A quiet-hours policy is a routing rule, not just a calendar reminder. It should answer which channel may send, which local-time window applies, and what happens to a message that reaches a blocked period. Keep the policy explicit per channel because an acceptable window for email may be inappropriate for SMS, and a WhatsApp marketing send may have different template and session constraints.
For SMS, evaluate the recipient's local time rather than the sender's clock or a fixed UTC offset. Daylight-saving changes make a UTC-pinned timer drift by an hour. The SMS send-time and quiet-hours guide shows the failure mode and the recipient-local alternative. When a send is blocked, defer it to the next allowed opening if the tenant's policy permits deferral; do not hide the decision as a generic delivery failure.
Use a per-channel review like this:
| Channel | Review before scheduling | Evidence after sending |
|---|---|---|
| SMS | Consent, destination-local quiet hours, sender registration, frequency | Accepted, delivered, failed, deferred, and opt-out outcomes by route |
| Template category, quality rating, pause state, recipient cap, consent | Template and sender feedback, delivery status, replies, and blocks | |
| Sending identity, suppression state, recipient engagement, message purpose | Delivery, bounce, complaint, and engagement trends by identity |
If the same audience receives messages through multiple channels, coordinate their cadence. A quiet SMS window should not simply push a promotional message into another channel at the same moment. Record the fallback route and its own consent and timing checks.
Make Insights exports part of the operating rhythm
A deliverability review needs more than a headline delivery percentage. Export the smallest useful slice from Insights → Reports, Insights → Logs, or Insights → Analytics, then compare it with the campaign's audience and policy.
- Insights → Logs gives the message-level view for checking direction, destination, status, timestamp, route, and cost.
- Insights → Reports gives a report-level view for channel performance, delivery, spend, and campaign comparisons.
- Insights → Analytics gives the period-level totals and channel mix that show whether a local problem is becoming a workspace trend.
The Insights export guide explains how to move those CSV snapshots into Power BI, Looker, or Tableau. Preserve the export date and selected range with the file so a later review knows exactly which population it represents. Keep phone numbers as text and timestamps in the operator's timezone when loading the file; otherwise a spreadsheet or BI tool can change the values before the investigation begins.
A useful weekly comparison has three levels:
- Workspace: total attempted, accepted, delivered, failed, deferred, and opted out.
- Channel and route: the same outcomes split by channel, sender, destination, and provider route where available.
- Message and recipient cohort: template or campaign, send-time band, country or region, and new versus established recipients.
This shape helps distinguish an audience problem from a route problem. If one sender degrades while another remains stable, inspect the sender and its traffic. If every sender degrades for one destination, inspect route status, registration, or destination conditions. If failures cluster around one template or time band, change the message or timing before changing infrastructure.
A practical deliverability review
Run this review before a high-volume campaign and again after its first meaningful sample:
- Define the audience. Confirm consent, suppression, destination eligibility, and the expected message category.
- Set the route. Choose the channel and sender that match the recipient and purpose. Document any fallback channel instead of allowing an unexamined fallback.
- Set the window. Apply each channel's quiet-hours policy against recipient-local time. Check a DST transition when the campaign spans a seasonal clock change.
- Stage the message. For WhatsApp, confirm template approval and quality state. For SMS and email, check the sending identity and category-specific requirements.
- Send a measured sample. Watch delivery, deferral, bounce, complaint, block, and reply signals before expanding the audience.
- Export the evidence. Save the relevant Logs or Reports export with its date range. Use Analytics for the workspace trend, not as a substitute for message-level diagnosis.
- Change one lever. If the result is weak, adjust audience, content, timing, or route one at a time so the next export can show what helped.
A deliverability program is working when the team can answer not only “what percentage delivered?” but also “which audience, on which channel, at what local time, with which message, and what will we change next?”
Frequently asked questions
Is deliverability the same as a delivered status?
No. A delivered status is one event in a channel's lifecycle. Deliverability review also considers consent, route acceptance, deferrals, bounces, complaints, blocks, replies, and channel-specific quality signals.
Should every channel use the same quiet-hours window?
No. Set windows per channel and evaluate them against the recipient's local time. A shared audience still needs coordinated frequency and consent checks when messages move between channels.
What should I do when a WhatsApp template is paused?
Stop using the paused copy, inspect its audience and feedback, revise it, resubmit it for review, and restart with a smaller cohort after approval. The quality rating and template pause guide explains the sequence and its limits.
Which Orbit export should I start with?
Use Insights → Logs when you need to explain individual outcomes, Insights → Reports for a channel or campaign comparison, and Insights → Analytics for a period-level trend. Export the narrowest view that answers the question.
How often should I review deliverability?
Review before a large campaign, after its first measured sample, and on a regular cadence that matches your volume. High-volume teams benefit from weekly route and channel comparisons; lower-volume teams can use a monthly trend plus a review after any complaint or quality change.