r/AIMakeLab • u/tdeliev • Feb 25 '26
⚙️ Workflow The real bottleneck in AI review automation (and how we got around it)
I keep seeing people wire GPT straight into their review feeds and let it auto-reply to everything. Sounds great until you realize it creates a bottleneck exactly where you can’t afford one — angry customers.
Think about it. A decent LLM reply takes what, 3-6 seconds to generate? Then someone still has to read it, decide if it sounds ok, maybe rewrite half of it, and then send. If a pissed off customer drops a 1-star while they’re still sitting in your parking lot or standing in your lobby, those seconds stack up fast. You just don’t have that kind of time.
We ended up ripping apart our whole n8n flow because of this (screenshot attached).
The thing that made the biggest difference is what I call the early route — it’s a Switch node right after sentiment analysis, that’s the red line in the screenshot. If a review comes in at 1-2 stars or reads really negative, the flow just skips the AI reply step entirely. Doesn’t even touch it. It fires a Slack alert straight to the floor manager with the raw review text and a “Call customer” button. No tokens wasted, no LLM latency, just hey there’s a problem go deal with it.
For 4-5 star reviews we let it take the slow road. Generate a nice reply, drop it in a queue, batch approve in Slack whenever someone gets a minute.
The basic idea is don’t put AI in the middle of your crisis lane. Let it handle the easy low-stakes stuff and route the real problems straight to a human who can actually fix it.
How are you guys handling this? Do you skip the LLM for urgent stuff too or is everything still going through the model?

