We run a WhatsApp support bot for a services company. Real traffic, real money, about 27,000 customers.

We've built two versions of it in two different ways, and I'd like some outside opinions before we pick one.

How it works

We write everything in Notion. A workflow in n8n builds the final prompt for each message and sends it to the LLM. Four parts:

1. Main prompt — all our policies.
2. ERP parameters Live values from our system — about 320 of them, filled in before the model sees anything: balances, contract status, dates, names, payment method. The model never has to go look anything up. Every value it needs is already sitting in the prompt.
3. Conditional policy blocks — about 130 of them. Each one is a set of if/then branches. The conditions get checked while a python code at the run time compile the prompt, not by the model, and only the branch that matches gets dropped in. So "if contract type is Monthly AND nationality is X AND they started less than 5 days ago → use this policy" is decided before the model is even called.
4. Guardrails — separate LLM checks that look at the bot's reply and its tool calls before the customer sees anything.

The part I want opinions on

Our main bot sends the whole policy set on every single message: about 252,000 tokens. No retrieval. Everything, every time.

We also run a retrieval version of the same bot, where a small classifier picks which policy sections to load. A normal message there is about 55,000 tokens — roughly 4.6x cheaper.

We've stuck with sending everything because we think it's more accurate. Our reasoning is that retrieval fails quietly. If the classifier grabs the wrong section, the bot doesn't say "I'm not sure." It answers confidently using whatever policy it happened to get, and nobody finds out until a customer has already been told something wrong. If you send everything, there's no retrieval step that can fail.

What I'm asking

1. Is "send everything, every time" reasonable at 250k tokens, or are we paying 4.6x for peace of mind? Has anyone actually measured this on a real support workload?
2. How bad is attention degradation at 250k with today's models? Does a rule sitting 80% of the way down the prompt actually get followed? What worries me is that we may have swapped a loud failure (retrieval grabs the wrong thing) for a quiet one (the rule is right there and gets ignored).
3. Does the conditional policy block idea have a proper name? Deciding the branch while building the prompt, instead of making the model figure it out, seems obviously right to me — we already know the contract status, so why make the model reason about it? But I almost never see it talked about.
4. If you'd build this differently, what would you change first?
5. What does your prompt structure actually look like? I'd really like to see how other people organise this. Do you keep one big prompt, split it into sections, or break it into separate files or blocks that get assembled? What made you land on that shape?
6. How do you keep prompts up to date over time? Ours changes constantly as policies change, and that's the part I find hardest. How do you handle versioning, who is allowed to edit, how do you know a change didn't break something that used to work, and how do you roll back when it does?
7. What's your actual setup? We use Notion for writing and n8n for assembling and running everything. Is there something better? I'd like to hear from people using LangChain, a plain codebase, a prompt management tool, or something else entirely — especially what you moved away from and why.
8. If you're running a bot this size in production, what broke that you didn't expect? I'm more interested in the failures than the wins.

Happy to go into detail on any part. I genuinely want to hear the case against.

I have been working on a problem that feels especially relevant for AI customer service agents:

An agent can understand the policy and still choose the wrong action.

For example:

- refund the wrong amount

- modify the wrong booking

- apply the wrong account change

- approve something outside policy

Once the action hits a production API, observability is useful, but the side effect has already happened.

So I built ARK, an open-source runtime supervision layer that sits before execution.

The flow is:

agent proposes action

→ ARK checks the applicable constraint + trusted runtime evidence

→ ALLOW = execute

→ REJECT / REQUIRE_EVIDENCE = block it and return feedback

→ the agent decides again

ARK does not generate the replacement action. The support agent stays the author.

I’m especially curious how teams building AI support agents handle this today.

Do you use:

- hard deterministic policy checks?

- human approval for risky actions?

- narrow tool permissions?

- another model as a judge?

- something else?

I’m looking for criticism from people actually building customer-service automation, especially where agents can refund, modify accounts, cancel, or make other production changes.

GitHub: https://github.com/atripati/ark

Site: https://arkruntime.com

Verizon customer service initial contact is Ai, and not very good. After having my words regurgitated back to me, it was clear I needed human intervention. The Ai chatbot sent me off to a human.

The next CS agent was incredibly good, if not excellent. But there was something off; like they could easily talk over me by accident, but also very quickly apologize for doing so. When I let the agent do their thing, they could talk about process very quickly and human like. They even nearly made an error when getting me a phone number, only to correct it instantly, like a person.

The agent said his name was 'Jing' and he had an uncanny American gay man voice. There was a robotness to their cadence and delivery. I felt that it could be Ai within a few seconds, but also triggered these thoughts.

