Flagship product · Founding pilot

Lead Reactivation.
Conversation with controls.

A controlled system concept for reviewing an existing lead list, approving who may enter, supporting the conversation path and verifying outcomes outside the message thread.

Founding pilotFounder-supervised activation onlyNo published results

Public system blueprint

Complex underneath.
Bounded at the controls.

This view explains the operating responsibilities without credentials, endpoints or implementation secrets. It is a product mechanism. It is not evidence of client performance.

PUBLIC SYSTEM BLUEPRINT / LR-01ABSTRACTED VIEW · OPERATING BOUNDARIES ONLY
01

Reviewed input

Known records enter

02

Decision layer

Rules · boundaries · stops

03

Human gate

Approval before action

04

Agent path

Contextual conversation

05

Verified outcome

Truth outside the message

06

Observable state

What happened · what did not

Human approval System path Current gate

Current intended path

A reviewed route from
record to verified outcome.

The system is designed around containment: known input, eligibility and suppression review, approved waves, a controlled conversation path, and a booking counted only when the calendar holds matching proof.

01 / INPUT

Reviewed CSV

Authenticated upload and mapping; no named CRM connector is claimed.

02 / GATE

Eligibility + suppressions

List source, exclusions and the exact campaign plan require review and approval.

03 / PATH

AI-assisted conversation

The intended conversation path uses managed transport, with dispatch and channel changes controlled.

04 / TRUTH

Verified booking

A matching scheduling record defines the outcome. Chat language alone does not.

Pilot fit boundary

A fit conversation needs
list evidence and an owner.

MAY BE WORTH DISCUSSING
  • an existing dormant-lead list;
  • a clear list source and suppression process;
  • one owner who can approve the campaign plan;
  • capacity to handle genuine replies and bookings.
NOT THE CURRENT PRODUCT
  • cold-list acquisition or scraping;
  • automatic campaign activation;
  • a booking or revenue promise;
  • a named CRM connector. The current product does not include one;
  • online checkout is not live.

Questions before enquiry

Clear boundaries
before a call.

01What stage is Lead Reactivation at?+

It is a founding pilot. It is offered to a small number of businesses first so the operating boundary and the reporting can be proven before it is opened up.

02What kind of list enters the system?+

Your own past enquiries and customers, uploaded as a file and mapped to fields you can see. The list source and any suppressions are reviewed with you before a campaign is planned.

03Does it connect directly to my CRM?+

No named CRM connector is claimed. A future integration can only be discussed against the actual environment and current product boundary.

04Does an AI agent send messages automatically?+

The intended path uses an AI-assisted conversation layer, but dispatch and channel changes remain controlled. Human approval and containment are part of the operating boundary.

05What counts as a booking?+

A conversation does not count by itself. The designed truth boundary requires a matching record in the approved scheduling system.

06Where are the results and testimonials?+

There are no verified client campaigns, results, testimonials or case studies to publish. They will not be simulated.

Lead Reactivation enquiry

Ask whether the founding pilot
fits your list and team.

Describe the dormant-list situation and the business process around it. This checks whether the founding pilot may fit your list and team. It does not start a campaign or take payment.

PRIVATE ENQUIRY

A product-specific readiness check before any campaign or booking discussion.

Add useful context Optional

Only provide business-process information you are authorised to share. Do not include passwords, health information, financial credentials or customer records. Read the form privacy notice. Read the website and enquiry terms.