Wellness One / More More
Open closer desk AI active

System and connections

Know what is connected.

A plain-English view of lead scoring, buyer readiness, PropertyData, customer channels and the controls protecting the live business.

Open API referenceCheck system health

Lead decision architecture

Two scoring layers, one clear handoff

Routine paused · last ran 16 Sep 2026
1

At enquiry

Live engine score

0–100

PropertyData postcode affluence, then product, stated budget and timing.

2

Stored classification

Lead grade

P · H · C · S · L

Priority, High, Commercial, Standard or Low enters the AI journey at Day 0.

3

During the journey

Buyer readiness

Long tail → Ready

Quote, reply, engagement and freshness determine the operating band.

4

Human handoff

Hard keep

Tony now

Only quote plus two-way evidence, buyer request or deposit produces a closer packet.

Rule source: owner-confirmed migration contract recorded 19 September 2026. The existing score_leads.py source is outside this repository, so these exact values are requirements for migration and regression testing—not a claim of repository-level verification.

Owner-confirmed engine contract · 0–100

How the lead score is built

Postcode affluence starts at 50 when unknown.

  • Household income: +35 at £80k+, +25 at £60k+, +15 at £45k+, +5 at £35k+, otherwise −5.
  • Average house price: +15 at £500k+, +10 at £350k+, +5 at £250k+.
  • Connect interest: +10 only when stated budget reaches about £23,370.
  • Lifestyle interest: +5 only when stated budget reaches about £17,100.
  • Budget below the product floor: −25.
  • Urgent timing words: +10; research/no-rush/next-year language: −10.

The final score is clamped to 0–100.

Owner-confirmed engine contract · classification

How the lead grade is assigned

  • Commercial: commercial-use answer, or hotel, gym and resort-style signals.
  • Priority: score 85+ with urgent timing. Researching alone is never Priority.
  • High: score 85+ without urgency, or score 70+.
  • Standard: score 50+.
  • Low: score below 50.

Priority and Commercial still complete AI Day 0. Grade alone never puts a buyer on Tony’s desk.

PropertyData

Existing engine source; new CRM adapter pending

Direct CRM connection not yet implemented

2 open CRM records currently have a postcode. The current live engine already uses PropertyData; this new CRM should receive the resulting score and source evidence first, then add a direct adapter only when migration ownership is agreed.

  1. Import the original engine score, grade, scoring time and version during lead conversion.
  2. Retain the PropertyData lookup reference and retrieved time as evidence.
  3. Show the score factors on the deal without silently rewriting them.
  4. After cutover, move the same rules behind one CRM-owned adapter with an audit trail and kill switch.
  5. Never use property data alone to trigger Tony work or customer contact.

CRM journey · current evidence

Why buyer readiness stays separate

The CRM’s Long tail, Serious, Ready candidate and Hard keep states measure what the buyer is doing now—not just the quality of the original enquiry.

  • Long tail: AI continues nurture.
  • Serious: stronger evidence, but AI still holds.
  • Ready candidate: test the strict handoff rules.
  • Hard keep: send an evidence packet to Tony.

Inspect buyer readiness →

Hermes and customer channels

One customer journey

Production front door stays / → /top30 at http://2.29.8.190:8080/. This app does not replace it.

  • Deal composer and tracking are present; sends remain paused.
  • Inbound replies appear on the deal timeline and SMS board.
  • Templates are browsed here but are not a second sales journey.

Standard email assets

One managed asset library

Original brochures, approved images, videos and documents belong in protected object storage. Approved delivery versions are served through the Wellness One CDN.

  • Files: object storage/CDN path email-assets/<family>/v<version>/<file>.
  • CRM database: IDs, version, URL, product scope, approval, source, checksum and timestamps only.
  • Email templates: reference a stable asset ID, never embed a local repository path.
  • Draft or retired assets never become sendable; the current approved version is resolved at render time.

The Git repository stores templates and code only—not marketing binaries or customer attachments.

Operating guardrails

What the CRM will not infer

  • No invented property value, wealth, price or purchase intent.
  • No automatic customer send from a grade or score.
  • No won or lost deal re-entering an open journey.
  • No hidden provider connection presented as live.