Manor
HomeScoreboard
Work
Needs meNo person 48h+VisitsVideosMy listApprovalsTurnoverRepliesCallsPromisesHotFollow-upQueueOpportunitiesLeadsLost auditDesk
Floor
ShowroomAppointmentsScheduleDeliveries
Numbers
SourcesRepsUsagePerformanceMetricsMoneyPricingLease
Machine
JobsAgentsWatcherHealthControlAI Control
More
ToolsTrainingHot dealsService deskReportsTo-doBoard

Success metrics

The baseline for how we will know the platform is working: response time, unanswered, re-engaged, appointments, deals, conversion, time saved, reliability, opportunities, what happens after a visit.
Data as of Baseline build 6:50 AM CT.
Last 14 days is 2026-11-07 to 2026-11-20 (today and the 13 days before it), Month to date is 2026-11-01 to 2026-11-20; all Central days. Built 6:50 AM CT, rebuilt every morning at 6:50 AM. A dot means the column does not apply; no data means it could not be counted honestly. Anything marked assumption or definition proposed rests on a rule Will has not signed off.

1. Customer response time: Customer message to first reply measured Replies

MeasureLast 14 daysMonth to dateRight now
Machine alone: median33.2 min2.6 min·
Machine alone: slowest 10% (p90)272 min73 min·
Machine alone: replies counted (n)915·
Machine draft, a person approved: medianno datano data·
Machine draft, a person approved: slowest 10% (p90)no datano data·
Machine draft, a person approved: replies counted (n)00·
A person typed it: median9 min12.9 min·
A person typed it: slowest 10% (p90)122 min145.3 min·
A person typed it: replies counted (n)4978·
Machine alone, message arrived while store open: median17.7 min2.3 min·
Person, message arrived while store open: median13.8 min12.9 min·
Everyone: answered within 15 minutes53.4%54.8%·
Everyone: answered within 60 minutes79.3%81.7%·
Answered after more than 24 hours (left out of the medians)36·
Customers whose latest message has no reply yet··4
How this is counted, and where it comes from

Definition. For each customer, minutes from their latest message to the first reply on the thread (the Reply check's lastInboundAt to answeredAt, the same pairs the Home strip's Median uses). Who answered: machine alone = the auto-responder or System; machine draft approved = the approvals sender (a person pressed approve); person = anyone else, a rep or manager typing (scripts/lib/machine-reply.ts rule: a reply from the shared login that lines up within 2 minutes with a machine send is the machine). Windowed by the day it was answered. Replies later than 24 hours are counted separately, not in the medians (a reply days later is not an answer to that message). Clock minutes, nights and Sundays included; the 'store open' rows keep only messages that arrived inside sales hours (config/store-hours.json).

Read with care.

  • One pair per customer: if a customer wrote twice, only the newer message is on file, so this is a sample, not every message. Pairs are saved in the daily file as they are seen, so month to date keeps them after a customer writes again.
  • The Reply check reads VinSolutions about every 2 hours; replies typed by a rep inside VinSolutions are in it, texts sent outside VinSolutions are not.
  • Medians over fewer than 10 are noise; n is shown. A p90 of a small n is just its slowest few.

Source files.

  • memory/reply-verify-latest.json as of Nov 19, 1:23 PM CT
  • memory/message-log.json as of Nov 19, 9:41 PM CT
  • data/store/metrics-daily.json as of 6:50 AM CT

2. Overdue and unanswered: Unanswered messages and overdue follow-ups measured Turnover

MeasureLast 14 daysMonth to dateRight now
Customers who wrote us83117·
Of those, latest message still has no reply44·
Average per day: customers waiting with no reply0.30.2·
Overdue: arrived in store hours, no reply within 60 min (proposed standard)1520·
Held replies that expired with no person answering1013·
Promises and callbacks due, still not done4357·
No reply yet, all dates··4
Promises and callbacks overdue now··69

By day (last 14 days)

DateCustomers who wroteLatest message, no reply yetOverdue (store hours, 60+ min)Held replies expiredPromises due, not done
2026-11-0740000
2026-11-0810010
2026-11-09180202
2026-11-1090104
2026-11-1150014
2026-11-12110324
2026-11-1360111
2026-11-14150122
2026-11-1500002
2026-11-16130105
2026-11-17100216
2026-11-1892206
2026-11-19102225
2026-11-2020002
How this is counted, and where it comes from