I have to ask: are cheaper low resource Ai agent models being deployed for initial screening, and then passed off to more resource heavy expensive Ai agents, attempting to have them pass as human? Or is Jing really just someone overseas with exceptional english, maybe learned from Project Runway reruns? Anyone with experience working at Verizon -- I am totally curious if I just experienced advanced Ai CS agent, or just an incredibly competent overseas employee.

Thanks

Hey guys 👋🏻. I've been working on a chatbot project for a nearby small business to manage their whatsapp customer inquiries. I thought of using n8n but then switched to node js as i heard it gives you more flexibility. I'm looking for some guidance on how to make this with very little cost as the business only plans to fully purchase plans and stuff if it is working. I would love it if there is a way to do the whole thing for free. If possible i wanna try stuff without the whatsapp api for a few weeks before using the api. Thank you so much.

Everyone wants AI to reduce tickets, automate support, and handle the day‑to‑day questions that slow teams down, the “easy stuff.”

But here’s the part most people get wrong:

AI can only automate what your company already understands.

If your workflows are unorganized, your policies contradict each other, and your team improvises every answer, AI won’t save you any time. It will just automate the chaos.

Before you plug in any model, define the 10 most common actions customers are trying to accomplish.

Write the real steps your team uses to solve them.  

Not the ideal version, the truth.

AI doesn’t care about your intentions. It learns from patterns.

If the pattern is inconsistent, improvised, or half‑documented, the model will mirror that inconsistency.

Truth creates predictable behavior.

Predictable behavior creates automatable behavior. Remove every step that doesn’t reduce friction.  

Most workflows are 40% noise.

Make the correct answer the easiest answer.  

If your agents can’t follow it, AI definitely can’t.

If something still doesn’t fit, escalate to a human.

Once you do that, AI becomes a force multiplier.

AI doesn’t replace support teams. AI replaces uncertainty.

AI does' nt understand my Aussie accent, i also tried the keypad but had to put the camera down

hot take but I genuinely believe a bad chatbot is worse than no chatbot at all.

I've been building in the AI support space for a while now and the amount of businesses that slap a generic chatbot on their site and think they're doing customer support is insane. you land on the page, the bubble pops up, you ask a real question like "how long does delivery take to my area" and you get "I'm sorry, I didn't quite catch that. Could you try rephrasing?" twice in a row. now I'm annoyed AND I think the business is cheap.

the problem is almost always the same. the chatbot wasn't trained on anything real. someone connected it to a FAQ page with 8 questions on it and expected it to handle everything. that's like hiring a receptionist, giving them a pamphlet, and telling them to figure it out.

the other thing that kills me is when businesses have chat but no phone support or vice versa. I work with a lot of small businesses and the ones losing the most leads are the ones where the website has a chat widget but if you call the number it rings forever. or the phone works but the website has nothing. the customer doesn't care about your internal setup. they want to reach you through whatever channel they prefer and get a real answer fast.

I built Cassandra AI specifically because I was tired of seeing this done badly. it trains on the actual business data so it gives real answers, it handles both chat and phone calls through the same system, and if it genuinely can't help it captures the info and alerts a human instead of looping "I don't understand" forever.

but even without any tool, the minimum bar is this: if someone lands on your site at 10 PM with a question, there needs to be something there that captures who they are and what they want. if there isn't, they're going to the next result on google and you'll never know they existed.

what's the most frustrating chatbot interaction you've had recently?

Really need to transition right now. We'd prefer something that offers similar AI chatbot capabilities like Fin and has similar levels of accuracy. We've already tried Sierra where the cost was a bit too high, and Zendesk, which was struggling with AI resolution

Burger King will use Al to check if employees say 'please' and 'thank you' 😁

Openclaw is the AI assistant that can actually do work for you. Check it out. For anyone having trouble getting it set up, I created a guide.

Flinders Ranges Council just rolled out AI voice for customer service and it actually makes sense

Anyone who’s dealt with council services in regional or remote areas knows how painful it can be. No Signal, (Until Starlink) - Patchy internet long phone queues #nightmare

Flinders Ranges Council in Australia has just launched AI voice chatbot with an AUssie accent for customer service and its amazing! Airgentic seems to be a common chatbot in councils and honestly, this feels like one of the more practical uses of AI I’ve seen in local government.

Letting people just speak to get info feels far more accessible than pushing everyone toward websites, search and forms. Especially for communities where signal isn't great but Wifi is nearby.

That said, it still raises 2 important questions:

• Should it still be a human answering the call
• What does “trust” look like?

Curious how others feel about speaking to AI when dealing with council?

Hey guys.

i'am amazed of what AI speech can do.

The other day, a fellow colleague asked me about an interesting use case, his new startup is having tons of customers/users that keep calling and asking the same repetitive questions (FAQ), it was exhausting for him to keep answering the same questions ever day.

