Module 03
Follow-up
No-shows, aged leads, reviews, and unpaid invoices worked on schedule until they close or stop.
For your revenue team
The console
What your team sees.
A mockup on sample data of the console this module writes to. Every row is an action, every status is a state your team can see, and anything marked for a person waits until one decides.
Follow-up queue, sample week
Sample data37
Open threads, sample week
- No-show, Tuesday 2pmRebooked
- Lead aged 14 daysTouch 3 of 5
- Invoice 30 days outReminder sent
- Review request, day 2Sent
- Asked to stopStopped
The problem
Most leads never say no. They go quiet, and after the second try nobody on the team has time for a third. The no-show never gets rebooked, the quote never gets a nudge, and the invoice sits unpaid until someone makes an awkward call. That is money we already earned the right to.
What it does
Reads, remembers, prepares, does.
- 01ReadsEvery place a thread can stall: the missed appointment, the quote with no reply, the lead that went quiet, the invoice past its date, the job that ended without a review.
- 02RemembersEvery touch already made, on every channel, so the fourth message reads like a person who has been paying attention, and a customer who asked to stop is never contacted again.
- 03PreparesThe next message in your voice, on the cadence you approved, with the rebooking link, the payment link, or the review link it needs.
- 04DoesSends on schedule by text, email, or voicemail drop, rebooks the no-show, and logs every touch in your CRM. When the thread closes or the customer says stop, it stops.
Your controls
Three hard limits, written into the install.
Standing permissions live in one written list, per action and per channel, with the reason for each. Not on the list means it cannot send.
- 01
Cadence set in writing
How many touches, how far apart, on which channels, for each kind of thread. It cannot add a touch or a channel on its own.
- 02
Read-only on the ledger
It can see that an invoice is open and send the reminder with your payment link. It cannot charge, credit, or change an amount.
- 03
Stop means stop
One reply asking to stop closes the thread on every channel and flags the record. Reopening it takes a person.
Proof
A company-owned system
Echelon runs this module on its own pipeline first. The inbound and outreach engines on the systems page show the same cadence, readback, and stop rules on sample data.
It connects to the rest
The other three modules.
Same connections, same customer record, same limits, same console. The second module installs faster than the first.
- 01Inbound ResponseFor your front desk and sales teamA thread opens the moment Inbound Response books a visit, texts back, or hears nothing.See the module
- 02End-to-End QuotingFor your sales teamOpen quotes from Quoting join the queue on the cadence you set.See the module
- 04Operations and VisibilityFor leadershipInvoice dates and no-shows are read from the records Operations keeps in step.See the module
Your first department
Bring the process you still run by hand.
One mapping call. You leave with the system design, the price in writing, and the date it goes live.
How it works
See how an install runs, from the mapping call to production.
Six steps, each with an output and a control, and the 90-day shape with a date agreed in writing.
See the process