Skip to content
PROTOTYPE — MOCK DATAFigures are generated fixtures derived from the registry. Not ACF actuals.
Menu (13)
Telesales
CUSTOMER · KPI · LEADING

Consent rateTS-03

4.5% On targetMANUAL
ACTUAL VS PLAN
CONSENT FUNNEL

Where does the dialling actually stop converting?

How much of this is measured: Stage 4 applies TS-05's 1.77% to consented leads. If ACF's ‘leads issued’ denominator is the campaign list rather than consented leads, stages 4–5 move by an order of magnitude. The funnel is built to surface that question, not to hide it (A-27).

VARIANCE TO PLAN — computed in-platform, not in Excel
DEFINITION
Formula
consents ÷ contacted leads
Unit / direction
pct · higher better
Source system
Consent portal ⚠ in no ACF inventory
Refresh
daily_t1
Target
≥ 4%
Target status
From an ACF document
Baseline in context/
4.89% vs 4% target (Apr-26)
OWNERSHIP — two roles, two people (R-G-02)
Metric owner — owns the target and the result
Head of Telesales
Data owner — owns the source system and pipeline
IT System Development

Both proposed by Ikigai and awaiting ACF confirmation (DEC-02).

GUARD METRIC — the check on this number (R-G-06)
QA / compliance call score
TS-08
No data
no series
UNMEASUREDStringeeX recordings○ NOT REPORTEDtarget proposed

Head of Telesales·IT System Development

A headline KPI is resolved with its guard, so the pairing cannot be forgotten by the UI.

COMMENTARY — why the number is what it is
  1. Head of Telesalesperiod 2026-09 · 19 Sep 2026

    Consent rate above target but the source has no owner. Number is keyed by hand until the Consent portal is in the inventory.

Commentary is attached to the metric and period, not to a slide. It survives the month — which is what makes a variance reviewable at the next meeting instead of re-argued. Prototype — read-only fixtures; at fullstack this is the COMMENT table with author identity from AD.