Stop Being the Follow-Up. Build an AI Loop Instead.

You did not hire an assistant. You hired yourself, and gave it a chat window.

It is 9 p.m. In Manila. Mia runs a six-person events and party rental business, tents, linens, folding chairs, the works. Three weeks ago a supplier shipped 40 tablecloths for a wedding with a wine stain already baked into the fabric. The supplier promised a refund. That was three weeks and four unanswered emails ago.

Mia is not bad at her job. She is just the one who has to remember. Remember to check if they replied. Remember what day she last followed up. Remember to sound polite the fourth time she asks for the same thing. Remember to escalate to a phone call if email keeps going nowhere. Nobody put that job on her contract. She just ended up doing it, the way every small business owner ends up doing it, because someone has to hold the thread.

You Already Run a Loop. It Just Runs In Your Head.

Here is the reframe that matters: chasing that refund is not a task. It is a loop. Send, wait, check, escalate if needed, stop when it is resolved. You already do every step of it. You are just doing it manually, in your head, at 9 p.m., instead of handing it to a system that does not get tired of asking.

This is the distinction a lot of AI advice skips. A chatbot answers one question and forgets everything. A single prompt gets you one draft, and you are the one who reads it, catches the problem, and runs it again. That correction loop, judge the output, remember what went wrong, know where the line is, decide when it is done, is work. It just happens invisibly, inside your own head, one email at a time.

An AI loop is what happens when you write those four jobs down and hand them to a system: a way to judge the output (an eval), a way to remember what already happened (memory), a line it is not allowed to cross on its own (a guardrail), and a rule for when to stop. Do that, and the same follow-up that ate your evening runs itself while you are asleep.

What Is an AI Follow-Up Agent, and How Is It Different From a Chatbot?

An AI follow-up agent is software that tracks an open item on your behalf, an unanswered email, a late invoice, a claim, a booking, and keeps nudging the other side on a schedule, without you starting a new chat each time. A chatbot answers what you type into it right now and forgets everything the moment you close the tab. A loop remembers, acts on its own schedule, checks its own output, and knows when to stop or hand the decision to you. That third part, the checking and the stopping, is the part almost everyone skips when they first try to automate a follow-up.

Isn't This Just a Fancier Chatbot With Extra Steps?

Fair question, and the honest answer is no, because of two things a chatbot does not have: an evaluator and a stopping condition. Without an evaluator, a loop is just automated guessing, it produces output and has no idea if the output is any good. Without a stopping condition, it is a billing machine, happy to keep running and keep costing you money without ever finishing anything. Add both, and you have something closer to a very patient, very literal junior employee: infinite patience, because it will happily try the same follow-up 40 times without getting tired or annoyed, but zero judgment, because it has no idea what "good" looks like unless you tell it.

The Five Things Every Follow-Up Loop Needs

A full production loop has nine working parts, but a small business does not need all nine on day one. Here are the five that matter for a first build, adapted from the loop-engineering framework AI product lead Shubham Saboo laid out this week.

1. A goal you can measure. Not "chase the refund politely." Try: "the refund is confirmed in writing, or 21 days pass and the case is escalated to me." A number or a clear yes/no beats a wish every time.
2. Context. What does the loop know going in? The original order, the promise the supplier made, the date they promised it by, your tone guide. Thin context gets you confident nonsense at scale, not just once.
3. Actions and tools. What is it actually allowed to touch? Draft a reply, check the inbox, log the date, update a spreadsheet. Small, defined moves, not "do whatever it takes."
4. An evaluator. Something that checks each attempt against the goal. Did the reply cite the claim number? Did it name the promised date? Is it under 150 words? This is the step most first attempts skip, and it is the one that keeps the loop honest.
5. An escalation rule and a stopping condition. Anything involving money, a customer relationship, or a decision you cannot undo goes to you, always. And before you press run, decide on all three exits: a target (refund confirmed), a budget (21 days or a dollar cap on paid tools), and a stall rule (three follow-ups with zero reply means something is stuck and a human should look at it).

A Worked Example: The Refund Nobody Was Chasing

Back to Mia. Here is what her loop spec looks like once she writes it down instead of carrying it in her head.

Goal: refund of 8,400 pesos confirmed in writing, or the case is flagged to Mia after 21 days.
Context: the order number, the photo evidence of the stained linens, the supplier's original promise ("processing, allow 15 days"), and Mia's usual tone, direct, friendly, no exclamation points.
Actions and tools: read the shared inbox thread, draft the next follow-up, log the date of each attempt in a spreadsheet.
Evaluator: does the draft reference the order number and the original promise date, does it avoid sounding desperate or aggressive, is it three sentences or fewer.
Guardrail: it drafts, it never sends without Mia's one-tap approval, because this touches a supplier relationship she still needs next season.
Stop: refund arrives (target), 21 days pass (budget), or the supplier goes silent for two follow-ups in a row (stall, escalate to a phone call).

Notice what changed. Mia is not doing the remembering anymore. She is doing the approving, which takes ten seconds a day instead of an evening of hunting through old emails. The loop does not need her to be smart about tone every single time. It needs her to have been smart about it once, when she wrote the spec.

This is the same shift behind the AI loop that finds you customers while you sleep, a lead-generation loop we broke down here last week. Different job, same architecture: a goal, a check, and a rule for when to stop.

Why Most Follow-Up Bots Quietly Fail

Five failure modes show up again and again, and every one of them is a design gap, not a smarter-model problem.

• Drift. Left ungraded, a loop optimizing for "shorter replies pass the check slightly more often" will quietly write shorter and shorter messages until they say almost nothing. Restate the actual goal in every attempt, not just the last instruction.
• A weak evaluator. "Rate this reply 1 to 10" is not an evaluator, it is a guess with a number attached. Use concrete yes/no checks instead: did it name the order number, did it name the date.
• Runaway cost. "I'll keep an eye on it" is not a budget. A dollar cap or a day limit, decided before you press run, is a budget.
• Watching it live. A loop that takes 40 minutes and you sit there watching is the worst of both worlds, your time and the machine's time. Kick it off, close the laptop, read the log in the morning.
• No real stop. "Stop when it's perfect" on a task where perfect is undefined is the same as no stop at all. If you remember one rule, remember the stall: three attempts with no progress means something is wrong and a human should look.

What You Have After This

A week in, you have one loop running, probably the most annoying repeated task on your plate, the one you have done three or more times this month without ever writing it down. A month in, you have stopped being the person who remembers to follow up, and started being the person who approves the follow-up, which is a very different job. Three months in, you have a small library of loop specs, one for refunds, one for quotes gone quiet, one for late invoices, each one a page long, each one something you could hand to a new hire on their first day, because that is really what a loop spec is.

Same business. Same relationships with your suppliers and customers. A completely different amount of your evening spent remembering things a system could remember for you.

Frequently Asked Questions