Definition. No reply yet = a customer whose latest message the Reply check shows nobody (person or machine) answered, and we have not texted since (the Home strip's 'No reply'). Wrote us = distinct customers with a message in the window (reply ledger + Reply check). Expired holds = customer replies the machine held for a person that ran out of time with no person answering (/turnover 'Expired, still unanswered'), counted on the day they expired. Overdue (PROPOSED standard, 60 minutes) = a message that arrived while the store was open and was answered later than that, or is still unanswered. Promises due and not done = commitments, video promises and missed-call callbacks whose due time (/promises rule: 4 hours, or noon next business day) fell in the window and are not marked fulfilled.

Read with care.

  • No reply yet is a snapshot of who is waiting now, grouped by the day they wrote; a customer who wrote twice is counted once, on the newer day.
  • /turnover only looks back 14 days, so Expired holds for a long month come from the saved daily file (starts when this job first ran).
  • Missed-call callbacks are most of the promises count and are never closed by the customer, so that number only falls when a person marks the call.

Source files.

  • memory/reply-verify-latest.json as of Nov 19, 1:23 PM CT
  • memory/reply-ledger.jsonl as of 6:33 AM CT
  • memory/message-log.json as of Nov 19, 9:41 PM CT
  • memory/pending-approvals.json as of 12:59 AM CT
  • memory/draft-class-ledger.jsonl as of Nov 19, 1:43 PM CT
  • memory/commitments.json as of Nov 19, 5:15 PM CT
  • memory/video-promises.json as of Nov 19, 7:00 PM CT
  • memory/missed-call-callbacks.json as of Nov 19, 7:25 PM CT

3. Re-engaged opportunities: Customers who wrote back after 14 or more quiet days measured Replies

MeasureLast 14 daysMonth to date
Customers re-engaged4664·
   after our outreach (we sent in the 72 hours before)2738·
   on their own1926·
   first reply ever on an old lead2028·
   still open (not closed lost, sold or dead)3547·
Left out: a new lead (wrote within 2 days of the lead being created)119181·
Left out: nothing to measure the quiet from01·
How this is counted, and where it comes from

Definition. A customer counts when they write us and the gap since their previous message from them (any text or email we know of: the reply ledger since 8/19, the Reply check, and the last 20 notes on the lead) is 14 days or more. With no earlier message at all, the gap is measured from the day the lead was created ('first reply ever'). A message within 2 days of the lead being created is the new lead itself and is left out. Counted once per customer per window. 'After our outreach' = we sent them something in the 72 hours before they wrote; the rest wrote on their own. 'Still open' leaves out customers the Reply check has since closed as lost, sold or dead.

Read with care.

  • Quiet means the customer was silent; we may have been texting them the whole time.
  • A customer with no message on file and no lead row cannot be measured and is skipped (count shown).
  • Out-of-window history is only as deep as the lead's last 20 notes plus the ledger from 8/19, so a quiet stretch can be overstated for a customer whose older messages fell off.

Source files.

  • memory/reply-ledger.jsonl as of 6:33 AM CT
  • memory/reply-verify-latest.json as of Nov 19, 1:23 PM CT
  • data/store/leads.json (Notes Summary, createdTime) as of 6:48 AM CT
  • memory/message-log.json as of Nov 19, 9:41 PM CT

4. Appointments: Appointments set and completed measured Appointments

MeasureLast 14 daysMonth to date
Appointments set (dated in the window)7496·
Completed (customer came)4662·
Missed2025·
Cancelled67·
Still set or confirmed22·
Other status (rescheduled)00·
Show rate: completed / (completed + missed)69.7%71.3%·
Appointments the machine bookedno datano data·
How this is counted, and where it comes from

Definition. Appointments dated in the window, from the VinSolutions appointment report (scripts/lib/appointments-truth.ts, the same reader Home, /appointments and /reps use). Set = every appointment dated in the window, any status. Completed = VinSolutions status COMPLETED (the customer came). Missed = MISSED. Show rate = completed / (completed + missed): appointments still open or cancelled are left out of it.

Read with care.

  • The feed keeps one appointment per customer (their latest) over a trailing 30 days, so a customer with two appointments in the window counts once.
  • RESCHEDULED appointments are not a status the readers count (shown as 'other').
  • The feed does not say who booked the appointment, so how many the machine booked is not measurable here (see the last row).

Source files.

  • data/store/vs-appointments.json as of 6:05 AM CT

5. Active deals and stalled negotiations: Deals being worked, and the ones gone quiet definition proposed Opportunities

MeasureLast 14 daysMonth to dateRight now
Active deals (What needs me, state Deal)··34
Stalled: a deal with no touch in 48 hours··17
Touched in the last 48 hours··17
Stalled share of active deals··50%
Compare: queue 'live negotiation' bucket··1
Compare: queue 'stalled deal' bucket (no outbound in 7 days)··32
How this is counted, and where it comes from

Definition. A deal is a customer with a price, payment or finance line in the notes this week, a live negotiation in the opportunity queue, a stalled deal that has written in the last 14 days, a showroom desking note in the last 2 days, or a credit app a person has since touched. Counted once per customer; someone more urgent (in the showroom, a reply to send, a hand-off, numbers owed, an appointment) shows in that state instead. Stalled means no touch, a message either way or a note, in 48 hours. Live, read when the page opens.

Read with care.

  • The saved daily file still holds its own older count (55), from a different rule. This page shows the engine's number so /needs-me, the Showroom and /metrics agree.
  • Notes are synced into the lead store about hourly, so a touch in the last hour can be missing.
  • A machine cadence text counts as a touch. If a person's touch is the one that matters, the stalled number goes up; that is the open question.
  • The queue's own 'stalled deal' bucket is a different, looser rule (no outbound in 7 days, any open lead) and is shown for comparison only.

Source files.

  • data/store/leads.json (Notes Summary, status fields) as of 6:48 AM CT
  • memory/message-log.json as of Nov 19, 9:41 PM CT
  • data/store/vs-appointments.json as of 6:05 AM CT
  • data/store/vs-sold.json as of 6:05 AM CT
  • memory/master-queue.json as of Nov 19, 8:42 PM CT
  • live: the What needs me engine (scripts/lib/needs-me.ts), the same object /needs-me and the Showroom read

6. Lead to sale conversion: Lead to sale by source, last 90 days measured Sources

MeasureLast 14 daysMonth to dateRight now
Leads (2026-08-23 to 2026-11-20)··1,627
Appointments set··378
Appointments shown··253
Sold··279
Lead to sale, all sources··17.1%
Units sold (Axcessa retail + lease, date sold)3038·

By source (90 days)

SourceLeadsAppointmentsShownSoldLead to sale %
Referral / repeat32766527322.3
Phone-up228100715725
Walk-in / drive-by19043235528.9
Credit-app tools17140303721.6
TrueCar16510442.4
Dealer site / Ford Direct / OEM16150332213.7
CarGurus11115898.1
AutoTrader8221131113.4
VinCue trade tools69201368.7
Carfax551100
Facebook / chat439549.3
Other253014
How this is counted, and where it comes from

Definition. The /sources report's own 90-day window (scripts/lead-source-report.ts buildReport): leads by source group, and how many were sold. A lead counts as sold if VinSolutions says Sold, or the buyer's name is on an Axcessa retail/lease delivery dated on or after the lead (120-day cap), or the VinSolutions sold feed has the same customer. Lead to sale = sold / leads. Credit-app tool leads are folded into where the customer really came from when the lead type says so. Ford ICI list imports and cross-store transfers are left out. Units sold (window columns) = Axcessa retail + lease rows by date sold.

Read with care.

  • Lead data pulled 2026-11-19T13:54:15.766Z.
  • The lead pull (VinSolutions reporting API) refreshes weekly, Mondays; the report says when. Leads from the last few weeks have not had time to close, so the newest sources look worse than they are.
  • Matching a delivery to a lead is by buyer name, so a buyer who used a different name on the lead is missed.

Source files.

  • data/store/lead-source-rows.json as of Nov 19, 7:54 AM CT
  • data/store/axcessa-cardeals.json as of Nov 19, 12:22 PM CT
  • data/store/vs-sold.json as of 6:05 AM CT

7. Manager time saved: Replies the machine handled without a person assumption Agents

MeasureLast 14 daysMonth to date
Replies the machine sent on its own2140·
Estimated manager hours saved (x 4 min, assumed)1.4 h2.7 h·
Machine drafts a person approved and sent99·
Sent by a person through desk-send120134·
All logged sends (any script)662951·
How this is counted, and where it comes from

Definition. Machine-handled replies = texts and emails the auto-responder sent on its own to a customer's message (message log, script vin-auto-responder; the Home strip's 'Auto-reply'). Time saved = those replies x 4 minutes. THE 4 MINUTES IS AN ASSUMPTION (a manager reading the message, looking up the vehicle and typing an answer), not a measurement; change MINUTES_PER_REPLY in scripts/metrics-baseline.ts.

