I built a support bot last week without opening n8n once.

Described what I needed out loud to Claude Code. It pulled the n8n docs, checked the Asana task where the client described requirements, built the workflow through n8n-mcp.com, and deployed it.

Then I said: test it.

It tested. I left one node disabled so responses wouldn't go live, and let executions accumulate for two days. Then I said: review the executions.

It analyzed hundreds of runs and came back with: "We missed several queries. Someone asked 'where is my invoice' instead of 'where is my order' and we didn't handle that."

I said: update the workflow.

It updated it.

Two years ago I was spending 95% of my time dragging blocks in the n8n UI. Today the ratio is almost inverted. I work in Claude Code, talk to my computer, and barely touch the canvas.

n8n didn't become less important. It stopped being the place where I build automation and became the place where I run it. The building moved to the conversation layer.

Hundreds of workflows built this way so far. Most of them voice-to-deploy.

Curious where other builders draw the line — what's the part of workflow building you still want to do by hand?

So I have been deep in this space for about a year now across our support queue and honestly the conversations I keep seeing online still feel too clean compared to what actually happens in production.

Here is what I have actually learned from running this:

Intercom Fin - strong at deflecting repetitive volume but the setup to get it talking properly about your specific product is more work than they make it sound

Zendesk AI - powerful if you are already deep in the ecosystem, felt clunky to configure outside of it

Ada - serious automation muscle but when it misses it misses confidently which is the worst version of wrong

Chatbase - been on this one the longest, about a year now. The Zendesk integration is what kept us on it. When the agent cannot resolve something the full conversation history transfers with the ticket automatically so agents never pick up cold. 71% resolution rate, CSAT held.

Freshdesk Freddy - fine for getting started, hit its ceiling faster than expected

The thing nobody talks about enough is the maintenance side. Every single one of these tools is only as good as what you feed it and how often you update it. The ones that fell apart on us fell apart because we treated them like infrastructure instead of something that needs a weekly 15 minute review.

The bar has shifted from can it reply to can it actually close the ticket. But I would add a third question now: can it stay accurate six months after you deployed it without someone actively maintaining it. That is where most of them quietly fail.

What are you all running? And genuinely curious if anyone else has had something work great in month one and then slowly fall apart.

I was spending about two hours a day answering the same emails. Shipping times, return policy, product specs, order status. All stuff that was already documented somewhere. Just nobody could find it and everyone wanted a direct answer.

I didn't want to hire someone for this. The volume wasn't there yet and it felt like the wrong use of money at my stage. So I spent a few weeks figuring out how to remove myself from the equation without the customer experience getting worse.

Here's what I actually did:

Step 1: Wrote down every question I'd answered more than twice.

Ended up with about 30. Shipping timeframes, sizing questions, return windows, compatibility questions. That list became the foundation for everything else.

Step 2: Built an AI agent trained on my actual business.

I used Chatbase for this. Fed it my FAQ doc, return policy, product pages, and that list of 30 questions with my exact answers. The key is training it on how you actually respond, not just the official policy doc. Took an afternoon to set up properly.

Step 3: Embedded it on the site and let it run.

Stuck the chat widget on my product pages and contact page. Didn't announce it, just let it start handling questions. Checked the conversation logs every few days the first month to catch anything it was getting wrong and fix it.

Step 4: Set up an email auto-draft for anything that came through anyway.

Some customers still email directly. I use Zapier to flag and categorize those so I can batch process them once a day instead of context switching all afternoon.

Three months later about 65% of support questions get handled without me touching them. The ones that still come through are genuinely complex, things that need a real answer from a real person. I don't mind those.

The whole stack costs me under $100 a month. A part time hire would have been ten times that and I'd still be answering the simple stuff.

Happy to answer questions if anyone is at the stage of figuring out whether this is worth the setup time.

My AI adoption Journey:

Today I had the opportunity to map AI implementation end-to-end, which was incredibly encouraging.

In my early Salesforce days, I remember creating traditional workflows like Email-to-Case. Now, layering AI on top of that process felt surprisingly straightforward.

Here’s a simple AI-enabled customer support workflow I mapped:

1. Customer sends a message (chat, email, WhatsApp)
2. Conversation captured in CRM (like Email-to-Case)
3. AI processes it: detects intent, summarizes, suggests responses
4. Agent reviews and sends the response
5. AI learns from resolved cases to improve over time

