# Support A help desk is a resource intended to provide the customer or end user with information and support related to a company's or institution's products and services. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Bringing Correctly Rounded Math to Production with LLVM-libc DevFeed: [Bringing Correctly Rounded Math to Production with LLVM-libc]() Original publisher: [Read original article]() Author: Cody Miller, Tue Ly, Michael Jones Published: 2026-09-16T22:09:50Z Content type: article Language: en Sources: [C++ Team Blog]() Topics: [LLVM](), [Support](), [C++]() Tags: [c-plus-plus](), [compiler](), [llvm](), [msvc]() ### AI overview This guest post explains LLVM-libc's design philosophy of portability and modularity, and discusses its math functions, including their use by MSVC for compile-time evaluation and runtime execution when /Zc:cmath is enabled. ### Source excerpt As we mentioned in the last cmath blog post, MSVC is using LLVM-libc for compile-time evaluation and runtime execution of math functions when /Zc:cmath is enabled. I invited LLVM-libc contributors Michael Jones and Tue Ly to write a guest blog post about how they've achieved what they've achieved. This is that blog post! I hope [...] The post Bringing Correctly Rounded Math to Production with LLVM-libc appeared first on C++ Team Blog. ## Building EasyReply: How We Used Laravel to Unify Customer Support DevFeed: [Building EasyReply: How We Used Laravel to Unify Customer Support]() Original publisher: [Read original article]() Author: Emma Blake Published: 2026-09-11T16:06:51Z Content type: article Language: en Sources: [Laravel]() Topics: [Laravel](), [Support](), [Artificial Intelligence](), [React](), [WebSocket](), [PHP](), [Single-page application (SPA)](), [email](), [Front end](), [Instagram]() Tags: [ai](), [api](), [development](), [email](), [frontend](), [instagram](), [laravel](), [queue](), [react](), [sponsor](), [support](), [ui](), [websocket]() ### AI overview This article explains how EasyReply uses Laravel to combine email, Slack, Instagram, and WhatsApp conversations in an AI-powered shared inbox. It describes Laravel Reverb for real-time updates, Inertia and React for the frontend, and queues for background processing. ### Source excerpt EasyReply pulls email, Slack, Instagram, and WhatsApp into one AI shared inbox, built on Laravel with Reverb, Inertia, React, and queues. The post Building EasyReply: How We Used Laravel to Unify Customer Support appeared first on Laravel News. Join the Laravel Newsletter to get Laravel articles like this directly in your inbox. ## Grok Bot vs. OpenClaw: How I replaced my entire agent stack DevFeed: [Grok Bot vs. OpenClaw: How I replaced my entire agent stack]() Original publisher: [Read original article]() Author: Claire Vo Published: 2026-09-02T12:03:39Z Content type: comparison Language: en Sources: [Lenny's Newsletter]() Topics: [OpenClaw](), [multi-agent](), [Bot](), [Pull Request](), [soc 2 compliance](), [Monitoring](), [Support](), [Slack]() Tags: [agents](), [bots](), [helpdesk](), [monitoring](), [multi-agent](), [openclaw](), [rbac](), [slack](), [soc-2-compliance]() ### AI overview A podcast episode compares Grok Bot with OpenClaw and explains why the host migrated a multi-agent setup to Grok Bot. It covers bots for inboxes, Slack, PR management, SOC 2 monitoring, customer support, family tasks, and personal activities, along with the migration process. ### Source excerpt Watch now | 🎙 I've been running Grok Bot for several weeks, and I've killed every OpenClaw I had. Here are the nine bots doing real work across my inbox, my kids' school pickups, my PR queue, and my wardrobe ## The gap between brand and consumer perceptions of AI agent disclosure DevFeed: [The gap between brand and consumer perceptions of AI agent disclosure]() Original publisher: [Read original article]() Author: Jesse Sumrak Published: 2026-08-31T00:00:00Z Content type: opinion Language: en Sources: [Twilio Blog]() Topics: [AI Agent](), [Artificial Intelligence](), [Support]() Tags: [ai](), [ai-agent](), [ai-transparency](), [customer-experience](), [industry-insights](), [trust](), [widget]() ### AI overview Twilio research finds that 81% of brands say their AI agents identify themselves, while only 22% of consumers report experiencing that disclosure. The article examines how unclear or inconsistent disclosures create a transparency and trust gap and recommends identifying the AI clearly at the start of interactions. ### Source excerpt 81% of brands say their AI identifies itself. Only 22% of consumers agree. Learn why the gap exists and how to close it. ## Why 78% of customers try to bypass your AI agent DevFeed: [Why 78% of customers try to bypass your AI agent]() Original publisher: [Read original article]() Author: Jesse Sumrak Published: 2026-08-28T00:00:00Z Content type: article Language: en Sources: [Twilio Blog]() Topics: [AI Agent](), [Support](), [Automation](), [Artificial Intelligence]() Tags: [agents](), [ai](), [ai-agent](), [ai-transparency](), [automation](), [customer-service](), [industry-insights](), [support]() ### AI overview Twilio research reports that 78% of consumers have tried to bypass an AI agent to reach a human, while 63% want an easy escalation path. The article attributes this behavior to concerns about transparency, high-stakes tasks, and inefficient interactions, and describes consumers' preferences for disclosure, human escalation, and reliable AI. ### Source excerpt New Twilio research finds 78% of consumers have tried to bypass an AI agent to reach a human. Here's why (and what to do about it). ## Meta AI Developer Assistant Now Available for Developer Support DevFeed: [Meta AI Developer Assistant Now Available for Developer Support]() Original publisher: [Read original article]() Published: 2026-08-04T16:00:48Z Content type: release Language: en Sources: [Facebook Developers]() Topics: [Meta](), [Artificial Intelligence](), [Support](), [Developer Platform](), [API]() Tags: [ai](), [api](), [compliance](), [developer](), [developer-platform](), [meta](), [support]() ### AI overview Meta is rolling out Meta AI Developer Assistant as the primary support path on developers.facebook.com/support. The assistant provides contextual answers about troubleshooting, compliance requirements, Meta's developer documentation, API references, and platform knowledge. The rollout is gradual and is expected to reach all developers by mid-September 2026. ### Source excerpt Get AI-powered answers to your product and compliance questions directly on developers.facebook.com/support/ ## Customer Billing Portal: Why Self-Serve Billing Cuts Churn DevFeed: [Customer Billing Portal: Why Self-Serve Billing Cuts Churn]() Original publisher: [Read original article]() Author: Aarthi Poonia Published: 2026-07-11T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [Support](), [To-Do]() Tags: [billing](), [churn](), [customer](), [guide](), [payment](), [saas](), [subscription](), [support]() ### AI overview This guide explains how customer billing portals let users manage payment methods, subscriptions, invoices, renewals, and related account actions without contacting support. It describes how self-serve billing can reduce support workload and help address involuntary churn caused by failed payments. ### Source excerpt A customer billing portal lets users manage plans, cards, and invoices themselves. See what a good self-serve portal includes, how it reduces support load and involuntary churn, and how to add one. ## The new product introduction process: How to make sure your Agent is ready every time you ship DevFeed: [The new product introduction process: How to make sure your Agent is ready every time you ship]() Original publisher: [Read original article]() Author: Sean Reid Published: 2026-06-26T17:40:52Z Content type: tutorial Language: en Sources: [The Intercom Blog]() Topics: [AI Agent](), [Support]() Tags: [agent](), [ai-agent](), [customer-service](), [features](), [how-to](), [npi](), [support]() ### AI overview The article explains Fin's new product introduction process for keeping an AI Agent's knowledge base current with product releases. It recommends involving support early, preparing and reviewing content, removing outdated information, and testing the Agent before launch. ### Source excerpt Every time you launch a product, your Agent's knowledge base needs to keep pace. Here's the NPI process Fin uses to make Agent readiness part of every release. ## The Importance of Documentation in B2B API Adoption DevFeed: [The Importance of Documentation in B2B API Adoption]() Original publisher: [Read original article]() Author: Anila Zaidi Published: 2026-06-23T16:15:00Z Content type: opinion Language: en Sources: [Squarespace](), [Squarespace Engineering Blog]() Topics: [Documentation](), [API](), [Support](), [Feathers]() Tags: [api](), [b2b](), [documentation](), [support](), [technical-documentation]() ### AI overview This article explains how improving public Commerce API documentation reduced support tickets and how documentation for the Domain Reseller API became a product asset. It argues that effective documentation can reduce support questions, align teams, and help potential B2B partners evaluate an API. ### Source excerpt We read reviews before buying a TV, a sweater, almost anything. Businesses do the same - potential enterprise partners evaluate APIs through every piece of content they come across. So, what happens when you improve all of it? ## Conversation design: How to make your AI Agent communicate like your team DevFeed: [Conversation design: How to make your AI Agent communicate like your team]() Original publisher: [Read original article]() Author: Fred Walton Published: 2026-06-18T16:55:07Z Content type: article Language: en Sources: [The Intercom Blog]() Topics: [AI Agent](), [Artificial Intelligence](), [Support]() Tags: [agent](), [ai](), [ai-agent](), [ai-agent-blueprint](), [ai-automation](), [communication](), [context](), [customer](), [customer-experience](), [customer-service](), [customers](), [designer](), [experience](), [process](), [responses](), [structure](), [support](), [teams](), [trust](), [voice]() ### AI overview This article explains how conversation design helps an AI Agent communicate consistently with a support team. It covers voice, tone, response structure, adapting language to customer context, and designing smooth handoffs to human support representatives. An Intercom example reports that a warmer opening message increased CSAT from 72.8% to 78.4%. ### Source excerpt If nobody on your team owns how your AI Agent communicates, it defaults to sounding like an LLM. Conversation design is the discipline that fixes that. ## Detecting Customer Churn with Structured Metrics and Behavioral Transitions DevFeed: [Detecting Customer Churn with Structured Metrics and Behavioral Transitions]() Original publisher: [Read original article]() Author: Mithil Oswal Published: 2026-06-17T09:05:24Z Content type: article Language: en Sources: [Helpshift]() Topics: [data](), [Framework](), [Support](), [Machine learning](), [Feature Engineering]() Tags: [analytics](), [case-study](), [churn](), [churn-analysis](), [churn-prediction](), [churn-rate](), [customer-churn](), [data](), [engineering](), [framework](), [metric](), [models]() ### AI overview This case study describes a Churn Intelligence Framework based on structured descriptive analytics rather than relying primarily on black-box predictive models. It uses revenue and support-ticket volume dynamics across current and previous periods to classify customers as attrited, declining, growing, new, or stable, with the goal of identifying multi-period decline before full attrition. ### Source excerpt Photo by Deng Xiang on UnsplashOne in a Million Ways to Detect Customer Churn -- Powered by Pure Metric EngineeringA real-world case study on building a Churn Intelligence Framework using revenue dynamics, structured KPI design, and behavioral transitions.😯 Wow, Churn Prediction sounds impressivePhoto by Ksenia Yakovleva on Unsplash Until you realize that most ML models struggle in production. -- Data fluctuates 🔢 -- Features change 💱 -- Stakeholders don't trust black-box outputs ⬛ Teams jump into feature engineering and classification algorithms, chasing accuracy scores -- while the business still lacks a clear behavioral definition of decline. The result? Black-box probabilities that stakeholders don't trust and Customer Success teams don't know how to act on. Predictive models attempt to forecast an outcome. But churn isn't just an outcome. It's a progression.So then what's new here? We use fundamentally structured descriptive analytics, aka real numbers. The objective was not to build another dashboard. It was to introduce intelligence into the existing reporting system. Specifically, the framework was designed to: Understand churn behavior structurally rather than as a single percentage metric or a boolean value. Track support ticket growth and decline across relative time periods, recognizing that volume trends directly influence revenue stability. Enable proactive client retention by identifying multi-period decline before full attrition occurs. Setting the ground❗At Helpshift, we used support ticket volume dynamics as a proxy for revenue. ➡ Definitions:- Start Date (filter) = Report start date that defines the Current Period End Date (filter) = Report end date that defines the Current Period Current Period = Revenue / issue volume for the current period timeframe Previous Period = Revenue / issue volume for the previous period timeframe, where Previous Period has been calculated by pulling back the "Current Period" dates by X days, where X is the difference betwe ## Fin extends Service Agent support to HubSpot and Freshworks DevFeed: [Fin extends Service Agent support to HubSpot and Freshworks]() Original publisher: [Read original article]() Author: Paul Adams Published: 2026-06-09T16:45:42Z Content type: release Language: en Sources: [The Intercom Blog]() Topics: [hubspot](), [Support]() Tags: [agent](), [apis](), [cli](), [customer-experience](), [docs](), [fin](), [fin-for-freshdesk](), [fin-for-hubspot](), [helpdesk](), [hubspot](), [integrations](), [mcps](), [news-updates](), [platform]() ### AI overview Intercom announces that Fin can operate as a Service Agent on top of HubSpot and Freshworks, allowing customers to integrate it without migrating from their existing helpdesk. The article also describes Fin's open-platform approach, including APIs, MCPs, CLI access, and public documentation. ### Source excerpt Fin can be used as a Service Agent on top of HubSpot and Freshworks, meaning you can use the world's best Agent without migrating off your helpdesk. ## Beyond the Menu Tree: How Yelp Built a Smarter Customer Success Chatbot with AI DevFeed: [Beyond the Menu Tree: How Yelp Built a Smarter Customer Success Chatbot with AI]() Original publisher: [Read original article]() Author: Lina Lee, Machine Learning Engineer; Nelson Lee, Engineering Manager Published: 2026-05-27T00:00:00Z Content type: article Language: en Sources: [Yelp]() Topics: [Retrieval Augmented Generation (RAG)](), [Support](), [AI Chat](), [Large Language Model](), [AI Development]() Tags: [ai](), [architecture](), [customer](), [deep-dive](), [engineering](), [large-language-model](), [legacy](), [llm](), [rag](), [retrieval](), [support](), [technical](), [workflow]() ### AI overview Yelp describes replacing its legacy Customer Success chatbot's fixed menu and phrase matching with an LLM-assisted system connected to an internal knowledge base through a Retrieval Augmented Generation pipeline. The system routes customer queries into specialized workflows, including question answering, refunds, and billing. ### Source excerpt The Evolution of Support: From Fixed Phrases to Conversation At Yelp, delivering responsive and accurate customer support is a core priority. For years, our legacy Customer Success (CS) Chatbot provided support by guiding users through a static support experience. Users either navigated a 2-step menu tree or typed a query that was matched against a fixed set of phrases to retrieve an answer. While functional, the legacy chatbot had a key limitation: its reliance on rigid matching meant that if a query didn't fit the menu structure or precisely match a known phrase, the user wouldn't be able to get... ## Turning support tickets into organization-wide intelligence DevFeed: [Turning support tickets into organization-wide intelligence]() Original publisher: [Read original article]() Author: Idit Matas Published: 2026-05-04T10:35:03Z Content type: tutorial Language: en Sources: [Developer Experience & Platform Engineering Blog | Port]() Topics: [Support](), [Artificial Intelligence](), [data](), [hubspot](), [Slack](), [bug]() Tags: [agents](), [ai](), [bug](), [hubspot](), [jira](), [slack](), [support](), [workflows]() ### AI overview The article explains how Port built an internal Support AI Hub on its Agentic Engineering Platform to analyze support-ticket information. It describes agents for ticket summaries, engineer handovers, escalations, health checks, and monthly trend analysis using data from systems including HubSpot, Zendesk, Jira, and Slack. ### Source excerpt Learn how to turn support tickets into organization-wide intelligence to uncover trends, improve workflows, and drive decisions. ## Introducing the Mintlify Help Center Starter Kit DevFeed: [Introducing the Mintlify Help Center Starter Kit]() Original publisher: [Read original article]() Author: Hahnbee Lee Published: 2026-05-01T00:00:00Z Content type: release Language: en Sources: [Mintlify Blog]() Topics: [Support](), [Artificial Intelligence](), [Documentation](), [Slack]() Tags: [ai](), [announcements](), [documentation](), [slack](), [support]() ### AI overview Mintlify introduces a Help Center starter kit with an AI assistant that answers questions from published documentation, provides citations and source links, accepts additional context such as files and code, and routes unanswered questions to support email. The release also highlights a web editor and Slack-based knowledge capture. ### Source excerpt Help centers are the first line of defense for customer support. The new Mintlify Help Center starter kit and AI ticket deflection make it faster than ever to launch one. ## Why Local Payment Methods Matter for Global Expansion DevFeed: [Why Local Payment Methods Matter for Global Expansion]() Original publisher: [Read original article]() Author: Rishabh Goel Published: 2026-04-17T00:00:00Z Content type: opinion Language: en Sources: [Dodo Payments Blog]() Topics: [Transactions](), [Support]() Tags: [brazil](), [checkout](), [china](), [global-expansion](), [india](), [newsletter](), [payment](), [paypal](), [revenue]() ### AI overview The article argues that global expansion depends on supporting payment methods people commonly use in each market. It highlights Pix in Brazil, UPI in India, and WeChat Pay in China, and says checkout and payment failures can limit revenue even when products are available in new regions. ### Source excerpt Local payment methods are becoming the default in global markets. We explore why checkout -- not acquisition -- is where growth stalls, and what we shipped to help you recover revenue you're already losing. ## Watch people work DevFeed: [Watch people work]() Original publisher: [Read original article]() Author: hi@swizec.com (Swizec Teller) Published: 2026-04-14T00:00:00Z Content type: opinion Language: en Sources: [Swizec Teller]() Topics: [Development](), [Users](), [Support](), [bug]() Tags: [bug](), [build](), [development](), [support](), [users]() ### AI overview This opinion article recommends watching engineers and other team members perform their work to uncover user pain, workarounds, bugs, inefficient processes, and communication gaps. It describes three such sessions and the issues they revealed across ordering, support, finance, and product workflows. ### Source excerpt We talk a lot about outcomes over outputs and how engineers are supposed to get us over the water, not blindly build a bridge because someone asked for a bridge. But how do you do that in practice? ## Credit Card Decline Codes: What They Mean and How to Fix Them DevFeed: [Credit Card Decline Codes: What They Mean and How to Fix Them]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-13T00:00:00Z Content type: tutorial Language: en Sources: [Dodo Payments Blog]() Topics: [API](), [Authentication](), [Support](), [Docker Compose]() Tags: [api](), [authentication](), [churn](), [developer-guide](), [developers](), [guide](), [how-to](), [payments](), [recovery](), [retry](), [revenue]() ### AI overview A practical guide for developers and revenue teams on interpreting credit card decline codes, grouping them into operational categories, and choosing appropriate recovery actions. It emphasizes customer self-correction, safe retries with idempotency keys, and distinguishing recoverable declines from generic issuer or authentication failures. ### Source excerpt A practical guide to credit card decline codes for developers and revenue teams, including what common declines mean and how to reduce failed payments. ## SaaS Refund Management: Policies, Automation, and Best Practices DevFeed: [SaaS Refund Management: Policies, Automation, and Best Practices]() Original publisher: [Read original article]() Author: Ayush Agarwal Published: 2026-04-11T00:00:00Z Content type: article Language: en Sources: [Dodo Payments Blog]() Topics: [Software as a service](), [Automation](), [Support]() Tags: [and-best-practices](), [automation](), [best-practices](), [billing](), [chargebacks](), [customers](), [retention](), [saas](), [saas-billing](), [subscription](), [support]() ### AI overview This article explains how SaaS companies can manage refunds through clear policies, efficient processes, and automation. It covers chargeback prevention, customer retention, manual-refund scalability, and policy decisions for subscriptions, usage charges, one-time purchases, renewals, and accidental charges. ### Source excerpt Build a SaaS refund policy that reduces chargebacks, retains customers, and scales without drowning your support team. Covers refund automation, partial refunds, and AI-powered refund workflows. ## Move fast and save things: A quick guide to recovering a hacked account DevFeed: [Move fast and save things: A quick guide to recovering a hacked account]() Original publisher: [Read original article]() Author: Christian Ali Bravo Tomáš Foltýn Published: 2026-03-20T10:00:00Z Content type: tutorial Language: en Sources: [WeLiveSecurity]() Topics: [Security](), [incident](), [password reset](), [passwords](), [Malware](), [Support]() Tags: [account](), [bank](), [digital-security](), [guide](), [incident](), [malware](), [password](), [phishing](), [recovery](), [support]() ### AI overview A practical guide to responding quickly after an online account is hacked. It covers checking access, beginning account recovery, contacting financial institutions, disconnecting potentially infected devices, scanning for malware, and preserving evidence. ### Source excerpt What you do - and how fast - after an account is compromised often matters more than it may seem ## Why more product managers are switching to Mintlify DevFeed: [Why more product managers are switching to Mintlify]() Original publisher: [Read original article]() Author: Peri Langlois Published: 2026-03-03T00:00:00Z Content type: opinion Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [Support]() Tags: [best-practices](), [developer](), [documentation](), [product](), [switching]() ### AI overview This article explains why product managers are turning to Mintlify to improve documentation, support organizational goals, and scale documentation-related tasks. It discusses documentation's effects on support, sales, feature adoption, and customer retention, and highlights Mintlify's usability and analytics. ### Source excerpt Understand why product managers are using Mintlify to help support org-wide goals. ## postmarketOS launches a contributor compensation programme funded by donations DevFeed: [postmarketOS launches a contributor compensation programme funded by donations]() Original publisher: [Read original article]() Published: 2025-12-19T00:00:00Z Content type: news Language: en Sources: [postmarketOS Blog]() Topics: [Development](), [maintenance](), [Documentation](), [Support](), [Tool](), [Repositories]() Tags: [contributions](), [contributors](), [development](), [documentation](), [financial](), [funding](), [kernel](), [metrics](), [postmarketos](), [processes](), [repositories](), [support](), [upgrades](), [work]() ### AI overview postmarketOS announces a Contributor Support Programme that offers financial compensation to contributors with high time commitments. The programme aims to support essential maintenance, support, and administrative work, while distributing funds using equal hourly compensation and logged work. ### Source excerpt We are excited to announce the Contributor Support Programme. This programme offers postmarketOS contributors with a high time-commitment the option to receive financial compensation for the work they do. It is designed to achieve the following goals: Address some of the sustainability challenges facing postmarketOS development. While we can oftentimes fund feature development through donations (e.g. wireplumber and callaudiod) or grants, other work like essential maintenance, support, and administrative tasks remains difficult to get funded with our current approaches. Some people have already been working on these topics full-time or part-time with no compensation. Ensure fairness and equality among participants and their contributions. Everybody is entitled to the same hourly compensation, regardless of location, kind of tasks, or any other variables. Fulfill our commitment to supporters who have donated specifically to compensate contributors, as stated on our Open Collective page. Establish metrics that strengthen future funding applications by demonstrating our current resource investment, and our ability to distribute funds fairly and efficiently. High level overview Every quarter, eligible contributors can opt in for the programme. The total amount of funds available is taken from excess donation income, while making sure that other budgeted items are not affected. Then, every month, contributors invoice proportionally to the hours they work, and report on the tasks that they spend time based on the logged hours. If you want to read more details about criteria, processes, and reasons, you can check the documentation. We see this as another small step towards improving the project and fulfilling the long-term goals! Monthly report November 2025 And as we started working on this programme in November, we are now able to provide our first report! During this last month: Stefan spent a lot of time looking at pmbootstrap, the tool we use for development. He opene ## Inside Mirakl's agentic commerce vision DevFeed: [Inside Mirakl's agentic commerce vision]() Original publisher: [Read original article]() Published: 2025-12-01T22:00:00Z Content type: article Language: en Sources: [OpenAI News]() Topics: [Artificial Intelligence](), [ChatGPT](), [Documentation](), [Support](), [Data Quality]() Tags: [agentic](), [ai](), [ai-agents](), [catalog](), [chatgpt](), [customer](), [data-quality](), [documentation](), [efficiency](), [support]() ### AI overview Mirakl describes an agentic commerce strategy in which AI becomes a company-wide capability and employees build agents for individual and team workflows. Using ChatGPT Enterprise and other AI systems, Mirakl reports faster technical documentation, improved customer-support efficiency with high satisfaction, faster catalog onboarding, fewer categorization errors, and multilingual 24/7 support. ### Source excerpt Mirakl is redefining commerce through AI agents and ChatGPT Enterprise--achieving faster documentation, smarter customer support, and building toward agent-native commerce with Mirakl Nexus. ## Swiss Airlines' AI-Powered Support Chat Prevents Online Flight Rebooking DevFeed: [Swiss Airlines' AI-Powered Support Chat Prevents Online Flight Rebooking]() Original publisher: [Read original article]() Published: 2025-11-17T07:00:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Artificial Intelligence](), [Support](), [Website]() Tags: [ai](), [channel](), [chat](), [support](), [web]() ### AI overview The author argues that replacing airline support with AI can fail when the system does not work and website information is outdated. The article recounts an attempt to rebook a Swiss Airlines flight that was redirected from the website to an AI-powered online chat. ### Source excerpt Remember the vendor consultants who persuasively told you how to use their gear to build a disaster recovery solution with stretched VLANs, even though the only disaster recovery they ever experienced was the frantic attempt to restart their PowerPoint slide deck? Fortunately, I was only involved in the aftermath of their activity when the laws of physics reasserted themselves, and I helped the poor victims rearchitect their network into a somewhat saner state. There's another batch of snake-oil salesmen consultants peddling their warez to the gullible incompetent managers: the AI preachers promising reduction in support costs. Like the other group of consultants, they have never worked in support and have never implemented a working AI solution in their lives, but that never bothered them or their audience. Unfortunately, this time I had the unfortunate "privilege" of having the painful front-row seat. Read more ... [Next page]()