Read with care.

  • Only replies the machine sent alone count. Drafts a person approved are shown but not counted as saved.
  • Texts a rep types inside VinSolutions are not in the message log, so the machine's share of all replies is overstated.
  • Counts come from the saved daily file once the message log has rolled past a date.

Source files.

  • memory/message-log.json as of Nov 19, 9:41 PM CT
  • data/store/metrics-daily.json as of 6:50 AM CT

8. Reliability and automation: Scheduler, feeds and the dashboard measured Jobs

MeasureLast 14 daysMonth to dateRight now
Job runs35,52450,508·
Failed runs692738·
Scheduler failure rate1.9%1.5%·
Timeouts (killed for running too long)3941·
Silent-job alerts sent to Will1316·
Stale-feed findings (health check, per feed per day)2339·
Dashboard restarts by the watchdog615·
Feeds stale or unreadable now (of 22 with a cadence)··3
Jobs in a failure state now (some may be paused on purpose)··35
Health check: checks failing now··3
Auto-responder: answered on its own2140·
Auto-responder: drafted for a person (held)226303·
Auto-responder: stopped by a safety gate4860·

Jobs that failed most, last 14 days

JobFailed runs
vin-first-touch259
vin-auto-responder201
credit-app-clock37
vs-daily-feeds31
covideo-rep-activity25
grid-delta-run15

