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

Application → disbursement conversionTS-06

73.0% No targetMANAGED
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).

DEFINITION
Formula
disbursed ÷ applications
Unit / direction
pct · higher better
Source system
LOOMS → T24
Refresh
daily_t1
Target
TBC
Target status
PROPOSED BY IKIGAI (T-01)
Baseline in context/
59.4%
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 Planning

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

GUARD METRIC — the check on this number (R-G-06)
FPD5+ on telesales-originated vintage
TS-09
2.6%
-1.4pp vs target 4.0%
MANUALDWH⏱ T+1

Head of Telesales·IT System Planning

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

No commentary recorded for this metric. A red tile with no explanation is the failure mode the current monthly pack already has.

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.