SHT-01Agent schedule
Three systems in production, 3,915 automated tests across them. One agent or one automation in the CRM you already have is the AI Automation Sprint, $999, 1-2 weeks. The full agent inside a system of your own is part of a custom CRM build, from $2,500, 30-45 days.
One of the systems we built has AI in it, and this is the only sheet where we say so. Everything below names the file it comes from. The agent's job is to hold the call, sort the reply, and put a person in front of the lead while it is still warm. AI goes where it closes a gap in the work, not where it looks good in a deck.
SHT-02Detail A · voice
A Vapi assistant holds the conversation. When it ends, Vapi posts the end-of-call report back into the system, which checks a shared secret before it believes anything, reads the duration to tell a real conversation from a wrong number or a voicemail, normalizes the number to E.164 and matches it to a lead record, and sends a Telegram alert carrying the summary, the reason the call ended, the front of the transcript and a link to the recording into one chat, the studio's own founder DM in that system, while the lead is still warm. Short calls and no-answers are recorded but not announced, because an alert that fires for everything gets ignored. Which line an assistant sits on is a setting in the phone provider's dashboard rather than something in the code, so this sheet does not tell you who called whom: what the file proves is the report and the handoff.
SHT-03Detail B · telephony behind the dialer
These routes carry the calls a person places, not the ones the voice agent handles: nothing in this directory mentions Vapi. A token endpoint lets the browser dial, and it grants outgoing only, with incoming switched off in one line. A voice route returns the instructions to dial. A status callback writes the final disposition onto the lead by itself, so nobody has to click a button to record that a number was dead. A hook fires when the recording finishes writing, fetches it and has it transcribed, which happens inside that hook rather than in a route of its own. Five files do that work. The sixth dials one hardcoded number and exists to prove the setup is alive.
SHT-04Detail C · follow-up engine
Automated follow-up is easy to build and easy to get wrong in ways nobody notices for a month. Each module below was written after a specific failure, and the failure is written into the top of the file.
Every message that came back used to count as a human answering. Bounces, out-of-office autoreplies, and opt-out shouts all promoted a lead to 'replied' and quietly paused its sequence, which then had to be undone by hand. The classifier separates the four cases and routes each one differently.
A lead that answered and has heard nothing back since is the most expensive thing in the pipeline. It goes into a daily digest and stays there until someone actually moves it, rather than being announced once and forgotten.
When sending volume is high and real replies are not, the daily cap comes down on its own. Sending harder into a spam folder costs the sending domain, and the domain is the one asset here that cannot be replaced.
Every wait in the system is counted in business days, and a step that lands on a Saturday moves to the Monday. A nudge that arrives on a Sunday reads as a machine, because it is one.
Steps are stored relative to the step before them, and where a subject line has variants, the variant is picked by a deterministic hash of the lead. The same lead always gets the same one, so a restarted sequence never reads as a different sender.
Sends over SMTP and reads replies back over IMAP from the actual mailbox, so a reply is a reply rather than an inference from a tracking pixel. Every message carries a working unsubscribe.
Proof · wallflow-saas · lib/followups/ (12 modules)
SHT-05Detail D · the dialer
A caller opens one tokenised page and works a list: the next number, who it is, what happened last time, and where the outcome goes. Eight endpoints stand behind that page, the campaign, the lead, the log, the callbacks, the calendar, the activity feed, the history, and the outreach record. Nothing is generated for the caller mid-conversation. The software's job is that they never have to look anything up.
SHT-06Detail E · scheduled work
The parts of the working week that depend on a person remembering are the parts that stop happening in a busy month, so they were written as jobs that run on a schedule. Then they were counted from the other side. Every one of them delivered into the same chat, this studio's own founder DM, at roughly six to eight Telegram messages a weekday, which the note filed with them calls the spam. On 2026-05-15 commit 1e0d7e6, 'pause the 8 founder-bot Telegram crons', took eight out of the schedule and left the code in the repository, callable by hand. Its author is the author who had added those alert crons a month before, which is the part worth sitting with: the person who wrote the reports is the person who switched them off. The lesson is not about cron. The ceiling on automated reporting is not what a system can send, it is what one reader will still open.
Proof · wallflow-saas · vercel.json crons, .github/workflows/daily-crons.yml, docs/paused-crons-2026-05-15.md
SHT-07General notes · what this page will not claim
SHT-08Detail F · what you can buy on its own
Not every business needs the whole system. The AI Automation Sprint is one piece with a written scope and one number it should move, built into the tools you already run and live on your own accounts at the end. Pick the leak.
$9991-2 weeks
See it on the ladder →SHT-09Cross-reference
An agent that handles a call and writes into nothing is a novelty. The reason the handoff works is that there is a system on the other side of it: the lead, the estimate, the deposit, the schedule. That is on its own sheet.
See the systemSHT-10Related guides
AI goes where it closes a gap in the work, not where it looks good in a deck. Built from Sacramento, wired into the tools you already run, on your own accounts.
AI goes where it closes a gap in the work, not where it looks good in a deck. A Florida LLC that started in South Florida, now building remotely from Sacramento, on your own accounts.
Two separate numbers: what it costs to build, and what it costs to keep answering. Most quotes only mention the first.
All three answer the phone. They differ in what exists five minutes after the caller hangs up, and that is the only part worth choosing on.
The interesting question is not whether it can answer the phone. It is what happens to the call afterwards, and what the thing is not allowed to decide on its own.
SHT-10Issued for construction
A short video walkthrough of where your lead flow leaks and what it would take to close it. Free, and there is no call afterwards unless you want one.
30 seconds to submit · delivered same day · no card, no call
