The Alert Fired. Nobody Was There.
A lead alert that reaches a place instead of a person, and records no acknowledgement, leaves an inbound buyer unowned even when every component works.
If someone fills in the contact form on your website tonight, who finds out, and how fast? And if the answer turns out to be nobody, how would you know?
The second question is the expensive one. A form that works, an alert that fires, and a person who never sees it produce the same silence as a form nobody filled in. From the owner's chair the two look identical. One is a quiet week. The other is a buyer who asked for a conversation and heard nothing back.
We ran into this on our own lead form last week. The form accepted a submission, our system stored it, and the small monitor we built for exactly this job alerted thirteen minutes later, then again in a summary the next morning. Both alerts went to a channel where no person had written since May. The lead sat a full day before anyone reviewed it.
It was our own test, so nothing was lost. What it showed is the point: every part did what it was built to do, and nothing in the system made sure a person knew someone was waiting.
The path, link by link
As it stood that Wednesday, the path was short. When a buyer filled in the readiness form on my agency's site, the site passed it to an operations service that held it in a review queue. The monitor checked for new leads every fifteen minutes and posted an alert when it found one. A second job posted a daily summary of anything still waiting.
Every link worked on Wednesday evening. The lead was stored at 5:02 pm, the monitor alerted at 5:15, and the summary repeated it at 8:30 the next morning. Measured by its parts, the path was healthy. Measured by what it exists for, a person who can respond finding out quickly that someone is waiting, it had failed, and nothing in the chain checked.
Who owned what
Every part of that path existed for this job. The monitor had been built two weeks earlier to notice inbound leads to my agency, because nothing else did. What no part owned was the sentence a buyer cares about: a person knows, and responds, within the time we promised.
Two details show where that gap lived. The AI assistant running the test for me said, eleven minutes after submitting, that nothing would notify me. The monitor posted its alert less than two minutes later. Even the assistant that had just submitted the lead did not know where the alert went.
And the alert went to a place, not a person: the default channel of our automation account. The change that would reroute it was already written. It waited nearly two days for my go and one input from me: a channel I would actually watch.
What the monitor could not tell
The monitor did what it was built to do: alert once per new lead, then stay quiet so it does not repeat itself. In the next 24 hours it checked 96 more times. Ninety-three of those checks saw one lead waiting and said nothing, because it had already posted. Three could not reach the review queue at all.
That is the mechanism. The system treated sending a message as the same thing as someone knowing. It could not tell the difference, because nothing recorded that a person had seen the alert, and nothing would have happened if no one had.
The channel history makes the point. Across the 28 Slack channels we audited, the 30 days to Friday brought 6,164 automated posts and 3 human messages, all mine. Not one automated post drew a reply or a reaction. The alert's own channel held 12 automated posts that month and no human message since May 26. The alert was not buried in noise. It landed in a quiet channel where nobody had spoken in months. Slack cannot show whether anyone read it. It can show that nobody answered.
Every part lit up on time, over an empty desk.
Two properties of a lead path that works
A lead path needs both of these.
A named receiver. The alert goes to a person who owns the response, on a surface that person actually checks. The test for whether you have a person or a place is simple: when did a human last write there?
An acknowledgement with a deadline. The person's "seen it" is recorded, and its absence is itself an event. If nobody acknowledges within a stated time, the alert goes to someone else. Without this, a missed alert and a handled one look the same from the outside. That is how our monitor could see a waiting lead 93 times and say nothing.
A named receiver, and a record that they saw it.
On Friday we addressed the first property. Lead alerts now go through an internal inbox that pushes urgent items, and nothing else, to a channel I created for them. We sent a labelled test to the live form's submission endpoint, and the alert went out about a minute after the lead was stored. The minute was luck. The monitor checks every fifteen minutes, with up to a minute of random delay, so on a healthy day an alert takes up to about sixteen minutes, and a failed check makes it longer.
The second property is not built. That inbox records an acknowledgement when I make one; nothing yet acts on its absence. A delivered alert that I never acknowledge is, today, silent. That is the next change. Until it exists, a delivered alert I miss waits until I next look at the inbox or the review queue myself.
Three questions for your own form
The first two take ten minutes. The third takes as long as your lead path does.
Who is told? Name the person, not the tool, who finds out when your form is submitted. Then open the place the alert lands and find the last message a human wrote there.
What happens if they miss it? Find the record that they saw it. If there is none, ask what happens thirty minutes after an alert nobody acknowledged. If the answer is "nothing," your lead path can fail without anyone noticing.
How long does it take, end to end? Submit a clearly labelled test tonight and time it from submit to a person saying "got it." Compare that time with what your thank-you page promises.
What it cost, and what a buyer would have met
Nothing in money. It was a test, and nobody was waiting for a reply.
Our thank-you page says: "If you requested a Readiness Scan, we'll review your submission and send calendar invites within 1 business day." Measured against that promise, the record shows no human review for a full day, and the review, when it came, did not happen because an alert had reached anyone.
It also produced a false alarm. The next day, another AI assistant in our system found the untouched test, could not match it to any test it knew of, and reported it to me as a real enquiry.
If you own an inbound workflow
Whichever of the three questions you start with, the answer comes down to two things: the name of the person who is told, and the time after which someone else is told if that person has not said they saw it. If the first answer is a channel or a tool, or the second is never, that is where a buyer can wait with nobody knowing.
That is the kind of gap the Readiness Scan my agency runs looks for: one workflow, where it can fail, and a plan for who owns the path and each handoff. Work with OIA on one workflow.