Compliance Health Score — The 0–100 read-only posture score carriers can infer from your traffic
What is Compliance Health Score?
A compliance health score is a 0–100 read-only rollup of the signals a carrier can observe about your messaging traffic — consent coverage, opt-out velocity, inbound STOP-reply rate, and carrier rejection rate — computed per organization, per sending number, and per campaign. The score exists so a sender reads the same pre-carrier warning before the carrier acts, and it carries no enforcement power: nothing in the surface blocks a send, suppresses a contact, or gates traffic. It is early-warning telemetry only; what you do with the signal stays your call.
More detail
The score blends four weighted factors: consent coverage (30%) as recipientsContacted vs recipientsWithConsent, opt-out velocity (15%) as new opt-outs per 1,000 sent, STOP-reply rate (25%) as inbound STOP as a share of sent, and carrier rejection (30%) as failed/undelivered as a share of sent. A factor with insufficient data is excluded, and the weights re-normalize — a critical factor floors the band at at_risk either way.
Each response returns a score, a band (healthy 85–100, watch 70–84, at_risk 50–69, critical 0–49, unknown when there is no traffic to evaluate), a per-factor status breakdown, a warnings[] array ordered most-severe first, and the raw signal counts behind every factor so you can confirm the math before changing anything.
The three endpoints (GET /compliance/health, /compliance/health/numbers, /compliance/health/campaigns) satisfy the same contract as the other tenant-owned compliance surfaces: emitting the posture, never acting on it. The alerting on band transitions, the warning thresholds, and the remediation are decisions the tenant configures and owns.
Frequently asked
- What is a compliance health score?
- A 0–100 read-only rollup of four carrier-visible messaging signals (consent coverage, opt-out velocity, STOP-reply rate, carrier rejections), computed per organization, per sender number, and per campaign. It tells you which scope is about to draw carrier attention before the traffic actually degrades, with no enforcement power attached.
- Does a low compliance health score block my sends?
- No — the surface is strictly read-only. A low score is an advisory signal with a recommendation, and nothing in the platform acts on it without you. Alerts, thresholds, and any remediation are tenant-owned decisions you configure.
- Why is my score unknown instead of a percentage?
- Every factor reported insufficient_data — usually a sender or campaign with no traffic in the polled window, or a window too narrow for a brand new sender. It is a no-data state, not a failing grade.
- Which factor moves first when a list import lands?
- Usually consent coverage: a large import may lower the recipients-with-consent share before the other factors catch up. The raw signals block in the API response shows recipientsContacted rising against recipientsWithConsent, which is how that drift reads before it becomes a warning.
See also
Build it on Orbit
Voice, messaging, email, video, and AI agents on one platform and one pay-as-you-go bill. Start free — no credit card required.