By day (last 14 days)

DateJob runsFailedTimeoutsSilent-job alertsStale-feed findingsDashboard restarts
2026-11-072,97650010
2026-11-081,86242030
2026-11-092,83130020
2026-11-102,80942022
2026-11-112,67320021
2026-11-122,69430001
2026-11-132,777140031
2026-11-142,88070031
2026-11-151,91200030
2026-11-162,894615130
2026-11-172,93970000
2026-11-182,926170010
2026-11-192,951563301200
2026-11-2040020000
How this is counted, and where it comes from

Definition. Job runs = 'Finished:' lines in the scheduler log. Failure = a non-zero exit, except exits the failstate line calls a known expected outcome. Failure % = failures / runs. Timeouts = jobs the scheduler killed for running too long. Silent-job alerts = 'JOB SILENT' alerts the heartbeat watchdog sent Will (a job missed its own cadence; the watchdog sends at most one per job per cooldown). Stale-feed checks = distinct feeds the health check listed as stale or out of date, counted once per check per day. Dashboard restarts = times logs/watchdog.log found the dashboard down and restarted it (includes restarts while code is being deployed). Feeds stale now = Home's own data stamps (dashboard/views/stamp.ts) older than their cadence or unreadable.

Read with care.

  • A job that exits 0 without doing its work is not a failure here. Health-check findings cover the known cases.
  • The scheduler log is archived about 15 days back; older days come from the saved daily file once this job has run for them.
  • Silent-job alerts have a cooldown, so a job silent for a day is one alert, not many.

Source files.

  • logs/scheduler.log as of 6:50 AM CT
  • logs/archive/scheduler-*.log.gz
  • logs/heartbeat-watchdog.log as of 6:28 AM CT
  • logs/watchdog.log as of Nov 14, 3:31 PM CT
  • memory/scheduler-failstate.json as of 6:45 AM CT
  • memory/health-status.json as of Nov 19, 6:50 PM CT
  • memory/responder-decisions.jsonl as of 6:49 AM CT
  • data/store/metrics-daily.json as of 6:50 AM CT

9. Additional opportunities identified: Opportunities the system found, and what was done with them measured Calls

MeasureLast 14 daysMonth to dateRight now
Missed-call callers recorded108178·
   acted on (called, reached, or phone-up created)47·
   still open104171·
Promises recorded (machine commitments + video promises)4664·
   acted on (marked fulfilled)1320·
   overdue and open2424·
Queue: stalled deals to re-engage··32
Queue: missed appointments to reschedule··34
Queue: new leads with no first touch yet··7
Queue: live negotiations needing a person··1
Queue candidates acted onno datano data·
How this is counted, and where it comes from