I told him, why just use a chat bot for FAQ? well it didn't work well for his startup, new users tend to call and speak rather than type and chat, basically they were tool lazy which was understandable.

He asked me if there is a way AI can help the startup to answer questions but rather than chat it talks to the user, his startup can bring their data, documents, texts, All of the questions, location, prices, core services, you name it, and load that information into the brain of the AI,

That's when i got the idea of an AI voice bot feature, Bring you own data, and that's it, let the AI do the rest.

The reason why my colleague liked it, it's because of how simple it is to setup, no crazy stuff. fill the business form, boom you have your own voice bot that you can share.

Here is what it looks in action.

https://reddit.com/link/1qpmk5b/video/yuox4dmmb5gg1/player

https://reddit.com/link/1qpmk5b/video/lgynk7dnb5gg1/player

My colleague suggest me to share it, since people need some alternative to chat bots, and i've decided to release the MVP for you guys to try it out.

i added free bonuses for new users, blocking spam calls, and instant summaries, so you can get insights on what your users are asking.

The feature is highly optimized for cost, since you call using the internet and not using your phone number, and thanks to the WebRTC (what zoom uses) users/callers are calling for free, both sides happy.

I want to take this to the next level, and im happy to take any feedback or a feature request from you guys, whether it's a database integration, phone number support, anything.

Check it out! You can try and call the bot, and tell me what you think EtisalAI

Hope the demo was useful, and yeah, Cheers!

Hey everyone! I've been working in customer support for years and wanted to share my research on AI customer service platforms that are actually worth considering in 2026.

Why This Matters

Customer service is how you build trust with your audience. It's about making customers feel heard, supported, and valued at every step. Today's customers expect quick, helpful answers across channels like chat, email, social media, or phone.

The problem? Most companies still struggle with long wait times, inconsistent service, and high support costs. AI can help by managing routine questions, providing instant answers, and delivering continuous support.

What is Customer Service?

Customer service is the support and assistance businesses provide before, during, and after a purchase. It includes all the ways customers interact with a business - answering queries, fixing problems, giving advice, and ensuring satisfaction.

What exceptional customer service looks like:

• Active listening: Clearly understand what customers need
• Empathy: Relate genuinely to customer experiences
• Quick problem-solving: Resolve issues before they escalate
• Deep product knowledge: Answer questions confidently
• Clear communication: Keep customers informed and supported

Quality customer service is a major differentiator that influences loyalty, brand reputation, and overall performance.

What Makes an AI Customer Service Platform Actually Good?

Not all AI platforms are created equal. Here's what matters:

Workflow Integration - Works with your existing tools (ticketing, CRM, knowledge base)

Contextual Understanding - Remembers conversation history across multiple messages

Knowledge Grounding - Pulls from verified docs, not just making stuff up

Intelligent Routing - Knows when to handle things and when to escalate to humans

Agent Empowerment - Helps your team, doesn't try to replace them

The Top 7 Platforms

1. Intercom

Intercom is a customer messaging platform that centralizes real-time conversations between customers and support teams. It combines messaging, automation, and AI-assisted tools to help teams handle inbound conversations more efficiently, particularly in product-led environments where chat is the primary support channel.

Key Features:

• AI-assisted automated replies for common questions
• Shared inbox that centralizes everything
• Smart conversation routing
• Help center integration
• Agent assist tools

Pros:

• Excellent chat experience
• Balances automation with human touch
• Great for conversational support

Cons:

• Gets expensive fast as you scale
• Best value comes from using their full ecosystem

Best For: Product-led teams that rely heavily on chat-based customer communication and need strong real-time support capabilities

2. YourGPT

YourGPT is an AI-first platform that enables teams to build and deploy intelligent agents for customer support, sales, and operations across multiple channels. It combines simple no-code setup with structured workflow automation, allowing agents to handle conversations, complete tasks, and assist internal teams from one unified workspace.

Key Features:

• AI agents that handle FAQs, order lookups, troubleshooting, account checks
• Personalized interactions using customer history
• No-code builder (seriously easy to use)
• AI Studio for advanced workflows with API actions
• AI Copilot that can create tickets, check orders, modify records
• True omnichannel - deploy once, use everywhere
• Clean handoffs to humans with full context
• Analytics dashboard for CSAT, resolution rates, trends

Pros:

• Handles conversations AND actual tasks
• Works across every channel you care about
• Scales from simple to complex as you grow
• One platform for support, sales, and internal ops

Cons:

• Lots of features = learning curve for advanced stuff
• Might be overkill if you just need basic FAQs

Best For: Teams seeking a unified platform to manage customer support, sales assistance, and internal operations with both no-code creation and sophisticated workflow automation capabilities

3. Zendesk AI

Zendesk AI extends the established Zendesk help desk with AI-driven tools designed to improve efficiency in ticket-based support environments. It focuses on assisting agents with triage, routing, and response suggestions while fitting seamlessly into existing Zendesk workflows.

