Consent-capture sprint
Six weeks of script changes and agent coaching should lift consent capture.
Recorded 2026-06-02, before the window opened on 2026-06-15. A hypothesis written afterwards is a description, and the difference matters when the result is read.
1 reported point inside the campaign and 2 in the baseline; 2 are needed in each. This series reports monthly, so a window this short cannot support a before-and-after at all. The refusal is the finding: it is not that the campaign failed, it is that the platform cannot tell you either way.
Campaign window 2026-06-15 → 2026-07-31 against a baseline of the same length immediately before it, 2026-04-29 → 2026-06-14. The baseline is not chosen — it is derived from the window, so it cannot be picked after the result is known.
| METRIC | BASELINE MEAN | WINDOW MEAN | CHANGE | GOAL |
|---|---|---|---|---|
| FPD5+ on telesales-originated vintage TS-09 · lower is better | 2.6% 2 pts | 2.7% 1 pts | +0.13pp moved the wrong way | 2.5% |
This campaign declares no guard, and its goal metric carries none in the registry. Where a metric does carry one, the campaign cannot be created without it.
- 1 other campaign ran over part of this window: DR readiness, spring.
- The window mean is an average of 1 points. One unusual month moves it materially.
- A movement that coincides with a campaign is not a movement caused by it. This platform reports the coincidence and does not attribute it — attribution needs a control group, and there is not one.
The goal of 2.5 is the campaign’s, not the registry’s. TS-09’s target is still whatever the registry says it is, its threshold is unchanged, and closing this campaign wrote nothing to either. R-G-16.