Cases · Case 01 · Auto Pivdenny · DEALER · KYIV
Case study · Drawing G2-026 · Auto PivdennySheet 01 / 04

From 52-minute first reply to 14 seconds — used-car dealership · Kyiv

Drawn by V. K. · Auspex Co.Pilot Q1 2024 · in service since
Client Auto Pivdenny
Vertical Used-car dealership
Size 6 yards · 38 staff
Module M-01 Lead Hunter
Pilot 2024-02-12 → 2024-02-26
Case №
P-01
In service · 28 mo.
§ 01The number in the contract — and the four around it
Median first reply
14sec
Was 52 min · contract ≤ 60 sec
Test-drive bookings
+38%
vs. 90-day pre-pilot baseline
Auto-qualified
0.71
No human touched the lead
CRM completeness
+44%
Fields populated per record
§ 02Existing condition
Existing condition · before pilot

Inbound from three channels — answered by humans on a desk between 09:00 and 19:00.

Auto Pivdenny ran six yards in greater Kyiv, with inbound from OLX, Instagram and the website all aggregating to a Telegram group three sales managers shared. Replies during business hours were merely slow (median 17 minutes). Outside business hours they were lost — silently — until somebody noticed a thread on Monday morning.

The owner, Pavlo, didn't want a chatbot on the website. He'd seen them. He wanted, in his words, "a worker who reads OLX at 11pm and books a test drive for tomorrow morning, who knows our 220 cars, and who writes the customer's number in the CRM."

We agreed on the contract number in the first call: median first reply ≤ 60 seconds, measured across all three channels, all hours. If we missed it, the pilot was free.

EXISTING · 2024-Q1OLXINSTAGRAMWEBSITETG GROUP · "INBOUND"~80 unread3 humans09:00–19:00⌀ 52 min · 0 nightsKEY CRMPARTIALLY KEPT~31% OF NIGHT INBOUND LOSTFIG. 02-A · EXISTING CONDITION
§ 03Proposed assemblyDay 1 → Day 14
PROPOSED · LEAD HUNTER · M-01OLXINSTAGRAMWEBSITETG · DMG2 · LEAD HUNTER8 qualification rulesInventory-aware (220 cars)UA · RU · EN24/7 · ⌀ 14 secKEY CRMCALENDARSALES TGINVENTORY⌀ 14 sec · CONTRACT ≤ 60 secFIG. 03-A · LEAD HUNTER ASSEMBLY
Proposed assembly · M-01 Lead Hunter

An inventory-aware lead hunter on every channel.

We connected the four channels to one agent core. The agent reads the live inventory feed (220 cars, updated nightly), greets the customer in their language, qualifies against eight rules co-written with Pavlo on Day 1, and books a test drive into the dealership's calendar — checking against staff capacity at the right yard.

The eight rules are unsexy and very specific to this dealer: budget & financing, trade-in or not, manual or automatic, mileage tolerance, body type, must-have features (panoramic roof was a real one), preferred yard, and crucially — whether the customer is "researching" or "ready Saturday".

Hot leads — defined as: ready in ≤14 days, budget within ±10% of a real car on the lot — go to the sales TG with a one-line summary and the booked slot. Cold leads stay in the CRM with a follow-up scheduled for day 7.

§ 04Construction sequence14 days
DayStageOutputOwner
Day 0BriefWorkflow scoped · 8 qualification rules · contract KPI co-signedVlad K. · Pavlo
Day 1–2Channel wiringOLX · Instagram · website · sales TG connected; agent identity provisionedMarko Y.
Day 3Inventory ingest220 cars indexed; nightly sync from KeyCRM establishedOlha B.
Day 4Tone calibrationPer-language voice profile written with the salesfloorIryna S.
Day 5–9Shadow modeAgent drafts; humans send. 312 conversations evaluated.All
Day 10Calibration reviewTone tightened; 3 escalation rules added; refusal contract signedIryna S. · Pavlo
Day 11–13Live · ramp10% → 50% → 100% of inbound. Daily metrics call at 19:00.Marko Y.
Day 14Hand-offContract KPI met. Move to ongoing service. Owner dashboard delivered.Kateryna L.
§ 05Measured outcomes

The contract called for ≤ 60 seconds. We hit 14.

Across all four channels, all hours, all languages — measured by the agent's own audit log and verified against KeyCRM timestamps. The largest single category of wins was the night shift, which used to be a graveyard.

  • +38% test drives booked in Q1 vs. the same quarter pre-pilot
  • 71% of leads auto-qualified end-to-end without a human
  • +44% CRM completeness — fields populated per record
  • 0 added headcount. The salesfloor stayed at 38.
  • Two managers reassigned from inbound to outbound proactive follow-up

What didn't work the first time. The agent's first month over-qualified — it was rejecting some "researching" leads who would have converted in 30 days. We added a soft-warm bucket that goes into the CRM with a 14-day check-in instead of a hot handoff. Conversion on that bucket runs around 18%.

FIRST-REPLY DISTRIBUTION · BEFORE / AFTER (N=2,840)0-30s2m15m2h12h+⌀ 14 sec⌀ 52 minBEFOREAFTER · 90 DAYS LIVE
Client testimonial

The contract said the worker would reply in under a minute, day or night. The first night, my night manager messaged me at 02:14 in a panic — he thought one of the salesfloor was awake on a Saturday. It was the agent. We sold the car a week later.

Pavlo M., Owner, Auto Pivdenny · Kyiv
§ 06Drawing metadata
Engagement
Pilot 14 days · ongoing service since 2024-03 · two named engineers · weekly review (90 days), monthly thereafter
Stack used
Claude Sonnet (reply) · Temporal (workflow) · Postgres+pgvector (recall) · KeyCRM API · OLX/IG/Web webhooks

Your inbound looks like Pavlo's? Let's draw your version.

A 30-minute call, your eight qualification rules, the number that goes in your contract.

▸ Commission a pilot
Case 01 · Auto Pivdenny — used-car dealership · Kyiv · Grow2.ai