Definition. Missed-call callers = numbers that called the sales line and got no one (CallRevu), first missed in the window, junk excluded; acted on = a person marked it called, reached, or a phone-up was created. Promises = commitments the machine made and video promises found in the thread, made in the window; acted on = marked fulfilled. Queue candidates = the opportunity queue's buckets right now (stalled deals to re-engage, missed appointments to reschedule, new leads with no first touch); the queue keeps no history of what was acted on.

Read with care.

  • Opportunities are counted when the system first records them, not when they would have closed.
  • 'Acted on' for the queue is not recorded anywhere, so it is no data.
  • A missed call from a number already in the CRM may be a customer we were already working.

Source files.

  • memory/missed-call-callbacks.json as of Nov 19, 7:25 PM CT
  • memory/commitments.json as of Nov 19, 5:15 PM CT
  • memory/video-promises.json as of Nov 19, 7:00 PM CT
  • memory/master-queue.json as of Nov 19, 8:42 PM CT

10. After the visit: Customers who came: sold within 7 days, and followed up after a visit with no sale definition proposed

MeasureLast 14 daysMonth to date
Customers who came (appointment completed), at least 3 days ago3955·
   sold within 7 days2532·
    on the same day as the appointment2532·
    on a later day00·
   no sale on record1423·
Sold within 7 days, share of those who came64.1%58.2%·
Bought on a later day, share of those who did not buy that day0%0%·
Showroom visits ended 24+ hours ago, no sale (judged)3047·
   person-typed call, text or email within 24 hours of the visit ending1427·
Follow-up within 24 hours, share of those visits46.7%57.4%·

Same measures over the last 30 days (the whole appointment feed)

MeasureLast 30 days
Customers who came (appointment completed), at least 3 days ago100
sold within 7 days53
on the same day as the appointment53
on a later day0
no sale on record47
Sold within 7 days, share of those who came (%)53
Bought on a later day, share of those who did not buy that day (%)0
Showroom visits ended 24+ hours ago, no sale (judged)66
person-typed call, text or email within 24 hours of the visit ending33
Follow-up within 24 hours, share of those visits (%)50
How this is counted, and where it comes from

Definition. Sold from shown: appointments VinSolutions marks COMPLETED on a day in the window and at least 3 days old (time to close), matched to a sale from that day through 7 days later: an Axcessa retail, lease or fleet delivery matched by buyer name, or the VinSolutions sold feed matched by customer id or name. 'Same day' = a sale record dated the day of the appointment in either file (the other file may date the same deal a few days later, a marking or delivery lag, which is not a second sale); 'later day' = the only sale records are 1 to 7 days after. Follow-up: each showroom visit the reps logged (data/store/showroom-visits) that ended 24 or more hours ago with no sale that day, the customer in the lead store, not a buyer or opt-out, and the lead re-read after those 24 hours; followed = a call, text or email typed by a person within 24 hours of the visit ending (machine sends left out; the same reader as /needs-me visits, scripts/lib/follow-through.ts buildVisits). Both are proposed definitions (baseline.md measures 4 and 5, 10/21/26); the follow-up denominator is the /needs-me visits rule, which leaves out buyers and opt-outs, so it is smaller than baseline.md's first reading (every visit not flagged sold that day) and the two should not be compared.

Read with care.

  • Same-day sales include customers who came to pick up a car already sold (their appointment is the delivery), so the sold share overstates how many new shoppers buy. The useful figure is the 'later day' share of those who did not buy that day.
  • A buyer whose Axcessa name differs from the appointment name is missed (understates). Sales after the newest Axcessa file are not in yet, which is why the last 3 days of appointments are left out.
  • A touch is read from VinSolutions note lines (the newest 20 per lead); a call made on a personal phone is invisible, and a visit nobody logged is not counted. Small windows swing: read n beside every percentage.
  • The appointment feed holds one appointment per customer (their latest) over a trailing 30 days.

Source files.

  • data/store/vs-appointments.json as of 6:05 AM CT
  • data/store/axcessa-cardeals.json as of Nov 19, 12:22 PM CT
  • data/store/vs-sold.json as of 6:05 AM CT
  • data/store/showroom-visits/*.json
  • data/store/leads.json as of 6:48 AM CT