Lucky Systems
EN ES
Book a mapping call
Home Solutions Builds Industries Insurance & risk Home services Custom Software About Book a mapping call
EN ES
Book a mapping call

Interactive demonstration · Follow-up

An estimate goes quiet for three days.

Play the run below. One approved message goes out, the customer answers, and a named person owns it by 11:45.

Run the demonstration See all six workflows

What this is: Lucky Systems builds AI, marketing and software systems for growing businesses. This one is customer follow-up — automated up to the point where a person has to decide, then handed to that person by name.

The follow-up sequence over time An estimate is sent on day one and goes unanswered for three days. On day three at 08:00 the silence is detected. Before anything is sent, a gate checks recorded consent, an approved template, and the sending window. At 08:02 one approved message goes out. At 11:42 the customer replies and the sequence pauses immediately. The run then ends in one of three decisions: booked, declined, or handed to a named human — in this run, handed to a human. DAY 1 SENT Estimate #4821 issued $1,450 · opened, no reply 3 DAYS OF SILENCE Where estimates quietly expire DAY 3 08:00 Silence detected GATE · BEFORE ANY MESSAGE Consent recorded Approved template, unedited Inside the sending window 08:02 One approved message sent One message, then it waits 11:42 Customer replies SEQUENCE PAUSES BOOKED Sequence closes DECLINED Reason recorded, contact stops HANDED TO A HUMAN This run · named owner + deadline The follow-up sequence over time An estimate sent on day one goes unanswered for three days. On day three at 08:00 the silence is detected. Before anything is sent, a gate checks recorded consent, approved wording and the sending window. One message goes out at 08:02. The customer replies at 11:42 and the sequence pauses. The run then ends in one of three decisions: booked, declined, or handed to a named human — in this run, handed to a human. Estimate sent Day 1 · #4821 · $1,450 3 DAYS OF SILENCE Where estimates expire Silence detected Day 3 · 08:00 GATE · BEFORE SENDING Consent recorded Approved wording Sending window One message sent 08:02 · then it waits Customer replies 11:42 · SEQUENCE PAUSES BOOKED Sequence closes DECLINED Reason recorded HANDED TO A HUMAN This run · named owner
Three endings. Silence is not one of them.

Guided run · five stages

Silence in.
Decision out.

Play it, step it, or jump to any stage. Every stage shows what arrived, what the system did, what the record says, and who owns it.

Scenario

Customer
Karen Ellis
Item
Estimate #4821 · $1,450
Sent
3 days ago
Last activity
Opened, no reply

Home services · estimate

Synthetic data. Karen Ellis, estimate #4821 and every timestamp below were invented for this run. The workflow is real; the customer is not.

1 / 5 stages

What arrived

Three days of silence

What the system did

Flagged the estimate

What the record says

Follow-up due

Who owns it

System

What arrived

Approved template FU-1

What the system did

Sent one message

What the record says

Attempt 1 of 1 sent

Who owns it

AI assistant

What arrived

“Can you do $1,200?”

What the system did

Stopped the sequence

What the record says

Paused on reply

Who owns it

System

What arrived

A price question

What the system did

Refused to answer it

What the record says

Pricing negotiation

Who owns it

Waiting on a person

What arrived

A person accepted it

What the system did

Created the task

What the record says

Due 12:00 PM

Who owns it

J. Rivera — sales

Stage 1 of 5 · 08:00

Inactive estimate detected

Silence raises a flag instead of expiring quietly.

Stage 2 of 5 · 08:02

Approved follow-up sent

One message, wording signed off before launch.

Stage 3 of 5 · 11:42

Customer replies

The sequence halts. No second nudge.

Stage 4 of 5 · 11:42

Reply classified

Price is never negotiated by a machine.

Stage 5 of 5 · 11:45

Task assigned to a person

A named owner, a deadline, the full thread.

SMS follow-up · Estimate #4821

  1. Business · Day 1 · 09:15

    Estimate #4821 for the water heater replacement — $1,450. Happy to answer anything before you decide.

  2. Days 1–3

    Opened on day 1. Then nothing — the three days this page is about.

  3. System · 08:00

    Estimate #4821 · $1,450 · no response for 3 days

  4. Sending gate · 08:02

    Consent on file · approved template FU-1 · inside the 08:00–20:00 window. Cleared to send one message.

  5. AI assistant · 08:02

    Hi Karen — still deciding on the water heater estimate? Happy to answer any questions.

  6. Customer · 11:42

    Yes — can you do it for $1,200?

  7. System · 11:42

    Sequence stopped on reply

  8. Rules engine · 11:42

    Classified: pricing negotiation → human required

  9. Human · 11:45

    J. Rivera — sales: taking it — calling before noon.

  10. System · 11:45

    Task due 12:00 PM · thread attached to the estimate

The record, live

EST-4821 Follow-up due
StatusInactive · 3 days
Last eventSilence detected · 08:00
OwnerSystem
Next actionSend approved follow-up
EST-4821 Sent
StatusAwaiting reply
Last eventFollow-up sent · 08:02
OwnerAI assistant
Next actionWatch for a reply
EST-4821 Reply received
StatusSequence paused
Last eventCustomer replied · 11:42
OwnerSystem
Next actionClassify the reply
EST-4821 Human required
StatusPricing negotiation
Last eventClassified · 11:42
OwnerWaiting on a person
Next actionAssign a named owner
EST-4821 Human owns it
StatusOpen · owned
Last eventTask created · 11:45
OwnerJRJ. Rivera — sales
Next actionCall before 12:00 PM
System
Watches and records. Sends nothing on its own.
AI assistant
One approved message, inside the sending window.
A named person
Price, scope, or anything the rules cannot classify.

