Built on provenance audit v2 · every panel marked by how we'll source it · maximizing data we can stand behind · HMIS connection treated as committed · production latest frozen at c7d14bcf
WHIT
ForKids Housing Crisis Hotline
Last update06/24/2026
ImpactBoard
ExecutiveCOO
Operationalfull detail
Data completionprovenance
live — pulled & proven nowready to source — data we hold / HMIS-confirmed; fills on connection or re-runconditional — needs the linkage build or enumeration confirmReporting window · hotline Sep 2025–Jun 2026 · HMIS enrolled through Jun 2026 · Dashboard v3 · feedback revision · 2026-07-06
Page filtersAll timeFY26FY25Custom…All citiesNorfolkVirginia BeachChesapeake+ 4 moreDesign preview · multi-select · applies to whole page at build
Reach & response · what we can prove today
Families across Hampton Roads reach for help — and WHIT is measuring the demand in full.
89,182
Calls
LIVE · Sep 2025–Jun 2026
63,020
Callers
LIVE · Sep 2025–Jun 2026
1.4
Average calls per caller
LIVE · derived · 89,182 / 63,020
23,118
After hours
LIVE · carried by AI · Sep 2025–Jun 2026
Demand
Calls over time ready · HMIS
Quick rangesAllFY26FY25Custom range…Preview · FY definition confirming with ForKids
Calls over timeHMIS + AI combined · unduplicated · shape illustrative until build
Who is calling
Who is calling — and why ready · HMIS + AI
FiltersHousing status · multi-selectAge group · multi-selectPreview · wired at build
Housing statusconfirmed table
Call purposeconfirm grain
EvictionHMIS
HomelessHMIS
UtilityHMIS
Household sizeHMIS + AI · PLACEHOLDER
1PH
2–3PH
4–5PH
6+PH
UnknownPH
AgeHMIS · PLACEHOLDER
Under 18PH
18–24PH
25–65PH
65+PH
UnknownPH
Read → moved from the Operational page per super-user feedback — purpose, housing status, household size (with unknown), and age groups, with multi-select filtering wired at build.
Read → answered volume is derivable from Vonage now; the abandoned layer needs the Akixi field confirmed in enumeration. Every lost call is a family that didn't reach help.
Capacity · the operating decision
When does demand outrun us?
Daily demand vs capacitycapacity line = modeled · grounding with ForKids or removingready · re-run demand confirm · Akixi capacity
Peak windowre-run
Tue–Thu
11a–3p
After-hoursre-run
31%
overnight/weekend
Capacity sourceconfirm
Akixi agent-state if present (enumeration); ForKids hourly roster as fallback — a near-static input, not a live feed.
Read → demand peaks are sourceable now; the capacity overlay confirms from Akixi agent-state, or a ForKids roster as fallback.
Act today + is it up
Worklist & catch rates
High-need callers
4+ contacts this month
sustained crisis
ready · re-run
Returned within 7 days
first contact didn't hold
via linkage
After-hours, no callback
awaiting a caseworker
confirm
Catch ratesPLACEHOLDER · pending Vonage field confirm
Intake catch ratePH %
All calls catch ratePH %
Transfer catch ratePH %
Intake = answered intake ÷ all intake (Call Result Type). All calls = (answered intake + AI calls) ÷ (all intake + AI calls). Transfer = answered ÷ all, among calls from the AI transfer line.
Read → the 4+ worklist is sourceable now; the three catch rates compute from Vonage once the Call Result Type field is confirmed in the data as delivered.
Page filtersAll timeFY26FY25Custom…Design preview · applies to whole page at build
Throughput
Speed and call timing conditional · Akixi confirm
Service levelAkixi depth
<30s
share answered confirm
p90
longest waits confirm
wait
mean wait confirm
Call-time breakdownring / talk / hold / wrap
Ringconfirm
Talkconfirm
Holdconfirm
Wrapconfirm
Read → these are Akixi telephony-depth fields — represented so the view is complete, flagged to confirm the field exists in enumeration.
Demand timing
When the load hits ready · re-run
MonTueWedThuFriSatSun
12a — 6a — 12p — 6p — 11p · derivable from the timestamps we hold
By day of weekre-run
After-hoursre-run
31%
overnight/weekend
Peakre-run
Tue–Thu
11a–3p
Read → the strongest "ready" band — every call carries a proven timestamp, so timing fills with real values on the next re-run, no HMIS dependency.
AI receptionist
What the automated layer does conditional · confirm
Outcomes
Resolvedconfirm
Escalatedconfirm
Messageconfirm
Why people call
Evictionconfirm
Homelessconfirm
Rent helpconfirm
Read → outcome and intent are AI-derived fields we're assuming exist — enumeration confirms or cuts them.
Caller patterns & identity
Repeat demand, reach, and duplicates
Call-back frequencyre-run
1 callre-run
2–3re-run
4+re-run
Duplicates as datalive · Sep ’25–Jun ’26
27,809
collapsed dupes
26,162
repeat contacts (derived)
Reachlive · Sep ’25–Jun ’26
2,336
out of state
3.7%
outside HR (derived)
Cross-source identity spinelive · proven
HMIS UCID
→
Vonage ref ID
→
AI / MapComm ref ID
→
One account-wide ID space
Verified by UTC-instant + sequential-contiguity proof — the spine that makes dedup work and the future caller-linkage possible.
Read → the dupe/reach/identity figures are live; the frequency split is one re-run from real.
Geography
Where the calls come from ready · re-run
By localitypost-normalization
Norfolkre-run
Virginia Beachre-run
Chesapeakere-run
Portsmouthre-run
Suffolkre-run
Hamptonre-run
Newport Newsre-run
Out of areaPH
Out of state2,336
UnspecifiedPH
Service-area compositionthe trust signal
Hampton Roadsre-run
Out of area · VAre-run
Out of state2,336
Unspecifiedre-run
Read → the trusted base is the HMIS Region field; the AI-extracted city shows only after the normalization delta buckets out-of-area and junk values. Out-of-state (2,336) is live; the rest fills on the re-run.
Read → these tables already exist in forkids_dw (stale at 2022–24). The connection makes them current — strongest "ready to source" band.
Sources
Last data received, by source live
HMIS / WellSkystale
06-15
last record date · freshness under review with the data vendor
Vonagecurrent
06-24
last record date
AI assistantcurrent
06-24
last record date
Why → moved from the page header per super-user feedback — the header now carries one date: the most recent data point across all sources.
Source freshness
The monitoring layer is the feature live
HMIS / WellSky06-15
Vonage / Akixi06-24
AI Receptionist06-24
10 days
HMIS staleness the Sentinel caught automatically
Why → every render-test passed while HMIS sat 10 days stale; the Sentinel flagged it anyway.
Source volume over time
Each feed's contribution ready · re-run
Records per month by sourceHMIS · Vonage · AI
Why → shows when a source lags or surges — derivable from records we already hold.
Record lineage
Raw to published, with the counts live · Sep 2025–Jun 2026
Raw
116,991
93,873 HMIS + 23,118 AI
→
Deduped
89,182
27,809 collapsed
→
Enriched
23,118
GPT-5-nano · US-pinned
→
Published
63,020
unique callers · sha-verified
Why → resolves "116,991 vs 89,182" — two counts, two bases, both labeled.
Drill to record
The call-level detail behind every chart build · query layer
Records exist and are published. An interactive filter / query / export view is a build — not in this version. Sample below shows the structure.
UCID
Timestamp (UTC)
Source
Purpose
Region
Status
UC-####
2026-06-24 02:14:07
AI
Eviction
Norfolk
At risk
UC-####
2026-06-24 01:58:33
Vonage
Rent help
Chesapeake
Doubled-up
UC-####
2026-06-23 23:41:12
HMIS
Homeless
Portsmouth
Homeless
Why → the records are live and published; an interactive drill / query / export layer is a separate build, scoped for v2, not committed in this dashboard.
Field completeness
How populated each field is confirm · enumeration · through Jun 2026
Call date/time~100%
Regionconfirm
Housing statusconfirm
Demographicsconfirm
Housing outcomelinkage
Why → real fill rates land from David's enumeration; the outcome bar stays low until the linkage build.
System reliability
Service health
Feed delivery · 30 daysready · re-run
received no data
Why → feed delivery health is live — each vendor’s last 30 days of receipts, straight from the re-run.
Integrity
Provenance & protection live
Verified publish
Live = exactly what passed proof. c7d14bcf…
Residency
US-pinned; raw PII never leaves region.
PII
Scrubbed pre-publish; sources git-ignored.
Rollback
Snapshot 2d5b3cc…; one-step restore.
Why → the SOC-2 / procurement story a reviewer can check, not take on faith.
