CollectiQ Analytics

Portfolio pulse

Total collection MTD

—

Total LAN Book

—

as-of period end

Total exposure POS

—

Total resolution A/c paid

—

accounts with ≥1 payment

Resolution % Of LAN

—

paid accounts ÷ book

How hard we're reaching out

Total attempts

—

Calls + messages, all channels

Unique numbers attempted

—

Distinct phone numbers touched

Total connected

—

Call connects + message deliveries

Unique connected

—

Distinct numbers with ≥1 connect

Contactability

—

Unique connected ÷ unique attempted (calls)

Dead attempts

—

Not connected / not delivered

Call intensity

—

Call attempts per account on book

Attempt intensity

—

All-channel touches per account

What the outreach produced

Answered (RPC proxy)

—

Answered-type dispositions; true RPC needs vendor taxonomy

PTP

—

Bot analysis + IVR "will pay" keypress

PTP → resolution

N/A

Needs PTP↔payment link (phone→LAN)

Broken PTP

N/A

Needs structured PTP (amount/date)

PTP follow-up intensity

N/A

Needs PTP case tracking

From first touch to money recovered Period totals · resolution not yet PTP-linked

How conversations ended

Channel performance

One view: effort in, results out Green cell = best in column

Field row shows no feed: field-visit data exists in production (confirmed via the company's Metabase Central_Dashboard — visit dispositions are tracked there) but isn't in the S3 pipeline this dashboard ingests from yet; wiring it in is an access/integration task, not a new data-collection ask. RPC is an answered-type proxy until vendors send a right-party taxonomy. Resolution isn't broken out per channel yet — it needs the phone→LAN bridge (P1-1) to link a payment back to the call that produced it.

Timing insights

Best hours to reach customers Connect ÷ attempts

Darker = better. Live connect rate by hour, per calling channel, for the selected period.

When WhatsApp actually gets read

Delivered as % of sent Read as % of sent

Performance by delinquency stage

Which channel wins at each stage PTP per connect · ★ best in stage · needs phone→LAN link for full coverage

Coverage note: per-bucket attribution works where a LAN key exists (bajaj via per_mob, dialer & SMS via LAN code). Calls that can't be tied to an account appear under the book's default stage.

Daily performance

Money collected each day

Accounts resolved each day

Reach to promise: how outreach converts

Connected % of attempts PTP % of connected

Accounts curing / slipping daily Roll rates

Not available yet — daily roll-back / roll-forward needs the bucket-migration pipeline (reconstruction from lead_history snapshots is planned; no new source data required).

Daily channel & bucket trends