Never empty, and it never just says “waiting”.

Activity through the current stage
TimeEventOwner
08:00Inactive estimate detectedSystem
08:02Approved follow-up sentAI assistant
11:42Reply received; sequence stoppedSystem
11:42Reply classified: pricing negotiationRules engine
11:45Task assigned; outcome recordedJ. Rivera — sales
—Not reached yet—
—Not reached yet—
—Not reached yet—
—Not reached yet—

Workflow complete

Named owner + deadline on the record

Current owner
J. Rivera — sales
Recorded result
Task assigned; outcome recorded
Human action
“Taking it — calling before noon.”

One spine, different work

The same sequence, three businesses.

The stages do not change. What changes is the approved wording, what counts as an exception, and which named person receives it.

Approved message · 08:02

Hi Karen — still deciding on the water heater estimate? Happy to answer any questions.

Customer reply · 11:42

Yes — can you do it for $1,200?

EST-4821 Human required
ItemEstimate #4821 · $1,450
Last activityOpened, no reply
ClassifiedPricing negotiation
Goes toJRJ. Rivera — sales

Price is never negotiated by a machine. It stops here, every time.

How a sequence ends

Every sequence ends in a decision —
never in silence.

Booked, declined, or handed to a named person with a deadline. A follow-up track that simply runs out of messages and stops is the failure mode we are here to remove.

Booked

The sequence closes and the appointment is written against real capacity.

STATE Closed · won

Declined

The reason is recorded and nobody is contacted about that estimate again, including by the next campaign.

STATE Closed · declined

Handed to a human

Price, scope, coverage, a complaint, or anything the rules cannot classify goes to a named person with the full thread and a deadline.

STATE Open · owned by a person

Stop conditions

Any one of these ends the sending immediately. They are agreed before launch, not tuned afterwards.

  • Paused The customer replies — in any channel, at any hour.
  • Paused A person opens the record and takes it over.
  • Closed The work is booked, or the customer declines.
  • Closed The approved number of attempts is reached — the estimate goes back to a person with its history, not into a void.
  • Suppressed An opt-out arrives, or consent expires. The contact is removed from every sequence, permanently.

Consent, wording, timing

Nothing leaves on
a hunch.

Every message above cleared the same three checks first. Fail one and the send is held — logged and visible — instead of going out anyway.

The sending gate Three inputs — the queued message, the contact's consent record, and the local clock — feed one gate. When all three checks pass the system sends a single approved message. If any check fails the message is held, logged, and retried when the window opens; if consent is missing it is never sent and the contact leaves the sequence. QUEUED MESSAGE Approved template FU-1 CONTACT RECORD Consent source and date LOCAL CLOCK Sending window · pacing SENDING GATE ALL THREE OR NOTHING PASS · SEND ONCE One message, then it waits. FAIL · HOLD AND LOG Visible in the queue, never silent.

Three inputs

Queued message

Approved template FU-1

Contact record

Consent source and date

Local clock

Sending window · pacing

Sending gate All three or nothing

Pass · send once

One message, then it waits.

Fail · hold and log

Visible in the queue, never silent.

No consent record → never sent, and the contact leaves the sequence.

Check 01

Verified consent

A contact is only in a sequence if there is a consent record with a source and a date. Opt-outs are honoured instantly and permanently, across every sequence you run.

Check 02

Approved templates only

The wording is signed off before launch. The system chooses which approved message applies — it does not improvise new copy, discounts, or commitments on your behalf.

Check 03

Quiet hours and pacing

Sending windows, minimum gaps between attempts, and a hard cap on attempts are set with you. A message due at 3am waits for the window to open — it is held, not dropped.

Never automated

  • Contact without a consent record
  • Negotiating a price
  • Reading a “no” as a “not yet”
  • Hiding that a system sent the message

Before and after

The same quiet estimate, two ways.

Manual today

  • Follow-up depends on someone remembering
  • Replies land in a personal inbox
  • Old estimates quietly expire

Nothing is wrong with the people. The work simply has no owner between “sent” and “forgotten”.

Connected system

  • Approved follow-ups go out on schedule
  • Sequences stop instantly on any reply
  • Replies become owned tasks with deadlines

The same team, the same messages — with the remembering, the timing and the routing taken off their desk.

Explore another workflow

Five more you can run right now.

Same engineering, same rules about human control, different part of the operation. All six run end to end in your browser.

01

AI receptionist

A missed call after hours becomes an answered one, with a person one step away.

02

Bilingual lead intake

One intake thread running in English and Spanish, structured onto one record.

03

Follow-up & reactivation

You are here — sequenced follow-up that ends in a decision.

04

Document portal

Missing documents surface themselves instead of stalling a file for weeks.

05

Operations dashboard

One outlier surfaced against a normal series, assigned to a named person.

06

Knowledge assistant

Answers drawn from your own documents, cited, and honest about what it doesn't know.

The demo is simple — the operating rules are specific

Map your follow-up workflow.

A real build starts from your approved messages, timing rules, stop conditions, and task owners — mapped together on one call. A mapping call is 30 minutes on one workflow, and you keep the map either way.

Book a mapping call Return to all builds