For anyone learning AI, here are some suggestions:
Start small, pick the automations you already know.
Consider how to add an AI layer to make workflows smarter and easier.
Experiment in a sandbox before scaling. :)

The next step for me is prototyping this flow in my sandbox.

I am curious to hear about the practical AI implementations you have seen work well in support teams. ?

I’m not an expert by any means. I’m simply sharing what I’m learning along the way in case it helps someone else who’s also exploring this space:)

I know how these posts usually go, so I'll just say upfront I'm going to be pretty rough and honest about all of these, including the ones I liked. I feel like each of them deserves a praise and comment as they have totally different approaches.

For context: I test AI tools constantly. Coding assistants, generative media stuff, random B2B SaaS. Usually I enjoy the crowded categories. But AI customer support platforms might be the most crowded AI category right now. Everyone claims to automate support, every demo looks amazing, and every sales rep makes it sound like you've just found the solution. The differences really only become obvious once you're inside the product.

So after way too many trials and sales calls, here's where I landed. Happy to hear from you I'm wrong.

Zendesk AI

If you're already on Zendesk, this is might bd the easiest move. AI triage, suggests responses from past cases, good routing. Very much a copilot approach,making agents faster rather than replacing them. Not flashy, but sometimes boring and reliable wins. The flip side is it feels like AI bolted onto a legacy product, not built from the ground up. You'll hit the ceiling eventually.

Zowie AI

The one I didn't see coming. Hadn't heard of them before the eval, then realized companies like Payoneer, Monos, and InPost are already running it, so apparently I was just late Implementation seemed faster than expected for enterprise setups, and they pair you with a pretty involved TAM during rollout.They use a deterministic decision engine for certain actions instead of letting the LLM freestyle, which helps avoid hallucinations. Also some interesting system-to-system automation (A2A) and visual troubleshooting aids inside conversations. But the orange logo made me smile haha looks a bit like some morse code.

Intercom Fin

Probably the most stable conversational quality I tested, unfortunately kinda blunt. Learns from agent edits, personalizes well, polished product. But it really wants you inside the Intercom ecosystem. If you're stitching together outside tools, expect friction. And pricing gets steep at volume, seriously, model your costs before you fall in love with zthe demon.

Ada

Probably one of the easiest for non-technical teams to get running. The flow builder is intuitive and handles common use cases well. But "common use cases" is doing a lot of work in that sentence. For anything involving complex backend integrations, order systems, billing, expect custom effort and longer timelines.

Freshworks Freddy AI

Best value pick for smaller teams but I mean small. Ticket classification, sentiment analysis, works out of the box with Freshdesk. If you need ab 80% of the capability at a fraction of the price, worth a look. Just don't expect it to keep up if your support operation gets complex.

LivePerson

The old veteran pick for some less regulated industries.More of a platform than a product though, you'll want a dedicated team to manage it, and the onboarding isn't cheap.

Kore.ai

Enterprise voice and complex IVR. Solid multilingual NLU and good templates. But this is not a self-serve deployment. I would think about hiring a technical team or paying them extra to get it done but it seemed kinda costly

Curious what’s others are running in production and what's still working at month 3. Thought about sharing a bit wit you the community up there although still feel kinda shy ahahah

Been lurking here for a while and figured I'd share something that actually saved me real time. I run a small online business and was spending 2-3 hours daily answering the same questions manually. shipping info, return policy, setup instructions, compatibility stuff. tried building Zapier workflows with keyword triggers to auto-respond but it was way too rigid. anything phrased slightly different from my exact triggers just fell through. what ended up working was an AI chatbot trained specifically on my documentation. you feed it your docs (PDFs, text files, markdown, or scrape your website directly) and it answers questions only from that content. not general purpose AI that makes stuff up, it only pulls from what you give it. runs as a chat widget on my site with one script tag. the part that felt like real automation was the Discord integration. I have a community server and the bot sits in channels I select. when moderators answer questions the bot missed, it evaluates the exchange and captures useful answers automatically for next time. casual replies and off topic stuff gets filtered out. so the system improves itself without me touching anything, which is the whole point of automation right. setup took an afternoon total. the widget was the fast part, building a good knowledge base took longer because I had to organize what content to include and what was outdated. real limitations: responses take 10-20 seconds, you rebuild the knowledge base manually when content changes (bot goes offline during this), and theres no human handoff yet so complex stuff still lands on me. but for the repetitive FAQ stuff that was eating my day, its handled. if anyone wants the specifc tool name just ask, didn't want this to feel like an ad.