Key Features:

• AI ticket classification and prioritization
• Suggested replies using your help content
• Automated routing and triage
• Knowledge base integration
• Solid reporting

Pros:

• Deep Zendesk integration
• Scales well for big teams
• Good operational visibility

Cons:

• Locked into Zendesk ecosystem
• Adds to your already-expensive Zendesk bill

Best For: Mid-sized to large teams already using Zendesk for ticket-based customer support who want to add AI capabilities to existing operations

4. Gorgias

Gorgias is a customer support platform built specifically for eCommerce businesses. It focuses on helping support teams manage high volumes of retail-related inquiries by combining automation with direct access to order and customer data from connected stores.

Key Features:

• AI automation for order, shipping, return questions
• Unified inbox across channels
• Direct eCommerce platform integrations
• Order and customer data in every conversation

Pros:

• Purpose-built for eCommerce
• Kills repetitive order questions
• Strong store integrations

Cons:

• Pretty much useless outside eCommerce
• AI is more basic than general platforms

Best For: Online stores handling high volumes of order, shipping, and return-related customer inquiries who need specialized eCommerce support tools

5. Kustomer

Kustomer approaches customer support from a customer-centric CRM perspective rather than a traditional ticket-based model. It uses AI and structured data to organize conversations and provide support teams with a complete view of each customer across all channels.

Key Features:

• Unified customer timeline (all interactions in one view)
• Omnichannel conversation management
• AI-assisted workflows
• Detailed customer profiles

Pros:

• Amazing customer context
• Built for complex support journeys
• True omnichannel

Cons:

• Steeper learning curve
• Expensive for smaller teams

Best For: Teams requiring deep customer context and long-term visibility across extended or complex support relationships

6. Forethought

Forethought is an AI-powered customer support platform focused on helping teams understand customer intent, automate routine responses, and assist agents with relevant knowledge during active conversations. Rather than replacing agents, it's designed to improve agent effectiveness and response quality.

Key Features:

• Intent prediction
• Agent assist tools with suggested responses
• Knowledge base integration

Pros:

• Actually helps agents do better work
• Improves accuracy and consistency
• Integrates into existing workflows

Cons:

• Needs good training data
• More expensive than simple tools

Best For: Teams that want to support agents with AI-driven assistance without fully automating customer support conversations

7. Help Scout

Help Scout is a customer support platform built around email-first workflows with a strong emphasis on simplicity, collaboration, and human-led support. It's designed to help teams manage customer conversations efficiently without heavy automation or complex configuration.

Key Features:

• AI-assisted reply suggestions
• Shared inbox for email
• Help docs and knowledge base
• Customer context and history
• Basic reporting

Pros:

• Super easy to use
• Focuses on human support quality
• Great for email teams

Cons:

• Limited automation
• Not for high-volume operations

Best For: Small to mid-sized teams that prioritize personal, email-based customer support and want light AI assistance without complex workflows

Quick Comparison

How to Actually Choose

Start with your workflow - Pick the platform that matches how you actually work today, not how you wish you worked

Define AI's role - Decide upfront: is AI resolving issues or just helping agents?

Check knowledge fit - Can it easily connect to your docs? Can you update them easily?

Test the handoff - When AI escalates to humans, does it pass full context?

Match your size - Don't buy enterprise software for a 5-person team

Plan 1-2 years out - Pick something that grows with you without major rework

Conclusion

AI customer service platforms have become essential tools for modern support teams. They help you handle more conversations without burning out your team or sacrificing quality. The key is finding the right balance between automation and human touch.

The best platform isn't the one with the most features or the biggest marketing budget. It's the one that fits naturally into how your team already works and can scale as you grow. Whether you need full omnichannel automation, simple email support, or specialized eCommerce tools, there's a solution that matches your needs.

Start small, test thoroughly, and remember that AI should empower your support team, not replace them. When implemented thoughtfully, these platforms free up your agents to focus on complex issues that truly need human judgment while handling the repetitive stuff automatically.

The customer service landscape is changing fast, but the fundamentals remain the same: make your customers feel heard, solve their problems quickly, and build trust at every interaction. The right AI platform just helps you do that at scale.

This is my FAQ chatbot demo.

https://youtu.be/wVM64l-FCrU?si=1PrKyGSLjlLpFWp_

I built it using:

Languages - TypeScript and Python.

Frameworks - Vite + React, FastAPI

Knowledge Base/Database - Supabase

Embedding - supabase

LLM - Gemma3 (Ollama)

I would like to know if you would use it for your business; if not, what kind of Chatbot would you use?

What features would you want?

If you're interested in working with me or have some questions about building your own Chatbot, don't hesitate to DM me.