On Friday morning the routine that checks my open proposals did not finish. Nothing told me. I found out at nine that night.
What the routine is for
Every weekday something looks at the proposals and quotes I have sent, works out which ones have gone quiet, and drafts the follow-ups for me to approve. I built it because I am the same as every owner I talk to. I send the quote, the week fills up, and the check-in I promised myself does not happen.
It has worked. On Wednesday it checked four open items and drafted one follow-up. On Thursday it checked again and nothing needed a draft.
On Friday 2 October it started at 07:52, hit an error part of the way through, and stopped. It did not write down that it had started. It did not write down that it had failed. The record of what needs following up was last touched on Thursday at 08:23, and it stayed that way all day.
The part that bothered me
A routine that fails loudly is easy. You see the error and you run it again.
This one failed the way a person forgets. No message, no red light, just a day where nothing happened and nothing said so. From the outside, a Friday with no follow-ups due and a Friday where nobody checked look exactly the same.
I do not yet know whether anything was due on Friday. Monday's run will tell me. That is the uncomfortable part: for three days the honest answer to "has everyone been followed up?" is "I think so".
What caught it
A second check did. It runs later in the day and asks a different question. Not "what went wrong?" but "what should have happened today and did not?" At 21:02 on Friday it reported the gap: the morning routine had fired, left no trace of finishing, and the record had not moved since Thursday.
It is not the first time. The same check flagged a missed day on 24 September, a public holiday, and another on 28 September. Later runs picked the work up both times. Both times I only knew because something went looking for silence.
What I took from it
I had treated follow-up as one job: send the message on time. It is two. Send the message, and prove the sending happened.
That is the same gap I see in businesses that run their customer conversations across a phone, a mailbox and a notebook. The follow-up is somebody's intention, and when it does not happen there is nothing to show that it did not. The customer simply hears nothing.
It is why, when we set up NexBrand for a business, the follow-up does not end quietly. A sequence that finishes without a reply becomes a task with a name on it. Silence turns into something a person has to look at.
My own routine has the same standard to meet. Monday's run will show whether Friday cost me anything. Either way, the lesson is already paid for: a follow-up system is only as good as its way of telling you it did not run.
I wrote up the customer side of this today: customer follow up, as a system that runs on dates and not memory. And this is the platform we set up and manage for it: NexBrand.
Frequently Asked Questions
What actually failed?
A routine that checks my open proposals each weekday and drafts follow-ups stopped part of the way through on Friday 2 October. It left no record of starting or failing, so the day simply looked quiet.
How was the failure noticed?
A separate check that runs later in the day looks for things that should have happened and did not. It reported the gap at 21:02 that evening, about thirteen hours after the morning routine had stopped.
What is the lesson for a business that follows up with customers?
Sending the follow-up is half the job. The other half is being able to see that it was sent, so a missed follow-up shows up as a task for someone and not as silence.